| Debugging SMS delivery |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 12, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Warren Faleiro New member Username: Warrenon Post Number: 1 Registered: 03-2004 |
My company makes an MMSC. I am using your NowSMS in a test environment on a Windows box that has a Nokia 5100 handset connected via DKU-5 cable as a GSM modem. For delivery of mm1 notification, our MMSC sends PAP to a Jataayu PPG that in turn, sends the notification to the NowSMS. I am having trouble with the delivery of the notification from the SMSC to the handset in some scenarios. In some cases it works and in others it does not work. In both cases, the PAP message is translated to two SMS messages that are SAR'd. In both cases the SMSOUT log for the NowSMS inidicates that two SAR messages are sent to the handset. The same server and handset is used in both scenarios. How can I debug this delivery issue and what are the parts of the PAP message that can affect this delivery? Warren | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2284 Registered: 10-2002 |
Hi Warren, The Nokia 5100 is one of the devices that requires the use of the Nokia PC Suite software, isn't it? That software emulates a GSM modem interface, and in general, I recommend trying to avoid it. Instead, if you're going to use a phone as a modem, use a GSM phone that has inbuilt GSM modem capabilities, so that it doesn't require an emulated driver like this. Most newer Nokia phones (both Series 40 and Series 60 devices) have this capability ... also the SonyEricsson T68/T68i/T610/T630 are good choices. (Do note that the Nokia Series 60 phones can send only, not receive.) I'm not sure that the Nokia PC Suite is a problem when sending long messages, but it is a cause for concern. Here's what I'd recommend ... First, let's try to take some of the different variables out of the equation. Use the NowSMS web interface to send a WAP Push message, and include a large amount of text in the push message (over 140 characters, so that the message will have to be split over multiple messages). Does this work reliably, or does it also have problems? You could also try downloading the NowSMS v5.50 beta (details at http://www.nowsms.com/newsletter). It supports PAP directly, so your MMSC could send the PAP request directly to NowSMS. That would cut out another potential variable. Beyond that, I'd suggest trying to look for any pattern in what messages work, and which do not. Correlate those results with our SMSOUT-yyyymmdd.LOG file, and if you're not seeing any patterns to what works and what doesn't, I can take a look. -bn | |||
