Re: test_ppg problem

Hi Stipe,

M-notification.ind file (mms.txt) is some thing like this

8c8298313235008d908a808e016488048102010083687474703a2f2f7777772e666c7965726f
6e652e636f6d2f00

and pap.txt

<?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="[email protected]"
progress-notes-requested="false">
                <address
address-value="WAPPUSH=+919848444808/[email protected]">
                </address>
        </push-message>
</pap>

which I copied from previous mails.

#./test_ppg
"http://202.56.199.69:8080/wap-push?username=foo&password=bar" -a mms -c mms
mms.txt pap.txt.

Access.log

2003-04-30 14:56:22 Sent SMS [SMSC:FAKE] [SVC:] [ACT:] [from:1234]
[to:+919848444808] [flags:0:2:0:0:0]
[msg:123:03061BBE963230322E35362E3139392E36393A3830383000AF848DDDB4803863383
2393833313332333530303864393038613830386530313634383830343831303230313030383
3363837343734373033613266326637373737373732653636366337393635373236663665363
53265363336663664326630300A] [udh:7:0605040B8423F0]

Is this correct. Or Am I  still missing something. Please bear with me for
my silly question.

Shridhar Raju

> Hi Shridhar,
>
> what you try to do *can't* work, because you are sending the
> M-Notification.ind in decoded (hence plain text) format to PPG.
>
> PPG is not responsible for encoding MMS PDUs. You have to deliver PPG
> the already encoded (binary) M-Notificaiton.ind.
>
> For an example of what works see the following mail from me in the
> list:
>
>   Subject: Re: MMSC server
>   Date: Mon, 28 Apr 2003 20:50:17 +0200
>
> you'll find there an explanation of the M-Notification.ind binary
> encoded structure as defined in WAP-MMSCEncapsulation document.
>
> Stipe