9 Jul
2010
9 Jul
'10
12:48 p.m.
On 7/8/10 2:07 PM, Alex Balashov wrote:
Even if it didn't, just add your own RR header.
when you know exactly the inbound/outbound interfaces, yes you can add
yourself the rr headers with textops and don't call rr.
rr has the advantage of adding the rr with outbound local IP in cases
such as location and mhomed, when is not easy to decide in config which
local socket to use for sending.
Cheers,
Daniel
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Jul 8, 2010, at 7:33 AM, Iñaki Baz Castillo <ibc(a)aliax.net> wrote:
> 2010/7/8 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:
>>> But be caredull with in-dialog requests as by default they would use
>>> the "default" source port ;)
>>>
>>
>> if invite is received on one socket and forwarded using a different
>> socket,
>> then it should get 2 record-route headers so the within-dialog
>> requests are
>> using same sockets without anything else in config than loose_route and
>> relay. Do you get it different?
>
> I was wondering exactly the same (the double Route header present in
> in-dialog request) but I remember a thread in which there was some
> problem with it (most probably due to a bad configuration).
>
> So yes, my fault, it works out-of-the-box :)
>
> Thanks for the clarification.
>
>
> --
> Iñaki Baz Castillo
> <ibc(a)aliax.net>
--
Daniel-Constantin Mierla
http://www.asipto.com/