04-21-2014 10:27 PM - last edited on 03-25-2019 08:29 PM by ciscomoderator
Hello,
I am in need of a little help in my home telephony lab. I recently added an Avaya IP Office 403 into the mix and I am connecting it to my 2851 via PRI. I am not very familiar with the Avaya system, so my trouble shooting ability towards that is limited, but on the Cisco side I am receivng the following messages:
Global ISDN Switchtype = primary-ni
ISDN Serial0/1/0:23 interface
dsl 1, interface ISDN Switchtype = primary-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 1 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Number of L2 Discards = 0, L2 Session ID = 83
Total Allocated ISDN CCBs = 0
debug isdn q921
-------------------------
Apr 22 05:19:29.331: ISDN Se0/1/0:23 Q921: L2_EstablishDataLink: sending SABME
Apr 22 05:19:29.331: ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 22 05:19:30.331: ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
Router-2851#
Apr 22 05:19:31.331: ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 22 05:19:32.331: ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
Router-2851#
Apr 22 05:19:35.499: ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F)
Router-2851#
Apr 22 05:19:36.527: ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F)
Router-2851#
Apr 22 05:19:37.555: ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F)
Apr 22 05:19:38.331: ISDN Se0/1/0:23 Q921: L2_EstablishDataLink: sending SABME
Apr 22 05:19:38.331: ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
Router-2851#
Apr 22 05:19:38.583: ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F)
Apr 22 05:19:39.331: ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
My router interface configs are as followes;
controller T1 0/1/0
clock source internal
cablelength short 133
pri-group timeslots 1-24
interface Serial0/1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
no cdp enable
My router is providing the clock source. I have attached a screen shot of the IP Office manager PRI config.
Any help in getting these devices to communicate is greatly appreciated.
Thanks
-Jeff
Solved! Go to Solution.
04-22-2014 08:37 AM
If you want Cisco side to do clocking, you should also make it the ISDN Network side:
interface Serial0/1/0:23
isdn protocol-emulate network
That should get the PRI up.
04-22-2014 08:37 AM
If you want Cisco side to do clocking, you should also make it the ISDN Network side:
interface Serial0/1/0:23
isdn protocol-emulate network
That should get the PRI up.
04-22-2014 10:37 AM
Brian,
That did the trick. Thanks for the info.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: