Avaya AEP 8.1.2 UniMRCP Integration having SIP compatibility issues

[Arun Santhebennur]

Hi 

We are trying to get UniMRCP 1.8 work with Avaya AEP 8.1.2 and we are having issues with continuing the SIP session. The first 30-40 seconds are okay and then the call ended by UniMRCP.

We are trying to force AAEP to use TCP. We now have <sip-transport>tcp</sip-transport>. But still the ACK message from Avaya Experience Portal seems to have an invalid value --> (Via: SIP/2.0/UDP). This is causing UniMRCP to reject the ACK message. What is wierd is that the INVITE message has TCP. 

Any suggestions on how we can force Avaya to keep TCP? 

Thanks

Arun

[Jacek Jarmulak]

Just to clarify. This is the common AAEP issue that has had a fix since 1.3.0  - basically setting  <sip-transport>tcp</sip-transport> should cause sofia-sip to include ;transport=tcp in the Contact field in the unimrcp responses and that in turn should make Avaya send ACK messages with SIP/2.0/TCP instead of SIP/2.0/UDP which unimrcp ignores.

However, no matter what we do the   ;transport=tcp  is not included in the Contact field, and the calls fail after 32 seconds timeout.
(we did checked the logs which confirm that config->transport is indeed tcp)

We tested with unimrcp 1.8.0 and 1.7.0

Anyone running these versions successfully with Avaya 8.1 with TCP transport?

[Jacek Jarmulak]

we fixed the problem by setting this contact string inside  mrcp_sofia_config_validate if ext_ip and transport were set

sofia_agent->sip_contact_str = apr_psprintf(pool, "<sip:%s:%hu;transport=%s>", config->ext_ip, config->local_port, config->transport);