| Is it possible to send rights with Now SMS to separate delivery OMA... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | ||||
| maor segev New member Username: Maorsegev Post Number: 1 Registered: 06-2009 |
Hi My question is about sending rights with Now SMS to separate delivery OMA DRM V2 files located on a mobile device. I’m able to send and get successfully OMA DRM V1 RO’s by using the “Send XML Settings Document “ option. However, doing the same with OMA DRM V2 RO’s - nothing happens and I fail to receive the rights on my mobile device. Any help or directions will be appreciated. Thank you | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 925 Registered: 08-2008 |
Hi, If you're using a real old version of NowSMS, no. But NowSMS 2008 and later do have support for DRM 2.1 ROAP trigger messages. Unfortunately, I don't know of any tools that support creation of the DRM 2.1 objects, so I don't have any simple tests objects that are known to work which you could use for validation. -- Des NowSMS Support | ||||
| maor segev New member Username: Maorsegev Post Number: 2 Registered: 06-2009 |
Thank you Des I'm using NowSMS/MMS Gateway v2008.06.03 I have the tools for creation of the DRM 2.1 rights objects and I have created OMA v1 and v2 ROAP trigger messages. The v1 work well The v2 fails  Thank you | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 936 Registered: 08-2008 |
That version should be fine. I have no way to test it. You may want to look at the SMSOUT-yyyymmdd.LOG to see the WBXML that NowSMS generates for the ROAP trigger message. I'm not aware of any problems with this encoding, but we currently have no way of testing it in the real world. If you want to post a ROAP trigger message that you are trying to send, I can manually check the encoding that we generate. -- Des NowSMS Support | ||||
| maor segev New member Username: Maorsegev Post Number: 3 Registered: 06-2009 |
Hi Des Plese see attached DRM 2.1 ROAP trigger message: <roap:roapTrigger xmlns:roap="urn:oma:bac:dldrm:roap-1.0" version="1.1"><roAcquisition id="id1"><riID><keyIdentifier xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xsi:type="roap:X509SPKIHash"><hash>I94/ovDhizE5m/K6t5f1holSdLM=</hash></keyIdentifier></riID><nonce>tecl6eP/UQP+AS5pYAJc</nonce><roapURL>http://192.116.217.182:8080/iop-server/roap.cm?procedure=DRM-2.1-int-34_Count_constraint&folder=NewDrm_IOP_2.1&u=SE_WM&offer=offer6091_jpg&cd=false</roapURL><roID>offer6091.1.uXJG979bPUvaJy3H_jpg</roID><contentID>cid:cid6091_jpg</contentID></roAcquisition></roap:roapTrigger>
| ||||
DRM 2.1 ROAP trigger message example
