thr3ads.net - asterisk users - [Asterisk-Users] PRI Question [Aug 2003]

If this information is useful, please help other people find it:
Share via:

Barry Porch

2003-Aug-18 12:19 UTC

[Asterisk-Users] PRI Question

I managed to get Asterisk working with my PBX using T1, now I am moving
on to trying to make PRI work.
 
I have my zaptel.conf and zapata.conf configured as follows:
 
Zaptel.conf:
 
span=1,1,0,esf,b8zs
bchan=1-23
dchan=24
loadzone=us
defaultzone=us
 
Zapata.conf:
 
[channels]
transfer=yes
immediate=yes
callprogress=yes
 
language=en
context=default
switchtype=national
signalling=pri_net
group=1
channel=1-23
 
I have a PRI port provisioned off my PBX to work with the above
settings.  When I start up Asterisk everything seems to come up (my PBX
"sees" a D-channel) but I get constant output as follows:
 
== D-Channel on span 1 up
 
B-channel 2 restarted on span 1
 
B-channel 3 restarted on span 1
 
B-channel 4 restarted on span 1
 
B-channel 5 restarted on span 1
 
B-channel 6 restarted on span 1
 
B-channel 7 restarted on span 1
 
B-channel 8 restarted on span 1
 
B-channel 9 restarted on span 1
 
B-channel 10 restarted on span 1
 
B-channel 11 restarted on span 1
 
B-channel 12 restarted on span 1
 
B-channel 13 restarted on span 1
 
B-channel 14 restarted on span 1
 
B-channel 16 restarted on span 1
 
D-Channel on span 1 down
 
D-Channel on span 1 up
 
B-channel 2 successfully restarted on span 1
 
B-channel 3 successfully restarted on span 1
 
B-channel 4 successfully restarted on span 1
 
B-channel 5 successfully restarted on span 1
 
.... And so forth with the D-channel going up and down and various
channels "successfully restarting" but inbound calls do not work.
 
I have tried changing the PRI protocol, I have swapped the CPE and NET
settings between the PBX and Asterisk and every combination gives me
this same result.
 
Any thoughts?
 
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20030818/8c14ba60/attachment.htm

Martin Pycko

2003-Aug-18 18:08 UTC

head link

[Asterisk-Users] PRI Question

First of all you should have callprogress=no and immediate=no for any kind
of a PRI. Also why is your d-channel going down ? Can you send a trace
"pri intense debug span 1" ?

regards
Martin

On Mon, 18 Aug 2003, Barry Porch wrote:
>
>
> I managed to get Asterisk working with my PBX using T1, now I am moving
> on to trying to make PRI work.
>
> I have my zaptel.conf and zapata.conf configured as follows:
>
> Zaptel.conf:
>
> span=1,1,0,esf,b8zs
> bchan=1-23
> dchan=24
> loadzone=us
> defaultzone=us
>
> Zapata.conf:
>
> [channels]
> transfer=yes
> immediate=yes
> callprogress=yes
>
> language=en
> context=default
> switchtype=national
> signalling=pri_net
> group=1
> channel=1-23
>
> I have a PRI port provisioned off my PBX to work with the above
> settings.  When I start up Asterisk everything seems to come up (my PBX
> "sees" a D-channel) but I get constant output as follows:
>
> == D-Channel on span 1 up
>
> B-channel 2 restarted on span 1
>
> B-channel 3 restarted on span 1
>
> B-channel 4 restarted on span 1
>
> B-channel 5 restarted on span 1
>
> B-channel 6 restarted on span 1
>
> B-channel 7 restarted on span 1
>
> B-channel 8 restarted on span 1
>
> B-channel 9 restarted on span 1
>
> B-channel 10 restarted on span 1
>
> B-channel 11 restarted on span 1
>
> B-channel 12 restarted on span 1
>
> B-channel 13 restarted on span 1
>
> B-channel 14 restarted on span 1
>
> B-channel 16 restarted on span 1
>
> D-Channel on span 1 down
>
> D-Channel on span 1 up
>
> B-channel 2 successfully restarted on span 1
>
> B-channel 3 successfully restarted on span 1
>
> B-channel 4 successfully restarted on span 1
>
> B-channel 5 successfully restarted on span 1
>
> .... And so forth with the D-channel going up and down and various
> channels "successfully restarting" but inbound calls do not work.
>
> I have tried changing the PRI protocol, I have swapped the CPE and NET
> settings between the PBX and Asterisk and every combination gives me
> this same result.
>
> Any thoughts?
>
> Thanks!
>

