Refer Not Converted To Invite
(Doc ID 2406363.1)
Last updated on JUNE 27, 2018
Applies to:Acme Packet 1100 - Version E-Cz7.2.0 and later
Information in this document applies to any platform.
SBC is selecting a wrong session-agent as origin of the traffic.
User created a new session-agent with the following information:
But Refer messages were failing. In the traces we saw that the Refer messages were being forwarded to the next-hop instead of being converted to Invite messages. These calls were originated in a different session-agent with the following configuration:
It seems the SBC identified the wrong SA as origin of the call even though they have different port and transport protocol. After restoring the old configuration (without the new SA) the SBC started to convert the Refer to Invite again.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!