[SIP Beyond VoIP] sending message to kamailio/msrprelay causes MSRP 501 error

Andreas Bachmann andreas at jibemobile.com
Wed May 23 20:02:01 CEST 2012

Hi Steve,

The Order of some headers in MSRP is important - as well as the existence
of some. 
For MSRP it's the same as with SIP: If u have an entity body - u have to
declare a content type header.
And this header MUST be the last header before the body (in combination
with other content related header).


From:  Steve Parrish <sparrish at d2tech.com>
Organization:  D2 Technologies
Date:  Mittwoch, 23. Mai 2012 19:13
To:  "sipbeyondvoip at lists.ag-projects.com"
<sipbeyondvoip at lists.ag-projects.com>
Subject:  Re: [SIP Beyond VoIP] sending message to kamailio/msrprelay
causes MSRP 501 error

I can't remember the MSRP spec's details at the moment but I don't see
where the Content-Type is defined in your MSRP message.  Maybe that's
required...You need to indicate if the MSRP SEND payload is CPIM or text,

On 05/23/2012 11:26 AM, Adrian Georgescu wrote:

OpenSIPS + MSRPRelay combination or
http://sip2sip.info <http://sip2sip.info> SIP service work just fine
unless you can prove otherwise.

For why the MSRP implementation of Kamailio is not able to handle properly
the MSRP methods you should ask its developers, the problem is on the
server side not the client.


On May 23, 2012, at 6:17 PM, Reichert Alexander wrote:

We are developing a Java based RCS gateway implementation and are
performing some integration tests on a kamailio/msrprelay platform.
The SIP signaling part works so far, but when sending a MSRP message, the
server always responds with a 501 ³Unknown method² error. On Protocol
level, everything look fine so far, the sequence executed is as follows:
<-- SIP/2.0 401 Unauthorized
<--SIP/2.0 200 OK
<--SIP/2.0 407 Proxy Authentication Required
<--SIP/2.0 180 Ringing
<--SIP/2.0 180 Ringing
<--SIP/2.0 200 OK
The INVITE is processed with the following SDP packet in the request:
o=- 1337788359935 1337788359935 IN IP4 localhost
s=MSRP Session
c=IN IP4 localhost
t=0 0
m=message 2855 TCP/MSRP *
a=accept-types:message/cpim text/* application/im-iscomposing+xml
And response:
o=- 3546777215 3546777216 IN IP4
s=sipsimple 0.20.0
c=IN IP4
t=0 0
m=message 57233 TCP/MSRP *
wNS43OC42OA==;tcp msrp://msrphost:57233/6bf6dd73b9e4587b65b6;tcp
a=accept-types:message/cpim text/* application/im-iscomposing+xml

But when sending the MSRP message, 501 is returned:
To-Path: msrp://msrphost:57233/6bf6dd73b9e4587b65b6;tcp
From-Path: msrp://localhost:52673/b10XadK9;tcp
Message-ID: 13377883623135c260a3568cc
Byte-Range: 1-*/14
Hello Francois
MSRP f0CHA1TD 501 Unknown method: SEND
To-Path: msrp://localhost:52673/b10XadK9;tcp
From-Path: msrp://msrphost:57233/6bf6dd73b9e4587b65b6;tcp
When testing with the sip-simple client, MSRP messaging works fine, but on
protocol traces we cannot identify any differences.
Does anyone have a hint on what is wrong in this message flow? Any advice
is appreciated.

SIPBeyondVoIP mailing list
SIPBeyondVoIP at lists.ag-projects.com

SIPBeyondVoIP mailing list
SIPBeyondVoIP at lists.ag-projects.comhttp://lists.ag-projects.com/mailman/lis

More information about the SIPBeyondVoIP mailing list