Re: Authorization failed for XML post
Hi, Have you checked with latest CVS user guide p. 89? I don't suspect that these would make a difference, but you could supply in the !DOCTYPE... and oa tags. Otherwise the POST seems normal. I don't know, however, what curl does with it. I am more of wget fan. Try running 'bearerbox conffile ' and 'smsbox conffile ' and check the logs generated. It would be also great if you could get a tcpdump of the packets sent and received. BR, Nikos - Original Message - From: Francis Vidal francisv.l...@gmail.com To: users@kannel.org Sent: Monday, December 15, 2008 9:30 AM Subject: Authorization failed for XML post Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: Authorization failed for XML post
for the curl XML POST request try use the same URL with the userpassword added Francis Vidal wrote: Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: CVS linux 5
Run the shell in debug mode (-x) Aarno On 12 Dec 2008, at 20:12, Surya wrote: I applied the message ID -%F patch.. [r...@localhost gateway]# make check utils/run-checks checks/check_counter checks/check_date checks/ check_ipcheck che cks/ check_list checks/check_octstr checks/check_compiler.sh checks/ check_fakesms c.sh checks/check_fakewap.sh checks/check_headers.sh checks/check_http.sh checks / check_httpsmsc_kannel.sh checks/check_ppg.sh checks/check_sendsms.sh checks/che ck_smpp.sh Check: checks/check_counter... OK. Check: checks/check_date... OK. Check: checks/check_ipcheck... OK. Check: checks/check_list... OK. Check: checks/check_octstr... OK. Check: checks/check_compiler.sh... OK. Check: checks/check_fakesmsc.sh... OK. Check: checks/check_fakewap.sh... OK. Check: checks/check_headers.sh... FAILURE! Check: checks/check_http.sh... checking SSL connections, too... OK. Check: checks/check_httpsmsc_kannel.sh... OK. Check: checks/check_ppg.sh... OK. Check: checks/check_sendsms.sh... FAILURE! Check: checks/check_smpp.sh... It stuck there… Any ideas ? Thanks in advance, Surya
Re: Authorization failed for XML post
Okay, tried adding ?username=userpassword=pass to the URL: curl -v -H Content-type: text/xm localhost:8081/cgi-bin/sendsms?username=userpassword=user Here's the output of CURL: * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) POST /cgi-bin/sendsms?username=userpassword=user HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* Content-type: text/xml Content-Length: 17 HTTP/1.1 403 Forbidden Server: Kannel/1.4.1 Content-Length: 32 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 Authorization failed for sendsms On Mon, Dec 15, 2008 at 4:20 PM, seikath seik...@gmail.com wrote: for the curl XML POST request try use the same URL with the userpassword added Francis Vidal wrote: Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: Authorization failed for XML post
Hi Nikos, Here's the output of smsbox.log (loglevel = 0): 2008-12-15 17:28:33 [16195] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-15 17:28:33 [16195] [2] DEBUG: HTTP: Created HTTPClient area 0x99ed0d0. 2008-12-15 17:28:33 [16195] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 17:28:33 [16195] [3] DEBUG: XMLParsing: XML: test-outbound.xml 2008-12-15 17:28:33 [16195] [3] DEBUG: Status: 403 Answer: Authorization failed for sendsms 2008-12-15 17:28:33 [16195] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 17:28:33 [16195] [1] DEBUG: HTTP: Destroying HTTPClient area 0x99ed0d0. 2008-12-15 17:28:33 [16195] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. On Mon, Dec 15, 2008 at 4:13 PM, Nikos Balkanas nbalka...@gmail.com wrote: Hi, Have you checked with latest CVS user guide p. 89? I don't suspect that these would make a difference, but you could supply in the !DOCTYPE... and oa tags. Otherwise the POST seems normal. I don't know, however, what curl does with it. I am more of wget fan. Try running 'bearerbox conffile ' and 'smsbox conffile ' and check the logs generated. It would be also great if you could get a tcpdump of the packets sent and received. BR, Nikos - Original Message - From: Francis Vidal francisv.l...@gmail.com To: users@kannel.org Sent: Monday, December 15, 2008 9:30 AM Subject: Authorization failed for XML post Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: SMPP connection disconnected when request DLR
Dear Falko, Thanks for reply, I have RX connection and I receiving MO there, so is it configuration thing from operator side? that he may be routing the DLR or something like that ? Regards Hafez On Mon, Dec 15, 2008 at 4:14 PM, Falko Ziemann fal...@gmail.com wrote: I might have a idea: Could it be that you only have a TX connection and no RX conn? When you send a message with DLR request, the smsc answers with a message waiting flag. When a smpp TX connection get's a message waiting flag it disconnects and connects a RX connection. So either you have to configure the RX connection or better you try to get a TRX connection, but you cannot receive DLRs over a TX connection. This is only a guess. Maybe you want to send the logfile of your SMPP connection. Regards Falko Am 15.12.2008 um 14:28 schrieb hafez ahmad: Hi, is there any ideas ? , is the problem from kannel side ot the operator side ? Regards, Hafez On Sun, Dec 14, 2008 at 2:46 PM, hafez ahmad hafezad...@gmail.com wrote: Dears, I am using kannel with the DLR group patch, when I send sms without adding the dlr-url and dlr-mask the SMS sent fine and there are no problem like the following: http://localhost:13013/cgi-bin/sendsms?username=testpassword=foocharset=UTF-8coding=2to=text=testfrom=1234smsc=TESTSMSCbinfo=100 but whene I add the dlr-url and dlr-mask to the URL my TX connection dissconected and reconecting like the following: http://localhost:13013/cgi-bin/sendsms?username=testpassword=foocharset=UTF-8coding=2to=text=testfrom=1234smsc=TESTSMSCbinfo=100dlr-mask=31dlr-url=http%3A//localhost/test.php%3Fdl%3D%25d is there any ideas why this happen? Regards, Hafez -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
Re: Hi
Your message is being stored in kannel queue since kannel does not know where to send the message to. try using smsc=xxx in your kannel call |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Mon, Dec 15, 2008 at 6:43 AM, Nikos Balkanas nbalka...@gmail.com wrote: Please address such questions to users. I am just another user, with limited time. Your routing is failing. Which smsc are you using and is it ACTIVE? Nikos - Original Message - From: Kaliya perumal To: nbalka...@gmail.com Sent: Monday, December 15, 2008 1:23 PM Subject: Hi I have installed kannel on Ubuntu ,and then i am running my kannel ,it running succesfully ,but when i sending sms,the message was not sent to the destination,whenever i am sending sms ,Queued for later delivery message will show on the browser ,So please provide the approbriate solution for that, When i sending sms through http interface http://127.0.0.1:13131/cgi-bin/sendsms?username=testerpassword=foobarfrom=kaliyato=919986131642text=Hello+world the result is 3: Queued for later delivery Below is my smsbox result 2008-12-15 09:29:48 [16051] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:30:48 [16051] [1] DEBUG: Timeout for fd:24 appeares. 2008-12-15 09:30:48 [16051] [1] DEBUG: HTTP: Destroying HTTPClient area 0x8144b90. 2008-12-15 09:30:48 [16051] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2008-12-15 09:32:52 [16051] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-15 09:32:52 [16051] [2] DEBUG: HTTP: Created HTTPClient area 0x8144b78. 2008-12-15 09:32:52 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:32:52 [16051] [3] DEBUG: Status: 403 Answer: Authorization failed for sendsms 2008-12-15 09:32:52 [16051] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:33:07 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:33:07 [16051] [3] INFO: sendsms used by tester 2008-12-15 09:33:07 [16051] [3] INFO: sendsms sender:tester:tester (127.0.0.1) to:919986131642 msg:Hello world 2008-12-15 09:33:07 [16051] [3] DEBUG: Stored UUID 73e4325c-c16e-46d7-bf5a-faca3428732d 2008-12-15 09:33:07 [16051] [3] DEBUG: message length 11, sending 1 messages 2008-12-15 09:33:07 [16051] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-15 09:33:07 [16051] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-15 09:33:07 [16051] [0] DEBUG: Got ACK (3) of 73e4325c-c16e-46d7-bf5a-faca3428732d 2008-12-15 09:33:07 [16051] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:33:32 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:33:32 [16051] [3] INFO: sendsms used by tester 2008-12-15 09:33:32 [16051] [3] INFO: sendsms sender:tester:tester (127.0.0.1) to:919986131642 msg:Hello world 2008-12-15 09:33:32 [16051] [3] DEBUG: Stored UUID 51962c19-c5b4-4c4d-9e12-158d6a27846f 2008-12-15 09:33:32 [16051] [3] DEBUG: message length 11, sending 1 messages 2008-12-15 09:33:32 [16051] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-15 09:33:32 [16051] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-15 09:33:32 [16051] [0] DEBUG: Got ACK (3) of 51962c19-c5b4-4c4d-9e12-158d6a27846f 2008-12-15 09:33:32 [16051] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:34:32 [16051] [1] DEBUG: Timeout for fd:24 appeares. 2008-12-15 09:34:32 [16051] [1] DEBUG: HTTP: Destroying HTTPClient area 0x8144b78. 2008-12-15 09:34:32 [16051] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2008-12-15 09:56:02 [16051] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-15 09:56:02 [16051] [2] DEBUG: HTTP: Created HTTPClient area 0x8143388. 2008-12-15 09:56:02 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:56:02 [16051] [3] INFO: sendsms used by tester 2008-12-15 09:56:02 [16051] [3] INFO: sendsms sender:tester:tester (127.0.0.1) to:919986131642 msg:Hello world 2008-12-15 09:56:02 [16051] [3] DEBUG: Stored UUID b745-e828-4513-81d8-d015c96e9229 2008-12-15 09:56:02 [16051] [3] DEBUG: message length 11, sending 1 messages 2008-12-15 09:56:02 [16051] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-15 09:56:02 [16051] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-15 09:56:02 [16051] [0] DEBUG: Got ACK (3) of b745-e828-4513-81d8-d015c96e9229 2008-12-15 09:56:02 [16051] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:57:02 [16051] [1] DEBUG: Timeout for fd:24 appeares. 2008-12-15 09:57:02 [16051] [1] DEBUG: HTTP:
Re: Kannel support
currently it is not supported. You must restart kannel to reload conf file modifications |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Mon, Dec 15, 2008 at 8:13 AM, Avinash Pawar // Viva avin...@vivainfomedia.com wrote: Dear sir I have few doubts in kannel :- How to apply changes in smskannel.conf on runtime without stopping kannel? I want to add new smsc group also want to keep changes in throughput as required. Can you please suggest me . Thanks Regards Avinash
Re: Authorization failed for XML post
Yes, those are the correct settings for the username and password. On Mon, Dec 15, 2008 at 5:57 PM, seik s...@4636.org wrote: well then check yous XML settings for the user/pass values is that correct ? : from useruser/user passuser/pass /from Francis Vidal wrote: Okay, tried adding ?username=userpassword=pass to the URL: curl -v -H Content-type: text/xm localhost:8081/cgi-bin/sendsms?username=userpassword=user Here's the output of CURL: * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) POST /cgi-bin/sendsms?username=userpassword=user HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* Content-type: text/xml Content-Length: 17 HTTP/1.1 403 Forbidden Server: Kannel/1.4.1 Content-Length: 32 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 Authorization failed for sendsms On Mon, Dec 15, 2008 at 4:20 PM, seikath seik...@gmail.com wrote: for the curl XML POST request try use the same URL with the userpassword added Francis Vidal wrote: Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: Authorization failed for XML post
This is more informative than the bearerbox logs. I imagine nothing interesting on smsbox logs, right? Could you post your configuration, and the CURL output from your (succesful) GET operation? Seems like your URL is not what kannel expects. BR, Nikos - Original Message - From: Francis Vidal francisv.l...@gmail.com To: seikath seik...@gmail.com Cc: users@kannel.org Sent: Monday, December 15, 2008 11:21 AM Subject: Re: Authorization failed for XML post Okay, tried adding ?username=userpassword=pass to the URL: curl -v -H Content-type: text/xm localhost:8081/cgi-bin/sendsms?username=userpassword=user Here's the output of CURL: * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) POST /cgi-bin/sendsms?username=userpassword=user HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* Content-type: text/xml Content-Length: 17 HTTP/1.1 403 Forbidden Server: Kannel/1.4.1 Content-Length: 32 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 Authorization failed for sendsms On Mon, Dec 15, 2008 at 4:20 PM, seikath seik...@gmail.com wrote: for the curl XML POST request try use the same URL with the userpassword added Francis Vidal wrote: Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: SMPP connection disconnected when request DLR
I might have a idea: Could it be that you only have a TX connection and no RX conn? When you send a message with DLR request, the smsc answers with a message waiting flag. When a smpp TX connection get's a message waiting flag it disconnects and connects a RX connection. So either you have to configure the RX connection or better you try to get a TRX connection, but you cannot receive DLRs over a TX connection. This is only a guess. Maybe you want to send the logfile of your SMPP connection. Regards Falko Am 15.12.2008 um 14:28 schrieb hafez ahmad: Hi, is there any ideas ? , is the problem from kannel side ot the operator side ? Regards, Hafez On Sun, Dec 14, 2008 at 2:46 PM, hafez ahmad hafezad...@gmail.com wrote: Dears, I am using kannel with the DLR group patch, when I send sms without adding the dlr-url and dlr-mask the SMS sent fine and there are no problem like the following: http://localhost:13013/cgi-bin/sendsms?username=testpassword=foocharset=UTF-8coding=2to=text=testfrom=1234smsc=TESTSMSCbinfo=100 but whene I add the dlr-url and dlr-mask to the URL my TX connection dissconected and reconecting like the following: http://localhost:13013/cgi-bin/sendsms?username=testpassword=foocharset=UTF-8coding=2to=text=testfrom=1234smsc=TESTSMSCbinfo=100dlr-mask=31dlr-url=http%3A//localhost/test.php%3Fdl%3D%25d is there any ideas why this happen? Regards, Hafez -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
Error - message in bearerbox
Hello I get thousands off this errors in my bearerbox : 2008-12-12 13:56:33 [22871] [6] ERROR: AT2[MC35]: Generic error: ERROR But MC35-AT-Modem works ? Any suggestion to stop this spaming ? Thank you Gottfried Huber
Re: Hi
Please address such questions to users. I am just another user, with limited time. Your routing is failing. Which smsc are you using and is it ACTIVE? Nikos - Original Message - From: Kaliya perumal To: nbalka...@gmail.com Sent: Monday, December 15, 2008 1:23 PM Subject: Hi I have installed kannel on Ubuntu ,and then i am running my kannel ,it running succesfully ,but when i sending sms,the message was not sent to the destination,whenever i am sending sms ,Queued for later delivery message will show on the browser ,So please provide the approbriate solution for that, When i sending sms through http interface http://127.0.0.1:13131/cgi-bin/sendsms?username=testerpassword=foobarfrom=kaliyato=919986131642text=Hello+world the result is 3: Queued for later delivery Below is my smsbox result 2008-12-15 09:29:48 [16051] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:30:48 [16051] [1] DEBUG: Timeout for fd:24 appeares. 2008-12-15 09:30:48 [16051] [1] DEBUG: HTTP: Destroying HTTPClient area 0x8144b90. 2008-12-15 09:30:48 [16051] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2008-12-15 09:32:52 [16051] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-15 09:32:52 [16051] [2] DEBUG: HTTP: Created HTTPClient area 0x8144b78. 2008-12-15 09:32:52 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:32:52 [16051] [3] DEBUG: Status: 403 Answer: Authorization failed for sendsms 2008-12-15 09:32:52 [16051] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:33:07 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:33:07 [16051] [3] INFO: sendsms used by tester 2008-12-15 09:33:07 [16051] [3] INFO: sendsms sender:tester:tester (127.0.0.1) to:919986131642 msg:Hello world 2008-12-15 09:33:07 [16051] [3] DEBUG: Stored UUID 73e4325c-c16e-46d7-bf5a-faca3428732d 2008-12-15 09:33:07 [16051] [3] DEBUG: message length 11, sending 1 messages 2008-12-15 09:33:07 [16051] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-15 09:33:07 [16051] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-15 09:33:07 [16051] [0] DEBUG: Got ACK (3) of 73e4325c-c16e-46d7-bf5a-faca3428732d 2008-12-15 09:33:07 [16051] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:33:32 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:33:32 [16051] [3] INFO: sendsms used by tester 2008-12-15 09:33:32 [16051] [3] INFO: sendsms sender:tester:tester (127.0.0.1) to:919986131642 msg:Hello world 2008-12-15 09:33:32 [16051] [3] DEBUG: Stored UUID 51962c19-c5b4-4c4d-9e12-158d6a27846f 2008-12-15 09:33:32 [16051] [3] DEBUG: message length 11, sending 1 messages 2008-12-15 09:33:32 [16051] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-15 09:33:32 [16051] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-15 09:33:32 [16051] [0] DEBUG: Got ACK (3) of 51962c19-c5b4-4c4d-9e12-158d6a27846f 2008-12-15 09:33:32 [16051] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:34:32 [16051] [1] DEBUG: Timeout for fd:24 appeares. 2008-12-15 09:34:32 [16051] [1] DEBUG: HTTP: Destroying HTTPClient area 0x8144b78. 2008-12-15 09:34:32 [16051] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2008-12-15 09:56:02 [16051] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-15 09:56:02 [16051] [2] DEBUG: HTTP: Created HTTPClient area 0x8143388. 2008-12-15 09:56:02 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 09:56:02 [16051] [3] INFO: sendsms used by tester 2008-12-15 09:56:02 [16051] [3] INFO: sendsms sender:tester:tester (127.0.0.1) to:919986131642 msg:Hello world 2008-12-15 09:56:02 [16051] [3] DEBUG: Stored UUID b745-e828-4513-81d8-d015c96e9229 2008-12-15 09:56:02 [16051] [3] DEBUG: message length 11, sending 1 messages 2008-12-15 09:56:02 [16051] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-15 09:56:02 [16051] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-15 09:56:02 [16051] [0] DEBUG: Got ACK (3) of b745-e828-4513-81d8-d015c96e9229 2008-12-15 09:56:02 [16051] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-15 09:57:02 [16051] [1] DEBUG: Timeout for fd:24 appeares. 2008-12-15 09:57:02 [16051] [1] DEBUG: HTTP: Destroying HTTPClient area 0x8143388. 2008-12-15 09:57:02 [16051] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2008-12-15 10:09:35 [16051] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-15 10:09:35 [16051] [2] DEBUG: HTTP: Created HTTPClient area 0x8144b60. 2008-12-15 10:09:35 [16051] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-15 10:09:35 [16051] [3] INFO: sendsms used by tester 2008-12-15 10:09:35 [16051] [3] INFO: sendsms sender:tester:kaliya (127.0.0.1)
Re: Start up Error: unknown login: kannel
Try asking BSD mail groups how to set up init scripts in BSD. As far as the rest of Unices, you move the script in /etc/init.d and make an S* link from your default runlevel (rc3.d) - ../init.d/kannel. Cheers, Nikos - Original Message - From: Aldo Zavala a...@cleartalk.net To: Nikos Balkanas nbalka...@gmail.com Sent: Monday, December 15, 2008 10:59 AM Subject: Re: Start up Error: unknown login: kannel Thanks for the reply, how should I do it then? Thanks, Aldo Zavala Mobile (760) 556-5050 GTalk: aldo.zav...@gmail.com - Original Message - From: Nikos Balkanas [mailto:nbalka...@gmail.com] To: users@kannel.org, Aldo Zavala [mailto:a...@cleartalk.net] Sent: Sun, 14 Dec 2008 23:43:28 -0700 Subject: Re: Start up Error: unknown login: kannel That's understood. Who told you to do it like that? - Original Message - From: Aldo Zavala a...@cleartalk.net To: Nikos Balkanas nbalka...@gmail.com; users@kannel.org Sent: Monday, December 15, 2008 8:27 AM Subject: Re: Start up Error: unknown login: kannel I added the line kannel_enable=YES to /etc/rc.conf in order to have the Kannel to start automatically when the system boots. The output of ls -ld /var/run/kannel is: [output] drwxr-xr-x 2 kannel wheel 512 Dec 14 21:10 /var/run/kannel [/output] And this is what top command shows: [top] PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 644 kannel 13 960 16916K 3860K ucond 0 0:01 0.00% bearerbox 737 mysql 10 960 62148K 20828K ucond 1 0:01 0.00% mysqld 688 root1 960 5896K 2348K select 0 0:00 0.00% nmbd 747 root1 960 26956K 14056K select 0 0:00 0.00% httpd 699 root1 960 7680K 5728K select 0 0:00 0.00% perl5.8.8 766 root1 960 5848K 3188K select 0 0:00 0.00% sendmail 654 kannel 1 80 7188K 2204K nanslp 0 0:00 0.00% run_kannel_bo 834 aldo1 960 8384K 3804K select 1 0:00 0.00% sshd 671 root1 960 3284K 2304K select 0 0:00 0.00% proftpd 666 kannel 9 960 16404K 3816K select 1 0:00 0.00% wapbox 831 root1 40 8384K 3824K sbwait 0 0:00 0.00% sshd 1234 root1 40 8384K 3832K sbwait 0 0:00 0.00% sshd 532 root1 960 3156K 1196K select 1 0:00 0.00% syslogd 776 root1 80 3184K 1248K nanslp 0 0:00 0.00% cron 692 root1 960 8088K 3748K select 0 0:00 0.00% smbd 1244 root1 200 4452K 2428K pause 0 0:00 0.00% csh [/top] - Original Message - From: Nikos Balkanas [mailto:nbalka...@gmail.com] To: users@kannel.org, Aldo Zavala [mailto:a...@cleartalk.net] Sent: Sun, 14 Dec 2008 23:08:38 -0700 Subject: Re: Start up Error: unknown login: kannel So you say that now you can log into radius as kannel without any passwords? Doesn't sound very safe. You shouldn't create the pid-files. What is the output from ls -ld /var/run/kannel/ ? BR, Nikos - Original Message - From: Aldo Zavala a...@cleartalk.net To: users@kannel.org; Nikos Balkanas nbalka...@gmail.com Sent: Monday, December 15, 2008 1:56 AM Subject: Re: Start up Error: unknown login: kannel Hello, now I have another error; I used the adduser command to add the kannel user (I dont know if there are another way to create a daemon user) This is what I did (according to an advice in the freebsd forums) radius# adduser Username: kannel Full name: Uid (Leave empty for default): Login group [kannel]: Login group is kannel. Invite kannel into other groups? []: Login class [default]: Shell (sh csh tcsh nologin) [sh]: Home directory [/home/kannel]: Use password-based authentication? [yes]: no Lock out the account after creation? [no]: Username : kannel Password : disabled Full Name : Uid: 1004 Class : Groups : kannel Home : /home/kannel Shell : /bin/sh Locked : no OK? (yes/no): yes adduser: INFO: Successfully added (kannel) to the user database. Add another user? (yes/no): no Goodbye! * And this is the error that now I am getting: radius# /usr/local/etc/rc.d/kannel start Starting kannel_bearerbox. /usr/local/sbin/run_kannel_box: open: /var/run/kannel/kannel_bearerbox.pid: No such file or directory Starting kannel_smsbox. /usr/local/sbin/run_kannel_box: open: /var/run/kannel/kannel_smsbox.pid: No such file or directory Starting kannel_wapbox. /usr/local/sbin/run_kannel_box: open: /var/run/kannel/kannel_wapbox.pid: No such file or directory radius# * Then I created manually the pid files, and after trying to start the kannel daemon again I got these errors: radius# /usr/local/etc/rc.d/kannel start Starting kannel_bearerbox. /usr/local/sbin/run_kannel_box: open: /var/run/kannel/kannel_bearerbox.pid: Permission denied Starting kannel_smsbox. /usr/local/sbin/run_kannel_box: open: /var/run/kannel/kannel_smsbox.pid:
src compiling failed... dont know why =(
Hello, I found buggy the FreeBSD Kannel port, so I tried to install it from latest source, I am following the INSTALL instructions, and I get this error when hit make command, do you guys know what this means? or how can I fix this? [output] radius# make ar rc libgw.a ranlib libgw.a ar rc libwmlscript.a ranlib libwmlscript.a ar rc libwap.a ranlib libwap.a ar rc libgwlib.a ranlib libgwlib.a gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o wmlscript/wmlsc.o -c wmlscript/wmlsc.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o wmlscript/wmlsdasm.o -c wmlscript/wmlsdasm.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o utils/seewbmp.o -c utils/seewbmp.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o utils/mtbatch.o -c utils/mtbatch.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o gw/bearerbox.o -c gw/bearerbox.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o gw/smsbox.o -c gw/smsbox.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o gw/wapbox.o -c gw/wapbox.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o utils/run_kannel_box.o -c utils/run_kannel_box.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o wmlscript/wmlsc wmlscript/wmlsc.o libgw.a libwmlscript.a libwap.a libgwlib.a -lssl -lrt -lm -lkse -L/usr/local/lib -lxml2 -lz -L/usr/local/lib -liconv -lm -L/usr/lib -lcrypto -lssl wmlscript/wmlsc.o(.text+0x125): In function `main': wmlscript/wmlsc.c:177: undefined reference to `ws_create' wmlscript/wmlsc.o(.text+0x1ea):wmlscript/wmlsc.c:236: undefined reference to `ws_compile_data' wmlscript/wmlsc.o(.text+0x236):wmlscript/wmlsc.c:248: undefined reference to `ws_free_byte_code' wmlscript/wmlsc.o(.text+0x32c):wmlscript/wmlsc.c:251: undefined reference to `ws_compile_file' wmlscript/wmlsc.o(.text+0x341):wmlscript/wmlsc.c:267: undefined reference to `ws_destroy' wmlscript/wmlsc.o(.text+0x3f1):wmlscript/wmlsc.c:260: undefined reference to `ws_result_to_string' wmlscript/wmlsc.o(.text+0x4f7): In function `pragma_meta': wmlscript/wmlsc.c:298: undefined reference to `ws_utf8_to_latin1' wmlscript/wmlsc.o(.text+0x511):wmlscript/wmlsc.c:299: undefined reference to `ws_utf8_to_latin1' wmlscript/wmlsc.o(.text+0x52e):wmlscript/wmlsc.c:300: undefined reference to `ws_utf8_to_latin1' wmlscript/wmlsc.o(.text+0x5ac):wmlscript/wmlsc.c:313: undefined reference to `ws_utf8_free_data' wmlscript/wmlsc.o(.text+0x5b4):wmlscript/wmlsc.c:314: undefined reference to `ws_utf8_free_data' wmlscript/wmlsc.o(.text+0x5c3):wmlscript/wmlsc.c:315: undefined reference to `ws_utf8_free_data' *** Error code 1 Stop in /gateway-1.4.1. [/output] Thanks, Aldo Zavala
Re: src compiling failed... dont know why =(
What is the output of your configure script? - Original Message - From: Aldo Zavala a...@cleartalk.net To: users@kannel.org Sent: Monday, December 15, 2008 9:16 PM Subject: src compiling failed... dont know why =( Hello, I found buggy the FreeBSD Kannel port, so I tried to install it from latest source, I am following the INSTALL instructions, and I get this error when hit make command, do you guys know what this means? or how can I fix this? [output] radius# make ar rc libgw.a ranlib libgw.a ar rc libwmlscript.a ranlib libwmlscript.a ar rc libwap.a ranlib libwap.a ar rc libgwlib.a ranlib libgwlib.a gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o wmlscript/wmlsc.o -c wmlscript/wmlsc.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o wmlscript/wmlsdasm.o -c wmlscript/wmlsdasm.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o utils/seewbmp.o -c utils/seewbmp.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o utils/mtbatch.o -c utils/mtbatch.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o gw/bearerbox.o -c gw/bearerbox.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o gw/smsbox.o -c gw/smsbox.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o gw/wapbox.o -c gw/wapbox.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o utils/run_kannel_box.o -c utils/run_kannel_box.c gcc -D_REENTRANT=1 -I. -Igw -g -O2 -pthread -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/include/openssl -o wmlscript/wmlsc wmlscript/wmlsc.o libgw.a libwmlscript.a libwap.a libgwlib.a -lssl -lrt -lm -lkse -L/usr/local/lib -lxml2 -lz -L/usr/local/lib -liconv -lm -L/usr/lib -lcrypto -lssl wmlscript/wmlsc.o(.text+0x125): In function `main': wmlscript/wmlsc.c:177: undefined reference to `ws_create' wmlscript/wmlsc.o(.text+0x1ea):wmlscript/wmlsc.c:236: undefined reference to `ws_compile_data' wmlscript/wmlsc.o(.text+0x236):wmlscript/wmlsc.c:248: undefined reference to `ws_free_byte_code' wmlscript/wmlsc.o(.text+0x32c):wmlscript/wmlsc.c:251: undefined reference to `ws_compile_file' wmlscript/wmlsc.o(.text+0x341):wmlscript/wmlsc.c:267: undefined reference to `ws_destroy' wmlscript/wmlsc.o(.text+0x3f1):wmlscript/wmlsc.c:260: undefined reference to `ws_result_to_string' wmlscript/wmlsc.o(.text+0x4f7): In function `pragma_meta': wmlscript/wmlsc.c:298: undefined reference to `ws_utf8_to_latin1' wmlscript/wmlsc.o(.text+0x511):wmlscript/wmlsc.c:299: undefined reference to `ws_utf8_to_latin1' wmlscript/wmlsc.o(.text+0x52e):wmlscript/wmlsc.c:300: undefined reference to `ws_utf8_to_latin1' wmlscript/wmlsc.o(.text+0x5ac):wmlscript/wmlsc.c:313: undefined reference to `ws_utf8_free_data' wmlscript/wmlsc.o(.text+0x5b4):wmlscript/wmlsc.c:314: undefined reference to `ws_utf8_free_data' wmlscript/wmlsc.o(.text+0x5c3):wmlscript/wmlsc.c:315: undefined reference to `ws_utf8_free_data' *** Error code 1 Stop in /gateway-1.4.1. [/output] Thanks, Aldo Zavala
Building a test environment
We're looking at building a test enviroment to evaluation of updates from our development team. After reviewing the documentation, I understand that I can setup multiple fakesmsc's. What I'm hoping for is to use one fakesmsc to send messages to the others. My understanding of the msg flow would be that my MO-fakesmsc would send messages through the bearerbox on to the smsbox (based on routing) and then onto the final fakesmsc's. Is this assumption correct? Richard Andrews
Cell phone companes - will they shut me down?
First I want to preface I'm in the USA. If I were to use a GSM modem and have an unlimited text plan, would I be shutdown for a high volume of SMS's? Or at what point would I be shut down? Is there anything else to worry about? Thanks Scott
Re: src compiling failed... dont know why =(
I think I see your problem. You seem to be missing libiconv. You need to get it for kannel. I am surprised that configure didn't fail because of that. Also it wouldn't heart to get pcre. BTW, 1.4.1 is ~4 years old. Download the latest CVS from the site. BR, Nikos - Original Message - From: Aldo Zavala a...@cleartalk.net To: Nikos Balkanas nbalka...@gmail.com; users@kannel.org Sent: Monday, December 15, 2008 9:38 PM Subject: Re: src compiling failed... dont know why =( Here the output of the ./configure , thanks for the reply. [output] radius# ./configure Configuring for Kannel gateway version 1.4.1 ... Running system checks ... checking build system type... i386-unknown-freebsd7.0 checking host system type... i386-unknown-freebsd7.0 checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for bison... no checking for byacc... byacc checking for flex... flex checking for yywrap in -lfl... yes checking lex output file root... lex.yy checking whether yytext is a pointer... yes checking for convert... no checking for perl... /usr/bin/perl checking for pthread_exit in -lc_r... no checking for pthread_exit in -lkse... yes checking for inline... inline checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for _LARGE_FILES value needed for large files... no checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for short... yes checking size of short... 2 checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 4 checking for long long... yes checking size of long long... 8 checking for log in -lm... yes checking for accept in -lsocket... no checking for inet_ntoa in -lnsl... no checking for inet_ntop in -lresolv... no checking for inet_ntop in -lbind... no checking for libiconv in -liconv... no checking for ANSI C header files... (cached) yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for sys/types.h... (cached) yes checking for unistd.h... (cached) yes checking sys/poll.h usability... yes checking sys/poll.h presence... yes checking for sys/poll.h... yes checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking iconv.h usability... no checking iconv.h presence... no checking for iconv.h... no checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking execinfo.h usability... no checking execinfo.h presence... no checking for execinfo.h... no checking for stdlib.h... (cached) yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/sockio.h usability... yes checking sys/sockio.h presence... yes checking for sys/sockio.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking for net/if.h... yes checking for gettimeofday... yes checking for select... yes checking for socket... yes checking for strdup... yes checking for getopt_long... yes checking for localtime_r... yes checking for gmtime_r... yes checking for backtrace... no checking for srandom... yes checking for getopt... yes checking for gethostbyname_r... yes checking for which type of gethostbyname_r... 6 checking for socklen_t in sys/socket.h... yes checking for getopt in stdio.h... no checking for getopt in unistd.h... yes checking regex.h usability... yes checking regex.h presence... yes checking for regex.h... yes checking for regcomp... yes Checking for POSIX threads support ... checking for working pthreads... yes checking for pthread_spinlock support... yes checking for pthread_rwlock support... yes checking for sem_init in -lrt... yes checking for semaphore support... yes Checking for libxml2 support ... checking for
Re: Building a test environment
fakesmsc is the client. It uses 2 modes: interactive and batch. In interactive mode it won't get only the messages it sent, but also messages sent by other means (i.e. ppg). Of course they need to be routed through fake smsc. It will get also DLRs when used by another service (i.e. ppg) but not when sending MOs by itself. I have submited a patch for that, but so far it hasn't been implemented. I have not tried a lot of fake smscs, but the client, fakesmsc, will receive its own messages. I use ppg - fakesmsc for testing purposes. BR, Nikos - Original Message - From: Richard Andrews randr...@pelmorex.com To: users@kannel.org Sent: Monday, December 15, 2008 10:10 PM Subject: Building a test environment We're looking at building a test enviroment to evaluation of updates from our development team. After reviewing the documentation, I understand that I can setup multiple fakesmsc's. What I'm hoping for is to use one fakesmsc to send messages to the others. My understanding of the msg flow would be that my MO-fakesmsc would send messages through the bearerbox on to the smsbox (based on routing) and then onto the final fakesmsc's. Is this assumption correct? Richard Andrews
Re: Cell phone companes - will they shut me down?
A company I consulted for once opened a few unlimited text plans Cingular for testing an M2M system. At the end of the first month they got a 5,460-page bill. The bill was only $30, but Cingular turned off the accounts after that. You mileage may vary. On Dec 15, 2008, at 1:27 PM, Scott wrote: First I want to preface I’m in the USA. If I were to use a GSM modem and have an unlimited text plan, would I be shutdown for a high volume of SMS’s? Or at what point would I be shut down? Is there anything else to worry about? Thanks Scott David A. Burgess Kestrel Signal Processing, Inc.
Re: Authorization failed for XML post
/var/log/kannel/smsbox.log: 2008-12-16 12:14:49 [4507] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-16 12:14:49 [4507] [2] DEBUG: HTTP: Created HTTPClient area 0x97aefd0. 2008-12-16 12:14:49 [4507] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-16 12:14:49 [4507] [3] INFO: sendsms used by user 2008-12-16 12:14:49 [4507] [3] INFO: sendsms sender:user:+ (127.0.0.1) to:+ msg:Hello world 2008-12-16 12:14:49 [4507] [3] DEBUG: Stored UUID e6669b3d-6b61-4956-a9ae-24d302a395cc 2008-12-16 12:14:49 [4507] [3] DEBUG: message length 11, sending 1 messages 2008-12-16 12:14:49 [4507] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-16 12:14:49 [4507] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-16 12:14:49 [4507] [0] DEBUG: Got ACK (0) of e6669b3d-6b61-4956-a9ae-24d302a395cc 2008-12-16 12:14:49 [4507] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-16 12:14:49 [4507] [1] DEBUG: HTTP: Destroying HTTPClient area 0x97aefd0. 2008-12-16 12:14:49 [4507] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. CURL output (verbose): curl -v http://localhost:8081/cgi-bin/sendsms?user=userpass=userto=09213116180text=Hello+world; * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) GET /cgi-bin/sendsms?user=userpass=userto=09213116180text=Hello+world HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* HTTP/1.1 202 Accepted Server: Kannel/1.4.1 Content-Length: 24 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 0: Accepted for delivery On Mon, Dec 15, 2008 at 6:37 PM, Nikos Balkanas nbalka...@gmail.com wrote: This is more informative than the bearerbox logs. I imagine nothing interesting on smsbox logs, right? Could you post your configuration, and the CURL output from your (succesful) GET operation? Seems like your URL is not what kannel expects. BR, Nikos - Original Message - From: Francis Vidal francisv.l...@gmail.com To: seikath seik...@gmail.com Cc: users@kannel.org Sent: Monday, December 15, 2008 11:21 AM Subject: Re: Authorization failed for XML post Okay, tried adding ?username=userpassword=pass to the URL: curl -v -H Content-type: text/xm localhost:8081/cgi-bin/sendsms?username=userpassword=user Here's the output of CURL: * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) POST /cgi-bin/sendsms?username=userpassword=user HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* Content-type: text/xml Content-Length: 17 HTTP/1.1 403 Forbidden Server: Kannel/1.4.1 Content-Length: 32 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 Authorization failed for sendsms On Mon, Dec 15, 2008 at 4:20 PM, seikath seik...@gmail.com wrote: for the curl XML POST request try use the same URL with the userpassword added Francis Vidal wrote: Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message I can send SMS using the normal HTTP method (i.e. http://localhost:8081/cgi-bin/sendsms?user=userpass=user;...) but when I use the CURL method above, I get Authorization failed. What am I doing wrong?
Re: Authorization failed for XML post
Dear Francis, I see a possible problem by Curl. In POST it sends Content-Length: 17, when the length of the xml file 50. This normally would lead to broken requests (bad requests), but since 17 characters end before the user credentials maybe it leads lto Forbidden access. This is further supported from bearerbox logs. It is not rejected by smsbox (server failed access), but after parsing the XML, bearerbox rejects it and generates 403. 3 things: 1) Remove all credentials from your configure file and XML and run the POST again. If possible get tcpdump, to capture exactly what curl sents. Expect to fail but with a different cause. 2) You need better logs. Reenable credentials please run: script bearerbox conffile smsbox conffile In another terminal run the curl POST w/credentials. 3) Test by hand: telnet 127.0.0.1 8081 POST /cgi-bin/sendsms HTTP/1.1 Host: localhost:8081 Content-Length: 270verify length by yourself. Every new line is 2 characters (\r\n) Content-type: text/html ?xml version=1.0 encoding=ISO-8859-1? message submit danumberthe_number/number/da udAnother+test+sms/ud !-- request from Kannel to application -- from useruser/user passuser/pass /from /submit /message Let me know how it goes, Nikos - Original Message - From: Francis Vidal francisv.l...@gmail.com To: users@kannel.org Sent: Tuesday, December 16, 2008 6:20 AM Subject: Re: Authorization failed for XML post /var/log/kannel/smsbox.log: 2008-12-16 12:14:49 [4507] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2008-12-16 12:14:49 [4507] [2] DEBUG: HTTP: Created HTTPClient area 0x97aefd0. 2008-12-16 12:14:49 [4507] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2008-12-16 12:14:49 [4507] [3] INFO: sendsms used by user 2008-12-16 12:14:49 [4507] [3] INFO: sendsms sender:user:+ (127.0.0.1) to:+ msg:Hello world 2008-12-16 12:14:49 [4507] [3] DEBUG: Stored UUID e6669b3d-6b61-4956-a9ae-24d302a395cc 2008-12-16 12:14:49 [4507] [3] DEBUG: message length 11, sending 1 messages 2008-12-16 12:14:49 [4507] [3] DEBUG: Status: 202 Answer: Sent. 2008-12-16 12:14:49 [4507] [3] DEBUG: Delayed reply - wait for bearerbox 2008-12-16 12:14:49 [4507] [0] DEBUG: Got ACK (0) of e6669b3d-6b61-4956-a9ae-24d302a395cc 2008-12-16 12:14:49 [4507] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2008-12-16 12:14:49 [4507] [1] DEBUG: HTTP: Destroying HTTPClient area 0x97aefd0. 2008-12-16 12:14:49 [4507] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. CURL output (verbose): curl -v http://localhost:8081/cgi-bin/sendsms?user=userpass=userto=09213116180text=Hello+world; * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) GET /cgi-bin/sendsms?user=userpass=userto=09213116180text=Hello+world HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* HTTP/1.1 202 Accepted Server: Kannel/1.4.1 Content-Length: 24 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 0: Accepted for delivery On Mon, Dec 15, 2008 at 6:37 PM, Nikos Balkanas nbalka...@gmail.com wrote: This is more informative than the bearerbox logs. I imagine nothing interesting on smsbox logs, right? Could you post your configuration, and the CURL output from your (succesful) GET operation? Seems like your URL is not what kannel expects. BR, Nikos - Original Message - From: Francis Vidal francisv.l...@gmail.com To: seikath seik...@gmail.com Cc: users@kannel.org Sent: Monday, December 15, 2008 11:21 AM Subject: Re: Authorization failed for XML post Okay, tried adding ?username=userpassword=pass to the URL: curl -v -H Content-type: text/xm localhost:8081/cgi-bin/sendsms?username=userpassword=user Here's the output of CURL: * About to connect() to localhost port 8081 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8081 (#0) POST /cgi-bin/sendsms?username=userpassword=user HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 Host: localhost:8081 Accept: */* Content-type: text/xml Content-Length: 17 HTTP/1.1 403 Forbidden Server: Kannel/1.4.1 Content-Length: 32 Content-type: text/html Pragma: no-cache Cache-Control: no-cache * Connection #0 to host localhost left intact * Closing connection #0 Authorization failed for sendsms On Mon, Dec 15, 2008 at 4:20 PM, seikath seik...@gmail.com wrote: for the curl XML POST request try use the same URL with the userpassword added Francis Vidal wrote: Hi all, I'm trying to send a test SMS message using CURL: curl -v -H Content-type: text/xml -d test.xml http://localhost:8081/cgi-bin/sendsms Here's the content of test.xml: ?xml
