SBC-480 Error Code Handling In IN-SLC For Volte MT Calls
(Doc ID 2965651.1)
Last updated on AUGUST 07, 2023
Applies to:Oracle Communications Network Charging and Control - Version 6.0.1 and later
Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On : 6.0.1 version, Adv Call Svcs
Given the scenario of VoLTE (Voice over LTE - Long Term Evolution) call, when the called number is located on 2G/3G network so he will not be able to take the call, hence the call is forwarded.
In this scenario, "480 Temporarily not available error" is sent by SBC (Session Border Controller) to OC-3C (Oracle Communications - Convergent Charging Controller), which is expected behavior.
Currently whenever OC-3C>SCA (Session Control Agent) received Error Code 480 (Temporarily not Available) from SBC end, call getting terminated.
As per business requirement, when this error code is received by OC-3C SCA, a SRI_Req (Send Routing Information Request) should be sent to HSS (Home Subscriber Server), for continuation of the call.
Customer tried to implement logic in control plan at SLC (Service Logic Controller) end for handling the error code 480. Customer changed control plan as following: it was observed that when 480 error code is received, ATTP-1335 (Attempt Terminate to Pending TN) feature node was exiting on specific error branch (Route-Select Failure). That exit was connected to a END node. As per the change implemented trying to obtain desired behavior, end node connected to that specific error branch was deleted and that exit was connected to node STML-6 (Store My Location).
After implementing the new flow, getting the error code 500 (Internal Server error) from SLC side.
How to implement in order to obtain desired behavior for this scenario?
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