We have an issue where some of our trunks accept the call but then provide no progress after the initial SIP/100.
Is there a setting to tell Yeti to move the call to another trunk if no responce reveived after X seconds? ie: 20? 15?
You can set the ringing timeout on the gateway, but be warned you might cut off calls that are legitimately ringing a phone and before it can go to voicemail, if you set too short.
This is one of the more annoying ones to deal with, if you can’t switch to a better upstream provider. One solution is to use the ASR Limit (Answer to Seizure Ratio) on the gateway Gateways — Yeti documentation and make sure ACD&ASR is enabled on the routing plan. Routing Plans — Yeti documentation
This way, if the trunk takes calls (seize) but lots of them are not being answered Yeti will stop routing them calls. When viewing a gateway you can see the current ASR stats on the left. It should probably be above about 0.8 but if this gateway isn’t one of your main gateways it might be handling a lot of calls that other gateways have already failed on, dropping the ASR ratio even though its not that gateway’s fault. Something to think about.
Though perhaps someone else will have a better idea.
We ended up trying lower values for SIP Timer B, which appeared to work correctly during our testing.
The default is 8000 but we’re not sure whether that’s 8000 milliseconds or another figure.
Yes. SIP Timer B (transaction timeout) intended exactly to set lower response timeout for gateway to perform faster failover. This option units are milliseconds.