Barry Porch

2003-Aug-19 07:45 UTC

head link

[Asterisk-Users] PRI Question

Martin,

Here is the trace you asked for.  It's quite lengthy so I'm attaching it
as a text file.  The way I generated this output was to start up an
instance of asterisk redirecting output to a text file.  Then I
connected in another terminal window as console and issued the debug
command.  I don't know if there's a better way to do this.

Also I can successfully connect to the PRI port on my PBX with my T1/PRI
tester (a Sunset T10) and I can also successfully connect to my Asterisk
box and place an inbound call.  I just can't connect the Asterisk box
directly to my PBX.  The PBX is a Mitel 3300, by the way.

Thanks for your help!

Barry

-----Original Message-----
From: Martin Pycko [mailto:martinp@digium.com] 
Sent: Monday, August 18, 2003 9:09 PM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] PRI Question

First of all you should have callprogress=no and immediate=no for any
kind
of a PRI. Also why is your d-channel going down ? Can you send a trace
"pri intense debug span 1" ?

regards
Martin

On Mon, 18 Aug 2003, Barry Porch wrote:
>
>
> I managed to get Asterisk working with my PBX using T1, now I am
moving> on to trying to make PRI work.
>
> I have my zaptel.conf and zapata.conf configured as follows:
>
> Zaptel.conf:
>
> span=1,1,0,esf,b8zs
> bchan=1-23
> dchan=24
> loadzone=us
> defaultzone=us
>
> Zapata.conf:
>
> [channels]
> transfer=yes
> immediate=yes
> callprogress=yes
>
> language=en
> context=default
> switchtype=national
> signalling=pri_net
> group=1
> channel=1-23
>
> I have a PRI port provisioned off my PBX to work with the above
> settings.  When I start up Asterisk everything seems to come up (my
PBX> "sees" a D-channel) but I get constant output as follows:
>
> == D-Channel on span 1 up
>
> B-channel 2 restarted on span 1
>
> B-channel 3 restarted on span 1
>
> B-channel 4 restarted on span 1
>
> B-channel 5 restarted on span 1
>
> B-channel 6 restarted on span 1
>
> B-channel 7 restarted on span 1
>
> B-channel 8 restarted on span 1
>
> B-channel 9 restarted on span 1
>
> B-channel 10 restarted on span 1
>
> B-channel 11 restarted on span 1
>
> B-channel 12 restarted on span 1
>
> B-channel 13 restarted on span 1
>
> B-channel 14 restarted on span 1
>
> B-channel 16 restarted on span 1
>
> D-Channel on span 1 down
>
> D-Channel on span 1 up
>
> B-channel 2 successfully restarted on span 1
>
> B-channel 3 successfully restarted on span 1
>
> B-channel 4 successfully restarted on span 1
>
> B-channel 5 successfully restarted on span 1
>
> .... And so forth with the D-channel going up and down and various
> channels "successfully restarting" but inbound calls do not work.
>
> I have tried changing the PRI protocol, I have swapped the CPE and NET
> settings between the PBX and Asterisk and every combination gives me
> this same result.
>
> Any thoughts?
>
> Thanks!
>
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------

