Hi：
I make a mistake. I use tcp with async that fix problem.
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/not-trigger-on-failure-route-0-when-use-mi-interface-tp7596480p7596574.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.co
Hello,
Not sure I understand what is taking more than 10 minutes ?
Why are you trying to change the maximum number of milliseconds of
OpenSIPS trying to retransmit a message ?
Best Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 16.04.2015 07:04, chow wrote:
Hi：
Hi：
It work for me with use $du that redirect request to Main route.
have another problem about retransmission
eg：
I followed the order sent 50 messages. 40 of message will be fast
store into db.
the remaining message (40-50) store into db that Spend more than 10
Hello,
Currently there is no failure_route support for SIP messages generated
internally by OpenSIPS.
What you can do is to loop the SIP Message back to OpenSIPS from the
local_route , and that way you will get the looped MESSAGE in your main
route , where you can arm a failure route.
Shor
in my understanding: mi interface will first enter local_route,
in local route , will generate SIP Message, this SIP Message will route
to main REQUEST_ROUTE.
in REQUEST_ROUTE, I have some code part like this:
t_on_failure("sip_message");
if this transaction have any er
Hi:
I use t_uac_dlg send message.
the destination user in my location table. actually，this user is
offline and not send unregister。
then, I sent lots of message to this user, only previous message can
trigger on_failure_route[].
some log like this:
Apr 14 14
