03-02-2005 12:36 PM - edited 03-03-2019 09:01 AM
I have a 2600 with a PRI card, when I try to do an isdn test call int s1/0:23 ######### the debug constantly comes back with "Cause i = 0x83E020 - Mandatory information element missing" Vendor states he doesn't see the SDN 'flag' coming through. I have both the isdn nsf-service, and the dialer map configured to use a class with the outgoing sdn command. Anyone else run into this?
03-04-2005 12:29 AM
Are your network specs right? Could we see all of your debug isdn q931, show isdn service outputs?
You can check and see whether you NSF supported services for AT&T switches match here http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800d9842.html#96209. Check the configuration for NSF call-by-call support (http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_configuration_guide_chapter09186a008008787b.html#xtocid2101619).
Also, the T1/E1 PRI troubleshooting flowcharts (http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801509d7.shtml, http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00800a70fc.shtml) are good resources for finding out what may be wrong.
Cheers,
Josef.
ps - rate if it 'elps ;-)
03-04-2005 05:31 AM
Unfortunately I have poured through those doc's repeatedly.. tried every combination of nsf-service. Opened a TAC case, worked with the vendor... Last night a break through. TAC came through with a bug ID (one of those ones that normal folks like us are not privi to) so I'm trying a code upgrade. Which will subsequently break my dialer watch configuration I'm fairly certain.
03-04-2005 05:57 AM
have you tried the command isdn sending-complete. This should work by sending the call setup information
03-04-2005 06:14 AM
Just tried... no luck.. thank you though.
*Mar 1 19:49:17.207: ISDN Se1/0:23 EVENT: UserIdle: callid 0x800B received ISDN_CALL (0x0)
*Mar 1 19:49:17.211: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x000B
Sending Complete
Bearer Capability i = 0x8890
Standard = CCITT
Transer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Called Party Number i = 0xA1, '##########'
Plan:ISDN, Type:National
Redirecting Number i = 0x7FE080, 'n_parser_map_lkup'
Plan:Reserved, Type:Reserved
Redirecting Number i = 0x########
Plan:Reserved, Type:Reserved
*Mar 1 19:49:17.267: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x800B
Cause i = 0x83E020 - Mandatory information element missing
*Mar 1 19:49:17.271: ISDN Se1/0:23 EVENT: process_rxstate: ces/callid 1/0x800B calltype 1 CALL_REJECTION
*Mar 1 19:49:17.275: ISDN Se1/0:23 EVENT: process_rxstate: ces/callid 1/0x800B calltype 1 CALL_CLEARED
show isdn status
Global ISDN Switchtype = primary-4ess
ISDN Serial1/0:23 interface
dsl 0, interface ISDN Switchtype = primary-4ess
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Number of L2 Discards = 0, L2 Session ID = 0
03-04-2005 06:40 AM
I forgot you had asked for a sho isdn service
PRI Channel Statistics:
ISDN Se1/0:23, Channel [1-24]
Configured Isdn Interface (dsl) 0
Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3
Service State (0=Inservice 1=Maint 2=Outofservice 8=MaintPend 9=OOSPend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2
03-09-2005 10:42 AM
I spoke to AT&T today... they removed the requirement for an nsf service to be passed by the cisco router and the ISDN came up... still pursuing cisco as to why it didn't work in the first place.
03-24-2005 06:14 PM
I'm fighting this exact same issue....did you find out what Cisco's issue was?
04-04-2005 04:23 AM
Unfortunately no. The site is in production now so I haven't been able to look into it more... although I do have another ISDN line to AT+T that's 'exclusively' dial in... that I may try to dial out with to figure out the issue. The work around was AT+T turned off the sdn service. If you would like I will send you the contact information of the people I worked with on the problem?
04-04-2005 04:53 AM
Thanks for the feedback. We ended up getting it to work by adding (isdn nsf-service megacom) to our serial interface.
e.g.
interface Serial1/0:23
no ip address
no logging event link-status
isdn switch-type primary-4ess
isdn incoming-voice voice
isdn nsf-service megacom
no cdp enable
10-13-2012 09:19 AM
Actually, AT&T wouldn't need to disable SDN, you would simply apply the following command to you serial interface to accept the SDN.
interface Serial1/0:23
isdn nsf-service sdn
03-07-2014 07:54 AM
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide