My Oracle Support Banner

SIP NOTIFY Message Contains Wrong Value in To: and From: Fields Which Causes a Break in the Call Flow (Doc ID 1560316.1)

Last updated on AUGUST 02, 2018

Applies to:

Oracle Communications Service Broker - Version 6.0.0.1.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Communication Service Controller/Broker (OCSC/OCSB) sends a SIP_SUBSCRIBE message to a SIP Application (OCCAS / Oracle Communications Converged Application Server).

In turn OCSC receives a SIP_202 message (status code = 202, which means Accepted) .

Later, OCSC sends a SIP_NOTIFY message to OCCAS with "To:" and "From:" fields which are exactly same as in the SIP_SUBCRIBE message.

SIP_SUBSCRIBE
To: sip:012345@msc
From: <sip:10.20.30.40:5060>;tag=db42e04e

SIP_NOTIFY
To: <sip:012345@msc>;tag=3db87779
From: <sip:10.20.30.40:5060>;tag=db42e04e

OCCAS does not receive the SIP_NOTIFY message, but OCCAS sends back a SIP_481 message (status code = 481, which means Call/Transaction Does Not Exist).

 

Cause

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
Symptoms
Cause
Solution
References


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