Beatrice
The only way I know to know an smsc status, is by using and parsing
the admin interface. Maybe hacking the bearerbox code, there is
another way to get that info ???
However, if you send a message to a virtual smsc and any of the smsc
belonging to that virtual smsc is not online, kannel will send it
through the available smsc. If all smsc are online kannel will
loadbalance between all smsc of that virtual smsc and if none of the
smsc is online, kannel will queue it until any of the smsc of the
corresponding virtual smsc gets online. So you really don't need to
worry about that... I think.
On the other side, when kannel send the message where you specified a
virtual smsc destination, the dlr will have the real smsc through wich
the message was sent. There is a parameter you can add to your dlr-url
for that. Therefore if you send the message to smsc_v2 and kannel send
it through smsc3, the dlr-url call will have that info and you can
reccord it for your needs.
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 Thu, Jan 21, 2010 at 11:15 AM, Beatrice Tamburrino
<[email protected]> wrote:
> forgot to ask:
>
>
> to retrieve the status of the specific SMSC? I mean, if I send a request
> with smsc=smsc_v3 and before doing the requests, I want to know if the link
> to SMSC2 or SMSC3 is online...
>
>
> I ask different: Is it possible to set this virtual routing table on kannel
> side? so that the app can just send the request and retrieve the defined SMSC?
>
>
> this would more comfortable for the support (administrator has to check if
> the kannel.conf is the same as defined in the app -> high risk of errors)
>
> thanks for any hint or ideas!
>
> cheers
>
> beatrice
>
>
> -------- Original-Nachricht --------
>> Datum: Thu, 21 Jan 2010 17:09:06 +0100
>> Von: "Beatrice Tamburrino" <[email protected]>
>> An: Alvaro Cornejo <[email protected]>
>> CC: [email protected]
>> Betreff: Re: routing on kannel
>
>> Hi Alvaro!
>>
>> Thanks!
>>
>> This was also the direction I was going... thank you for the examples. If
>> this really works in that way.. then im really happy :)
>>
>> cheers beatrice
>>
>> -------- Original-Nachricht --------
>> > Datum: Thu, 21 Jan 2010 10:27:44 -0500
>> > Von: Alvaro Cornejo <[email protected]>
>> > An: Beatrice Tamburrino <[email protected]>
>> > CC: [email protected]
>> > Betreff: Re: routing on kannel
>>
>> > Hi Beatrice
>> >
>> > I solved this issue by using "virtual" smsc-id in my application.
>> >
>> > In my app I define the following "virtual" routes:
>> >
>> > smsc_v1 (for smsc 1)
>> >
>> > smsc_v2 (for smsc 1,2 and 3)
>> >
>> > smsc_v3 (for smsc 2 and 3)
>> >
>> > In kannel I use:
>> >
>> > group=smsc
>> > smsc-id=SMSC1
>> > allowed-smsc-id=SMSC1;SMSC_v1;SMSC_v2
>> > ...
>> >
>> > group=smsc
>> > smsc-id=SMSC2
>> > allowed-smsc-id=SMSC2;SMSC_v1;SMSC_v2;SMSC_v3
>> > ...
>> >
>> > group=smsc
>> > smsc-id=SMSC3
>> > allowed-smsc-id=SMSC3;SMSC_v2:SMSC_v3
>> > ...
>> >
>> >
>> > Finally in my app, when I send a message to kannel I have to add the
>> > parameter &smsc=virtual_smsc where "virtual_smsc" is the virtual smsc
>> > route I want to use.
>> >
>> > something like:
>> >
>> >
>> >
>> http://smsbox.host.name:13013/cgi-bin/sendsms?username=foo&password=bar&to=0123456&smsc=SMSC_v2&text=Hello+world
>> >
>> > This way if I specify an smsc = smsc_v2 the message can go through
>> > either 1, 2 or 3 but if I use smsc=smsc_v3 it will go through either
>> > smsc 2 or 3 only
>> >
>> > This can also permit me to specify, from my app, a message that can
>> > only go through one smsc specifying with smsc=smscx.
>> >
>> > Finally I think smsroute functionality from kannel should do
>> > somenthing similar but for my specific requirements this is enough
>> > flexible and easy to manage from my app.
>> >
>> > hope helps
>> >
>> > 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 Thu, Jan 21, 2010 at 4:45 AM, Beatrice Tamburrino
>> > <[email protected]> wrote:
>> > > good morning!
>> > >
>> > > Im having some trouble to understand this routing stuff on kannel. I
>> > know there are a lot of reading stuff about this issue, but I could^n't
>> find a
>> > solution that would match my problem.
>> > >
>> > > situation:
>> > >
>> > >
>> > > I can have multiple applications (based on different servers) which
>> can
>> > send request to the kannel:
>> > >
>> > > server 1 ---------> SMSC1
>> > >
>> > >
>> > SMSC2
>> > > server 2 ----------> Kannel -------->
>> > >
>> > SMSC3
>> > >
>> > > server 3 ---------> SMSC4
>> > >
>> > >
>> > > I have 4 different SMSC connection to one provider (emi over VPN). I
>> > need to have some kind of routing possibility to be able to do that:
>> > >
>> > > - server 1 can only send through SMSC1
>> > > - server 2 can send to all SMSC
>> > > - server 3 can only send through SMSC3 and SMSC4
>> > >
>> > > This means, before I send the request to the kannel, the applications
>> on
>> > the server check which SMSC they can use (defined on the server itself).
>> > example:
>> > >
>> > > server 1 wants to send a request, so before sending request, the app
>> > checks if kannel is ready and checks also the status.xml if the SMSC1 is
>> > ready. if both are ok, the request will be made. i guess I need to add
>> the cgi
>> > parameter "smsc=SMSC1" to the request and also in the kannel.conf I need
>> to
>> > define the routing (allowed-smsc-id... ).
>> > >
>> > >
>> > > My 2 questions are:
>> > >
>> > > 1. how are the request (sendsms interface) look like, I mean for the
>> > server 1 its clear, just add "smsc=SMSC1" but for server3 and 2??? can I
>> just
>> > add "smsc=SMSC1;SMSC2;SMSC3;SMSC4"
>> > >
>> > > 2. how should the routing be done on kannel side??? so that if kannel
>> > get a request from server 1 it wont send with SMSC2!!
>> > >
>> > > I made up a table, but I think this is not going to worK:
>> > >
>> > >
>> > > group=smsc
>> > > smsc-id=SMSC1
>> > > allowed-smsc-id=SMSC1
>> > >
>> > > group=smsc
>> > > smsc-id=SMSC2
>> > > allowed-smsc-id=SMSC1;SMSC2;SMSC3;SMSC4
>> > >
>> > > group=smsc
>> > > smsc-id=SMSC3
>> > > allowed-smsc-id=SMSC3;SMSC4
>> > >
>> > > group=smsc
>> > > smsc-id=SMSC4
>> > > allowed-smsc-id=SMSC1;SMSC2;SMSC3;SMSC4
>> > >
>> > >
>> > >
>> > > Hope somebody can give me a hint!! thanks!
>> > >
>> > > cheers
>> > >
>> > > beatrice
>> > >
>> > >
>> > > --
>> > > Haiti-Nothilfe! Helfen Sie per SMS: Sende UIHAITI an die Nummer 81190.
>> > > Von 5 Euro je SMS (zzgl. SMS-Gebühr) gehen 4,83 Euro an UNICEF.
>> > >
>> > >
>>
>> --
>> Haiti-Nothilfe! Helfen Sie per SMS: Sende UIHAITI an die Nummer 81190.
>> Von 5 Euro je SMS (zzgl. SMS-Gebühr) gehen 4,83 Euro an UNICEF.
>
> --
> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
>
