Dear Mr. Bloch,

I might add, downloaded and saved it - ie. the operator logo.

Nice huh - Im doing this *without* MCC/MNC values...!

(the logo says L.S/M.F.T in handwritten cursive letters)

Kind Regards,
Bernino Lind

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bernino Lind
Sent: 9. januar 2002 22:49
To: Nisan Bloch; [EMAIL PROTECTED]
Subject: RE: test logo


Dear Mr. Bloch,

Thank you very much for your kindness.

I have succesfully downloaded the logo to my phone. It works.

At your request I will never send an ota file to the list again.

I have now the mclass and mwi working also.

Im wondering: is it possible to send a mwi without a text messages in the
at2 SMSC mode ?

Im also wondering: how did you do your logo - which steps/code does it
involve from a gif/png picture to the hex? incoded text ?

Kind Regards,
Bernino Lind

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Nisan Bloch
Sent: 9. januar 2002 22:30
To: Bernino Lind; [EMAIL PROTECTED]
Subject: RE: test logo


Hi

>In Denmark I have experienced something weird:
>Sending a logo without MNC and MCC does not matter. It works either way!


aah.. but can you then save it so it becomes a operator logo?

here is a full logo

udh=%06%05%04%15%82%00%00&text=%56%f5%01%00%48%0E%01%00%00%00%00%10%00%00%00
%00%00%00%00%00%30%00%00%00%00%00%00%00%00%60%00%00%00%00%00%0C%03%C0%C6%71%
F9%FC%00%00%0C%06%C0%8C%E0%C0%60%00%00%18%06%01%9C%E1%80%60%00%00%18%07%03%3
F%C1%F0%C0%00%00%30%03%06%
2E%C3%00%C0%00%00%70%13%0C%6C%C3%01%80%00%00%7E%9E%48%4D%96%11%90%00%00%00%0
0%10%00%00%00%00%00%00%00%00%30%00%00%00%00%00%00%00%00%20%00%00%00%00%00%00
%00%00%20%00%00%00%00%00

this has a mcc mnc for my operator. the logo will display, but you wont be
able to use it as a operator logo unless you modify the operator code bit
%56%f5%01


>Could that be due to one of the following:
>
>a. we have operator independency (ie. telephone numbers can follow the
>customer if one so wishes from provider to provider) ?

mm.. provider or network operator?

>Finally I have a question about udh headers:
>Exactly who and where are they specified. I have found udh for multipart
sms
>messages, logos, ologos, ringtones, vcards and vcalender - but I still miss
>for CLI icons and I still miss for mclass: or is mclass implemented some
>other way in kannel ?

mclass is DCS encoding fields.. it doesnt necessary need udh.
the GSM docs give you all these details. In most implementations the UDH
along with the Data make up the SMS message. This is why you have fewer
bytes to play with when you set a udh.


>Does anyone out there have an application they are willing to share with
the
>rest of us, for example an icon sender, a ringtone sender or ... ?


Kannel will do it for you.


>Just for fun, I have attached the OTA logo to this messages (and its not I
>love you virus, but a very romantic logo for my girlfriend).

please do not do this to the list!!!!!


nisan


>Best Regards,
>Bernino Lind
>
>-----Original Message-----
>From: Nisan Bloch [mailto:[EMAIL PROTECTED]]
>Sent: 9. januar 2002 00:29
>To: Bernino Lind; [EMAIL PROTECTED]
>Subject: Re: test logo
>
>
>Hi Berino
>At 10:06 PM 1/8/02 +0100, Bernino Lind wrote:
> >Hello users,
> >
> >Could someone please send me a test logo in the form that sendsms accepts
> >(binary, but I mean so that it can be copy pasted into a url...).
>
>The hex for the ologo is dependent on the destination msisdn.
>
>Basically it is as follows:
>The logo using OTA:
>byte 0: Version & flags. Usually %00
>byte 1: width of the image
>byte 2: height of the image
>byte 3: bithdepth of the image. %01 for black and white.
>byte 4: and following are the pixels of the image.
>
>the udh part in the sendsms for a ologo would be
>&udh=%06%05%04%15%82%00%00
>
>but then you need to calculate the "operator code" which is made up of the
>MCC (mobile country code) and MNC (mobile network code) of the destination
>phone.
>
>So assuming a MCC = 234 and a MNC=10
>you will get %32%F4%01
>
>so the &text=... in sendsms would be
>&text=%32%F4%01 followed by the ologo header and data.
>
>
>
>Nisan




Reply via email to