That document certainly is informative, thanks. I actually went with
a tn464F that I happen to have and from the lucent side I have no problem
setting it up as a signaling trunk group. Asterisk starts up, registers 1
D-Channel, and 23 B-Channels, but thats as far as I get.
When I try to dial the asterisk via the Feature access code I
defined on the definity I don't get any sign of a connection. The definity
dials, and then waits until timeout at which point I get a busyback.
Similarly, if I try to dial out from the Asterisk I get an all busy. I
turned on pri intense debug span 1, to see if there were any obvious errors.
When I do a dial I get the following traceback:
---- start incredibly long debug message ------
> [
> [02
> [02 01
> [02 01 01
> [02 01 01 38
> [02 01 01 38 ]
> [02 01 01 38 ]
> Supervisory frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
> N(R): 028 P/F: 0
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [
< [02
< [02 01
< [02 01 38
< [02 01 38 be
< [02 01 38 be 08
< [02 01 38 be 08 02
< [02 01 38 be 08 02 80
< [02 01 38 be 08 02 80 f8
< [02 01 38 be 08 02 80 f8 5a
< [02 01 38 be 08 02 80 f8 5a 08
< [02 01 38 be 08 02 80 f8 5a 08 02
< [02 01 38 be 08 02 80 f8 5a 08 02 81
< [02 01 38 be 08 02 80 f8 5a 08 02 81 d1
< [02 01 38 be 08 02 80 f8 5a 08 02 81 d1 ]
< [02 01 38 be 08 02 80 f8 5a 08 02 81 d1 ]
< Informational frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< N(S): 028 0: 0
< N(R): 095 P: 0
< 9 bytes of data
-- ACKing all packets from 94 to (but not including) 95
-- 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=9
< Call Ref: len= 2 (reference 33016/0x80F8) (Terminator)
< Message type: RELEASE COMPLETE (90)
< Cause (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location:
Private network serving the local user (1)
< Ext: 1 Cause: Invalid call reference value (81), class
Invalid message (5) ]
Sending Receiver Ready (29)
> [
> [02
> [02 01
> [02 01 01
> [02 01 01 3a
> [02 01 01 3a ]
> [02 01 01 3a ]
> Supervisory frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
> N(R): 029 P/F: 0
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [
< [02
< [02 01
< [02 01 3a
< [02 01 3a be
< [02 01 3a be 08
< [02 01 3a be 08 02
< [02 01 3a be 08 02 80
< [02 01 3a be 08 02 80 f8
< [02 01 3a be 08 02 80 f8 5a
< [02 01 3a be 08 02 80 f8 5a 08
< [02 01 3a be 08 02 80 f8 5a 08 02
< [02 01 3a be 08 02 80 f8 5a 08 02 81
< [02 01 3a be 08 02 80 f8 5a 08 02 81 d1
< [02 01 3a be 08 02 80 f8 5a 08 02 81 d1 ]
< [02 01 3a be 08 02 80 f8 5a 08 02 81 d1 ]
< Informational frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< N(S): 029 0: 0
< N(R): 095 P: 0
< 9 bytes of data
-- ACKing all packets from 94 to (but not including) 95
-- 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=9
< Call Ref: len= 2 (reference 33016/0x80F8) (Terminator)
< Message type: RELEASE COMPLETE (90)
< Cause (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location:
Private network serving the local user (1)
< Ext: 1 Cause: Invalid call reference value (81), class
Invalid message (5) ]
Sending Receiver Ready (30)
---- End incredibly long debug message ------
Any suggestions? I feel like I am close.. but no cigar. :) Invalid message
(5) anyone? I haven't looked at the libpri code but perhaps there is further
explanation in there.
I'm using pri_cpe channels 1-23, dchan=24, bchan=1-23.
Any help is appreciated... thanks again,
Matt
-----Original Message-----
From: Ken Godee [mailto:ken@perfect-image.com]
Sent: Monday, January 19, 2004 5:53 PM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] Lucent and ISDN-PRI
Matthew Branton wrote:
> Hi Everyone,
>
> So I have been further exploring the integration of our asterisk server
> and our lucent definity g3si system. I took the suggestion of setting up
> an isdn-pri line added the two way tie trunk and the signalling group,
> but can't seem to get the PRI signalling working on the asterisk
> correctly. I've set pri type to network on the lucent, and pri_cpe in
> zapata on the asterisk, but I am a bit confused as to the zaptel
> settings in this situation. It seems no matter what signaling mode I
> choose in zaptel.conf (with the exception of clear) I get an error on
> asterisk startup complaining about requested PRI vs unknown signalling.
>
> Any help would be appreciated in getting this working / ironing out some
> of my conceptual issues. :) I did get the lucent ot work under an e&m
> based tie group but that didn't seem to give me any more functionality
> than I had managed before.
>
> Thanks,
>
>
> Matt
>
Matt,
You know I'll be following this thread!
Found a good reference for G3 isdn-pri you should
have a look. Go's into good detail, more then the
stock implementation manuals do.
http://support.avaya.com/elmodocs2/multivantage/025107_1/025107_1.pdf
I noticed you said you where going to use a TN767(E) circuit pack, did you?
Depending on your system(version) you might have to use TN464 for ISDN-PRI
It's questionable as to weither you can use a TN767 for ISDN-PRI w/FAS
Some systems you can, others you can not.
You might need to install a packet adjunct TN555
Are you sure your D channel is up?
It's seems the TN767 is mostly used as ISDN-PRI w/NFAS.
Anyhow just a thought, cause that's where I'm at right now
is trying to figure out which circuit pack I need to use.
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040120/3735acf5/attachment.htm