Not able to receive XML OMA settings on many phones

Not able to receive XML OMA settings on many phones SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 16, 2008 » Not able to receive XML OMA settings on many phones « Previous || Next »
Author Message
Rishi Dawar
New member
Username: Rishidawar

Post Number: 1
Registered: 08-2008
Posted on Wednesday, August 06, 2008 - 09:14 am:   

Hi Can anyone pls help me out in resolving my issue.
I have a DRM content with separate delivery .dr file. i am sending the Key via NowSMS using xml setting. The issue is some of the phones are receiving the message but many phones like Nokia 7610, E50, E61 and many other SE phones are not receiving the message.

if any one has any clue on this please help me out.

Here is the example of OMA Delivery:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE o-ex:rights PUBLIC "-//OMA//DTD DRMREL 1.0//EN"


waiting for anyone's reply.

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 12
Registered: 08-2008
Posted on Tuesday, August 19, 2008 - 04:55 pm:   


Here are a few notes that may help you out:

SonyEricsson phones generally don't tell you that a DRM activation message was received, unless it successfully activates a piece of content.

Many Nokia phones have a problem with some constraints not working properly. Specifically, there appears to be a bug in the firmware of quite a few Nokia phones where these phones do not properly support separate delivery acivation constraints that include a date range, or time interval (such as number of days).

Aside from the above issues, you should make sure that your key value is correct, and that your UID (content-id) value is correct.

We have noticed that some phones have problems with some UID formats. For example, I notice in your example above that the UID is "cid:http://0009.3gp". I believe that will cause a problem in some devices, because they do not like the "cid:" prefix in front of an HTTP URL. In this case, the UID should simply be "http://0009.3gp". Or actually ... I would recommend that since you do not have host name in your URL, you do not use the "http://" prefix, and only use a "cid:" prefix ... but the value of this parameter (after the "cid:") must match up with the content-id of the object.

I'd suggest that you experiment with the DRMCOMP utility that is included with NowSMS to perform some encodings ...

NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics