Correction:

(1) bearerbox will panic if cannot access the spool directory when starting up. 
So apparently permissions were right when it started and then someone changed 
them.
(2) Store queue is used by outgoing SMS, not incoming.

Is that clear?
Nikos
  ----- Original Message ----- 
  From: Tony Kirkham 
  To: Nikos Balkanas 
  Cc: Alvaro Cornejo ; [email protected] 
  Sent: Tuesday, March 31, 2009 10:09 PM
  Subject: Re: SMS receiving quit working


  That is extremely interesting.  I would like to better understand this so 
allow me to give the specific details,  that I can remember, and maybe 
something will shake loose.

  Through out this process nearly 200 SMSs are sent each day so Kannel was 
actively sending.
  - I set up my new config files and restarted Kannel.  Messages were sent just 
fine for several days.
  - From a phone I sent a couple of messages to one of the modem numbers.
  - I looked at the status via http.../status request to simply see that kannel 
got the messages.
  - Nothing was received.
  - I restarted Kannel and tried the same steps again. - No change
  - I ask the question on the users mailing list
  - A few days went by (SMSs being sent fine each day)
  - I looked at the bearerbox log and saw:
  ...
  2009-03-30 14:05:49 [13054] [17] DEBUG: boxc_receiver: sms received
  2009-03-30 14:05:49 [13054] [17] ERROR: Could not create directory 
`/var/spool/kannel/spool//2'.
  2009-03-30 14:05:49 [13054] [17] ERROR: System error 13: Permission denied
  2009-03-30 14:05:49 [13054] [17] DEBUG: send_msg: sending msg to box: 
<127.0.0.1>
  ...
  - I realized that I hadn't set permissions for my new spool location and that 
was causing the errors.
  - I set the permissions on the directory ( the directory was writable only by 
root )
  - I changed the store-location in the config file to remove the trailing '/', 
(I'm like that)
  - I then restarted Kannel 
  - and sent another message from my phone
  - Kannel picked it up without a problem
  - bearerbox log appears as it should (no errors)

  Is there anything in this lengthy discourse that flags anyone out there as to 
why I couldn't receive messages but could send without a problem and then could 
send and receive after changing the permissions on the spool file?

  Thanks,

  -Tony



  2009/3/31 Nikos Balkanas <[email protected]>

    This doesn't make much sense:

    1) bearerbox will panic if it cannot access the spool directory.
    2) Spool directory is used for outgoing SMS, not incoming, so you shouldn't 
be able to send SMS.

    Nikos
      ----- Original Message ----- 
      From: Tony Kirkham 
      To: Alvaro Cornejo 
      Cc: Nikos Balkanas ; [email protected] 
      Sent: Tuesday, March 31, 2009 5:11 PM
      Subject: Re: SMS receiving quit working


      Hi, guys,  

      Life's been crazy as of late and I am just getting back to looking at 
this problem.  It helps to look in the logs a bit closer (yes, I feel silly).  
It appears that it was a permissions problem.  When I added the other modems to 
my configuration I also moved my spool directory and in doing so I forgot to 
set the permissions so Kannel could use it.  It is interesting to note that 
Kannel will still send messages with a malfunctioning spool, but doesn't seem 
to want to receive them.  Once I changed the permissions on the spool directory 
everything worked fine.

      Thanks for your help,

      -Tony


      On Fri, Mar 27, 2009 at 6:54 AM, Alvaro Cornejo 
<[email protected]> wrote:

        Hi Tony

        I think it might be something on your routing config in kannel

        I've a setup with over 14modems and have no problems

        Regards

        Alvaro

        
|-----------------------------------------------------------------------------------------------------------------|

        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



        2009/3/26 Nikos Balkanas <[email protected]>:

        > Hi,
        >
        > Unfortunately we cannot tell much without configuration files or 
detailed
        > logs. You can always add them as an attachment. But just the relevant 
ones.
        >
        > It doesn't make much sense that the amount of SMScs is the problem, 
more
        > like some of the modems are configured wrong. Are all the modems the 
same?
        >
        > Comment out all but 2 modems in your configuration (adjust 
smsbox-route
        > accordingly). Repeat with different pairs until you reproduce 
problem. If
        > not try adding 1 more at a time until you reproduce. If at any point 
you get
        > the problem post relevant logs (please only relevant portions) 
@loglevel 0,
        > and relevant conf parts.
        >
        > BR,
        > Nikos
        >
        > ----- Original Message -----
        > From: Tony Kirkham
        > To: [email protected]
        > Sent: Thursday, March 26, 2009 11:01 PM
        > Subject: SMS receiving quit working
        > I have had Kannel running for quite some time now.  I had two GSM 
modems
        > functioning and had been doing some testing of messages sending from 
one
        > modem to the other without any problems so, I am certain that, at 
that time,
        > I could both send and receive.  Recently, I added a few more modems.  
When I
        > did this I split my config file into two, one for the smsc 
definitions and
        > the other for everything else.  The modems all seem to work great for
        > sending SMS but, I cannot receive now.  I send an SMS from a phone to 
one of
        > the modem numbers and nothing shows up in the http://.../status page.
        >
        > All of my smsc group definitions are done in a seperate config file 
that I
        > include into the main config and I am sure that the main config file
        > continues to be read after those definitions because my send-sms  
group is
        > defined after the inclusion and I can send without a problem.  I have 
turned
        > sim_buffering on in all of the smsc groups and have set the 
storage_type in
        > the modem group to "SM" just in case but none of that seems to help.
        >
        > Does anyone have an idea what could be going on?  I didn't include my 
config
        > files for sake of breavety but, I will be happy to if needed.
        >
        > Thanks,
        >
        > -Tony
        >




Reply via email to