Hi Dziugas, thanks for your answer! But sorry, you're right. BMP of siemens mobilephones means a windows bitmap format black/white.
With siemens ota you can "split" this files in many, many messages. The mobilephone saves this file in the original format to the phone-memory. Its nothing different one, than a dispatching of an attachement - like email. At this time I send siemens-ota messages via an expensive gateway and now I want to convert and send it by myself. But I have some customers, they want to have and use today this feature. One example: polyphone-melodies to siemens-phones only can be sent as siemens-ota and not via ems :-( Okay.. you think, I have to send the siemens-ota message as text? In attachment I send to you the siemens-ota message in the original format (before/without encoding to hex). So I only have to "url-encode" the text and send it to the sendsms.php script as udh-string? Many thanks for your help! -- Best regards Mit freundlichen Gr�ssen Dominik Simon Dominik Simon mailto:[EMAIL PROTECTED] am Sonntag, 9. M�rz 2003 um 16:28 schrieben Sie: DB> Hallo, DB> sorry for mixing your head. recently I analized sendsms.php code in DB> kannel's contrib directory and found that siemens OTA information should DB> be sent as text. here is a snip from the code: DB> -- DB> while ($count < $max) { DB> if ( $count == $max - 1 ) { # Last Packet DB> $packet_size = $file_size % $max_size; DB> } DB> $fields['text'] = ""; DB> $fields['text'] .= "//SEO"; DB> $fields['text'] .= "%01"; # Version 1 DB> $fields['text'] .= "%". sprintf("%02X", $packet_size % 256). "%". sprintf("%02X", floor($packet_size / 256)); # Data Size on this message DB> $fields['text'] .= "%00%00%00%00"; # Reference DB> $fields['text'] .= "%". sprintf("%02X", ($count+1) % 256). "%". sprintf("%02X", floor(($count+1) / DB> $fields['text'] .= "%". sprintf("%02X", $max % 256). "%". sprintf("%02X", floor($max / 256)); # Max DB> $fields['text'] .= $object_size; # Object Size DB> $fields['text'] .= "%". sprintf("%02X", strlen($mmc_file_type)). $mmc_file_type; # Object Type DB> $fields['text'] .= "%". sprintf("%02X", strlen($mmc_file_name)). $mmc_file_name; # Object File Name DB> $fields['text'] .= substr($file, $count * $max_size * 3, $packet_size * 3); DB> #print $fields['text']. "<br>"; DB> #$debug = 1; DB> sendsms(); DB> $count++; DB> } DB> -- DB> i'm using imagemagick in order to convert gif or jpeg images to otb (over DB> the air bitmap) format, which is fixed in size - 130 bytes. it's mainly DB> suitable for nokia phones but stripping few bytes from the header i can DB> easy send it as EMS message. what is your experience in Siemens? I hope DB> BMP doesn't mean "windows bitmap format" of huge size? :) the same is with DB> MIDI files - the same melody could fit into different sized files, despite DB> the fact, that midi file itself holds a lot of unnesessary information in DB> it's headers (Author's name, instruments, channels and so on). as bigger DB> is the file, as much sms traffic you generate, which from the business DB> view isn't very useful :) DB> regards, DB> Dziugas Baltrunas DB> p.s. sorry for spelling mistakes.
1046960333rUIvJMA4_underberg1.seo
Description: Binary data
