03-28-2003 09:28 AM - edited 03-12-2019 11:16 PM
CM 3.2.2c H323 PRI ISDN DMS100 gateway. Q.931 Disconnect cause code 0x8AFF indicates PSTN returning error from a network beyond the internetworking point. Anyone experienced anything like this? Thanks.
Solved! Go to Solution.
03-28-2003 01:35 PM
I think what may be happening is it gets passed to lucent switch for cellular then goes SS& to mobile, Lucent I believe needs to see calling party as national for it to get mapped correctly to ISUP.
Try putting this on serial interface 3/0:23 as a test
isdn map addr . plan isdn type nat
03-28-2003 12:49 PM
okay its private network serving remote user, interworking unspecified cause.
is what kind of gateway ? is gateway connected to switch or pbx ? can I see
debug isdn q931 from setup to disconnect ?
usually you see this when you go gateway to gateway and one side is setup to a pbx running qsig ( which is vendor dependent)and the other is a standard such as dms or ni2. You see it when the qsig side does a facility or a shift to codest that the other side can't map into the standard stack.
03-28-2003 01:06 PM
3660 nm-hdv-2t1 MFT h.323 gw connected to siemens pbx using ISDN DMS100. New CIPT implementation using new DID range 604-676-XXXX. I'm wondering if the remote cellular service provider serving 416-821 and 822 does not recognize 604-676 DID range?
Mar 28 16:34:09.712: ISDN Se3/0:23 Q931: TX -> SETUP pd = 8 callref = 0x2147
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x00, 0x81, '6046764910'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '814168218384'
Plan:Unknown, Type:Unknown
Mar 28 16:34:09.796: ISDN Se3/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xA14
7
Channel ID i = 0xA98397
Exclusive, Channel 23
Mar 28 16:34:10.940: ISDN Se3/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0xA147
Cause i = 0x8AFF - Interworking error; unspecified
Progress Ind i = 0x8581 - Call not end-to-end ISDN, may have in-band inf
o
Mar 28 16:34:10.944: ISDN Se3/0:23 Q931: TX -> STATUS pd = 8 callref = 0x2147
Cause i = 0x80E4 - Invalid information element contents
Call State i = 0x04
03-28-2003 01:35 PM
I think what may be happening is it gets passed to lucent switch for cellular then goes SS& to mobile, Lucent I believe needs to see calling party as national for it to get mapped correctly to ISUP.
Try putting this on serial interface 3/0:23 as a test
isdn map addr . plan isdn type nat
03-28-2003 06:19 PM
This solved the problem. Thanks so much. Lunch is on me.
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