ISDN BRI Problem

I'm having problems connecting to a main PRI circuit from a remote branch. Any suggestions appreciated. Looks like isdn connects for 20 seconds and then drops. I verified the passwords.

thank you.!

Here is q921 output:

Oct 16 21:58:38.653: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=65 nr=30 Oct 16 21:58:38.669: ISDN BR0/1/0 Q921: User RX RRp sapi=0 tei=66 nr=0 Oct 16 21:58:39.125: ISDN BR0/1/0 Q921: User RX INFO sapi=0 tei=65, ns=30 nr=30 Oct 16 21:58:39.653: ISDN BR0/1/0 Q921: User RX INFO sapi=0 tei=65, ns=31 nr=32 Oct 16 21:58:44.645: ISDN BR0/1/0 Q921: User RX INFO sapi=0 tei=65, ns=32 nr=33 Oct 16 21:58:44.769: ISDN BR0/1/0 Q921: User RX INFO sapi=0 tei=65, ns=33 nr=33 Oct 16 21:58:45.649: ISDN BR0/1/0 Q921: User RX SETUP pd = 8 callref =

0x13 Bearer Capability i = 0x8890 Standard = CCITT Transfer Capability = Unrestricted Digital Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0x83 Keypad Facility i = '1630xxxxxxx' Oct 16 22:00:47.610: ISDN BR0/1/0 Q931: RX SETUP pd = 8 callref = 0x14 Bearer Capability i = 0x8890 Standard = CCITT Transfer Capability = Unrestricted Digital Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0x83 Keypad Facility i = '1630xxxxxxx' Oct 16 22:00:53.610: ISDN BR0/1/0 Q931: RX
Reply to
NetWorkMan
Loading thread data ...

...

...

Thats not normal. Could definately cause some problems.

Bring up that part with the telco?

Reply to
Doug McIntyre

Looks like the BRI is not configured to allow data calls. The clue is that when the ISDN call comes in you see ISDN progress message " Progress Ind i =

0x8A81 - Call not end-to-end ISDN". In not configured for data calls, all calls (including data calls) are "clipped" to 56k. This is fine for voice calls, but for data calls it will garble the data packets. They do this because "data" calls are charged at a higher tariff than voice, and may router companies (including Cisco) figured out a way to make a call appear to the phone company as a voice call, when in fact it was a data call. Call the phone company and open a trouble and make sure the BRI is provisioned for "data".

Reply to
Thrill5

~ NetWorkMan writes: ~ >I'm having problems connecting to a main PRI circuit from a remote ~ >branch. Any suggestions appreciated. Looks like isdn connects for 20 ~ >seconds and then drops. I verified the passwords. ~ ~ ... ~ > Progress Ind i = 0x8A81 - Call not end-to-end ISDN, may have in-band info ... ~ ... ~ ~ Thats not normal. Could definately cause some problems. ~ ~ Bring up that part with the telco?

The 0x8A part of the cause code is an interesting clue:

%isdn_cause_code_octet_1_2 = ("80","From User Router", "81","From Private Network near Local User", "82","From Public Network near Local User", "83","From Transit Network", "84","From Public Network near Remote User", "85","From Private Network near Remote User", "87","From International Network", "8A","From a Network Beyond internetworking point");

So it would seem that this message is coming from a truly weird circuit path (perhaps a VoIP call leg?)

If you are lucky, then this will merely indicate that you are going thru a 56k trunk (i.e. one using RBS and/or AMI/SF). In which case, just be sure to handle the call on each end as 56k instead of 64k sync PPP, and you should be golden.

If you are unlucky, this indicates that the call is going thru a path that can't handle anything but voice (i.e. it goes thru a codec.) In which case, you'd have to use something other than ISDN for connectivity. (Or use a different circuit.)

Aaron

Reply to
Aaron Leonard

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.