| Nokia 7600 not supporting DRM |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Confused and fed up Unregistered guest |
Hi, We are currently trying to get DRM forward locking working across a range of handsets. The nokia 7600 device seems to recognise the fact that the mesage is indeed copyrighted however it doesn't play the file - it simply puts an image on the screen representing a piece of film The timer counts down showing that it is playing the message as per the paragraph definition field in the smil. All the details about the file can be displayed, down to name whether it's copyrighted etc ok, If you try to forward the content it fails with the nice "cannot forward copyrighted files" message. The strange thing is - this works correctly on other handsets, the video can be played, whilst the message cannot be forwarded. if we send it un"DRM'D" it plays ok..... Also whe we down load the asset direct to the phone, with it set as a protected file it can be played. Any ideas is we need an extra field specifically for the Nokia?? or is it just that the mms poush client cannot recognise the media type and fails to fire up the media player? Some message details are shown below: note these are edited highlights <MsgBody>Subject:Content_Disposition_DRM Content-Type: application/vnd.wap.multipart.related; boundary="57CC%23411X1CF-0090-001C0X.5886835873726 837043"; start="<CONTSMIL>"; type="application/smil" MIME-Version: 1.0 --57CC%23411X1CF-0090-001C0X.5886835873726837043 Content-Type: application/smil Content-Id: <CONTSMIL> <smil><head><meta name="title" content="" /><layout><root-layout width="130" height="116" /><region id="image" top="0" left="0 " height="76" width="130" fit="meet" /></layout></head><body><par dur="10s"><video src="cid:MA_CID_1" region="image"/></par></ body></smil> --57CC%23411X1CF-0090-001C0X.5886835873726837043 Content-type: application/vnd.oma.drm.message Content-Disposition: inline Content-location: Content.dm Content-Id: <MA_CID_1> <MA_ATTACHED_ENTITY>file:///opt/projects/content/CONTENT.dm</MA_ATTACHED_ENTITY> --57CC%23411X1CF-0090-001C0X.5886835873726837043--</MsgBody> </Message> </Header> the top of the content.dm file contains this encoding --mime_content_boundary Content-Type: video/3gpp Content-Transfer-Encoding: binary ...... ... ... --mime_content_boundary-- | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3697 Registered: 10-2002 |
And it works on other phones? I'm confused with the whole "MA_ATTACHED_ENTITY" bit, and I don't see where the "mime_content_boundary" is declared for the "application/vnd.oma.drm.message" content type. Add "boundary=mime_content_boundary" to the "Content-type: application/vnd.oma.drm.message" header, and lose the <MA_ATTACHED_ENTITY> stuff. Does that get you closer? | |||
| confused and fed up Unregistered guest |
The encoding tool we are using - puts the boundary direct into the .dm file as shown at the bottom of the text. If we declare it outside the .dm file it still fails, if we declare it in both places it fails We have encoded the file with both the nokia tool and another and get the same results.... I was just wondering if you had come across this issue with 7600's? Dont worry about the MA_attached bit's thats a bit of code we use to automatically add content into messages from different locations - depending upon what the message being sent is and it's not relevant to this issue. thakns for the help | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3717 Registered: 10-2002 |
I'm afraid that I'd have to see the exact message that is being sent out. If there is some conversion tool that is applying conversions, I can only guess. Does it only happen with Video? What happens if you put an image in there instead? | |||
