Acme Packet (MOSC)

MOSC Banner

R-URI host part fulfilled with SA hostname instead of SA IP address when using SAG

edited Sep 9, 2014 7:09PM in Acme Packet (MOSC) 6 commentsAnswered ✓

Hi

 

I use SD4500 CX6.2.

SD has 2 physical interfaces, one in access side, one in core side.

 

on the access side we use :

a session-agent SA-IPBX1 for IPBX1 which belongs to a nested-realm : ACCESS-IPBX1 and to a shared parent realm SIP-ACCESS.

same way for IPBX2 : a session-agent SA-IPBX2 for IPBX2 which belongs to a nested-realm : ACCESS-IPBX2 and a shared parent realm SIP-ACCESS.

 

on the core side we use :

a session-agent SA-MGC for softswitch which belongs to a any realms (realm-id = * ) on the SIP side of the SBC

 

Routing

routing between access and core is done through local-policies.

But INVITE from core softswitch to SBC (so as to reach IPBX) include a ROUTE header  looking like this :

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