Skip to content
This repository was archived by the owner on Sep 18, 2021. It is now read-only.
This repository was archived by the owner on Sep 18, 2021. It is now read-only.

Parsing Delivery Receipt Issue #105

Open

Description

@gruntday

Hello,

Need help regarding below error

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

DeliveryReceipt.parseShortMessage(dlrStr, DateTimeZone.UTC);

Appreciate your support

Activity

  1. krasa commented on Jun 10, 2015

    @krasa
    Contributor

    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).

  2. jjlauer commented on Jun 10, 2015

    @jjlauer
    Contributor

    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:

    Your new SMSC sends you wrong DeliveryReceipt, either force them to fix
    it, or work around it.

    —
    Reply to this email directly or view it on GitHub
    #105 (comment)
    .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions