Acme Packet (MOSC)

MOSC Banner

REFER with Replaces

Hi All

We picked-up an issue with our ACMEs when we receive REFER messages using Replaces.

Starting with the call flow (2 Calls made via ACME):
Party A Calls Party B

Flow: Party A —> Peer Realm —> ACME —> Core Realm —> Soft Switch —> Routes to Party B

Party A Calls Party C

Flow: Party A —> Peer Realm —> ACME —> Core Realm —> Soft Switch —> Routes to Party C

Both these calls successfully establish. Party A then requests to merge these two calls using REFER with Replaces on Call - Party A to B.
The ACMEs are configured as a B2BUA and creates a unique Call-ID on the internal leg (ACME to Soft Switch)

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