MMS m-notification-ind problem

Vjacheslav Chekushin <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization LMT
Message-ID <[email protected]>
Hi,

I send m-notification-ind through PPG. I get successfull response from gateway
and message is delivered to phone (I can check it at SMSC level).
But nothing is happening on the phone.

What is wrong with my example?
May be some expert in MMS helps me with it.

I send to PPG following data:

<---- Start
POST /cgi-bin/wap-push.cgi HTTP/1.1
Host: locahost:8090
Content-type: multipart/related; boundary=qwerty12345asdf;
type="application/xml"
X-WAP-Application-Id: x-wap-application:mms.ua
Content-length: 670

--qwerty12345asdf
Content-type: application/xml

<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP//EN"
          "http://www.wapforum.org/DTD/pap_1.0.dtd">
<pap>
<push-message push-id="12345678901234567890" progress-notes-requested="false">
<address address-value="WAPPUSH=+3719248319/[email protected]"/>
<quality-of-service network-required="true" bearer-required="true" network="GSM"
delivery-method="unconfirmed" bearer="SMS" priority="medium"/>
</push-message>

</pap>

--qwerty12345asdf
Content-type: text/vnd.wap.mms-message

▄┌≤1-c0c9█░┼─▌l┬─?"j╤┐http://10.10.253.4/mms/retrieve.pl?id=12345678901234567890

--qwerty12345asdf--
<----- End

And hex encoding for mms (just for transparancy):

d a d a 8c 82 98 31 2d 63 30 63 39 0 8d 90 8a 80 8e 2 2 6c
88 80 4 3f 22 6a b6 83 68 74 74 70 3a 2f 2f 31 30 2e 31 30
2e 32 35 33 2e 34 2f 6d 6d 73 2f 72 65 74 72 69 65 76 65 2e
70 6c 3f 69 64 3d 31 32 33 34 35 36 37 38 39 30 31 32 33 34
35 36 37 38 39 30 0 d a d a 



-- 
Vjacheslav Chekushin                                mailto:[email protected]
Latvian Mobile Phone Company                        http://www.lmt.lv
Network Support and Information Technology Group    +371 7773436
                                                    +371 9248284 (mobile)
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.