Transfer fail between Avaya IP Office set and CISCO CUCM Sets

[Julian Igareda]

Hi,

We have a Avaya IP Office R9.1 interconected with CISCO CUCM 9.1 with SIP Trunk. When we make a call from Avaya to Cisco and that one transfers to another CISCO, the Avaya set is put on hold and always it keeps in this state.

We have traced the call (Avaya extension is 133370, CISCO extensions are 107650 and 107643) and attached in this thread.

Any idea about this issue?

Thanks in advance.

Best Regards,

 

[janni78]

Doesn't show anything obvious, what does the Cisco trace say?

"Trying is the first step to failure..." - Homer

 

[kyle555]

I see a few things wrong. What is in between your Cisco and IPO? The IPO is in private address space and Cisco is in public space.

the c=0.0.0.0 and a=inactive is an old way of holding and not the same as a=sendonly

Every time Cisco sends you a reinvite with no SDP, you answer with a 200OK with 2 way SDP advertising your capabilities to recover from the hold.

Cisco always sends you back inactive media for whatever reason. Something on it's trunk configuration or in between you is messing up how to hold/unhold.

All I can see is every time you're solicited for capabilities via a reinvite with no SDP, you always answer that you can do two way audio and are willing to end the hold.