As Rene said
use the same smsc-id for your connections this way kannel wil find the
dlr to match to
For admin purposes, you can use the new parameter added by A. Guerreri
called something like "smsc admin id".
However If you use access logs to do billing, I dont know if you will
be able to separate traffic from logs per each smsc.
What I use is:
smsc1:
smsc-id = sc1
allowed-smsc= sc1; sc
smsc2:
smsc-id = sc2
allowed-smsc= sc2; sc; sc23
smsc3:
smsc-id = sc3
allowed-smsc= sc3; sc23
smsc4:
smsc-id = sc4
allowed-smsc= sc4; sc
Where "sc" is some sort of "virtual smsc"
This way you can:
- route your messages to "sc" using ...&smsc=sc&... in the sendsms url call,
- kannel will automagicaly balance the traffic between all links where
the virtual link is allowed sc =(sc1, sc2, sc4), sc23 = (sc2, sc3),
- you can still do separate billing per sc
- you can still route any message to a specific link with &smsc=scx in
your sendsms url call.
- You can create any "virtual smcs" you might need by just adding the
virtual id to the allowed-smsc string ie sc23, sc14, sc24, etc.
- You can even combine different types of smsc's in the same virtual route.
Hope helps
Regards
Alvaro
|-----------------------------------------------------------------------------------------------------------------|
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 Sun, May 30, 2010 at 11:17 AM, Rene Kluwen <[email protected]> wrote:
> The obvious answer would be: Why not giving each smsc the same smsc-id?
>
> But then again… you may have valid reasons to do it.
>
>
>
> == Rene
>
>
>
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Konstantin Vayner
> Sent: zondag 30 mei 2010 11:59
> To: Kannel Users
> Subject: DLR queue problems.
>
>
>
> Hi Everyone!
>
>
>
> I'm having troubles with DLRs.
>
>
>
> 1) We have multiple links (smpp / ucp) to same remote SMSC with same
> credentials
>
> 2) When a DLR arrives, remote SMSC randomly pushes it to one of the active
> links that are connected with credentials that pushed the message
>
> 3) When the DLR is pushed to kannel over "wrong" link (not the same one that
> pushed it to remote), kannel cannot match the reciepted dlr to dlr queue..
>
>
>
> Right now, i have distinct unique smsc-id for each connection (e.g.
> smsc_operA_mt1 , smsc_operA_mt2 , ... smsc_operB_mt1 , smsc_operB_mt2 ,
> ...).
>
>
>
> Any ideas?
>
>
>
> P.S. I'm digging architecture docs atm as i want to understand how
> dlr-routing works, but i would appreciate an answer from someone who has
> experience in such configurations.
>
>
>
> Thanks in advance,
>
> Konstantin
