Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.1.0 and later
Information in this document applies to any platform.
When MM is configured to relay a Delivery Receipt (DR) (e.g. between an ASP and a SMSC), it turns out that MM is actually creating a new DR.
MM not only changes some parameters like Calling/Called parties but also the payload of the incoming DR.
A delivery receipt relating to a a message which had been previously submitted with the submit_sm operation and the ESME had requested a delivery receipt via the registered_delivery parameter. The delivery receipt data relating to the original short message will be included in the short_message field of the deliver_sm.
As an example, here is the original payload of an incoming DR:
Here is the modified payload by MM:
"id:162828xxx sub:000 dlvrd:000 submit date:1111161510 done date:1111161510 stat:DELIVRD err:000 Text:Dear Friend, Hello"
The ESME (e.g. ASP) might not recognize the DR sent by MM, which leads to thinking the message was not delivered.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms