| SMPP Message Id length |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 20, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| Chris Frequent Contributor Username: Chrisc Post Number: 65 Registered: 12-2008 |
Hi guys We have recently connected to a new upstream SMSC but it appears that their message ids are excruciatingly long which makes us wonder if NowSMS will be able to process it. To explain what we're seeing at our end, when an MT message is sent, we receive this Id in the SMSOUT file, which comes from the submit_sm request: 447987654321-0641110919371483 The trouble is, when the deliver_sm request is processed and NowSMS forwards the receipt via 2-way HTTP command, we see this: Text="Message id:447987654321-0641110919371483 sub:000 dlvrd:000 submit date:1211091037 done date:121109104205 stat:DELIVRD err:000 text:Test Message 1";SMSCRouteName=SomeMTRouteName Usually we would expect the NowSMS generated message Id which we use to match the receipts back to the messages. Because this message Id is something we don't have, it cannot be matched so our customers have no idea what's happened to these messages. We think it could be because of the lenght, however we'd like to hear from you guys what you think of this particular scenario. Hope to hear from you soon. Regards Chris | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4195 Registered: 08-2008 |
Hi Chris, That length should be ok. I can't find any more specific references, but I did find the following thread: http://support.nowsms.com/discus/messages/12/59729.html In that thread I did some research to find that at one point there was a 50 character limit on our tracking, but that it was expanded to 150. That said, I'm not sure how often in practice we see such lengthy IDs, so there may be other length related issues introduced since that post. I'd be curious to see raw SMPP data. I'm wondering if the receipt message ID is encoded in the TLV correctly, and maybe there is a limit to how many characters are parsed from the text of the receipt if we don't find the TLV. Can you capture the raw data, either in an SMPPDEBUG.LOG or with a Wireshark trace? I need both the submit and the deliver that comes back with the receipt. It would also help to see the exact SMSOUT and SMSIN log records to be able to spot other possible inconsistencies. Feel free to forward that information to nowsms@nowsms.com if it contains too much detail to post here. Just put Attention: Des in the subject line of the message, and please post a follow-up here to remind me to look for it if necessary. -- Des NowSMS Support | |||
