Acme Packet (MOSC)

MOSC Banner

Session Agent status determination by Pinging (SIP OPTIONS)

edited May 21, 2019 3:01AM in Acme Packet (MOSC) 31 commentsAnswered ✓


Hi everyone,

I'm posting this here as i've seen different customers in the field trying to understand exactly how do we monitor the availabiliy of a SA via SIP OPTIONS, and how it bounces between the different possible status:

I: In-Service
O: Out-of-Service
Disabled
C: Constraints exceeded
S: Transitioning from “O” to “I”.


This information is extracted from Acme Packet - 520-0013-06 - TECHNOTE-Theory of the Session-agent, available for download in the support portal.

 

A response to OPTIONS or INFO lets the SD‟s SIP proxy know that the agent's SIP stack is functioning – with the assumption being that it is therefore capable of receiving customer traffic. So, the SD keeps the session-agent IN-Service on getting a response.

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