hello,
I'm not sure how you'll impliment it, but you need to
be sure that the URL has no spaces inbetween the
values for the parameters. when there's a break the
URL may not be properly represented.
EG: BAD
username=ppgusername&password=ppgpassword&dlr-mask=31&dlr-url="" class="moz-txt-link-freetext" href="http://192.168.0.1/my">http://192.168.0.1/my
midi file.mid
EG: GOOD
username=ppgusername&password=ppgpassword&dlr-mask=31&dlr-url="" class="moz-txt-link-freetext" href="http://192.168.0.1/my%20midi%20file.mid">http://192.168.0.1/my%20midi%20file.mid
--- Julien Buratto <[EMAIL PROTECTED]> wrote:
Mike Nwaogu wrote:
Hello Julien,
The position on your dlr-mask in the post command
is
what I think the issue is.
Maybe you are true, but if I do
POST /wappush HTTP/1.1
Host: 10.100.10.5:8080
Connection: close
Content-Type: multipart/related; boundary=123321;
type="application/xml"
Content-Length: 1174
username=ppgusername&password=ppgpassword&dlr-mask=31&dlr-url=""
url]
<XML ATTACHMENT CUT>
then the ppg says:
HTTP/1.1 401 Unauthorized
Server: Kannel/1.4.0
Content-Length: 32
Connection: close
WWW-Authenticate: Basic realm=berlinzoo"wappush"
You must show your credentials.
if I do:
POST
/wappush?username=ppgusername&password=ppgpassword
HTTP/1.1
Host: 10.100.10.5:8080
Connection: close
Content-Type: multipart/related; boundary=123321;
type="application/xml"
Content-Length: 1174
username=ppgusername&password=ppgpassword&dlr-mask=31&dlr-url=""
url]
(same as before but with user/pass in the POST url)
the I get:
HTTP/1.1 202 Accepted
Perhaps you should URL ENCODE the content or
relocate
the dlr-mask parameter before the actual message.
I
could be wrong though but I think that's what it
is.
It is encoded,the protocol implementation seems ok
to me, I think is
something different related to the box receiving and
decoding the
paramenters.
Cheers
Julien
--- Julien Buratto <[EMAIL PROTECTED]> wrote:
Hello
I'm reposting this question because I have still
no
clue.
1) In the past I used binary SMS messages to send
WAP-PUSHES
in that way I was able to set dlr-mask=31 and a
dlr-url and I have been
receiving DLRs easily when the phone received the
SMS.
Sometimes the phone did not understand the
wap-push
message as a
binary-message but the DLR arrived in any case.
The 'call' was something like GET /sendsms? and I
was using the
bearerbox and the smsbox to send those binary sms.
2) Now I use the bearerbox, smsbox and wapbox and
I
send XML files to
the wapbox using a POST but when I set the dlr-url
and dlr-mark
variables in the POST, I receive no DLRs at all.
Does anyone know if the transcodification from XML
to BINARY made by the
wapbox do include dlr ?
Thanks
PS: I'm not interested to be notified if the
wappush
is understood or
not, I just want to know if the wappush sms is got
by the phone.
Mike Nwaogu
Metro Technologies & Resources Ltd.
48 Tunde Idiagbon Road, Tanke, Ilorin.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Mike Nwaogu
Metro Technologies & Resources Ltd.
48 Tunde Idiagbon Road, Tanke, Ilorin.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
