Ah... you mentioned it is... that is really strange, because this simple
logic works on 1.8 -> master.
If the "socket" column is defined, it will precede the module parameter.
Are there any errors in the logs? What does "opensipsctl fifo ps" say?
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 03/25/2014 12:17 PM, Liviu Chircu wrote:
Hello Wilmar,
Is OpenSIPS listening on udp:192.168.0.10:5060 as well? Otherwise, it
will send the pings from the other interface.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 03/24/2014 10:08 PM, Wilmar Campos wrote:
Hi Bogdam,
I went back to version 1.8.3. But it stopped working.
I basically have in the dispatcher table, the socket with
UDP:192.168.0.10:5060 <http://192.168.0.10:5060> wich is the IP I
want to use to send the probind and invites from. it continues
sending the invite from main interface.
Is there another parameter that ovewrites the value in the column socket?
Thanks,
On Fri, Mar 21, 2014 at 11:16 AM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hello,
In the dispatcher table (
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN2767
), you have a socket column - you can configure there what is the
preferred interface to be used by dispatcher in relation to that
destination.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 20.03.2014 23:11, Wilmar Campos wrote:
Hi Group,
I came into a situation that my opensips is listening only to
the secondary IP in the eth0.
I have include Listern:udp:192.168.0.10:5060
<http://192.168.0.10:5060> wich is the secondary IP for eth0.
Now, when dispatcher is probing, its sending the probing from
the ip 192.168.0.9 wich is the Primary IP in the interface.
I am using Opensips 1.10.1, already test mhomed
and advertised_address.
I am also using the dispatcher config:
modparam("dispatcher", "ds_probing_sock", "udp:192.168.0.10:5060
<http://192.168.0.10:5060>")
But doesn't do any difference.
Any ideas please?
Thanks,
Wilmar
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
