Thank you (Stipe and Aarno) very much for helping me. the problem has been sorted out by adding the smsc-at and deleting the http smsc
rgs -----Original Message----- From: Stipe Tolj [mailto:[EMAIL PROTECTED]] Sent: 04 March 2002 12:45 To: Stone Zhang Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: Re: wap push test Stone Zhang wrote: > > I have a problem when I tried wap push with kannel cvs version. I am using a > Nokia premicell as a SMSC you're definitly conseptually wrong here, I'll try to explain: > the I followed the User' Guide, > 1. gw/bearerbox pushkannel.conf > gw/wapbox pushkannel.conf > > 2. test/test_http_server -p 10001 > > 3. test/tes_ppg -q http://localhost:10000 > > then I got a error message -- "Authorization failed for sendsms" you have defined a smsc_http group for PPG transportation. That is definitly wrong! BTW, I can't see your smsc_at group for the Nokia premicell you are talking about, or are you relaying to a different kannel installation that runs the premicell?! Ok, PPG requests are defined in the ppg group, hence (given your config) you would address http://localhost:8080/cgi-bin/wap-push.cgi and POSTing the document to it. the PPG inside sends it then via the available smsc groups to the device. Keep in mind that your PAP document contains accordingly the bearer type (in your case SMS and no IPv4) to address the client device. Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 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 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.
