Re: [OpenSIPS-Users] mhome asymmetric port issue

[SamyGo]

Hi Satish,

I can't understand this:

"*...use t_relay() in dispatcher then its consuming REGISTER packet and
sending AUTH challenge to client instead **of sending that REGISTER to
backend dispatcher..*"

t_relay has nothing to do with "consuming" REGISTER packets. I've done it
so many times, the AUTH must be coming from your backend servers.

Please take a packet capture on ALL of your interfaces you must be looking
at the one interface where client is sending packets to and hence makes you
think that OpenSIPS is sending AUTH.

Regards,
Sammy







On Thu, Mar 3, 2016 at 5:22 PM, Satish Patel  wrote:

> Thanks Razvan,
>
> Problem is we have legacy application running on ser-0.10 older
> version and we have did lots of other customization in ser I tried to
> use force_send_socket() but look like that support isn't in RR module.
>
> if i enable "mhomed=1" and use t_relay() in dispatcher then its
> consuming REGISTER packet and sending AUTH challenge to client instead
> of sending that REGISTER to backend dispatcher..
>
> if i use forward(uri:host, uri:port); function then it doesn't
> understand socket correctly. atleast t_relay() is working but
> consuming REGISTER, we have very simple code like following
>
> else if ( (method=="REGISTER")  || (method=="INVITE") ) {
> if ( !ds_select_dst("2", "2") ) {
> xlog("L_ERR", "Unable to route REGISTER\n");
> sl_send_reply("500","Unable to route REGISTER");
> break;
> }
> ..
> ..
> t_relay()
>
> On Thu, Mar 3, 2016 at 3:39 AM, Răzvan Crainea 
> wrote:
> > Hi, Satish!
> >
> > By default, OpenSIPS uses the same interface to send the reply. However,
> > when using mhomed=1, the operating system decides where the reply should
> be
> > sent to. And in your case, the operating system simply chooses a
> different
> > interface. So it seems this is the normal behavior, there's nothing
> wrong.
> > If you really want to use the same interface for replies, you should use
> the
> > force_send_socket() function to set the desired interface.
> >
> > Best regards,
> > Răzvan
> >
> >
> > On 03/02/2016 11:10 PM, Satish Patel wrote:
> >>
> >> mhome=1
> >> listen=udp:10.0.0.1:6060 udp:10.0.0.1:5060 udp:192.168.100.1:6060
> >> udp:192.168.100.1:5060
> >>
> >>  From client when i send REGISTER to 5060 then server sending reply
> >> back using port 6060, it should send reply back client using 5060
> >> right???
> >>
> >> If i use mhome=0 everything works!
> >>
> >> ___
> >> Users mailing list
> >> Users@lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> > --
> > Răzvan Crainea
> > OpenSIPS Core Developer
> > http://www.opensips-solutions.com
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mhome asymmetric port issue

[Satish Patel]

Thanks Razvan,

Problem is we have legacy application running on ser-0.10 older
version and we have did lots of other customization in ser I tried to
use force_send_socket() but look like that support isn't in RR module.

if i enable "mhomed=1" and use t_relay() in dispatcher then its
consuming REGISTER packet and sending AUTH challenge to client instead
of sending that REGISTER to backend dispatcher..

if i use forward(uri:host, uri:port); function then it doesn't
understand socket correctly. atleast t_relay() is working but
consuming REGISTER, we have very simple code like following

else if ( (method=="REGISTER")  || (method=="INVITE") ) {
if ( !ds_select_dst("2", "2") ) {
xlog("L_ERR", "Unable to route REGISTER\n");
sl_send_reply("500","Unable to route REGISTER");
break;
}
..
..
t_relay()

On Thu, Mar 3, 2016 at 3:39 AM, Răzvan Crainea  wrote:
> Hi, Satish!
>
> By default, OpenSIPS uses the same interface to send the reply. However,
> when using mhomed=1, the operating system decides where the reply should be
> sent to. And in your case, the operating system simply chooses a different
> interface. So it seems this is the normal behavior, there's nothing wrong.
> If you really want to use the same interface for replies, you should use the
> force_send_socket() function to set the desired interface.
>
> Best regards,
> Răzvan
>
>
> On 03/02/2016 11:10 PM, Satish Patel wrote:
>>
>> mhome=1
>> listen=udp:10.0.0.1:6060 udp:10.0.0.1:5060 udp:192.168.100.1:6060
>> udp:192.168.100.1:5060
>>
>>  From client when i send REGISTER to 5060 then server sending reply
>> back using port 6060, it should send reply back client using 5060
>> right???
>>
>> If i use mhome=0 everything works!
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> --
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mhome asymmetric port issue

[Răzvan Crainea]

Hi, Satish!

By default, OpenSIPS uses the same interface to send the reply. However, 
when using mhomed=1, the operating system decides where the reply should 
be sent to. And in your case, the operating system simply chooses a 
different interface. So it seems this is the normal behavior, there's 
nothing wrong. If you really want to use the same interface for replies, 
you should use the force_send_socket() function to set the desired 
interface.


Best regards,
Răzvan

On 03/02/2016 11:10 PM, Satish Patel wrote:

mhome=1
listen=udp:10.0.0.1:6060 udp:10.0.0.1:5060 udp:192.168.100.1:6060
udp:192.168.100.1:5060

 From client when i send REGISTER to 5060 then server sending reply
back using port 6060, it should send reply back client using 5060
right???

If i use mhome=0 everything works!

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] mhome asymmetric port issue

[Satish Patel]

mhome=1
listen=udp:10.0.0.1:6060 udp:10.0.0.1:5060 udp:192.168.100.1:6060
udp:192.168.100.1:5060

>From client when i send REGISTER to 5060 then server sending reply
back using port 6060, it should send reply back client using 5060
right???

If i use mhome=0 everything works!

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users