t: Re: [SR-Users] Best approach for TCP/TLS connection re-use for nated
Contacts
Am 09.03.2012 20:56, schrieb Giacomo Vacca:
One of the solutions I've found is using always add_contact_alias() in
onreply_route when handling the 200 OK, and then use handle_ruri_alias() when
defining the desti
Am 09.03.2012 20:56, schrieb Giacomo Vacca:
One of the solutions I've found is using /always /add_contact_alias()
in onreply_route when handling the 200 OK, and then use
handle_ruri_alias() when defining the destination for the ACK.
Yes, that the pragmatic approach I always use. IMO it is als
Hello,
you can do nat_uac_test() for reply and it will detect is it natted, then
you can call fix_nated_contact() -- this being another option.
Cheers,
Daniel
On Fri, Mar 9, 2012 at 8:56 PM, Giacomo Vacca wrote:
> Hi all,
>
> I have a scenario where it’s not clear to me what the best approach
Hi all,
I have a scenario where it's not clear to me what the best approach should be
(Kamailio 3.2.0 on Squeeze, although I think it's a matter of routing logic
only).
I have a client behind NAT that sends an initial REGISTER request with a
Contact containing private ip:port (e.g.
Contact: "GV
