HOW ABOUT PROVISION MESSAGE

Stone Zhang <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Aarno,

Thanks for ur help. I have another question : 

What is the token for application/vnd.wap.connectivity-wbxml

and when I have to turn first bit when I need ture the second bit.

for example, we need ture second  bit for SI with content 0X05 | 0x40
and we need turn first and second bit for Indication element with content
and attibutes 0x06|0x40|0x80

which specification I should refer to?

cheers

stone


-----Original Message-----
From: Aarno Syvänen [mailto:[email protected]]
Sent: 24 October 2002 11:50
To: Stone Zhang
Subject: Re: content type


Token for application/vnd.wap.sic 0x2e, but you must turn first
bit, to show that the token is a short integer. So SMS should
have 0xae.

Aarno

On Thursday, October 24, 2002, at 01:22 PM, Stone Zhang wrote:

> what is content type for SI PDU, is it AE or 2E?
>
>
>
>
>
> NOTICE AND DISCLAIMER:
> This email (including attachments) is confidential.  If you have 
> received
> this email in error please notify the sender immediately and delete 
> this
> email from your system without copying or disseminating it or placing 
> any
> reliance upon its contents.  We cannot accept liability for any 
> breaches of
> confidence arising through use of email.  Any opinions expressed in 
> this
> email (including attachments) are those of the author and do not 
> necessarily
> reflect our opinions.  We will not accept responsibility for any 
> commitments
> made by our employees outside the scope of our business.  We do not 
> warrant
> the accuracy or completeness of such information.
>
>



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.
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.