[OpenSIPS-Users] uac_registrant : forced socket parameter

[Ovidiu Sas]

Bonjour Sebastien,

Thank you for troubleshooting and pointing this out.
I did an update on the README to mark this out.

Merci Beaucoup,
Ovidiu Sas

-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

On Fri, Dec 9, 2011 at 6:03 AM, Sebastien CRUAUX <scruaux at halys.fr> wrote:
> Hi Ovidiu,
>
> Finally after days and days of this issue making me crazy, I found out where
> the problem came from !
> I thought it could be helpful to share it, it might help other users having
> the same problem.
>
> Actually, the parameter "listen=ip_you_want_opensips_to_listen_on" is
> MANDATORY if you want to use the forced_socket parameter in uac_registrant.
> For example, if you define the following line in opensips.cfg :
>
> modparam("uac_registrant",
> "uac","sip:my_domain,,sip:my_user at my_domain,,my_user,my_password,sip:my_user at my_contact_ip,,,udp:172.17.1.131:5060")
>
> you have to define the following line :
>
> listen=172.17.1.131
>
> before in opensips.cfg, otherwise, uac_registrant will consider the
> forced_socket as invalid. By default in opensips.cfg the listen parameter is
> not defined and opensips listens by default on all IPs, but uac_registrant
> does not recognize the open sockets.
>
> Best regards,
>
> Sebastien
>
>
> Le 24/11/2011 16:11, Ovidiu Sas a écrit :
>
> The difference between trunk and 1.7 is that if a forced socket is
> invalid, an error will be printed and opensips will stop.
> On 1.7, is a forced socket is invalid, it will be ignored and a
> default one will be used.
> You can copy the whole module from trunk into your 1.7 repo if you
> want to test the new behaviour.
>
> Regards,
> Ovidiu Sas
>
> On Thu, Nov 24, 2011 at 9:57 AM, Sebastien CRUAUX <scruaux at halys.fr> wrote:
>
> Hi Ovidiu,
>
> Sorry about the late reply.
> Are these changes included in the new Opensips 1.7.1 ?
>
> Best regards,
>
> Sebastien
>
> Le 17/11/2011 15:45, Ovidiu Sas a écrit :
>
> Actually, it was implemented completely and it is working ok.
> If the forced socket (in the uac param) is not a valid one, it is
> discarded and opensips will choose a valid one from it's own list.
>
> I pushed a check in the trunk (if a socket is forced and it is
> invalid, opensips will fail to start).
> Please pull the latest trunk and try again (you will get an error if
> you are forcing a bad socket).
>
> Regards,
> Ovidiu Sas
>
> On Wed, Nov 16, 2011 at 12:22 PM, Sebastien CRUAUX<scruaux at halys.fr>
>  wrote:
>
> Thank you very much for your quick answer Ovidiu ! :)
>
> Le 16/11/2011 18:15, Ovidiu Sas a écrit :
>
> It seems that you are right.  I forgot to completely implement this
> feature.
> I will take care of it.
>
> Regards,
> Ovidiu Sas
>
> On Wed, Nov 16, 2011 at 12:00 PM, Sebastien CRUAUX<scruaux at halys.fr>
>  wrote:
>
> Hi,
>
> It seems that the forced socket parameter in the uac_registrant module
> is
> ignored.
> I have 3 IP addresses on my Opensips server :
> - 172.17.1.126 on eth0
> - 172.17.1.13 on eth0:1
> - 172.17.1.131 on eth1
>
> I would like my REGISTER requests to go through the eth1 interface so I
> used
> the following line in opensips.cfg :
>
> modparam("uac_registrant",
>
>
> "uac","sip:mydomain.org,,sip:my_user at mydomain.org,,my_user,my_password,sip:my_user at my_ip,,,172.17.1.131")
>
> However, the REGISTER requests are going out through the IP address
> 172.17.1.13 (eth0:1 interface). I tried replacing the last parameter of
> the
> above line by "udp:172.17.1.131:5060" but the behaviour did not change.
> Note
> that Opensips is listening on all 3 IP addresses.
>
> Thanks,
>
> Sebastien