Re: wml in wap push

Aarno Syvänen <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
And adding to this: the phone must support application/vnd.wap.wlmc.
(Check header UA Profiling document). Simulator accepting wml deck
does not guarantee that any phones would accept it. (Idea of push it:
you send notification, user accepts, phone loads.)

Aarno

On Sunday, June 8, 2003, at 02:06 PM, Stipe Tolj wrote:

> Hi Amit,
>
>> amits schrieb:
>>
>> Hiii
>>
>> We are trying to push a multipart wap push to the phone......we done
>> SI and SL successfully......but in this case we are facing
>> problems....nothing is delivered on the phone....
>>
>> we try same in two ways....
>>
>> First we create a multipart message through nokia internet mobile
>> toolkit 3.1...in this file we add one .sic file and one wmlc file
>> according to nokia docs.....and it working fine on
>> simulator.........we tried to send this file using test_ppg with a
>> working pap.....
>> but nothing comes on the phone.....
>>
>> Second we created a file having a pap and wml code in a single
>> file....but test_mime sows error while parsing....
>>
>> if u need the files code pls inform us...we shall send you....
>>
>> pls guide us to do same in right way...
>
> first of all, the PAP document has to be seperate from the content
> itself. Can you send us the files you pass to test_ppg and the exact
> command line you use while calling it?!
>
> Can you also describe what you are trying to do? Pushing a
> pre-compiled wml deck?
>
> Stipe
>
> [email protected]
> -------------------------------------------------------------------
> Wapme Systems AG
>
> Vogelsanger Weg 80
> 40470 Düsseldorf
>
> Tel: +49-211-74845-0
> Fax: +49-211-74845-299
>
> E-Mail: [email protected]
> Internet: http://www.wapme-systems.de
> -------------------------------------------------------------------
> wapme.net - wherever you are
>
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.