Yes, I have the same issue with 1.4.2 version.
On 28. 06. 2010 19:08, Geoffrey Mina wrote:
I am having an issue with 1.5.4 where force_send_socket()
isn't behaving as I would expect.
I have an LCR scenario where depending on which gateway I am sending
to, I send from a different socket.
It appears that calling force_send_socket from failure_route has no
affect on the routing. In my initial route block I call
force_send_socket(X.X.X.180:5060). In my failure_route I am calling
force_send_socket(X.X.X.179:5060), yet after calling the subsequent
time, my sip trace and tcpdump are clearly showing kamailio is still
sending from X.X.X.180:5060.
I have added a lot of debug lines, so I am 100% sure the second call to
force_send_socket is happening.
Am I misusing this module in some way?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Ernest Mavrel
technical support
Novatel d.o.o.
informacijske tehnologije
Mariborska 88, SI - 3000 Celje
tel: +386 (0)82 800 823
fax: +386 (0)82 800 821
mobile: +386 (0)51 436 453
e-mail: ernest.mav...@novatel.si
|
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
