[SIP SIMPLE client] sylk is not relaying chat messages

Juha Heinanen jh at tutpro.com
Sat Apr 30 11:43:58 CEST 2011

Adrian Georgescu writes:

> Rewriting SIP URIs is indeed permitted in SIP Proxies and one must
> consider when and if is necessary to do such thing. The conference
> rooms are based on this URIs in this case. So if the application is
> non-VoIP related is best to avoid rewriting any headers unless
> necessary as they may be required by the application.


just to clarity, my proxy didn't rewrite any headers, just request uri.

the problem seems to be caused by the fact that this re-written request

INVITE sip:+35892345671*5393*2075 at test.fi

is not the same as To uri in MSRP message

MSRP 67f6bc8806564bba SEND
To-Path: msrps://;tcp
From-Path: msrps://;tcp
Message-ID: 24aaf301f5546d68
Byte-Range: 1-175/175
Success-Report: yes
Failure-Report: yes
Content-Type: message/cpim
From: <sip:foo at test.fi>
To: <sip:+35892345671*5393*2075 at cf.test.fi>

thus sylk does not match the above msrp message to the conference joined
by the invite.

i don't know what the rfcs say about this, but it would seem to be
better to do matching of MSRP messages to the conference based on the
tags in these headers

To-Path: msrps://;tcp
From-Path: msrps://;tcp

instead of To URI.  those tags were in the invite/200 ok exchange when
user joined the conference and would thus uniquely identify the

-- juha

More information about the SIPBeyondVoIP mailing list