Mi Reflejo wrote:
Hi Stipe,
On 6/14/06, Stipe Tolj <[EMAIL PROTECTED]> wrote:
that's a problem indeed. AFAIU the smsbox connects to the sqlbox
rather then the
bearerbox port. So sqlbox acts (from the view of smsbox) as bearerbox.
Ok, that's why you guys need to seperate and add the config. But I
think you
should use a different .conf file for sqlbox, where the "normal
bearerbox port"
is set addequate to reflect the sqlbox(bearerbox)-port. This is a
benefit, since
it doesn't require to patch smsbox at all. Right?
So, using 2 configs with core groups different for bearerbox port
would solve
the smsbox patching need.
I don't see how a different config file *only* for sqlbox will solve
anything since smsbox is who needs bearerbox port to connect. If we
use a different .conf file *only* for sqlbox, smsbox would still
connecting to original bearerbox-port.
If we take this way, maybe a very ugly solution is to start smsbox and
sqlbox with one config file and bearerbox with other but i don't like
this way.
Hi Martin,
now, you would have one config file for bearerbox and sqlbox (upsteam.conf) and
a slightly modified for smsbox (smsbox.conf). That's it.
In the upstream.conf the sqlbox picks it's required smsbox-port from the core
group to connect in the role of a smsbox-instance to bearerbox.
And in the smsbox.conf your smsbox instance get's a different value for the
smsbox-port in core group to connect to sqlbox.
So, this is clean, if the user really knows what he is doing and how to set the
config values right.
I agree that it's more burdon to be clear of the roles the boxes take then
simply to add config directives in the groups where we "naively" think they
belong. But that's the too-easy approach IMO.
I do think that the smsbox-port belongs to core group. If sqlbox plays a
bearerbox role on the one side and a smsbox role on the other side, then it has
to provide the "relayed" smsbox an own config file with an "own" core group,
since it's playing the role of bearerbox for that specific smsbox instance.
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
