Re: Siemens SEO Specification

Aarno Syvänen <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Hi Dominic,

I am interested about ota to siemens, too. Are there public specs  
available ?
What port do ota messages use ?

Aarno

On Saturday, March 8, 2003, at 03:16 PM, Dominik Simon wrote:

> Hi Soren,
>
> here is my specification of siemens-ota (seo), I use:
>
> - - - -
>
> 5 [2F 2F 53 45 4F] - Identifier ASCII "//SEO"
> 1 [01] - Version 1,
> 2 [67 00] - DataSize = 103 Byte
> 4 [79 07 00 00] - Referenz-ID
> 2 [01 00] - ActPacketNumber = 1
> 2 [08 00] - NumberOfPackets = 8
> 4 [EE 02 00 00] - ObjectSize = 750 Byte
> 4 [03 62 6D 70] - ObjectType = 3 "bmp"
> 13 [OC 4F 70 65 72 61 74 6F 72 2E 62 6D 70] - ObjectName = 12  
> "Operator.bmp"
> 103 [70 42 4D ...] Data of the Bitmap in BMP-Format
> = 140 Bytes (if the last sms is less, you have to fill out with 00  
> (zero).
>
> - - - -
>
> If you have a look on my seo-example, here I split and tell you more  
> about
> the first sms:
>
> 2F2F53454F       = //SEO
>
> 01               = Seo-Version 1
>
> 6600             = my Data-Size is 102 Byte
>
> 2664673E         = my ID of the seo-sms (must be the same in every sms)
>
> 0100             = message-number 1
>
> 0500             = of 5 messages
>
> C3010000         = 451 byte data-size (here from my midi)
>
> 036D6964         = 3 number of letters / BMP
>
> 0D756E646572626572672E6D6964 = 13 number of letters / UNDERBERG.MID
>
> 4D546864000000060001000201E04D54726B0000004700FF0314417564696F496E73742 
> 02031
> 2A6B6F706965727400FF01124445564943453D47454E4552414C2E4D445600FF5804040 
> 22408
> 00FF5902000000FF5103087A2300FF2F004D54726B0000015E00
> = DATA of the midifile
>
> - - - -
>
> Now I want to send this seo-string to my kannel-gateway, as udh-string
> - but it only works with ems-messages :-(( no siemens.
>
> Thanks for your help!
>
> -- 
> Best regards,
>  Dominik                          mailto:[email protected]
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.