[OpenSIPS-Users] Delete alias references in SIP messages
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Fri Aug 15 15:05:23 CEST 2008
Hi Olle,
it is good to know we are still RFC compliant even if we allow the
changing of the FROM - to be honest I was not aware of the RFC4916,
neither of the backdoor from the RFC3261.
Thank you for the hint! i will consider adding the TO changing also (in
the same way as FROM changing).
Thanks and regards,
Bogdan
Johansson Olle E wrote:
>
> 12 aug 2008 kl. 23.17 skrev Bogdan-Andrei Iancu:
>
>> Hi Guillaume,
>>
>> Changing TO header is more or less against the RFC3261 and you should
>> not do it. More or less the same discussion as for the FROM header.
> Actually this is against SIP version 1, not really SIP version 2 in
> RFC3261.
> There is a new RFC that change the From headers for caller ID
> updates (which is a change of RFC3261 that kept this just for backwards
> compatibility).
>
> From RFC4916:
>
> " This solution involves changing the URI (not the tags) in the To and
> From header fields of mid-dialog requests and their responses,
> compared with the corresponding values in the dialog forming request
> and response. Changing the To and From header field URIs was
> contemplated in Section 12.2.1.1 of RFC 3261 [1], which says:
>
> "Usage of the URI from the To and From fields in the original
> request within subsequent requests is done for backwards
> compatibility with RFC 2543 [6], which used the URI for dialog
> identification. In this specification, only the tags are used for
> dialog identification. It is expected that mandatory reflection
> of the original To and From URI in mid-dialog requests will be
> deprecated in a subsequent revision of this specification."
>
> This document therefore deprecates mandatory reflection of the
> original To and From URIs in mid-dialog requests and their responses,
> which constitutes a change to RFC 3261 [1]."
>
> This RFC describes ways to update Caller IDs during a call.
>
> /Olle
More information about the Users
mailing list