Acme Packet (MOSC)

MOSC Banner

How to prevent SBC from using RURI host of a received REGISTER as a next-hop?

edited Jan 9, 2026 7:48AM in Acme Packet (MOSC) 8 commentsAnswered

Hello!

I am trying to force an SBC to stop using RURI host of a received REGISTER request as a next-hop. The conditions of the case are following:

  • sip-interface in 'Access' realm has sip-ims-feature=enabled, route-to-registrar-disabled.
  • sip-interface in 'Core' realm has route-to-registrar-disabled
  • sip-config has 'home-realm-id' uncofigured
  • local-policy rule is not set

A host sends REGISTER sip:ims.testnet;transport=udp SIP/2.0 to the sip-interface in 'Access' realm. Sipd uses the RURI host 'ims.testnet' to route the request when fails to apply a LocalPolicy.

The only thing that I did not try to disable is 'sip-ims-feature'. I have a strong feeling that described behavior is a kind of a standard for IMS. As I rememeber, local-policy absence made routing unavailable for REGISTER methods. Does anybody know how to force SBC to use local-policy only for the first REGISTER request?

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center