...

 [chan_zap.so] => (Zapata Telephony w/PRI)

  == Parsing '/etc/asterisk/zapata.conf': Found

    -- Registered channel 1, PRI Signalling signalling

    -- Registered channel 2, PRI Signalling signalling

    -- Registered channel 3, PRI Signalling signalling

    -- Registered channel 4, PRI Signalling signalling

    -- Registered channel 5, PRI Signalling signalling

    -- Registered channel 6, PRI Signalling signalling

    -- Registered channel 7, PRI Signalling signalling

    -- Registered channel 8, PRI Signalling signalling

    -- Registered channel 9, PRI Signalling signalling

    -- Registered channel 10, PRI Signalling signalling

    -- Registered channel 11, PRI Signalling signalling

    -- Registered channel 12, PRI Signalling signalling

    -- Registered channel 13, PRI Signalling signalling

    -- Registered channel 14, PRI Signalling signalling

    -- Registered channel 15, PRI Signalling signalling

    -- Registered channel 16, PRI Signalling signalling

    -- Registered channel 17, PRI Signalling signalling

    -- Registered channel 18, PRI Signalling signalling

    -- Registered channel 19, PRI Signalling signalling

    -- Registered channel 20, PRI Signalling signalling

    -- Registered channel 21, PRI Signalling signalling

    -- Registered channel 22, PRI Signalling signalling

    -- Registered channel 23, PRI Signalling signalling

  == Registered channel type 'Zap' (Zapata Telephony Driver w/PRI)

  == Registered channel type 'Tor' (Zapata Telephony Driver w/PRI)

  == Starting D-Channel on span 1

...

Asterisk Ready.

  == D-Channel on span 1 up

    -- B-channel 1 restarted on span 1

    -- B-channel 2 restarted on span 1

    -- B-channel 3 restarted on span 1

    -- B-channel 4 restarted on span 1

    -- B-channel 5 restarted on span 1

    -- B-channel 6 restarted on span 1

    -- B-channel 7 restarted on span 1

    -- B-channel 8 restarted on span 1
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 1 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 2 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 3 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 4 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 5 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 6 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 1, retransmitting frame 7 now, updating n_r!

    -- B-channel 9 restarted on span 1

    -- B-channel 10 restarted on span 1

    -- B-channel 11 restarted on span 1

    -- B-channel 12 restarted on span 1

    -- B-channel 13 restarted on span 1

    -- B-channel 14 restarted on span 1

    -- B-channel 15 restarted on span 1

    -- B-channel 16 restarted on span 1

    -- B-channel 17 restarted on span 1

    -- B-channel 18 restarted on span 1

    -- B-channel 19 restarted on span 1

    -- B-channel 20 restarted on span 1

    -- B-channel 21 restarted on span 1

    -- B-channel 22 restarted on span 1

  == D-Channel on span 1 down
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
S-frame while link down

  == D-Channel on span 1 up

    -- B-channel 1 successfully restarted on span 1

  == D-Channel on span 1 down

  == D-Channel on span 1 up

    -- Remote UNIX connection

    -- B-channel 2 restarted on span 1

    -- B-channel 3 restarted on span 1
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 0, retransmitting frame 0 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 0, retransmitting frame 1 now, updating n_r!
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
reject for frame 0, retransmitting frame 2 now, updating n_r!

    -- B-channel 4 restarted on span 1

    -- B-channel 5 restarted on span 1

    -- B-channel 6 restarted on span 1

    -- B-channel 7 restarted on span 1

    -- B-channel 8 restarted on span 1

    -- B-channel 9 restarted on span 1

    -- B-channel 10 restarted on span 1

    -- B-channel 11 restarted on span 1

    -- B-channel 12 restarted on span 1

    -- B-channel 13 restarted on span 1

  == D-Channel on span 1 down

  == D-Channel on span 1 up

