On Fri, 2009-04-17 at 15:51, Elton Hoxha wrote:
> In theory it can be right what you said Milan, but practically I have
> started multiple bearerbox instances running on the admin-port 13000 without
> having problems for weeks :)

Well, you can setup kannel however you want but as I wrote in previous
mail it can lead to problems if you configure it in non-canonical way.

Chapter 3 of userguide says:
------------------------------------------------------------------------
Configuring the gateway                                                         
                                                
                                                                                
                                                
   The configuration file can be divided into three parts: bearerbox
   configurations, smsbox configurations and wapbox configurations.
   Bearerbox part has one 'core' group and any used SMS center groups,
   while wapbox part has only one wapbox group. In smsbox part there is
   one smsbox group and then number of sms-service and sendsms-user
   groups.
------------------------------------------------------------------------

Notice words: "Bearerbox part has one 'core' group and any used SMS
center groups".

I just looked in the Debian package I made for lenny and noticed that it
has two 'core' group sections. I never use default config so it stays
unnoticed for years :)

However I noticed that the bearerbox uses last 'core' group section in
config file and "ignores" previous one.

Could you check how many instances of bearerbox running on
your machine and check does all ports you specified in config are
actually listening?

> On Fri, Apr 17, 2009 at 3:44 PM, Milan P. Stanic <m...@arvanta.net> wrote:
> > On Fri, 2009-04-17 at 15:00, Elton Hoxha wrote:
> > > Actually I use 4 bearerbox instances separating my connections. I never
> > had
> > > this type of error even using this configuration below.
> > Interesting idea :). But it is useless (at least) and can lead to
> > problems.
> >
> > Actually, that can be cause of your problem. First instance of bearerbox
> > binds to port 13000 and other instances cannot bind and "bark" to log
> > files.

Looks like I made mistake here. Looks like bearerbox uses last core
group section.
 
-- 
Kind regards,  Milan

Reply via email to