| How to send OMA DS server alert notification? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| eagleliang New member Username: Eagleliang Post Number: 1 Registered: 09-2007 |
Hi guys, I'm trying to send a syncML server alert notification to device to start a synchronizing via nowSMS 2007. Is there a web interface to do that? I tried use "advance" push type of "send WAP push message" page, but failed. Anyone could tell me how to send out the syncML server alert notification, whose body is a binary message, via nowSMS 2007? Is it still use http post via PAP? Any help would be appreciated. | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 222 Registered: 12-2006 |
HTTP POST via PAP would be the preferred way to do it programmatically. From the web interface, "Send WAP Push Advanced" would be the solution. Tell me what fields you filled out in the "Send WAP Push Advanced", and what message data you supplied, and we can try to help you troubleshoot further. | |||
| eagleliang New member Username: Eagleliang Post Number: 2 Registered: 09-2007 |
hi, Malcolm,thanks for your reply. I filled content-type "4e", which is encoded, and content "4732EED45C3D2D6D909F3F9228961F48030800000000010D537953796E632053657276657210600 0000708636F6E7461637473" which is a hex String(I clicked "Hex String(convert to binary)"). But, on device, I only got one bit. I also tried fill content-type "application/vnd.syncml.ds.notification", it also "fail". BTW, if using PAP, how can I do? Thanks | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 242 Registered: 12-2006 |
Only one byte is received on the device? What does the SMSOUT-yyyymmdd.LOG file show? If I send the above, I see the following: UDH=0605040B8423F0;Data=4D0601CE4732EED45C3D2D6D909F3F9228961F48030800000000010D 537953796E6320536572766572106000000708636F6E7461637473 That looks correct. Note that I sent it out specifying "application/vnd.syncml.ds.notification" as the content type, as this interface does not understand a content-type that is already encoded in hex. (That might be an idea of something for us to support in the future.) I'm not real familiar with DS notifiations, but I believe you should also set the X-WAP-Application-ID header in order to be sure to route the content to the correct application on the phone. (Some phones may route to the correct application based upon the content-type alone, but others may require the application id header.) Off-hand, I'm not sure what value you should be using for this, but you should find it in the relevant spec. As far as the PAP interface, here is some basic info: http://support.nowsms.com/discus/messages/485/3293.html | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 243 Registered: 12-2006 |
I may have sent you on a wild goose chase with regard to the X-WAP-Application-ID header. I don't see any references to the push application id in the SAN spec. But it still might be worth trying a value of x-wap-application:push.syncml in one of your tests. | |||
