Diameter SMS and MMS AVP Mapping of MSISDN to BRM
(Doc ID 1599747.1)
Last updated on SEPTEMBER 29, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterOracle Communications Online Mediation Controller - Version 6.1.0 to 6.1.0 [Release 6.1]
Information in this document applies to any platform.
Symptoms
The current mapping between Diameter and PCP BRM of the calling and called number fields (MSISDN) is done through the below fields:
Calling-Station-Id
Service-Information->IMS-Information->Calling-Party-Address
Called-Station-Id
Service-Information->IMS-Information->Called-Party-Address
Service-Information->IMS-Information->Calling-Party-Address
Called-Station-Id
Service-Information->IMS-Information->Called-Party-Address
However, the Calling-Station-Id and Called-Station-Id may contain the APN instead of the MSISDN and the standard offers additional AVPs for mapping the MSISDN in SMS and MMS.
Those AVPs are:
For SMS:
SMS-Information(2000)/Recipient-Info(2026)/Recipient-Address(886) AVP for sending the recipient of the SMS.
SMS-Information(2000)/Originator-Received-Address(2027) AVP for sending the originator of the SMS.
SMS-Information(2000)/Originator-Received-Address(2027) AVP for sending the originator of the SMS.
For MMSC:
MMS-Information(877)/Recipient-Address(1201) for sending the recipient of the MMS
MMS-Information(877)/Originator-Address(886) for sending the originator of the MMS.
MMS-Information(877)/Originator-Address(886) for sending the originator of the MMS.
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 |
| Goal |
| References |