My Oracle Support Banner

SIP MADDR Parameter Population When Public Listen Address Is Not Multicast (Doc ID 1366140.1)

Last updated on AUGUST 14, 2019

Applies to:

Oracle Communications Converged Application Server - Version 5.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 06-Jan-2014


When engines are behind load balancer (LB) and public network channel is configured for public listen address as LB IP, OCCAS populates SIP MADDR parameter with LB IP. This is happening for INVITE, BYE, NOTIFY, CANCEL and REFER requests. This creates an issue for external environment such as IMS that is receiving the requests from OCCAS. In that instance IMS reports MADDR contains multicast address and SIP doesn't support multicast. According to RFC 3261 Section 18:

A client that sends a request to a multicast address MUST add the "maddr" parameter to its Via header field value containing the destination multicast address, and for IPv4, SHOULD add the "ttl" parameter with a value of 1. Usage of IPv6 multicast is not defined in this specification, and will be a subject of future standardization when the need arises.

However, OCCAS is adding MADDR even when the public listen address is not a multicast address.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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