Hello,
you can tune the transaction timeouts with tm configuration values and also tm functions to your needs. But I agree that at a server failure in ringing state it takes usually longer
to go to the failure_route.
For that reasons you use dispatcher probing, it will detect the failure and then route the next calls to a working server. The calls in ringing state will of course not handled by that
and probably fail.
Cheers,
Henning
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com
From: Devang Dhandhalya <devang.dhandhalya@ecosmob.com>
Sent: Wednesday, January 4, 2023 10:07 AM
To: Henning Westerholt <hw@gilawa.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] Recover call in ringing state
Hello Henning
Thanks for Response, When Remote Server goes down in Ringing Call state we will not get any Negative Response from remote server and we should not wait for transaction timeout because its to 1-2 min
so in this case there is anything that we found Remote server is down and we can check INVITE transaction failover and we generate INVITE using that same transaction.
Using the Dispatcher event route we will get if any of the remote servers are down but how we can get a call transaction is failed and can generate a call.
Regards
Devang Dhandhalya
On Tue, Dec 6, 2022 at 3:12 PM Henning Westerholt <hw@gilawa.com> wrote:
Hello,
you can do this by using a failure_route. There is one example for voicemail I think in the Kamailio default configuration.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
From: sr-users <sr-users-bounces@lists.kamailio.org> On Behalf Of Devang Dhandhalya
Sent: Wednesday, November 30, 2022 7:16 PM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: [SR-Users] Recover call in ringing state
Hello All
I have below setup :
SBC -> kamailio -> Media server(remote) -> web-client
Call comes from sbc to kamilio and it relays to Remote server to end user, In Ringing state if remote server goes down then in kamailio there is any way to Recover that ringing call like we can generate new invite for other Remote server which is active state, for relaying call i am using dispatcher module..
I tried with tm.cancel RPC command but it works only if the remote server is running , when I crash the remote server at that time tm.cancel is not generating cancel to remote server.
Please suggest if there is any other way to generate INVITE.
Regards
Devang Dhandhalya
Disclaimer
In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded.
Confidentiality
This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error.
Caution for viruses, malware etc.
This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.
--
Regards,
Devang Dhandhalya
Disclaimer
In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are
solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis
of any of the information contained in this email is hereby excluded.
Confidentiality
This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information
that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error.
Caution for viruses, malware etc.
This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware,
interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be
liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.