27 Oct
2017
27 Oct
'17
5:44 p.m.
Hello.
Have a problem with some uplinks. They sometimes respond "100 Trying" on
initial INVITE and... that's all. A caller waits for about 30 seconds
and cancel a call deciding there's something wrong with our network. How
to use failure route when 180/183 answers don't arrive in 5 or 10
seconds after INVITE?
27 Oct
27 Oct
5:53 p.m.
On Fri, Oct 27, 2017 at 09:44:55AM +0300, Yu Boot wrote:
Have a problem with some uplinks. They sometimes
respond "100 Trying" on
initial INVITE and... that's all. A caller waits for about 30 seconds and
cancel a call deciding there's something wrong with our network. How to use
failure route when 180/183 answers don't arrive in 5 or 10 seconds after
INVITE?
Use t_set_fr() to set a timeout of 5 sec or whatever, then reset it
(e.g. t_reset_fr()) to a more reasonable default in an onreply_route
when a 18x reply is received.
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
6:02 p.m.
Thanks!
27.10.2017 9:53, Alex Balashov пишет:
On Fri, Oct 27, 2017 at 09:44:55AM +0300, Yu Boot
wrote:
Have a problem with some uplinks. They sometimes
respond "100 Trying" on
initial INVITE and... that's all. A caller waits for about 30 seconds and
cancel a call deciding there's something wrong with our network. How to use
failure route when 180/183 answers don't arrive in 5 or 10 seconds after
INVITE?
Use t_set_fr() to set a timeout of 5 sec or whatever, then reset it
(e.g. t_reset_fr()) to a more reasonable default in an onreply_route
when a 18x reply is received.
2642
days inactive
2642
days old
2 comments
2 participants
participants (2)
-
Alex Balashov -
Yu Boot