SBC not Sending OPTIONS to Configured Session Agents

Asset ID:	1-72-2399366.1
Update Date:	2018-05-21
Keywords:

Solution Type Problem Resolution Sure

Solution 2399366.1 : SBC not Sending OPTIONS to Configured Session Agents

Applies to:

Acme Packet 6300 - Version S-Cz7.2.0 and later
Information in this document applies to any platform.

Symptoms

1. SBC is not sending out OPTIONS to certain SA configured .

2. Below error messages were observed in debug logs -

May 1 01:59:49.714 [SIP] (6) OPTIONS 410 req-send: do_header_manipulation: local=[<IPV6 IP>]:5060; remote=<IPV4 IP>:5066 sts=0
May 1 01:59:49.714 [SIP] (6) OPTIONS 410 no outbound manipulation realm=IPV6Access_Ch1 SA=xx.xx.xx.xx
May 1 01:59:49.714 [SIP] (6) OPTIONS 410 no sip-manip-pattern realm=IPV6Access_Ch1 SA=xx.xx.xx.xx
May 1 01:59:49.714 [SERVICE] (6) UDPPacket::encode() IP address family mismatch!

May 1 01:59:49.714 [SERVICE] (6) 0000: 4f 50 54 49 4f 4e 53 20 73 69 70 3a 36 39 2e 31 OPTIONS sip:69.1
May 1 01:59:49.714 [SERVICE] (6) 0010: 33 34 2e 31 33 31 2e 32 31 31 3a 35 30 36 36 20 34.131.211:5066
May 1 01:59:49.714 [SIP] (6) OPTIONS 410 req-send: error loading request. ret=0
May 1 01:59:49.714 [TRANS] (6) OPTIONS 410 B<C-Initial> CTSend: failed to send request to :0/ status=500
May 1 01:59:49.714 [SIPREG] (6) OPTIONS 410 B<C-Initial> failed to send ping request (SA xx.xx.xx.xx[]); rc=500
May 1 01:59:49.714 [DNS] (6) -DnsResolver[0x5378a0d8] tran=(nil)(0) agent=(nil)(0)

Concerned error messages were -

May 1 01:59:49.714 [SERVICE] (6) UDPPacket::encode() IP address family mismatch!

May 1 01:59:49.714 [SIP] (6) OPTIONS 410 req-send: error loading request. ret=0
May 1 01:59:49.714 [TRANS] (6) OPTIONS 410 B<C-Initial> CTSend: failed to send request to :0/ status=500

Changes

Cause

There Configuration was wrong . They had realm-id as * in all Session agents where SBC was unable to send Options -

session-agent

hostname xx.xx.xx.xx
ip-address xx.xx.xx.xx
port 5066
state enabled
app-protocol SIP
app-type
transport-method UDP
realm-id *

As here realm-id is * , it is taking the egress-realm from global sip-config . Here is the global sip-config configuration -

sip-config

state enabled
operation-mode dialog
dialog-transparency disabled
home-realm-id IPV6Core
egress-realm-id IPV6Access
nat-mode Public
registrar-domain *

As realm-id was mentioned as * in session-agent configuration , SBC was sending Options using global config from sip-config and selecting egress-realm as IPV6Access , which is IPV6 .

The sip-interface associated with the realm is configured with IPV6 address . This is not a supported configuration.

SBC cannot have a SA configured in IPV4 and sip-interface configured in IPV6. It can either work if both are configured for IPV4 or IPV6.

Solution

We changed the config of session-agent and changed realm-id from * to desired realm . This solved the user's issue .

Apart from this we can also make changes in global sip-config by changing ipv6 realm to ipv4 in egress-realm-id .

Attachments

This solution has no attachment