My Oracle Support Banner

ECAS Adds Incorrect Reason Header In BYEs When DE Releasing Call (Doc ID 2593389.1)

Last updated on AUGUST 24, 2020

Applies to:

Oracle Communications Evolved Communications Application Server - Version 7.1.0 to 7.1.0 [Release 7.1.0]
Information in this document applies to any platform.


On : 7.1.0 version, Installation and Initial Setup

When destination endpoint (DE) releases a call, it sends a SIP BYE message.
This message arrives to ECAS (Evolved Communications Application Server) and ECAS sends it towards initiating endpoint (IE).

Even this is a normal release, ECAS is adding the following header to BYE towards IE.


This is incorrect because it's a normal release initiated by the endpoint.
This is impacting iOS devices - display an "error" to calling when this release is received due to this header (making user think something is wrong when it's not the case).

Expected behavior is:

- ECAS shall be propagating headers in BYE to IE as they come in BYE to DE (except the ones normally changed due to B2B behavior, i.e. Contact, To/From tags etc).

- That is, no error Reason shall be added. If a Reason comes from the DE, shall be kept as it is (as any other header coming from the DE except the ones B2B related).




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

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

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