Why does sipd give up trying another next-hops if the first is OOS?
Hello,
Do you know, how to force SBC to apply second and third alternative routes within LRT if first route fails due to SA out-of-service state?
<route format="weighted">
<user type="string">342591200</user>
<next prio="4" weight="10" type="regex">!(^.*$)!sip:\1@1.2.3.107!</next>
<next prio="2" weight="10" type="regex">!(^.*$)!sip:\1@10.20.30.51!</next>
<next prio="3" weight="10" type="regex">!(^.*$)!sip:\1@40.50.60.100!</next>
</route>
Theoretically, the second route 10.20.30.51 shall be applied to INVITE, but in log.sipd I see this behavior:
Mar 27 16:48:04.814 [SESSION] {multi2} (3) checkAvailability:1.2.3.107 status='Out Of Service'0
Mar 27 16:48:04.814 [SIP] {multi2} (3) INVITE 473 B<C-Initial> ctx-forward-req: 95.217.148.246 is unavailable Non-PRIO
Mar 27 16:48:04.814 [TRANS] {multi2} (3) INVITE 473 B <C-Initial:503> created internal response; stop trying next hops