Please attach your config file so that we can see what you missed out.

Try lynx -dump 'http://localhost:13015/cgi-bin/sendsms?
from=0987654321&to12345&username=nork&password=z0rk<http://localhost:13015/?from=0987654321&to12345&username=nork&password=z0rk>&smsc=<your
smsc id>'

On Fri, Aug 31, 2012 at 5:55 AM, Willy Mularto <sangpr...@gmail.com> wrote:

> Just compiled the latest svn execute the bearerbox:
> 2012-08-31 09:54:35 [28393] [0] INFO: HTTP[kannel]: Initiated and ready
> 2012-08-31 09:54:35 [28393] [8] DEBUG: Thread 8
> (gw/smsc/smsc_http.c:httpsmsc_send_cb) maps to pid 28393.
> 2012-08-31 09:54:35 [28393] [0] DEBUG: Started thread 10
> (gw/bb_smscconn.c:sms_router)
>
> Try to hit it:
> sprabv@smsgw1:~/gw/test$ lynx -dump 
> 'http://localhost:13015/?from=0987654321&to12345&username=nork&password=z0rk&smsc-id=<your
> smsc 
> id><http://localhost:13015/?from=0987654321&to12345&username=nork&password=z0rk>
> '
>
> Looking up localhost:13015
> Making HTTP connection to localhost:13015
> Sending HTTP request.
> HTTP request sent; waiting for response.
> Alert!: Unexpected network read error; connection aborted.
> Can't Access `
> http://localhost:13015/?from=0987654321&to12345&username=nork&password=z0rk
> '
> Alert!: Unable to access document.
>
> lynx: Can't access startfile
>
>
> The log said:
> 2012-08-31 09:54:43 [28393] [7] DEBUG: HTTP[kannel]: Got request
> `/?&from=0987654321&to12345=&username=nork&password=z0rk'
> 2012-08-31 09:54:43 [28393] [7] PANIC: sbin/bearerbox() [0x49257c]
> 2012-08-31 09:54:43 [28393] [7] PANIC: /lib/libpthread.so.0(+0xf8f0)
> [0x7f0b2c5a18f0]
> 2012-08-31 09:54:43 [28393] [7] PANIC: sbin/bearerbox() [0x44e1f8]
> 2012-08-31 09:54:43 [28393] [7] PANIC: sbin/bearerbox() [0x47e5be]
> 2012-08-31 09:54:43 [28393] [7] PANIC: /lib/libpthread.so.0(+0x69ca)
> [0x7f0b2c5989ca]
> 2012-08-31 09:54:43 [28393] [7] PANIC: /lib/libc.so.6(clone+0x6d)
> [0x7f0b2bfa5cdd]
>
> The weird is bearerbox can't identify the smsc-id name. It is said null
>
>
>
>
> Willy Mularto
> F300HD+MR18DE (NLC1725)
>
>
>
>
>
>
>
>
>
>
>

Reply via email to