[OpenSER-Users] Adding "Reason: SIP ; cause=200" header when CANCEL in forking scenarios
Hi, according to RFC 3326 [1] (Reason Header):
3.1 Call Completed Elsewhere
A proxy forks an INVITE request and one of the branches returns a 200 (OK). The forking proxy includes this status code in a Reason header field in the CANCEL request that it sends to the rest of the branches.
Reason: SIP ;cause=200 ;text="Call completed elsewhere"
With this behaviour, if an AoR is registered in two phones and one of them answers a call, that call will not appear as MISSED in the other phone (if the phone supports "Reason" headers).
Is it possible OpenSer to add this header when cancelling the rest of ringing branches? If not, do you think it could be a feature request?
[1] http://www.faqs.org/rfcs/rfc3326.html
Hi Iñaki,
Right now this RFC is not supported, but it is very doable - you just need somebody to do it :).
Just go for a feature request.
Regards, Bogdan
Iñaki Baz Castillo wrote:
Hi, according to RFC 3326 [1] (Reason Header):
3.1 Call Completed Elsewhere
A proxy forks an INVITE request and one of the branches returns a 200 (OK). The forking proxy includes this status code in a Reason header field in the CANCEL request that it sends to the rest of the branches.
Reason: SIP ;cause=200 ;text="Call completed elsewhere"
With this behaviour, if an AoR is registered in two phones and one of them answers a call, that call will not appear as MISSED in the other phone (if the phone supports "Reason" headers).
Is it possible OpenSer to add this header when cancelling the rest of ringing branches? If not, do you think it could be a feature request?
On Monday 21 January 2008 17:26:38 Bogdan-Andrei Iancu wrote:
Hi Iñaki,
Right now this RFC is not supported, but it is very doable - you just need somebody to do it :).
Just go for a feature request.
Hi, I already opened a feature request:
https://sourceforge.net/tracker/?func=detail&aid=1875757&group_id=13... XD
I'd like to try to add it but have to get some practise programming C before. Please, could you tell me if you consider correct the solution proposed in the above feature request in order to try to implement it?
Regards.
-
Bogdan-Andrei Iancu -
Iñaki Baz Castillo -
Iñaki Baz Castillo