| Any other way to send XML rights objects in separate delivery method |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| subashini New member Username: Subhi Post Number: 1 Registered: 06-2007 |
Hello everybody, am new to this forum, is there any other way to send XML rights objects to the device other than "XML settings document" option in NOW SMS. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7164 Registered: 10-2002 |
No, there is not. The command-line DRMCOMP utility can be used as an aid for creating those rights object files. But for sending them you need to go through the "Send XML Settings" interface ... at least for submitting via the web interface. To send the settings in an automated fashion, you can use HTTP POST, using either PAP, or this simple HTTP POST interface that we have for any of the document types supported by "Send XML Settings" ... Open an HTTP connection to the port for the NowSMS web interface, and then issue an HTTP POST: POST /?PhoneNumber=xxxxxxxx&OTA=POST HTTP/1.0 Content-Length: yyyyyy (*insert blank line here to end HTTP Header*) <xml settings document> When submitting an OTA request in this manner, the HTTP POST request must include a “Content-Length:” header. This should match the length of your XML document. NowSMS will scan the XML content to automatically determine what the content type is ... so that it can be encoded properly for sending over the air. If you need to use a PIN on the settings (not typically used with rights objects, but used with other XML documents), add "&OTAPIN=xxxx" to the URL, along with "&OTAPINTYPE=USERPIN" or "&OTAPINTYPE=NETWPIN". The only other bit that I should mention is user authentication. If you have NowSMS configured to require user accounts for message submission, then you need to specify which of the "SMS Users" accounts is used by the submission. To do this, include "&User=username&Password=password" in the URL request. (Or you can use an HTTP Basic Authentication "Authorization:" header.) -bn | |||
