Voice ISDN BRI - INS64 - Outbound issue

mikezul · ‎06-27-2019

Hi all,

Having a bit of problem in configuring INS64/BRI for 1 of our office in Japan.

Topology is simple, HQ CUCM -MGCP- ISR4351 -BRI- NTT ONU/Device

Call control is MGCP, and established

ISDN to NTT device is good, MULTIPLE_FRAME_ESTABLISHED

Inbound is not a problem.

However, outbound is rejected immediately, tested many digit manipulation and still failed.

Anyone knows what this error means? *yes, checked google and ISDN codes but not very helpful.

002921: Jun 27 09:59:12.276: ISDN BR0/3/0:0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x81
Cause i = 0x82D8 - Incompatible destination
Progress Ind i = 0x8283 - Origination address is non-ISDN

This was a PBX migration so if I connect it back to the PBX, it would work.

Appreciate any help I can get.

Thanks,

MZ

002920: Jun XX 09:59:12.231: ISDN BR0/3/0:0 Q931: TX -> SETUP pd = 8 callref = 0x01 
Sending Complete 
Bearer Capability i = 0x9090A3 
Standard = CCITT 
Transfer Capability = 3.1kHz Audio 
Transfer Mode = Circuit 
Transfer Rate = 64 kbit/s 
Channel ID i = 0x89 
Exclusive, B1 
Progress Ind i = 0x8083 - Origination address is non-ISDN 
Calling Party Number i = 0x4181, '050XXXXXXXX' 
Plan:ISDN, Type:Subscriber(local) 
Called Party Number i = 0x80, '117' 
Plan:Unknown, Type:Unknown
002921: Jun 27 09:59:12.276: ISDN BR0/3/0:0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x81 
Cause i = 0x82D8 - Incompatible destination 
Progress Ind i = 0x8283 - Origination address is non-ISDN

Brandon Buffin · ‎06-27-2019

Get the telco involved and troubleshoot with them. Is 117 a valid number - looks like this is the called party number. Make sure plan/type are what the telco is expecting. Do you have details on the PBX configuration to check digit manipulation for outbound calls, plan/type configuration, etc.?

Brandon

mikezul · ‎06-27-2019

Hi,

Thanks for replying.

Yes, 117 is a valid destination, it's something like time announcement.

It's working in our other office with INS1500/PRI circuit to the same carrier.

So issue also happen in all outbound call and this is just example.

I don't have access to the PBX, unfortunately, which is the painful part.

I tested the usual digit manipulation, i.e. include area code, last 4 digit, E164, numbers only, add prefix 9, plan type subscriber, unknown, all kind of thing I can imagine..

Any idea from the error or any debug which can be done to see what's the expected number?

Thanks.

Brandon Buffin · ‎06-28-2019

Best option is to get on a call with the carrier, perform a test call and see what they are seeing. They should be able to tell you why you are receiving the error.