| SI by PAP? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi, I'm testing the 60 day trial of NowSMS 5.50. I have been trying to send a Service Indication via a Nokia 6220 connected by DKU-5 by means of posting a PAP-document to NowSMS. As a result, I get a push-response with the response-result code 1001, and the log-entries state, that the delivery to the given telephone-number would have been ok. However, my cellphone does not receive the SI nor does the notification report ever reach the server configured for the purpose (may ssl using self-generated cert be interfering?). Using NowSMS web interface, I am able to post SIs successfully and my cellphone does receive them properly. There are some differences when comparing PAP vs gui delivery: a)NowSMS webgui's delivery logentries contain the string "WAPPush" whereas the other says "SendMMS" and b)the pap-delivery's sms-DATE.log-file's data-information seems to be truncated (8 chars), since the NowSMS-gui-generated SI produces a notably longer data-attribute. Any clues about the fate of the SIs would be appreciated.. thanks.. -Jani | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3737 Registered: 10-2002 |
Hi Jani, I'd suggest you update to v5.51. Not that I am aware of any problems in v5.50 in this area, but in order to troubleshoot this, that would be my first suggestion. Next, I'd need to see the PAP document that you are submitting. That way I can try it on my end ... see exactly what you are submitting, and determine what is going wrong. -bn | |||
| Anonymous |
Thanks for the quick answer Bryce, I will submit the PAP document shortly, but first let me give some feedback on another matter. I re-wrote the code to submit the service indication via the URL interface. So far so good as long as everything is up and running. However, if there was a malfunction between SMSC and modem, specifically - the phone was temporarily removed and re-attached without restarting the service, the PPG-URL-interface will still respond with a HTTP 200 OK and state that the message was submitted successfully. That can be somewhat confusing - especially if there is no mechanism for delivery notifications. I would much prefer if the service status would be reported, for example, by standard HTTP response codes, I hope it is feasible, since it could prove a valuable feature indeed. I would suggest something like this: - Instantly delivered: 200 OK (eg 3000 ms timeout/configurable) - Backlog: 202 Accepted - SMSC service malfunction: 500 internal server error | 503 Service Unavailable I will regenerate and submit the PAP document shortly. Thanks again -Jani | |||
| Anonymous |
--multipart-boundary Content-Type: application/xml <?xml.version="1.0"?> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN" "http://www.wapforum.org/DTD/pap_1.0.dtd"> <pap product-name="My Application"> <push-message push-id="abc-1100257612683" source-reference="MyApp" ppg-notify-requested-to="http://localhost:8443/notify" progress-notes-requested="true"> <address address-value="WAPPUSH=+358401234567/TYPE=PLMN@null" /> </push-message> </pap> --multipart-boundary Content-Type: text/vnd.wap.si <?xml.version="1.0"?> <!DOCTYPE si PUBLIC "-//WAPFORUM//DTD.SI.1.0//EN" "http://www.wapforum.org/DTD/si.dtd"> <si> <indication href="http://www.example.com/MyApp/MyApp.jad"> Check out My Application </indication> </si> --multipart-boundary-- | |||
