Incompatible URI Prefixes Between XMS and SCA
(Doc ID 2089581.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]Information in this document applies to any platform.
Symptoms
In all versions of Oracle Communications Network Charging and Control (NCC) up to and including 5.0.3, there is an incompatibility between the Uniform Resource Identifier (URI) prefix passed between Xtreme Message Services (XMS) and Session Control Agent (SCA).
When XMS uses SCA as a gateway to send a Short Message Service (SMS) over Session Initiation Protocol (SIP), it sets the prefix of the recipient of the SMS to "tel:", for example: "tel:123456". SCA on the other hand expects (and will only accept) prefixes in the format "sip:", for example: "sip:123456".
Changes
Addition of outgoing SMS' over SIP to the deployed NCC
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 |
| Changes |
| Cause |
| Solution |
| References |