Acme Packet (MOSC)

MOSC Banner

SBC fails to add a Service-route

Hello, colleagues.


Does anybody know what can prevent SBC to set the Service-Route, which was recorded in the reg-cache, when it forwards a request from registered endpoint? What is the action called: hardLockOnSipUser ?


Oct 10 12:19:35.197 [SIPREG] {srvcc} (3)  do not add service-route:

Oct 10 12:19:35.197 [SIPREG] {srvcc} (3)    <sip:originating@scscf.silj0.ims.mnc0XY.mcc2XY.3gppnetwork.org:5090;reg-id=BSA1696932354645907;lskpmc=SBSA;lr;ms_rest_id=SBS65252398>

Oct 10 12:19:35.197 [SIPREG] {srvcc} (3) SipProxy::hardLockOnSipUser Acquiring the SipUser lock sip:2XYXY0000495632@ims.mnc0XY.mcc2XY.3gppnetwork.org

Oct 10 12:19:35.197 [SIPREG] {srvcc} (3) set_from_user=sip:2XYXY0000495632@10.56.8.225:8400 VoLTE-PGW1



Thanks and regards,

Daureen

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