[SR-Users] Missing Route headers in locally generated BYE
Daniel-Constantin Mierla
miconda at gmail.com
Wed Dec 11 09:41:52 CET 2013
Hello,
On 11/12/13 09:38, Alex Balashov wrote:
> Carsten,
>
> On 12/11/2013 03:36 AM, Carsten Bock wrote:
>
>> why should Kamailio add a route for himself to an outbound request?
>> 172.30.105.18 is obviously the proxy itself; so adding the
>> Route-Header makes no sense.... (at least from a SIP-Perspective).
>>
>> Record-Route:
>> <sip:172.30.105.18;lr=on;ftag=ervXH3ycHcgpK;vsf=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA--;proxy_media=yes;dlgcor=fa8.9ea>
>>
>> 03:27:37.464071 IP 172.30.105.18.5060 > 172.30.105.20.5060: SIP,
>> length: 367
>>
>> Or am i missing something here?
>
> That depends, philosophically, on whether the intention of this
> feature is to spoof BYEs so that they appear to come from the
> respective UAs toward each other through the proxy (or, in substance,
> act as if they were), or for Kamailio to unexpectedly take on the role
> of a UAC mid-call. :-)
there must not be any route for proxy itself, even when BYE is sent by
end UA the Route is consumed by proxy, so it is no difference from this
perspective.
In the initial email on this thread, there was a second proxy, so I
wanted to see the route header stored for that proxy.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
More information about the sr-users
mailing list