Acme Packet (MOSC)

MOSC Banner

Record-Route header

edited May 13, 2025 9:09PM in Acme Packet (MOSC) 7 commentsAnswered

I am working on integrating SBC for Call setup with other service provider. Call invite is routing from SBC to other service provider whitout Record-Route.
But far end is sending Record-Route header with loose Routing and Require: 100rel header in 183 Session Progress and expecting Record-Route header in PRACK routing back to other service provider.
I have tried adding Record-Route in HMR but it didnt help.

Can SBC provide/Support/add Record-Route header in ACK which is based on Record-Route from 183 session progress from Client side?

SBC Acme Packet OS VM SCZ9.2.0 Patch 4

SIP/2.0 183 Session Progress

Record-Route: <sip:x.x.x.x:xxxx;transport=udp;lr;Ssrpt=7800_116;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=1397;CxtId=3;TgId=1277>

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