Charging and Control Applications (MOSC)

MOSC Banner

SMS Delivery Receipt using optional field 'user_message_reference'

edited Apr 19, 2010 2:24AM in Charging and Control Applications (MOSC) 2 commentsAnswered
 I am unable to setup sms delivery receipts in OCSG because my SMSC does not return message_id in submit_sm_resp. But deliver_sm contains an id in its message body. Since this id was not reported earlier by SMSC therefore OCSG rejects the delivery receipt. 
For correlation of delivery receipts, can an additional optional parameter 'user_message_reference' be used in submit_sm? Which will be echoed by smsc in deliver_sm's 'user_message_reference' field.

SMPP 3.4 spec mentions about deliver_sm's optional parameter 'user_message_reference'.

"A reference assigned by the originating SME to the message.
In the case that the deliver_sm is carrying an SMSC delivery receipt, an SME delivery acknowledgement or an SME user acknowledgement (as indicated in the esm_class field), 

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center