are you able to connect manually using tip or cu?

cheers

iain

On Thu, 5 Oct 2006, Adam Block wrote:

Hi. I posted this a couple times -- I compiled Kannel with minimal problems
but can't get bearerbox to come up properly. It gets into a failure loop,
logging: "System error 35: Resource
temporarily unavailable". Details below. Any thoughts on solving this would
be much appreciated!

/afb



On 9/24/06, Adam Block <[EMAIL PROTECTED]> wrote:
>
> I'm running Kannel 1.4.0 on Mac OS X 10.4.7.
>
> I have a Wavecom WMOD2 connected to the computer with a Keyspan
> USB-Serial converter at /dev/tty.KeySerial1. The serial connection
> works fine with minicom, serial APIs for Ruby and Perl, etc. I can
> manually send SMS using minicom (and an AT command reference guide :)
> ).
>
> My configuration file looks like this:
>
> group = core
> admin-port = 13000
> admin-password = XXXXXX
> status-password = XXXXXX
> log-file = "/tmp/kannel.log"
> log-level = 0
> access-log = "access.log"
> smsbox-port = 13001
>
> include = "modems.conf"
>
> # SMSC GSM
> group = smsc
> smsc = at
> modemtype = wavecom
> device = "/dev/tty.KeySerial1"
> speed = 9600
>
> # SMSBOX SETUP
> group = smsbox
> bearerbox-host = localhost
> sendsms-port = 13013
> log-file = "/tmp/smsbox.log"
> log-level = 0
>
> Modems.conf is unchanged from the default that ships with the distro.
>
> When I start bearerbox, I get the following debug output:
>
> 2006-09-24 14:05:18 [5523] [0] INFO: Debug_lvl = -1, log_file =
> <none>, log_lvl = 0
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Loading include file
> `modems.conf' (on line 10 of file kannel.conf).
> 2006-09-24 14:05:18 [5523] [0] WARNING: DLR: using default 'internal'
> for storage type.
> 2006-09-24 14:05:18 [5523] [0] INFO: DLR using storage type: internal
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Kannel bearerbox version `1.4.0'.
> Build `Sep 24 2006 13:16:14', compiler `4.0.1 (Apple Computer, Inc.
> build 5250)'.
> System Darwin, release 8.7.3, version Darwin Kernel Version 8.7.3: Wed
> Aug 16 18:54:06 PDT 2006; root:xnu-792.11.5.obj~1/RELEASE_I386,
> machine i386.
> Hostname XXXXXX
> Libxml version 2.6.16.
> Using native malloc.
>
> 2006-09-24 14:05:18 [5523] [0] INFO: Added logfile `/tmp/kannel.log'
> with level `0'.
> 2006-09-24 14:05:18 [5523] [0] INFO: Started access logfile
> `access.log'.
> 2006-09-24 14:05:18 [5523] [0] INFO: SSL not supported, no SSL
> initialization done.
> 2006-09-24 14:05:18 [5523] [0] INFO: HTTP: Opening server at port 13000.
>
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 1
> (gwlib/fdset.c:poller)
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 2
> (gwlib/http.c:server_thread)
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 3
> (gw/bb_http.c:httpadmin_run)
> 2006-09-24 14:05:18 [5523] [0] DEBUG: starting smsbox connection module
> 2006-09-24 14:05:18 [5523] [0] INFO: BOXC: 'smsbox-max-pending' not
> set, using default (100).
> 2006-09-24 14:05:18 [5523] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller)
> maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 4
> (gw/bb_boxc.c:sms_to_smsboxes)
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 5
> (gw/bb_boxc.c:smsboxc_run)
> 2006-09-24 14:05:18 [5523] [2] DEBUG: Thread 2
> (gwlib/http.c:server_thread) maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [3] DEBUG: Thread 3
> (gw/bb_http.c:httpadmin_run) maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [4] DEBUG: Thread 4
> (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [0] INFO: DLR rerouting for smsc id
> <(null)> disabled.
> 2006-09-24 14:05:18 [5523] [5] DEBUG: Thread 5
> (gw/bb_boxc.c:smsboxc_run) maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [0] INFO: AT2[/dev/tty.KeySerial1]:
> configuration shows modemtype <wavecom>
> 2006-09-24 14:05:18 [5523] [0] DEBUG: AT2[/dev/tty.KeySerial1]:
> Reading modem definitions from <kannel.conf>
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Loading include file
> `modems.conf' (on line 10 of file kannel.conf).
> 2006-09-24 14:05:18 [5523] [0] DEBUG: AT2[/dev/tty.KeySerial1]: Found
> <11> modems in config
> 2006-09-24 14:05:18 [5523] [0] INFO: AT2[/dev/tty.KeySerial1]: read
> modem definition for <Wavecom>
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 6
> (gw/smsc/smsc_at.c:at2_device_thread)
> 2006-09-24 14:05:18 [5523] [6] DEBUG: Thread 6
> (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [6] INFO: AT2[/dev/tty.KeySerial1]: opening
> device
> 2006-09-24 14:05:18 [5523] [0] DEBUG: Started thread 7
> (gw/bb_smscconn.c:sms_router)
> 2006-09-24 14:05:18 [5523] [7] DEBUG: Thread 7
> (gw/bb_smscconn.c:sms_router) maps to pid 5523.
> 2006-09-24 14:05:18 [5523] [0] INFO:
> ----------------------------------------
> 2006-09-24 14:05:18 [5523] [7] DEBUG: sms_router: time to sleep
> 2006-09-24 14:05:18 [5523] [0] INFO: Kannel bearerbox II version 1.4.0starting
> 2006-09-24 14:05:18 [5523] [0] INFO: MAIN: Start-up done, entering
> mainloop
> 2006-09-24 14:05:18 [5523] [0] DEBUG: AT2[/dev/tty.KeySerial1]: start
> called
> 2006-09-24 14:05:18 [5523] [7] DEBUG: sms_router: list_len = 0
> 2006-09-24 14:05:18 [5523] [6] DEBUG: AT2[/dev/tty.KeySerial1]: device
> opened
> 2006-09-24 14:05:19 [5523] [6] DEBUG: AT2[/dev/tty.KeySerial1]: device
> opened
> 2006-09-24 14:05:19 [5523] [6] INFO: AT2[/dev/tty.KeySerial1]: init
> device
> 2006-09-24 14:05:19 [5523] [6] INFO: AT2[/dev/tty.KeySerial1]: speed set
> to 9600
> 2006-09-24 14:05:19 [5523] [6] DEBUG: AT2[/dev/tty.KeySerial1]: -->
> ATZ^M
> 2006-09-24 14:05:22 [5523] [6] ERROR: AT2[/dev/tty.KeySerial1]:
> Couldnot write to device.
> 2006-09-24 14:05:22 [5523] [6] ERROR: System error 35: Resource
> temporarily unavailable
> 2006-09-24 14:05:26 [5523] [6] ERROR: AT2[/dev/tty.KeySerial1]:
> Opening failed. Terminating
> 2006-09-24 14:05:26 [5523] [6] INFO: AT2[/dev/tty.KeySerial1]: closing
> device
>
> Then bearerbox proceeds to repeatedly try to connect to the modem,
> with the same sequence of errors as the last 10 lines of the log file
> shown above.
>
> If I run minicom at the same time as bearerbox -- this should cause
> problems but I was curious -- I can see that 'ATZ' is being sent and
> the modem is responding with 'OK'. Bearerbox doesn't seem to see the
> response, though.
>
> Any ideas why the application is having trouble connecting to the modem?
>
> Thanks!
>
> /afb
>




Reply via email to