IP Trunk between Cisco and Avaya

[Samanody]

Dear all
I have to do a tie between Cisco Call Manager 6.1 and Avaya Media Server s8720 (CM3.1.2).
IP trunk is in service
H.323 Signaling aslo in service
But when I dial from avaya sets to Cisco: i hear silence only and from Cisco sets to avaya sets: only ring then nothing
this is the list trace:
dial 712 route:UDP|AAR
16:06:34 term trunk-group 26 cid 0x1564
16:06:34 dial 712 route:UDP|AAR
16:06:34 route-pattern 960 preference 1 cid 0x1564
16:06:34 seize trunk-group 26 member 2 cid 0x1564
16:06:34 Calling Number & Name 8191 Nabih Al Akoum
16:06:34 Proceed trunk-group 26 member 2 cid 0x1564
16:06:47 denial event 1190: No circ/chan avail D1=0x830032 D2=0x50122
16:06:47 idle trunk-group 26 member 2 cid 0x1564

Please help me

 

[uzumaki]

The far-end switch doesnt accept the numbers that avaya is throwing.

16:06:47 denial event 1190: No circ/chan avail D1=0x830032 D2=0x50122

Can you ask your cisco guys how their equipment will accept the digits you are throwing.

 

[Konri]

There are no free (voip) channels on FarEnd device (Cisco)
Signalling is working well.

K

 

[Samanody]

Is should be the same number of IP channels between them?

 

[Midstream]

What are the Cisco folks telling you about the information they are seeing in their traces?

 

[Samanody]

Dear all
thx for your reply
i changed the Ip address for Cisco Side: Call Manager IP , not IP Gateway...
Now from Avaya Sets can call Cisco Ip Phones but from Cisco randomly talk...i am waiting to fix the number of channels in Cisco Side...

 

[eatlog]

Hi Snoopy


Can you check the codec of the far end side (cisco). Codec
should be the same. If I may suggest try G.729.

 

[Samanody]

Dear eatlog
we work in this issue (ip-codec), G.729 then G.711MU and many ip-codec, and its not resolve the problem.

 

[eatlog]

Do you still have same trace on your trunk? Can you set of both systems to G.729. Try also to double check the IP of the node-names it should be the IP of the CallManager and same from your CallManager it should be the IP of your CLAN.

 

[eatlog]

Hi Snoopy

Try to download this pdf and review your config.

ttp://rapidshare.com/files/177832270/IP_TRUNKING__Avaya_-_Cisco__1_.pdf.html

 

[Samanody]

Dear eatlog
thx, i have this document before, but Good New:
its working finally
the problem is about signaling
using Wire Shark, we detect that no RTP, so the signaling between two sides not comaptible...we enable FastStart inbound and outband in CCM and its working.

 

[2telguy]

Eatlog,

Can you post that doc again? Thanks!

 

[eatlog]

2telguy

check the link below