Issue Regarding Minimum Timer / Delay for Reroute Feature
Hello,
While testing an RTP broken scenario where the SBC reroutes and resends the INVITE to an alternate destination, I noticed that even though both initial-guard-timer and subsq-guard-timer are set to 3 seconds, the reroute action still takes 15 seconds to trigger.
Looking at the packet capture, it appears the SBC indeed waits for 15 seconds before sending a [RST, ACK] to the disconnected party, and then immediately sends the INVITE to the reroute target.
Does anyone know why this happens?
Thanks,
YyL