Hi All,
I am trying to integrate Unimrcp with Avaya Experience portal. Unimrcp is returning Unsupported media type 415 in response to SIP invite from Avaya Experience portal. Requesting Arsen and other group members to throw some light on this.
Attaching SIP log for reference.
2019-11-22 09:19:18.889807 recv 1205 bytes from tcp/[AvayaPublicIP]:31077
INVITE sip:mresource@MyPublicIP SIP/2.0^M
From: sip:mpp@aaeppom;tag=18d9b7b275bea12f4e00a8c02bd2^M
To: sip:mresource@MyPublicIP^M
Call-ID: 4ad9b7b275bea1304e00a8c02bd2^M
CSeq: 1 INVITE^M
Max-Forwards: 70^M
Via: SIP/2.0/TCP AvayaPrivateIP:5000;branch=z9hG4bKb4e2b7b275bea1324e00a8c02bd2^M
User-Agent: Avaya-VoicePortal/7.2.3.0.0433^M
Supported: 100rel, timer, replaces, join, histinfo^M
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER, OPTIONS, INFO, PUBLISH, UPDATE^M
Contact: <sip:AvayaPrivateIP:5000;transport=tcp>^M
Session-Expires: 1200;refresher=uac^M
Min-SE: 1200^M
Content-Type: multipart/mixed;boundary="ccdeb7b275bea1314e00a8c02bd2"^M
Content-Length: 529^M
^M
--ccdeb7b275bea1314e00a8c02bd2^M
Content-Type: application/p-nuance-session-config^M
^M
^M
--ccdeb7b275bea1314e00a8c02bd2^M
Content-Type: application/sdp^M
^M
v=0^M
o=- 1 1 IN IP4 AvayaPrivateIP^M
s=-^M
t=0 0^M
m=audio 11344 RTP/AVP 18 0 8 127^M
c=IN IP4 AvayaPrivateIP^M
a=rtpmap:18 G729/8000^M
a=rtpmap:0 PCMU/8000^M
a=rtpmap:8 PCMA/8000^M
a=rtpmap:127 telephone-event/8000^M
a=sendonly^M
m=application 9 TCP/MRCPv2 1^M
c=IN IP4 MyPublicIP^M
a=setup:active^M
a=connection:new^M
a=cmid:1^M
a=resource:speechrecog^M
--ccdeb7b275bea1314e00a8c02bd2--^M
^K
2019-11-22 09:19:18.890504 sent 536 bytes to tcp/[AvayaPublicIP]:31077
SIP/2.0 415 Unsupported Media Type^M
Via: SIP/2.0/TCP AvayaPrivateIP:5000;branch=z9hG4bKb4e2b7b275bea1324e00a8c02bd2;received=AvayaPublicIP;rport=31077^M
From: sip:mpp@aaeppom;tag=18d9b7b275bea12f4e00a8c02bd2^M
To: <sip:mresource@MyPublicIP>;tag=3yX9BtDBgrvam^M
Call-ID: 4ad9b7b275bea1304e00a8c02bd2^M
CSeq: 1 INVITE^M
User-Agent: UniMRCP SofiaSIP 1.6.0^M
Accept: application/sdp^M
Accept-Encoding: ^M
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE^M
Supported: timer, 100rel^M
Content-Length: 0^M
^M
^K
2019-11-22 09:19:18.953293 recv 402 bytes from tcp/[AvayaPublicIP]:31077
ACK sip:mresource@MyPublicIP SIP/2.0^M
From: sip:mpp@aaeppom;tag=18d9b7b275bea12f4e00a8c02bd2^M
To: <sip:mresource@MyPublicIP>;tag=3yX9BtDBgrvam^M
Call-ID: 4ad9b7b275bea1304e00a8c02bd2^M
Via: SIP/2.0/TCP AvayaPrivateIP:5000;branch=z9hG4bKb4e2b7b275bea1324e00a8c02bd2;received=AvayaPublicIP;rport=31077^M
CSeq: 1 ACK^M
Max-Forwards: 70^M
User-Agent: Avaya-VoicePortal/7.2.3.0.0433^M
Content-Length: 0^M
My SIP config in unimrcpserver.xml is as below
<sip-uas id="SIP-Agent-1" type="SofiaSIP">
<!--
By default, "ip" and "ext-ip" addresses, set in the properties, are used. These parameters can
explicitly be specified per "sip-uas" by means of "sip-ip" and "sip-ext-ip" correspondingly.
-->
<!-- <sip-ip>10.10.0.1</sip-ip> -->
<!-- <sip-ext-ip>a.b.c.d</sip-ext-ip> -->
<sip-port>8060</sip-port>
<sip-transport>tcp</sip-transport>
<force-destination>true</force-destination>
<!--
This parameter can be used to disable the Sofia SIP SDP Offer/Answer Engine Module (soa).
This should only be done when dynamic payload type negotiation is needed with MRCPv2 AND
the clients only use the 'Basic Call' SDP Offer/Answer scenario. More complex scenarions
will most probably not work with soa disabled.
-->
<disable-soa>true</disable-soa>
<ua-name>UniMRCP SofiaSIP</ua-name>
<sdp-origin>UniMRCPServer</sdp-origin>
<!-- <sip-t1>500</sip-t1> -->
<!-- <sip-t2>4000</sip-t2> -->
<!-- <sip-t4>4000</sip-t4> -->
<!-- <sip-t1x64>32000</sip-t1x64> -->
<sip-session-expires>600</sip-session-expires>
<sip-min-session-expires>120</sip-min-session-expires>
<sip-message-output>true</sip-message-output>
<sip-message-dump>sofia-sip-uas.log</sip-message-dump>
</sip-uas>
I have also attached SIP debug logs for reference. NOTE : I have hidden IP addresses for security reasons.