Oh, yes. It is. I updated Documentation a few weeks ago, so that UG know
points to the latest snapshots. add-smsc is in there.
BR,
Nikos
----- Original Message -----
From: brett skinner
To: Nikos Balkanas
Cc: Users
Sent: Tuesday, August 24, 2010 3:42 PM
Subject: Re: Kannel restart command
Works like a charm. I also tested remove-smsc too.
Sorry I was looking in the UG I downloaded off the website. I have no idea
if the add-smsc/remove-smsc is in the UG in trunk. I guess that is where I
should have been looking.
Thanks again.Β
2010/8/24 Nikos Balkanas <[email protected]>
Add a new smsc in your configuration, while bb is running. Then, from the
admin page choose:
add-smsc
Let me know how it works.
BR,
Nikos
----- Original Message ----- From: brett skinner
To: Users
Sent: Tuesday, August 24, 2010 12:17 PM
Subject: Re: Kannel restart command
@Alvaro: As Nikos said. According to UG it is only the DLRs that are safe
and my question is about queued SMS not DLR.
@Nikos. Thanks, it is in the configuration file already. There didn't appear
to be a restart-smsc so I used so stop-smsc and start-smsc and that did the
trick. Something else you said reminded me of a question I had been meaning
to ask. If we wanted to add an SMSC to our configuration would it be
possible to start that bind without having to restart the bearerbox. I
attempted to add a new bind yesterday and use the start-smsc command but I
kept getting could not restart smsc response from Kannel. I looked in the
logs but didn't see any errors or warnings. I restarted Kannel and the bind
connected straight away.
Regards,
2010/8/24 Nikos Balkanas <[email protected]>
Not quite. Internal storage refers to dlr-storage. You can start bearerbox
without *any* storage specified and that would do the trick, but that is
extreme operation and asking for trouble.
@brett: Alvaro is mostly right, but there is still a chance of loosing 1-2
SMS, accepted by bb, before they are stored to filesystem. Your best bet
would be to switch it first to isolated or suspended (don't remember which -
check user's guide) wait a couple of minutes and then restart.
However, if your inactive SMSc is already in your configuration file, you
can just go tyo http admin and choose "restart-smsc" without the need to
restart bearerbox.
BR,
Nikos
----- Original Message ----- From: "Alvaro Cornejo"
<[email protected]>
To: "brett skinner" <[email protected]>
Cc: "Users" <[email protected]>
Sent: Monday, August 23, 2010 5:57 PM
Subject: Re: Kannel restart command
If you do have setup kannel to store the messages on a file or store,
you wont loose any message. You will if you do use "internal storage"
that is held in RAM
|-----------------------------------------------------------------------------------------------------------------|
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, Aug 23, 2010 at 2:38 AM, brett skinner
<[email protected]> wrote:
Hi Users
We had a situation on Saturday where one of our SMSC experienced connection
difficulties with their ISP. When they came back 2 of the 3 binds were
re-established correctly. The 3rd bind reported being connected but all
messages to that bind were getting queued to the bearerbox. I looked at the
user guide for a way to drop and re-establish the connection without losing
all the SMS traffic in memory. I saw the restart but it didn't say if it
would destroy the in memory queue.
Is there a way to re-establish the connections without loosing the in memory
queues? Will the restart command do that?
Regards,
