Avaya Experience portal integration with Unimrcp - Unsupported media Type 415

157 views
Skip to first unread message

James

unread,
Nov 23, 2019, 3:20:57 AM11/23/19
to UniMRCP
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.






sofia-sip-uas.log.debug

Wilmar Pérez

unread,
Nov 24, 2019, 5:27:23 PM11/24/19
to uni...@googlegroups.com
Hi James,

In your SDP directives it seems you are supporting G.729 along with G711.

a=rtpmap:18 G729/8000^M
a=rtpmap:0 PCMU/8000^M
a=rtpmap:8 PCMA/8000^M

I believe unimrcp does not support G729  

You can check the rtp-settings session in your unimrcpsever.xml config file.  You should see something like this:

<codecs own-preference="false">PCMU PCMA L16/96/8000 telephone-event/101/8000</codecs>

or this:

 <codecs own-preference="false">PCMU PCMA L16/96/8000 telephone-event/101/8000 PCMU/97/16000 PCMA/98/16000 L16/99/16000 telephone-event/102/16000</codecs>

I do not recall having seen an option for G729. You can probably setup your Experience Portal to only use G711A or G711u.

Best,

Wilmar.



--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/576d1eea-ae53-4596-93ff-1ca2f2821dce%40googlegroups.com.


--
--------------------------------------------------------
Wilmar Pérez 

Bharath Shankar

unread,
Nov 25, 2019, 10:21:01 AM11/25/19
to UniMRCP
Thanks for your reply Wilmar.

But please correct me if I am wrong. G.729 might be one the capabilities in rtpmap. However SIP negotiation should settle in on PCMU/8000 or PCMA/8000 as it is supported by both parties. Right ?

Also looking at "Unsupported media type 415" response from Unimrcp. It has included

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

SIP invite from Avaya EP is a multipart message with one of the content types

Content-Type: application/p-nuance-session-config

Does Unimrcp support 

Content-Type: application/p-nuance-session-config



To unsubscribe from this group and stop receiving emails from it, send an email to uni...@googlegroups.com.


--
--------------------------------------------------------
Wilmar Pérez 

Arsen Chaloyan

unread,
Nov 25, 2019, 9:00:51 PM11/25/19
to UniMRCP
Hi Bharath,

You properly identified the problem, which is indeed in the multipart/mixed content of the incoming SIP INVITE message. Please note that application/p-nuance-session-config is a proprietary addition of Nuance. There are no plans to support this content type. Not sure how you configured AAEP to make it send an offer in such format. If you are using a profile for Nuance, then consider making it compliant with NSS 5 but not 6.



To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/20003208-8570-4897-aa38-701fc7404058%40googlegroups.com.


--
Arsen Chaloyan
Author of UniMRCP
http://www.unimrcp.org

Bharath Shankar

unread,
Nov 27, 2019, 6:37:41 AM11/27/19
to UniMRCP
Hi Arsen,

Thanks for your reply.

If I interpret your answer correctly, unimrcp natively supports NSS 5. So if Avaya EP can be configured to use NSS 5 then things should go through ?

Arsen Chaloyan

unread,
Nov 27, 2019, 10:26:35 PM11/27/19
to UniMRCP
Hi Bharath,

Your statement is not entirely correct. While implementing UniMRCP, I strictly followed the relevant standards without attempting to mimic any other implementation. If you configure AAEP to use the generic MRCP protocol without any extensions, then everything would seamlessly work. And yes, NSS 5 does not have the proprietary extension added in NSS 6 I referred to.

To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/1158debc-13da-4f2b-9a8d-50a93b0fb3e7%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages