Cisco to Avaya trunking - Call Failure from Cisco into Avaya

[wareemba76]

Hi Everyone,

We've been having a fun time trying to get SIP trunk up and working between Avaya SM\CM and Cisco.

We can make calls from Avaya to Cisco perfectly.

However, when Cisco attempts to call back to Avaya we see 500 Server internal error on SM, and on the ingress CM trunk we see the below errors, which i don't understand.

Hoping anyone out there might be able to offer any pointers?

14:38:15 TRACE STARTED 11/26/2019 CM Release String cold-01.0.532.0-25221
14:40:01 SIP<INVITE sip:115115@ourdomain.com SIP/2.0
14:40:01 Call-ID: 6b998400-ddc19e91-5d59df-28e2700a@10.112.226.4
14:40:01 0
14:40:01 denial event 2314: No channel resources D1=0xa4 D2=0x32
14:40:01 SIP>SIP/2.0 500 Server Internal Error
14:40:01 Call-ID: 6b998400-ddc19e91-5d59df-28e2700a@10.112.226.4
14:40:01 0
14:40:01 denial event 1644: Orig block/invalid digits D1=0x504c8 D2=0x800173a
14:40:01 active trunk-group 16 member 187 cid 0x173a
14:40:01 SIP<ACK sip:115115@ourdomain.com SIP/2.0
14:40:01 Call-ID: 6b998400-ddc19e91-5d59df-28e2700a@10.112.226.4

Thank you!

 

[kyle555]

got a sig group on CM with near/far IP/port and far end domain ourdomain.com?

Calling to Cisco you've got trunk 16 and on the bottom right of page 1 you pick a sig group. You need that sig group # to have domain ourcompany.com and be the same IP/port pair that matches what SM is sending when Cisco calls in.

 

[avayatech2018]

Watching this post as we'll be doing this soon!

40 years in Telecom. New to Avaya! Go easy.

 

[jimbojimbo]

Did you configure an adaptation module for the Cisco Entity on System Manager using the CiscoAdpater?

Use the traceSM and include call processing. NOTE: if you have heavy traffic then perform after hours. This will give you a breakdown of how the SM is attempting to match the dialed number and domain to determine if/how it should route the call.

 

[wareemba76]

Thanks Guys,

I do have a far-end domain. However it is set to use just standard SIP domain used for Avaya. I might test this in a few days, its an angle we hadn't been down. Although we are doing some domain manipulation on the adaptation.

We're using the CiscoAdapator yes. I will try the Call processing option also and see if it yeilds any clue for why CM spits back on the call.

 

[wareemba76]

Still at this one. Hope to have some positive update soon.

 

[avayaguy23]

It’s been a while since I did this set up but you should look at the devconnect configuration.

https://www.devconnectprogram.com/fileMedia/download/928b54c1-8da3-4101-b2f3-6a97cb6417e9

 

[dialtonebone]

14:40:01 denial event 2314: No channel resources D1=0xa4 D2=0x32"

https://downloads.avaya.com/elmodocs2/comm_mgr/R5_2/03_602793_1.pdf

My quick, but possibly inaccurate interpretation is: Sounds like the signal group can not find a DSP to connect the audio with.

Is the signal group configured into a network region which has access to DSPs?

 

[avayaguy23]

the Network region doesn’t have any gateways so it can’t get dsp

 

[wareemba76]

i'm glad to report that this issue has been cracked by one of our very clever inhouse Engineers. The series of ambiguous denial events turned out to be that when an incoming Cisco call was received via the SIP trunk and presented to CM that CM did not have an appropriate network region mapping between that defined for the remote CuCM subscriber cluster and our internal\core\data centre IP network region.