[reSIProcate] no Contact allowed in MESSAGE

Scott Godin sgodin at sipspectrum.com
Thu Jun 19 13:14:50 CDT 2014


You are still allowed to send a MESSAGE request within an existing dialog.
Many applications will send a MESSAGE request in a SIP Invite dialog.  This
change would break that capability.  For out of dialog MESSAGE requests -
the PagerMessage logic doesn't use a Contact header.

Scott


On Thu, Jun 19, 2014 at 1:24 PM, John Gregg <jgregg at aylus.com> wrote:

> As per RFC 3428, section 4:
>
> MESSAGE requests do not initiate dialogs.  User Agents MUST NOT
>    insert Contact header fields into MESSAGE requests.
>
> Accordingly, I think the following change should be made to
> Dialog::makeRequest() (diff from Dialog.cxx, version 1.9.6 attached):
>
>    request.remove(h_Contacts);
>    if (method != MESSAGE) // RFC 3428, section 4: no Contact allowed in
> MESSAGE
>    {
> request.header(h_Contacts).push_front(mLocalContact);
>    }
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20140619/f66f9837/attachment.htm>


More information about the resiprocate-devel mailing list