Hi Leon,
The idea is nice - it is backward compatible, allows per destination
pinging and you can also have a default socket (if none in the
destination definition).
Regards,
Bogdan
On 11/24/2011 07:01 PM, Leon de Rooij wrote:
Hello Bogdan,
If you can wait a bit, I'm trying to implement it :-) will let you know when
I'm done, am planning on spending tonight on it..
what do you think of this syntax:
1 udp:1.0.0.2:5060/sip:1.0.0.4:5060
where the part before the slash (including the slash itself) is optional and
sets the socket that will be used (if not set, fallback to current behaviour)..
also nice to have this variable in an avp like is made available with for
example attrs..
regards,
Leon
On Nov 24, 2011, at 5:00 PM, Bogdan-Andrei Iancu wrote:
Hi Leon,
for option 1) , if you come up with a good idea on how to provision, I can
implement it, as it seams an interesting feature.
Regards,
Bogdan
On 11/24/2011 03:17 PM, Leon de Rooij wrote:
Hello Bogdan,
Thanks for your quick reply ! I will try to find a way around it then.
Regards,
Leon
On Nov 24, 2011, at 2:02 PM, Bogdan-Andrei Iancu wrote:
Hi Leon,
Unfortunately something like that is not possible with the current code:
1) dispatcher module has a single "send_socket" for all sets/destinations
2) local route does not allow you to do routing changes (outbound socket is
considered routing info), so this is why it has no effect in your case.
Options will be:
1) make dispatcher module able to use per-set send socket, but not sure how
something like this should be configured.
2) enhance the capabilities of local route, to allow changing of send
socket, but this is hard one.....
Regards,
Bogdan
On 11/24/2011 11:54 AM, Leon de Rooij wrote:
Hi all,
I'm using dispatcher to probe several sets but I want to be able to send out
the SIP OPTIONS packets from a different socket per set that I'm probing, for
example:
listen=udp:1.0.0.2:5060
listen=udp:1.0.0.3:5060
and in dispatcher.list
1 sip:1.0.0.4:5060
2 sip:1.0.0.5:5060
Now I'd like to send probes to 1.0.0.4 originating from 1.0.0.2, but I want
probes to 1.0.0.5 to originate from 1.0.0.3.
Is that at all possible ?
I tried not setting the ds_probing_sock and created a local_route to try and
force the send socket per destination in the RURI:
local_route {
if (is_method("OPTIONS")) {
if ($rd=="1.0.0.4"&& $rp=="5060") {
append_hf("X-Probe: (SET 1) You alive ?\r\n");
force_send_socket(udp:1.0.0.2:5060);
}
if ($rd=="1.0.0.5"&& $rp=="5060") {
append_hf("X-Probe: (SET 2) You alive ?\r\n");
force_send_socket(udp:1.0.0.3:5060);
}
}
}
But no luck.. I do see the header appended, but the originating IP is still the
same for all SIP OPTIONS...
Anyone tried this before ?
Thanks,
Leon
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"
--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"
--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
