| EMS picture + text submission through url |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Edward Parris New member Username: Epso Post Number: 1 Registered: 05-2007 |
Is it possible to send an EMS message along with a small amount of text if you are submitting it to the server via a construced URL? Would i have to encode the text by hand, if so how is this done? Thanks alot | |||
| Edward Parris New member Username: Epso Post Number: 2 Registered: 05-2007 |
After much investigation I have come to a few conclusions but also ended up with a few more questions. It does not seem possible to send a multipart EMS message through the binary message webform. is there a way to do this either by using the form or with url submission progrmaticaly. When i sent a very small image (so it would fit in one message) using a UDH i created myself the phone said the message was too big, so i must have done somthing wrong. the message content looked like this: 71166F00424D6E000000000000003E00000028000000200000000C0000000100010000000000 300000000000000000000000000000000000000000000000FFFFFF00FF87F87FFF87F87FFE4F E4FFFC3FC3FFFC3FC3FFF27F27F9E1FE1FF0E1FE1FF093F93FC90FF0FF870FF0FF879FF9FFCF (has been truncated so as not to make the page very wide). 71 length (113 hex pairs) 16 for picture message (is this correct, is there a definitive list of the different EMS message types anywhere) 6F remaining length (111 hex pairs) 00 offset 42... image data PID=0 not even quite sure what this is DCS=0 0 for hex format right? have i gotten the total length/rest of length correct? How exactly does nowsms convert an uploaded/linked image to hex? I see a copy of imagemagick's convert util in the install directory but what exactly is it used for? I presume making it a 2bit monochrome image and the converting it to hex, does the bitmap header get stripped? I saw a post on here somewhere about the ems image hex starting with 00 followed by the width then height in hex, how does this get there? I then tried to create a concatenated message and send each part with the binary form but they arrived as separate blank messages. Is it possible to send them like this? After sending a legitimate message through the EMS picture message form, I sent this back to NOWSMS to have a look at the file. it seems to be the tail end of the picture as it was bigger than 1 message i beleive. there is a long UDHwhich checks out for its size etc but then there is also a DATA part, what is contained within this data part? can I put a line of text to display in this 'data' part? UDH=34163200002F911400007202020002381069CB391638B6140E071C0E381C7038841401003208 7A8518108ED8EB06030C06180C3018 Data=502800 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7206 Registered: 10-2002 |
Hi Edward, Apologies for having missed this thread when it was originally posted. Unfortunately, we don't have any web form option for sending an EMS message that includes both an image and text (we do have a web form for including the predefined animations with text, but not custom images). EMS encoding is definitely a pain ... especially if an image is too large for a single message UDH (and not all EMS compatible phones support the technique that allows them to span multiple messages). I did post some good example "how-to's" ... quite some time ago. Here's one that deals with splitting an image across multiple messages ... http://support.nowsms.com/discus/messages/1/1758.html As for the actual picture conversion. We do use ImageMagick. It is primarily used by the MMSC. But it does get used in converting images for EMS. Basically, we convert to an ".otb" format (OTA Bitmap) which is a type of monochrome bitmap ... strip the headers and put the EMS image headers in place. The EMS standard has been rolled into 3GPP TS 23.040, so you can find it described there: http://www.3gpp.org/ftp/Specs/archive/23_series/23.040/ -bn | |||