< [00 01 01 01 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 0

-- Since there was nothing left, stopping T200 counter

-- Stopping T203 counter since we got an ACK

-- Nothing left, starting T203 counter

-- Unsolicited RR with P/F bit, responding

Sending Receiver Ready (0)
> [00 01 01 01 ]
> Supervisory frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
> [02 01 00 00 08 02 00 00 46 18 03 a9 83 83 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 0
> 13 bytes of data
Stopping T_203 timer

Starting T_200 timer
> Protocol Discriminator: Q.931 (8)  len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive 
> Dchan: 0
>                        ChanSel: Reserved
>                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3
>                       Ext: 1  Channel: 3 ]
> Restart Indentifier: [ Ext: 1  Spare: 0  Resetting Indicated Channel 
> (0) ]
-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 83 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (1)

-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 83 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (2)

-- T200 counter expired, What to do...

-- Timeout occured, restarting PRI

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
  == D-Channel on span 1 down

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
< [02 01 73 ]
< Unnumbered frame:

< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1

<   M3: 3   P/F: 1 M2: 0 11: 3  [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

-- Got UA from cpe peer  Link up.

  == D-Channel on span 1 up

< [00 01 01 01 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 0

-- Since there was nothing left, stopping T200 counter

-- Stopping T203 counter since we got an ACK

-- Nothing left, starting T203 counter

-- Unsolicited RR with P/F bit, responding

Sending Receiver Ready (0)
> [00 01 01 01 ]
> Supervisory frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
> [02 01 00 00 08 02 00 00 46 18 03 a9 83 84 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 0
> 13 bytes of data
Stopping T_203 timer

Starting T_200 timer
> Protocol Discriminator: Q.931 (8)  len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive 
> Dchan: 0
>                        ChanSel: Reserved
>                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3
>                       Ext: 1  Channel: 4 ]
> Restart Indentifier: [ Ext: 1  Spare: 0  Resetting Indicated Channel 
> (0) ]
-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 84 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (1)

< [02 01 01 03 ]
< Supervisory frame:

< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 001 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 1

-- ACKing packet 0, new txqueue is -1 (-1 means empty)

-- Since there was nothing left, stopping T200 counter

-- Nothing left, starting T203 counter

-- Got RR response to our frame

< [00 01 01 03 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 001 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 1

-- Since there was nothing left, stopping T200 counter

-- Stopping T203 counter since we got an ACK

-- Nothing left, starting T203 counter

-- Unsolicited RR with P/F bit, responding

Sending Receiver Ready (0)
> [00 01 01 01 ]
> Supervisory frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
< [00 01 00 02 08 02 80 00 4e 18 03 a9 83 84 79 01 80 ]
< Informational frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< N(S): 000   0: 0
< N(R): 001   P: 0
< 13 bytes of data

-- ACKing all packets from 0 to (but not including) 1

-- Since there was nothing left, stopping T200 counter

-- Stopping T203 counter since we got an ACK

-- Nothing left, starting T203 counter

< Protocol Discriminator: Q.931 (8)  len=13

< Call Ref: len= 2 (reference 32768/0x8000) (Terminator)

< Message type: RESTART ACKNOWLEDGE (78)

< Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive
Dchan: 0

<                        ChanSel: Reserved

<                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3

<                       Ext: 1  Channel: 4 ]

< Restart Indentifier: [ Ext: 1  Spare: 0  Resetting Indicated Channel (0) ]

Sending Receiver Ready (1)
> [00 01 01 02 ]
> Supervisory frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 001 P/F: 0
> 0 bytes of data
    -- B-channel 4 successfully restarted on span 1
> [02 01 02 02 08 02 00 00 46 18 03 a9 83 85 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 001   0: 0
> N(R): 001   P: 0
> 13 bytes of data
Stopping T_203 timer

Starting T_200 timer
> Protocol Discriminator: Q.931 (8)  len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive 
> Dchan: 0
>                        ChanSel: Reserved
>                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3
>                       Ext: 1  Channel: 5 ]
> Restart Indentifier: [ Ext: 1  Spare: 0  Resetting Indicated Channel 
> (0) ]
-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 02 03 08 02 00 00 46 18 03 a9 83 85 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 001   0: 0
> N(R): 001   P: 1
> 13 bytes of data
-- Rescheduling retransmission (1)

-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 02 03 08 02 00 00 46 18 03 a9 83 85 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 001   0: 0
> N(R): 001   P: 1
> 13 bytes of data
-- Rescheduling retransmission (2)

-- T200 counter expired, What to do...

-- Timeout occured, restarting PRI

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
  == D-Channel on span 1 down

< [02 01 73 ]
< Unnumbered frame:

< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1

<   M3: 3   P/F: 1 M2: 0 11: 3  [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

-- Got UA from cpe peer  Link up.

  == D-Channel on span 1 up

T203 counter expired, sending RR and scheduling T203 again

Sending Receiver Ready (0)
> [00 01 01 01 ]
> Supervisory frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
> [02 01 00 00 08 02 00 00 46 18 03 a9 83 84 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 0
> 13 bytes of data
Stopping T_203 timer

Starting T_200 timer
> Protocol Discriminator: Q.931 (8)  len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive 
> Dchan: 0
>                        ChanSel: Reserved
>                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3
>                       Ext: 1  Channel: 4 ]
> Restart Indentifier: [ Ext: 1  Spare: 0  Resetting Indicated Channel 
> (0) ]
< [00 01 01 01 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 0

-- Something left to transmit (0), restarting T200 counter

-- Got RR response to our frame

-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 84 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (1)

< [00 01 01 01 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 0

-- Something left to transmit (0), restarting T200 counter

-- Got RR response to our frame

-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 84 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (2)

< [00 01 01 01 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

-- ACKing all packets from 0 to (but not including) 0

-- Something left to transmit (0), restarting T200 counter

-- Got RR response to our frame

-- T200 counter expired, What to do...

-- Timeout occured, restarting PRI

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
  == D-Channel on span 1 down

< [00 01 01 01 ]
< Supervisory frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data
WARNING[1167272000]: File chan_zap.c, Line 5386 (zt_pri_error): PRI: !! Got
S-frame while link down

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
< [00 01 7f ]
< Unnumbered frame:

< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1

<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
< 0 bytes of data

-- Got SABME from cpe peer.

Sending Unnumbered Acknowledgement
> [00 01 73 ]
> Unnumbered frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 0 11: 3  [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
  == D-Channel on span 1 up

T203 counter expired, sending RR and scheduling T203 again

Sending Receiver Ready (0)
> [00 01 01 01 ]
> Supervisory frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
> [02 01 00 00 08 02 00 00 46 18 03 a9 83 86 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 0
> 13 bytes of data
Stopping T_203 timer

Starting T_200 timer
> Protocol Discriminator: Q.931 (8)  len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive 
> Dchan: 0
>                        ChanSel: Reserved
>                       Ext: 1  Coding: 0   Number Specified   Channel Type:
3
>                       Ext: 1  Channel: 6 ]
> Restart Indentifier: [ Ext: 1  Spare: 0  Resetting Indicated Channel 
> (0) ]
-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 86 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (1)

-- T200 counter expired, What to do...

-- Retransmitting 17 bytes
> [02 01 00 01 08 02 00 00 46 18 03 a9 83 86 79 01 80 ] Informational 
> frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 1
> 13 bytes of data
-- Rescheduling retransmission (2)

-- T200 counter expired, What to do...

-- Timeout occured, restarting PRI

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
  == D-Channel on span 1 down

Sending Set Asynchronous Balanced Mode Extended
> [02 01 7f ]
> Unnumbered frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
>   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode
extended) ]
> 0 bytes of data
< [02 01 73 ]
< Unnumbered frame:

< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1

<   M3: 3   P/F: 1 M2: 0 11: 3  [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

-- Got UA from cpe peer  Link up.

  == D-Channel on span 1 up

Executing last minute cleanups

  == Destroying any remaining musiconhold processes

Barry Porch

2003-Aug-20 10:37 UTC

head link

[Asterisk-Users] PRI Question

My switch doesn't let me set up a loop but I am confident that
everything is OK at the T1 layer.  I can connect via robbed bit to the
Asterisk box with no problem.  Also I can use my T1/PRI tester towards
either systems and it works fine with PRI and I can place and receive
calls.

There seems to be some incompatibility between Mitel's PRI
implementation and Asterisk.  I have tried all supported flavors of PRI
(ni2, dms100, 4ess, 5ess) with the same result.  I have also tried
changing pri_cpe vs pri_net between the 2 machines.  Everything gives me
the same result with the d channel going down and coming back up
constantly.  I have been running on a cvs from about 2 weeks ago so I
also did a cvs update yesterday with no change.

It appears that I may be out of luck connecting the Mitel directly to
the Asterisk box via PRI.  If someone has other experience I'd love to
hear it.  

Has anyone else run into PRI implementations that they cannot make work
with Asterisk?

Barry

-----Original Message-----
From: Martin Pycko [mailto:martinp@digium.com] 
Sent: Wednesday, August 20, 2003 12:32 PM
To: asterisk-users@lists.digium.com
Subject: RE: [Asterisk-Users] PRI Question

Can you do remote loopup from your switches side ... and look asterisk's
T1 and check if your transmission is ok ?

regards
Martin

On Tue, 19 Aug 2003, Barry Porch wrote:
> Martin,
>
> Here is the trace you asked for.  It's quite lengthy so I'm
attaching
it> as a text file.  The way I generated this output was to start up an
> instance of asterisk redirecting output to a text file.  Then I
> connected in another terminal window as console and issued the debug
> command.  I don't know if there's a better way to do this.
>
> Also I can successfully connect to the PRI port on my PBX with my
T1/PRI> tester (a Sunset T10) and I can also successfully connect to my
Asterisk> box and place an inbound call.  I just can't connect the Asterisk box
> directly to my PBX.  The PBX is a Mitel 3300, by the way.
>
> Thanks for your help!
>
> Barry
>
> -----Original Message-----
> From: Martin Pycko [mailto:martinp@digium.com]
> Sent: Monday, August 18, 2003 9:09 PM
> To: asterisk-users@lists.digium.com
> Subject: Re: [Asterisk-Users] PRI Question
>
> First of all you should have callprogress=no and immediate=no for any
> kind
> of a PRI. Also why is your d-channel going down ? Can you send a trace
> "pri intense debug span 1" ?
>
> regards
> Martin
>
> On Mon, 18 Aug 2003, Barry Porch wrote:
>
> >
> >
> > I managed to get Asterisk working with my PBX using T1, now I am
> moving
> > on to trying to make PRI work.
> >
> > I have my zaptel.conf and zapata.conf configured as follows:
> >
> > Zaptel.conf:
> >
> > span=1,1,0,esf,b8zs
> > bchan=1-23
> > dchan=24
> > loadzone=us
> > defaultzone=us
> >
> > Zapata.conf:
> >
> > [channels]
> > transfer=yes
> > immediate=yes
> > callprogress=yes
> >
> > language=en
> > context=default
> > switchtype=national
> > signalling=pri_net
> > group=1
> > channel=1-23
> >
> > I have a PRI port provisioned off my PBX to work with the above
> > settings.  When I start up Asterisk everything seems to come up (my
> PBX
> > "sees" a D-channel) but I get constant output as follows:
> >
> > == D-Channel on span 1 up
> >
> > B-channel 2 restarted on span 1
> >
> > B-channel 3 restarted on span 1
> >
> > B-channel 4 restarted on span 1
> >
> > B-channel 5 restarted on span 1
> >
> > B-channel 6 restarted on span 1
> >
> > B-channel 7 restarted on span 1
> >
> > B-channel 8 restarted on span 1
> >
> > B-channel 9 restarted on span 1
> >
> > B-channel 10 restarted on span 1
> >
> > B-channel 11 restarted on span 1
> >
> > B-channel 12 restarted on span 1
> >
> > B-channel 13 restarted on span 1
> >
> > B-channel 14 restarted on span 1
> >
> > B-channel 16 restarted on span 1
> >
> > D-Channel on span 1 down
> >
> > D-Channel on span 1 up
> >
> > B-channel 2 successfully restarted on span 1
> >
> > B-channel 3 successfully restarted on span 1
> >
> > B-channel 4 successfully restarted on span 1
> >
> > B-channel 5 successfully restarted on span 1
> >
> > .... And so forth with the D-channel going up and down and various
> > channels "successfully restarting" but inbound calls do not
work.
> >
> > I have tried changing the PRI protocol, I have swapped the CPE and
NET> > settings between the PBX and Asterisk and every combination gives me
> > this same result.
> >
> > Any thoughts?
> >
> > Thanks!
> >
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users

Don Pobanz

2003-Aug-20 11:04 UTC

head link

[Asterisk-Users] PRI Question

This may have nothing to do with it but have you verified your timing? 
Make sure one end of the T1 is using an internal clock and the other 
end is using timing off of the T1.

Don Pobanz

On Wednesday, August 20, 2003 12:37 PM, Barry Porch 
[SMTP:bporch@watsonconnects.com] wrote:> My switch doesn't let me set up a loop but I am confident that
> everything is OK at the T1 layer.  I can connect via robbed bit to
> the
> Asterisk box with no problem.  Also I can use my T1/PRI tester
> towards
> either systems and it works fine with PRI and I can place and receive
> calls.
>
> There seems to be some incompatibility between Mitel's PRI
> implementation and Asterisk.  I have tried all supported flavors of
> PRI
> (ni2, dms100, 4ess, 5ess) with the same result.  I have also tried
> changing pri_cpe vs pri_net between the 2 machines.  Everything gives
> me
> the same result with the d channel going down and coming back up
> constantly.  I have been running on a cvs from about 2 weeks ago so I
> also did a cvs update yesterday with no change.
>
> It appears that I may be out of luck connecting the Mitel directly to
> the Asterisk box via PRI.  If someone has other experience I'd love
> to
> hear it.
>
> Has anyone else run into PRI implementations that they cannot make
> work
> with Asterisk?
>
> Barry
>

Barry Porch

2003-Aug-20 11:40 UTC

head link

[Asterisk-Users] PRI Question

Don,

Thanks very much for the suggestion.  That fixed the problem.

It's very strange because I should be providing clocking on the PBX PRI
port but as soon as I changed my span configuration to 1,0,0,esf,b8zs it
came up and worked perfectly.

Thanks again!

Barry

-----Original Message-----
From: Don Pobanz [mailto:dpobanz@hastingsutilities.com] 
Sent: Wednesday, August 20, 2003 2:04 PM
To: 'asterisk-users@lists.digium.com'
Subject: RE: [Asterisk-Users] PRI Question

This may have nothing to do with it but have you verified your timing? 
Make sure one end of the T1 is using an internal clock and the other 
end is using timing off of the T1.

Don Pobanz

On Wednesday, August 20, 2003 12:37 PM, Barry Porch 
[SMTP:bporch@watsonconnects.com] wrote:> My switch doesn't let me set up a loop but I am confident that
> everything is OK at the T1 layer.  I can connect via robbed bit to
> the
> Asterisk box with no problem.  Also I can use my T1/PRI tester
> towards
> either systems and it works fine with PRI and I can place and receive
> calls.
>
> There seems to be some incompatibility between Mitel's PRI
> implementation and Asterisk.  I have tried all supported flavors of
> PRI
> (ni2, dms100, 4ess, 5ess) with the same result.  I have also tried
> changing pri_cpe vs pri_net between the 2 machines.  Everything gives
> me
> the same result with the d channel going down and coming back up
> constantly.  I have been running on a cvs from about 2 weeks ago so I
> also did a cvs update yesterday with no change.
>
> It appears that I may be out of luck connecting the Mitel directly to
> the Asterisk box via PRI.  If someone has other experience I'd love
> to
> hear it.
>
> Has anyone else run into PRI implementations that they cannot make
> work
> with Asterisk?
>
> Barry
>
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users

Tim Chandler

2005-Mar-21 21:07 UTC

head link

[Asterisk-Users] PRI Question

Hi Everyone,

Thanks for all the input you add to the list.  This seems to be a very good
list.

I am still new to Asterisk.  If I run a PRI integrated T1 line into my office,
do I need to split the line between the data and voice before plugging it into
the asterisk box or is there some other way to do that?  What are some good
options for splitting the line?

Thanks for any input.

Tim

BTW - Giving everyone "a hug" is an expression in Brazil.  Everyone
says it... it's like saying "have a good one" or "good to see
you."

Tim Chandler

2005-Mar-21 21:16 UTC

head link

[Asterisk-Users] PRI Question

Let me further clarify this.  I am looking to buy the TE110P.  The website says
that "The TE110P with Asterisk will route voice and data traffic, and
eliminate the need for an external router."  How does this work?  How is
the data transferred - as a pass-through like a NAT to the server's network
card?  What kind of network slowdown are we looking at?  How does this affect
the processor?  I would appreciate some more information on how this works.

Thanks,
Tim Chandler

---------- Original Message ----------------------------------
From: "Tim Chandler" <tim.chandler@multiling.com>
Reply-To: tim.chandler@multiling.com,Asterisk Users Mailing List -
Non-Commercial Discussion <asterisk-users@lists.digium.com>
Date:  Mon, 21 Mar 2005 21:07:39 -0700
>Hi Everyone,
>
>Thanks for all the input you add to the list.  This seems to be a very good
list.
>
>I am still new to Asterisk.  If I run a PRI integrated T1 line into my
office, do I need to split the line between the data and voice before plugging
it into the asterisk box or is there some other way to do that?  What are some
good options for splitting the line?
>
>Thanks for any input.
>
>Tim
>
>BTW - Giving everyone "a hug" is an expression in Brazil. 
Everyone says it... it's like saying "have a good one" or
"good to see you."
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users@lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

Paul Mahler

2005-Mar-23 18:03 UTC

head link

[Asterisk-Users] PRI Question

You can also use * and linux to partialize the T1. You better plan on
spending a lot of time on making it work. You have to install the Linux
packages to split the line. NON trival. Works great,
though. 

Paul

Paul Mahler
pmahler@signate.com
www.signate.com

On Mon, 2005-03-21 at 21:16 -0700, Tim Chandler wrote:> Let me further clarify this.  I am looking to buy the TE110P.  The 
> website says that "The TE110P with Asterisk will route voice and data 
> traffic, and eliminate the need for an external router."  How does 
> this work?  How is the data transferred - as a pass-through like a NAT 
> to the server's network card?  What kind of network slowdown are we 
> looking at?  How does this affect the processor?  I would appreciate 
> some more information on how this works.
Look here http://www.voip-info.org/wiki-Asterisk+cmd+ZapRAS for one option.

or here for the other http://www.google.com/search?q=hdlc+zapata
> >Hi Everyone,
> >
> >Thanks for all the input you add to the list.  This seems to be a
> very good list.
> >
> >I am still new to Asterisk.  If I run a PRI integrated T1 line into
> my office, do I need to split the line between the data and voice 
> before plugging it into the asterisk box or is there some other way to 
> do that?  What are some good options for splitting the line?
> >
> >Thanks for any input.
> >
> >Tim
> >
> >BTW - Giving everyone "a hug" is an expression in Brazil. 
Everyone
> says it... it's like saying "have a good one" or "good
to see you."
--
Steven Critchfield <critch@basesys.com>

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.4 - Release Date: 3/18/2005
 


Paul Mahler
www.signate.com

Reasonably Related Threads

Search for more reasonably related threads

asterisk users - Aug 2003 - PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

[Asterisk-Users] PRI Question

Reasonably Related Threads