SIEMENS LOGO Problem (SEO)

SIEMENS LOGO Problem (SEO) SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2005 » SIEMENS LOGO Problem (SEO) « Previous || Next »
Author Message
Mike
Unregistered guest
Posted on Saturday, April 16, 2005 - 02:13 pm:   

I read that page http://support.nowsms.com/discus/messages/1/602.htm l

I have the same problem as (Anonymous SEO)
Can you help me?

Mike
Unregistered guest
Posted on Saturday, April 16, 2005 - 02:15 pm:   

Also, i want to know how to make the SIEMENS mobiles understand my SIE Logos as logos, not as hex text?
thanks
Mike
Unregistered guest
Posted on Monday, April 25, 2005 - 07:15 am:   

Any suggestions???
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4366
Registered: 10-2002
Posted on Monday, April 25, 2005 - 04:40 pm:   

Hi Mike,

There are lots of different questions/problems in the thread that you reference.

Could you please be more specific?

If you are referring to the problem at the end of the message, the NowSMS fix that was referenced was introduced in versions of NowSMS since March 2004. The current v5.51 release would include this fix.

If you are still having a problem, I suspect we need more information about what exact data you are attempting to send.

-bn
Mike
Unregistered guest
Posted on Wednesday, April 27, 2005 - 10:51 am:   

Hi Bryce,

I have encoded Siemens Logo as in (ota_specification_release1.0.2.pdf) and put it in the DATA field, and put '00' in the UDH field as in the PDF, ok?

I sent that logo to a siemens mobile phone, but it was received as HEX text "//SEO...", not a logo.

So can you tell me where is the problem?
Thanks again.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4422
Registered: 10-2002
Posted on Wednesday, April 27, 2005 - 06:11 pm:   

Hi Mike,

Why are you putting 00 in the UDH field?

(Ah ... as I read the specification, I see how it mentions setting the TP-UDHI field to 0 ... but that is actually different from the UDH field. If TP-UDHI is 1, this means UDH is present. If TP-UDHI is 0, this means that UDH is NOT present. NowSMS sets this flag automatically based upon whether or not UDH is present.)

What if before trying your own content, you try the 3 messages in "Anonymous SEO's" message in the thread you reference. Try sending those 3 at the start of his message, under "SMSOUT START HERE".

-bn

Mike
Unregistered guest
Posted on Thursday, April 28, 2005 - 08:01 am:   

I sent those 3 messages that were without UDH right?.
But each one was received individually as HEX text on the phone.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4429
Registered: 10-2002
Posted on Thursday, April 28, 2005 - 02:37 pm:   

Hi Mike,

I'm not an expert on Siemens phones. In fact, I don't even have one in my lab ... I usually have to try to borrow one for any testing.

SEO messages are sent without UDH. If a message requires segmentation, the segmentation is handled within the content of the message.

Let's take a look at those messages from the other thread ...

Binary=1;DCS=F5;Data=2F2F53454F0169000400000001000300E600000003626D700A323030303 4392E626D70424DE6000000000000003E00000028000000480000000E0000000100010000000000A 80000000000000000000000020000000000000000000000FFFFFF003E184CC454466430F80000006 330E86CAA6C2E198C000000CC613238AA38990C6600000086C26710FE11CC

Binary=1;DCS=F5;Data=2F2F53454F0169000400000002000300E600000003626D700A323030303 4392E626D7086C30000001384C9207C0926439100000029121C23558870912800000044292247EFC 48928440000004444C9867CC32644440000002929224638C489292800000013921C2638C87093910 0000086C4C92739C92646C3000000CC626713FF91CC8C6600000063313231

Binary=1;DCS=F5;Data=2F2F53454F0169000400000003000300E600000003626D700A323030303 4392E626D70FF1899198C0000003E18E848FE242E30F800000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000

The first thing that you should notice is that the first 35 bytes are basically the same in each message, except for one byte that is the packet number which increments.

2F2F53454F = //SEO
01 = version
69 00 = Data Size = 105 bytes
04 00 00 00 = Reference ID
01 00 = ActPacketNumber = 1 (2 & 3 in subsequent packets)
03 00 = Number Of Packets = 3
E6 00 00 00 = object size = 230 bytes
03 62 6D 70 = object type = "bmp"
0A 32 30 30 30 34 39 2E 62 6D 70 = object name = "200049.bmp"

The content of the actual BMP forms the rest of the message, with sequential pieces of the data in each of the messages.

What do you see on the phone?

Do you see the hex text ... e.g., starting with "2F2F53454F"?

Or do you see text starting with "//SEO"?

If you see hex text, then it sounds like you are not submitting the message properly as a binary message. (Or your service provider has an issue with binary messages.) I have no information on your configuration, so I don't know what the issue is here.

If you see text starting with "//SEO", then it sounds like the phone you are sending to does not actually support SEO.

-bn

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