Re: Possible bug with smsc-stop

Bill Brigden wrote:
> 
> Hi,
> 
> Im running cvs-20030811, and we have 9 connections to our providers:
> 
> 1 transmitter/receiver to provider 1
> 3 transmitters to provider 2
> 1 receiver to provider 2
> 1 transceiver to provider 3
> 2 transmitters to provider 4
> 1 receiver to provider 4
> 
> now each provider has the same smsc-id, so it will load balance within each
> set of provider connections.... However, if I do a smsc-stop via the http
> admin, it will only stop the first smsc-id that matches, and the other smsc
> connections with the same smsc-id stay connected. Is this behaviour
> expected?

this brings up again to the case that we want 'group = smsc-group' to
have "gathering" real smsc-ids that have *unique* IDs to groups for
start/stop'ing a whole bunch of "local" smsc connections.

I'll see how fat I get with this in the coming days.

BTW, I also worked in smsc aliases. Espacially to solve SMPP related
configuration issues with more than 1 configured smsc group, but only
one of those with a real connection.

Unfortunatly seting up such virtual smsc groups in Kannel is not as
easy as I thought. It's pretty tricky to have the messages re-routed
in case the real smsc goes away while routing happens.

Anyone having a good idea on how to implement smsc aliases *without*
changing the code too heavily?

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are