Acme Packet (MOSC)

MOSC Banner

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

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center