Refer Not Converted To Invite (Doc ID 2406363.1)

Last updated on AUGUST 23, 2023

Applies to:

Symptoms

SBC is selecting a wrong session-agent as origin of the traffic.

User created a new session-agent with the following information:

session-agent
hostname SessionAgent1
ip-address 10.100.10.100
port 5061
transport-method StaticTLS
realm-id realmBosch
refer-call-transfer disabled

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:

session-agent
hostname SessionAgent2
ip-address 10.100.10.100
port 5060
transport-method UDP
realm-id realmBosch
refer-call-transfer enabled

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.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.