Acme Packet (MOSC)

MOSC Banner

Route entry wrongly removed

edited Aug 29, 2016 9:58AM in Acme Packet (MOSC) 8 commentsAnswered

Hello everybody,

I have an issue with a specific scenario where the call comes in/out several times different sip-interfaces of the sbc before being delivered.

In one of these steps, I have an INVITE incoming with a Route entry (only 1 entry) having the host part an FQDN which matches a SA. From the log.sipd it results that this Route entry does match an SA but not a sip-interface (so not a local address), as a result the sbc continues to process the routing until it finds out that it has to route based on tgrp / context present in the R-Uri, which it eventually does.

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