Acme Packet (MOSC)

MOSC Banner

User-to-User field is 22 hexadecimal character instead of 16

edited May 17, 2015 11:00PM in Acme Packet (MOSC) 2 commentsAnswered ✓

Hello,

I currently have a setup where I have a Cisco UCM with a SIP trunk to an Oracle SBC which has a local policy that passes the call to an Avaya Session Manager. The calls pass through correctly and work well. The only problem is our recording solution is grabbing the user-to-user field in the SIP message and it is 22 hexadecimal digits so Avaya doesn't use it and creates its own ucid. My session agent is setup with the spl options provided as an example in the Enterprise Session Director Configuration Guide "UCID-App-ID=0023,replace-ucid,convert-to=Avaya" These are getting applied because the

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