rerouting on error code Cause i = 0x80FF - Interworking error; unspecified

[acolmagro]

Hi,

I have a problem with my operator. It has a regional crash ant I received this error code

Cause i = 0x80FF - Interworking error; unspecified

I have BRI backup with an other operator but the call manager does not reroute the call.

I try to put the BRI in the same route group or in an another route group but in the same rout list.

*Feb 25 09:20:00.355: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8  callref = 0x1A99

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9839F

                Exclusive, Channel 31

        Calling Party Number i = 0x0081, '565552838'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '0615405708'

                Plan:Unknown, Type:Unknown

*Feb 25 09:20:00.375: ISDN Se0/0/1:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x9A99

        Channel ID i = 0xA9839F

                Exclusive, Channel 31

*Feb 25 09:20:00.423: ISDN Se0/0/1:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x9A99

        Cause i = 0x80FF - Interworking error; unspecified

*Feb 25 09:20:00.447: ISDN Se0/0/1:15 Q931: TX -> RELEASE pd = 8  callref = 0x1A99

*Feb 25 09:20:00.455: ISDN Se0/0/1:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x9A99

I need help please.

Pierre

[Ayodeji Okanlawon]

Audrey,

We need to be sure that CUCM didnt route the call to the backup BRI. Can you send a "debug voip ccapi inout" for the failed call? What version of CUCM are you using

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

[acolmagro]

Yes i am sure it does not rerout the call. When I put my BRI first in the top down route group, the call can go out.

I am in version 9.1.2.10000

[Ayodeji Okanlawon]

AUdrey,

Can you sedn detailed CUCM traces? There is a bug in CUCM9.X where the Route List cant find any more device in the RG after trying the first device...I will see if I can get the bug details

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

[Carlo Poggiarelli]

Hi Audrey.

Try to put CUCM service parameters "Stop routing on unallocated number flag" and "Stop routing on user busy flag" to false and try an outgoing call

HTH

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

[acolmagro]

I try that but not succefully

[Carlo Poggiarelli]

So... in this case, as my friend Deji suggested, collect CUCM trace and please post here so we can analyze them and see what is happening.

Thanks

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

[Ayodeji Okanlawon]

Here is a similar Thread...

https://supportforums.cisco.com/message/3927483#3927483

https://supportforums.cisco.com/message/4004578#4004578

Use can use the work around,..,

Remove the BR1 from the route group, reset the Route lists and re-add the BR1 back and test again

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"