Use getRefNo() on the status report message.

But, RefNo is not enough. Ref Numbers are numbers going from 0 -> 255 and
back to 0.
Use another key as well, for example use Recipient + RefNO in order to
minimize collisions.

On 4 March 2013 11:55, font via SMSLib Discussion Group <
smslib+noreply-apn2wqfjcgb_yqc6yqv8mowmvodwz07fuhcbkzrey11cdp...@googlegroups.com
> wrote:

> Hi all,
>
> I'm having a problem when I process the StatusReportMessage.
> I recive the messages correctly and when I print them, the information is
> fine, but the problem comes when I use their methods to get the info.
> I need the RefNo to udpate the status of the message in the db. Maybe
> there is other solution to determine if a message has been sent correctly.
> Anyway, here's a example:
>
>
> ===============================================================================
> << OutboundMessage >>
>
> -------------------------------------------------------------------------------
>  Gateway Id: modem.com1
>  Message Id: 0
>  Message UUID: 9d8a19e0-e893-48b1-9987-e032e2d49c4c
>  Encoding: 7-bit
>  Date: Mon Mar 04 10:34:27 CET 2013
>  SMSC Ref No: 183
>  Recipient: 665547442
>  Dispatch Date: Mon Mar 04 10:34:30 CET 2013
>  Message Status: SENT
>  Failure Cause: NO_ERROR
>  Validity Period (Hours): -1
>  Status Report: true
>  Source / Destination Ports: -1 / -1
>  Flash SMS: false
>  Text: Hello, how are you?
>  PDU data: C8329BFD6681D0EF3B282C2F83F2EFFA0F
>  Scheduled Delivery: null
>
> ===============================================================================
>
>
>
> ===============================================================================
> << StatusReportMessage >>
>
> -------------------------------------------------------------------------------
>  Gateway Id: modem.com1
>  Message UUID: b4516268-c300-41bd-ace6-8618a11c4915
>  Encoding: 7-bit
>  Date: null
>  Dispatched via SMSC: null
>  Text: 00 - Succesful Delivery.
>  PDU data: null
>  Originator:
>  Original Recipient: 34665547442
>  Delivery Status: DELIVERED
>  SMSC Ref No: 183
>  Sent Date: Mon Mar 04 10:34:30 CET 2013
>  Delivered Date: Mon Mar 04 10:34:32 CET 2013
>  Memory Index: 0
>  Multi-part Memory Index:
>  Memory Location: SM
>  Source / Destination Ports: -1 / -1
>
> ===============================================================================
>
> msg.getDate() -> null
> msg.getDCSMessageClass() -> null
> msg.getDstPort() -> -1
> msg.getEncoding()ENC7BIT
> msg.getEndsWithMultiChar() -> false
> msg.getGatewayId() -> modem.com1
> msg.getId() ->
> msg.getMessageId() -> 1
> msg.getMemIndex() -> 0
> msg.getMemLocation() -> SM
> msg.getMpMaxNo() -> 0
> msg.getMpMemIndex() ->
> msg.getMpRefNo() -> 0
> msg.getMpSeqNo() -> 0
> msg.getOriginator() ->
> msg.getPduUserData() -> null
> msg.getPduUserDataHeader() -> null
> msg.getSmscNumber() -> null
> msg.getSrcPort() -> -1
> msg.getText() -> 00 - Succesful Delivery.
> msg.getType() -> STATUSREPORT
> msg.getUuid() -> b4516268-c300-41bd-ace6-8618a11c4915
> -----------------------------------------------
>
> I'm using a Huawei E220.
> I'm also getting  a "modem.com1: Callback indications were *not* set
> succesfully!" that don't know where does it come.
> Any help would be very appreciated.
>
> Thanks in advance.
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "SMSLib Discussion Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msg/smslib/-/-zxz2PxZXD0J.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"SMSLib Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


  • [smslib] getMpRefN... font via SMSLib Discussion Group
    • Re: [smslib] ... SMSLib Discussion Group on behalf of Thanasis Delenikas

Reply via email to