Acme Packet (MOSC)

MOSC Banner

Understanding the validation process in SD

edited May 21, 2013 1:52PM in Acme Packet (MOSC) 8 commentsAnswered ✓

Can anyone shed some light over the validation that takes place when a UA tries to initiate a new session through the SD?

 

If a UA registers from one port but calls from another, the SD will reject the INVITE with 403 Forbidden.
In this case, log.sipd indicates that the endpoint trying to set up a session, is not registered.
This is done after several attempts to match the incomming messsage to the registration cache entry.

(I have the log.sipd for this, but didn't want to mess up this message!)

 

 

Similar, if a UA is registering with one contact header and attempting to set up sessions with another - the call is rejected. So far, so good, that all makes sense.

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