SIP Status Code 486 (Busy Here) Mapped to Route Select Failure Release Cause
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 2.2.0 to 4.4.1 [Release 2.2 to 4.4]
Information in this document applies to any platform.
When SCA receives a SIP 486 (Busy Here) Response Code, it is being mapped to a Route Select Failure Release Cause instead of a User Busy Release Cause.
This can break the service logic because a Branch on Event Report Request BCSM Code node will exit through the wrong exit branch.
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 hundreds of Community platforms