Re: SMPP implementation in current CVS build

2002-01-29 Thread Stipe Tolj
Alex Judd wrote: > > Illogical and strange but thanks for looking at it (and the fix). > > We don't check for host as a default config value either so you get an > octstr error if you don't specify it. Quick diff fix for that. > > # cvs diff -u gw/smsc_smpp.c > Index: gw/smsc_smpp.c > =

Re: SMPP implementation in current CVS build

2002-01-29 Thread Alex Judd
Illogical and strange but thanks for looking at it (and the fix). We don't check for host as a default config value either so you get an octstr error if you don't specify it. Quick diff fix for that. # cvs diff -u gw/smsc_smpp.c Index: gw/smsc_smpp.c

Re: SMPP implementation in current CVS build

2002-01-28 Thread Stipe Tolj
Andreas Fink wrote: > > >Alex Judd wrote: > >> > >> Just my luck that I upgrade to a SMPP connection and have lots of fun > >> trying to get Kannel to run with it :) From my (brief) investigations it > >> looks like the way that gwthread_create is implemented has changed - so > >> that the ol

Re: SMPP implementation in current CVS build

2002-01-28 Thread Andreas Fink
>Alex Judd wrote: >> >> Just my luck that I upgrade to a SMPP connection and have lots of fun >> trying to get Kannel to run with it :) From my (brief) investigations it >> looks like the way that gwthread_create is implemented has changed - so >> that the old format of the function passes the

Re: SMPP implementation in current CVS build

2002-01-28 Thread Alex Judd
I'm pretty sure there is definitely something broken in the CVS SMPP code as with a default CIMD SMSC in the config file the program works fine, and with the default SMPP SMSC in the config file kannel has the mutex locking problem CIMD # gw/bearerbox cimd.conf System SunOS, release 5.8, vers

Re: SMPP implementation in current CVS build

2002-01-28 Thread Alex Judd
> > 2002-01-27 19:08:48 [5] PANIC: mutex_lock: Managed to lock the mutex twice! > > Alex and Nisan, can you both please check if the recent change I > commited to smsc_smpp.c has broke something for you? Even while I > think it should not. The version I checked out from cvs is pre those changes

Re: SMPP implementation in current CVS build

2002-01-27 Thread Stipe Tolj
Alex Judd wrote: > > > We havent seen this behavior. Please could you send us some beaererbox logs. > > 2002-01-27 19:08:48 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) > 2002-01-27 19:08:48 [0] DEBUG: Started thread 2 > (gwlib/http.c:server_thread) > 2002-01-27 19:08:48 [0] DEBUG: Started

Re: SMPP implementation in current CVS build

2002-01-27 Thread Stipe Tolj
Alex Judd wrote: > > Just my luck that I upgrade to a SMPP connection and have lots of fun > trying to get Kannel to run with it :) From my (brief) investigations it > looks like the way that gwthread_create is implemented has changed - so > that the old format of the function passes the wrong pa

Re: SMPP implementation in current CVS build

2002-01-27 Thread Alex Judd
> We havent seen this behavior. Please could you send us some beaererbox logs. 2002-01-27 19:08:48 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2002-01-27 19:08:48 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2002-01-27 19:08:48 [0] DEBUG: Started thread 3 (gw/bb_http.c:httpad

Re: SMPP implementation in current CVS build

2002-01-27 Thread Nisan Bloch
Hi Alex At 02:00 PM 1/27/02 -0600, Alex Judd wrote: >With the SMPP code this causes the mutex lock code to try and lock the >same mutex twice and hence panics the box. > >Before I look into moving the smpp code to a format similar to smsc_emi2 >or smsc_http has anyone already done this or is ther

SMPP implementation in current CVS build

2002-01-27 Thread Alex Judd
Just my luck that I upgrade to a SMPP connection and have lots of fun trying to get Kannel to run with it :) From my (brief) investigations it looks like the way that gwthread_create is implemented has changed - so that the old format of the function passes the wrong parameters to it - for exa