Acme Packet (MOSC)

MOSC Banner

Why SBC is adding an extra Route header?

edited Oct 7, 2013 6:25PM in Acme Packet (MOSC) 4 commentsAnswered ✓

Hi,

 

We have different type of IP-PBX'es configured on the access side of the SBC. We noticed that ACME is adding an extra route header while sending the INVITE to the Core.

 

As we already add a Route: header via an HMR from access towards the Core, this second Route: header is causing call failure in out IMS Core.

 

See below the sip message from SBC to Core.

 

INVITE sip:0177654036@ims.imscore2.net:5060 SIP/2.0
Via: SIP/2.0/UDP 10.45.212.164:5060;branch=z9hG4bKeqglri302o40ke41p7o0.1
From: <sip:+31312206101@ims.imscore2.net;user=phone>;tag=SDifhr501-1068930~dcc7993e-8b63-4e01-b7e9-7fd5c013d293-23701390

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