Delivery reports problem | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
Author | Message | |||
Darek Chorazewicz Frequent Contributor Username: Daro Post Number: 59 Registered: 03-2004 |
Hi. I'm using samsung c100 and have problems with getting right message id in dr's. Here you have a sample log: 16:29:25:125 [10] SMPPServerReceiveMessageCallback: inbound message: sender=+48692753449, recip=+48696061543, pid=0, dcs=0, msgFlags=2, udh=, msg=albert 16:29:25:265 [5] ThreadProcessModem: Processing 45BF639F.req... 16:29:25:265 [5] ThreadProcessModem: OUT: AT+CMGS=19 16:29:25:375 [5] ThreadProcessModem: IN: > 16:29:25:375 [5] ThreadProcessModem: OUT: 0021020B918496061645F300000661B6B82CA703 16:29:28:953 [5] ThreadProcessModem: +CMGS:137 OK 16:29:39:375 [5] ModemReceiveMessages: +CMGL:2,0,,25 07918406921511F106140B918496061645F3701003619241407010036192914000 OK OK 16:29:39:375 [5] ModemReceiveMessages: Decoding received message index 2 from message storage ME 16:29:39:375 [5] ModemReceiveMessages: 07918406921511F106140B918496061645F3701003619241407010036192914000 16:29:39:375 [5] ModemReceiveMessages: SMSC address len = 7 16:29:39:375 [5] ModemReceiveMessages: SMSC Address = +48602951111 16:29:39:375 [5] ModemReceiveMessages: SMS Message Type = SMS-STATUS-REPORT 16:29:39:375 [5] ModemReceiveMessages: Recipient address len = 11 16:29:39:375 [5] ModemReceiveMessages: Receipient Address = +48696061543 16:29:39:375 [5] ModemReceiveMessages: Message = id:unknown sub:001 dlvrd:001 submit date:0701301629 done date:0701301629 stat:DELIVRD err:000 16:29:39:375 [5] ModemReceiveMessages: AT+CMGD=2 16:29:39:859 [7] ThreadProcessInboundSMS: Processing 45BF63A0.in... 16:29:39:984 [5] ModemReceiveMessages: OK As you see "id:unknown". Why is that? Dariusz | |||
Malcolm - Now Support Moderator Username: Malcolm Post Number: 143 Registered: 12-2006 |
Hi Dariusz, I don't know if it is a modem issue, or an issue specific to your mobile operator's network. However, the problem is that the id within the delivery report does not match the id that was returned when the message was originally submitted. When the message was submitted, the +CMGS response indicates that a message reference id of "137" was assigned. However, the delivery report that comes back contains a message reference id of "20". This reference id is just one of the attributes that we use for matching up receipts with their original message. But we do require an exact match of this value. I'm guessing that it is a modem issue, and that the modem is not returning the message reference id in the "+CGMS" response, and is instead just returning a generic counter value. -- Malcolm Now Wireless Support | |||
Darek Chorazewicz Frequent Contributor Username: Daro Post Number: 60 Registered: 03-2004 |
Hi. I also think it's modem issue bcoz when I use Nokia 6230i all is ok. I have another problem from nokia 6610i. Here you have the logs: 14:45:14:018 [10] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:45:14:018 [10] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2B48696061543&Text=testing222&InfoCharCo unter=&PID=&DCS=&Submit=Submit 14:45:14:018 [10] Debug: 1 recipient entries 14:45:14:018 [10] ThreadProcessConnection: Before message loop 14:45:14:018 [10] ThreadProcessConnection: Before message loop 14:45:14:018 [10] ThreadProcessConnection: Begin message loop 14:45:14:018 [10] ThreadProcessConnection: End message loop 14:45:14:034 [10] ThreadProcessConnection: Request processing complete 14:45:14:112 [10] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:45:14:112 [10] ThreadProcessConnection: Processing request /favicon.ico 14:45:14:112 [11] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:45:14:112 [11] ThreadProcessConnection: Processing request /favicon.ico 14:45:14:128 [11] ThreadProcessConnection: Request processing complete 14:45:14:128 [10] SendData: Error on send data 14:45:14:128 [10] ThreadProcessConnection: Request processing complete 14:45:14:393 [5] ThreadProcessModem: Processing 45C33FF7.req... 14:45:14:393 [5] ThreadProcessModem: OUT: AT+CMGS=22 14:45:14:472 [5] ThreadProcessModem: IN: > 14:45:14:472 [5] ThreadProcessModem: OUT: 0021020B918496061645F300000AF4F29C9E769F653219 14:45:18:972 [5] ThreadProcessModem: +CMGS: 4 OK 14:45:20:643 [5] ModemReceiveMessages: +CMGL: 12,0,,25 07918406921511F106040B918496061645F3000000000000000000000000000020 OK 14:45:20:643 [5] ModemReceiveMessages: Decoding received message index 12 from message storage ME 14:45:20:643 [5] ModemReceiveMessages: 07918406921511F106040B918496061645F3000000000000000000000000000020 14:45:20:643 [5] ModemReceiveMessages: SMSC address len = 7 14:45:20:643 [5] ModemReceiveMessages: SMSC Address = +48602951111 14:45:20:643 [5] ModemReceiveMessages: SMS Message Type = SMS-STATUS-REPORT 14:45:20:643 [5] ModemReceiveMessages: Recipient address len = 11 14:45:20:643 [5] ModemReceiveMessages: Receipient Address = +48696061543 14:45:20:643 [5] ModemReceiveMessages: Message = id:45C33FF7 sub:001 dlvrd:000 submit date:0000000000 done date:0000000000 stat:REJECTD err:020 14:45:20:643 [5] ModemReceiveMessages: AT+CMGD=12 14:45:20:722 [5] ModemReceiveMessages: OK 14:45:21:487 [4] ThreadProcessInboundSMS: Processing 45C33FF8.in... 14:45:29:128 [5] ReceiveModemCommand: Processing +CMT: Message 14:45:29:128 [5] ReceiveModemCommand: +CDS: 25 07918406921511F106040B918496061645F3702020415471407020204154324000 +CPMS: ("ME","SM"),("ME","SM"),("MT") OK 14:45:29:128 [5] ReceiveModemCommand: AT+CNMA 14:45:29:128 [5] ModemReceiveMessages: 07918406921511F106040B918496061645F3702020415471407020204154324000 14:45:29:128 [5] ModemReceiveMessages: SMSC address len = 7 14:45:29:128 [5] ModemReceiveMessages: SMSC Address = +48602951111 14:45:29:128 [5] ModemReceiveMessages: SMS Message Type = SMS-STATUS-REPORT 14:45:29:128 [5] ModemReceiveMessages: Recipient address len = 11 14:45:29:128 [5] ModemReceiveMessages: Receipient Address = +48696061543 14:45:29:128 [5] ModemReceiveMessages: Message = id:45C33FF7 sub:001 dlvrd:001 submit date:0702021445 done date:0702021445 stat:DELIVRD err:000 14:45:29:487 [4] ThreadProcessInboundSMS: Processing 45C33FFA.in... Why 2 delivery reports are returned? Of course message was delviered but why "REJECTED" status was returned first? Dariusz | |||
Malcolm - Now Support Moderator Username: Malcolm Post Number: 159 Registered: 12-2006 |
Hmm ... We're getting a report of a temporary error condition, indicating "network congestion". I guess this indication does not mean a delivery failure. According to the specifications, this status report indicates that there is a temporary delivery failure, but that the SMSC will continue to retry. We will have to make a change to suppress this delivery report from getting translated to SMPP. -- Malcolm Now Wireless Support |