Hi Nikos, 

  

Thanks for your explanation. Sounds logic J

So how do I connect the bearerboxes? Just by defining an smsbox for every 
bearerbox I use on every Kannel installation? 

  

Documentation of Kannel is not very clear about how the system connect and 
communicate L

  

Regards, 

-- 

Toni Van Remortel

System Engineer @ Precision Operations NV

+32 3 451 92 20 - [email protected]


  

From:Nikos Balkanas [mailto:[email protected]] 
Sent:Monday, May 11, 2009 5:50 PM
To:Toni Van Remortel; [email protected]
Subject:Re: Distributed setup: what's the best solution? 



  

Hi,


  


To work in your distributed environment, you need to have a connection between 
your China & Belgium setups at the bearerbox level. Bearerbox is doing all SMSc 
routing, and doesn't understand sms-service.


  


HTTP relaying is used for just what you do: To explicitly push SMSs through the 
relay at the sms-service level. That is probaply not what you need. Since 
SMSC_1 is down, you will never receive SMS from it, to use the relay. And even 
if you did, that would mean that SMSC_1 is active, therefore no need to relay.


  


I am afraid you approach the whole thing in the wrong way. For a redundant 
setup, you should have redundant links to both your SMScs in each of your 
installations. Then with with SMSc directives "accepted-smsc" and 
"preferred-smsc" you can redirect your traffic from your queue, whenever one 
smsc becomes inactive.


  


BR,


Nikos


----- Original Message ----- 


From:Toni Van Remortel 


To:[email protected] 


Sent:Monday, May 11, 2009 4:45 PM 


Subject:Distributed setup: what's the best solution? 


  


Hi all, 

  

I'm testing Kannel with this setup: 

- Bearerbox + smsbox + SMSC linked to a local modem = SMSC_1 (location: 
Belgium) 

- Bearerbox + smsbox + SMSC linked to a local modem = SMSC_2 (location: China) 

  

When I only use the preferred-prefix options for the SMSC's, it is working very 
nice: SMS'es for China are sent through SMSC_2, others through SMSC_1. 

  

But: 

- When the SMSC_2 is down, the messages are in an infinite queue to be 
delivered, instead of being re-routed to SMSC_1 and sent. 

- When using explicit SMSC id's, the preferred-prefix setup doesn't work 
anymore and all SMS'es are sent through SMSC_1. 

  

Is there a way to have Kannel to reroute SMS'es to SMSC_1 if SMSC_2 is down? 

  

Thanks. 

-- 

Toni Van Remortel

System Engineer @ Precision Operations NV

+32 3 451 92 20 - [email protected]


Reply via email to