You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 18, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 18, 2021. It is now read-only.
com.cloudhopper.smpp.util.DeliveryReceiptException: Unable to find [sub] field o
r empty value in delivery receipt message
Delivery Receipt Parse Message works well with other SMSCs but when tried to connect to a new SMSC connection we are facing above exception while parsing the DLR String
Your new SMSC sends you wrong DeliveryReceipt, either force them to fix it, or work around it (make your own DeliveryReceipt.parseShortMessage, or just alter the shortMessage you pass into it).
I concur your new SMSC vendor is returning invalid delivery receipts. Ask
them what specifications they are following? The "sub" part for SMPP v3.3
receipts is pretty well defined in the specs.
An alternative (if they support it) is to not parse the text and rely
purely on SMPP 3.4 optional parameters to fetch delivery receipt info. You
can find out if they support optional parameters for that info and then
skip trying to parse the text of the message for it.
Activity
krasa commentedon Jun 10, 2015
Your new SMSC sends you wrong DeliveryReceipt, either force them to fix it, or work around it (make your own DeliveryReceipt.parseShortMessage, or just alter the shortMessage you pass into it).
jjlauer commentedon Jun 10, 2015
I concur your new SMSC vendor is returning invalid delivery receipts. Ask
them what specifications they are following? The "sub" part for SMPP v3.3
receipts is pretty well defined in the specs.
An alternative (if they support it) is to not parse the text and rely
purely on SMPP 3.4 optional parameters to fetch delivery receipt info. You
can find out if they support optional parameters for that info and then
skip trying to parse the text of the message for it.
On Wed, Jun 10, 2015 at 7:06 PM, Vojtěch Krása notifications@github.com
wrote: