Reply to self: Found the problem after reading this post:
http://lists.digium.com/pipermail/asterisk-dev/2010-March/042735.html
You need to set timert1 in the peer config to *something*, otherwise it
will ignore the timerb setting. Bug? It now looks like this and works fine:
[peer01]
host=1.2.3.4
type=peer
context=nowhere
disallow=all
allow=alaw
allow=ulaw
canreinvite=no
dtmfmode=rfc2833
timert1=500
timerb=2000
timert1=500 is the default anyway, according to sip.conf comments...
Regards
Markus
Am 07.01.2019 um 17:23 schrieb Markus:
Dear list,
Asterisk 11.25.0 user here. I'm trying to set up failing over to a
second SIP peer if the first SIP peer doesn't answer on our SIP INVITE
within 2 seconds.
In sip.conf I set timerb=2000 for this peer, but it doesn't seem to have
any effect. The timeout is 6.5 seconds instead, which is in line with
this description from sip.conf:
"timerb: Call setup timer. If a provisional response is not received in
this amount of time, the call will autocongest. Defaults to 64*timert1
(Which is 100 ms = rougly 6.5 seconds)"
Maybe I cannot set timerb on a peer-basis? Here's my peer config:
[peer01]
host=1.2.3.4
type=peer
context=nowhere
disallow=all
allow=alaw
allow=ulaw
canreinvite=no
dtmfmode=rfc2833
timerb=2000
Thank you!
Markus
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
