Re: [SR-Users] NatHelper ignoring force_socket module parameter

2015-08-28 Thread Asgaroth
ehalf Of Daniel-Constantin Mierla Sent: Friday 7 August 2015 18:37 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] NatHelper ignoring force_socket module parameter You have to set server_id to be different for each node in order to send keepalive only for registration received di

Re: [SR-Users] NatHelper ignoring force_socket module parameter

2015-08-10 Thread Asgaroth
:37 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] NatHelper ignoring force_socket module parameter You have to set server_id to be different for each node in order to send keepalive only for registration received directly, however, iirc, this feature is only in master branch

Re: [SR-Users] NatHelper ignoring force_socket module parameter

2015-08-07 Thread Daniel-Constantin Mierla
You have to set server_id to be different for each node in order to send keepalive only for registration received directly, however, iirc, this feature is only in master branch. Cheers, Daniel On 23/07/15 15:19, Asgaroth wrote: > some more info on this one, it looks like this is only happening on

Re: [SR-Users] NatHelper ignoring force_socket module parameter

2015-07-23 Thread Asgaroth
some more info on this one, it looks like this is only happening on nodes that have been replicated to, for example, If a registration is processed on node 1, then the nathelper send the locally generated options message out of the correct socket, I presume it gets the sending socket details f