According to the documentation, forced-smsc accepts only a single smsc id as
a parameter. It's probably trying to force "smsc1;smsc2" which it doesn't
exist, so the rule is effectively ignored.
Try naming smsc1 and smsc2 as "smsc1" instead.

Regards,

Alejandro
On Fri, Oct 16, 2009 at 4:46 PM, Monchanin Eric <[email protected]>wrote:

>  forcing to only 1 smsc is ok.
> the sms gets routed to smsc1 and only to smsc1,
> I sent a dozen messages and none got routed to smsc3
>
> (but then no message is routed to smsc2)
>
> Le 16/10/2009 16:19, Alejandro Guerrieri a écrit :
>
> Can you try using force-smsc with only one smsc name and see if the problem
> still happens? e.g force-smsc=smsc1 ?
>  Regards,
>
>  Alex
>
> 2009/10/16 Monchanin Eric <[email protected]>
>
>>  That is the case already, here is a piece of my config :
>>
>> ### SMSC1
>> group                   = smsc
>> smsc-id                 = smsc1
>> smsc                    = smpp
>> (...)
>> allowed-prefix          = 1;+1
>> denied-smsc-id          = "smsc2;smsc3"
>>
>> ### SMSC2
>> group                   = smsc
>> smsc-id                 = smsc2
>> smsc                    = smpp
>> (...)
>> denied-prefix          = 1;+1
>> denied-smsc-id          = "smsc1;smsc3"
>>
>> ### SMSC3
>> group                   = smsc
>> smsc-id                 = smsc3
>> smsc                    = smpp
>> (...)
>> allowed-prefix          = 1;+1
>> denied-smsc-id          = "smsc1;smsc2"
>>
>>  ### sendsms-user
>> group                   = sendsms-user
>> username                = user1
>> password                = foobar1
>> forced-smsc             = "smsc1;smsc2"
>>
>> ### sendsms-user
>> group                   = sendsms-user
>> username                = user2
>> password                = foobar2
>> forced-smsc             = "smsc3"
>>
>> And still, when sending using :
>>
>>
>> http://192.168.1.10:13013/cgi-bin/sendsms?&username=user1&password=foobar1&text=hello&to=%2B1xxxxxxxxxx
>>
>> It will route either to smsc1 or smsc3
>>
>> PS: thank you for the help, I'm really sorry for all this bugging :)
>>
>>
>>
>> Le 16/10/2009 15:45, Nikos Balkanas a écrit :
>>
>> Yeap. You have also to put in group smsc3:
>>
>> denied-smsc-id = "smsc1;smsc2"
>>
>> Nikos
>>
>> ----- Original Message -----
>> *From:* Monchanin Eric <[email protected]>
>> *To:* Nikos Balkanas <[email protected]>
>> *Cc:* [email protected]
>> *Sent:* Friday, October 16, 2009 4:26 PM
>> *Subject:* Re: Routing Question
>>
>>  Hello,
>>
>> Thank you for the answer,
>>
>> I configured my sendsms-user with the following :
>>
>> # GENERIC SEND-SMS USERS
>> group                   = sendsms-user
>> username                = foo
>> password                = bar
>> concatenation           = true
>> max-messages            = 5
>> forced-smsc             = "smsc1;smsc2"
>>
>> and still, when I send to US numbers ( +1... ) it uses smsc3 ( approx
>> every 2 sms, kannel uses smsc3 )
>> it seems the forced-smsc is not even considered
>>
>> note that, when I send to a european number ( non +1 ) then it uses the
>> smsc2 correctly, that part at least is great.
>>
>>
>>
>> Le 16/10/2009 13:28, Nikos Balkanas a écrit :
>>
>> Hi,
>>
>> I don't know Mbuni. You should ask an mBuni forum for that.
>>
>> No other smsc directives exist for sendsms-user
>> You can add as many smscs as you would like:
>>
>> forced-smsc="A;B;C;..."
>>
>> What this will do is to redirect all sendsms traffic for this user to
>> those smscs.
>>
>> BR,
>> Nikos
>>
>> ----- Original Message -----
>> *From:* Monchanin Eric <[email protected]>
>> *To:* Nikos Balkanas <[email protected]>
>> *Cc:* [email protected]
>> *Sent:* Friday, October 16, 2009 2:02 PM
>> *Subject:* Re: Routing Question
>>
>>  Hello Nikos,
>> Thank you for your answer.
>>
>> mBuni will connect to kannel with only one sendsms-user setting,
>> furthermore, it doesn't pass any smsc-id parameter.
>>
>> My mBuni sendsms-user has to route the messages between 2 smsc :
>> smsc1 => USA
>> smsc2 => Europe
>> Which I can configure using the allowed-prefix and denied-prefix settings.
>> Since mBuni can only send to one sendsms-user, without smsc-id, this is I
>> think the only solution.
>>
>> However, I have this smsc3, which is also linked to USA, and to which I
>> don't want to route those messages.
>> ( I actually configured a 2nd sendsms-user only for this smsc3 )
>>
>> In this case, the allowed-prefix can not choose between smsc1 and smsc3
>> since they both accept the same prefix (+1;1)
>>
>> Is there a way to deny a sendsms-user to access a particular smsc ? or
>> Is there a way to specify more than one "forced-smsc" or "default-smsc" to
>> a particular sendsms-user ?
>>
>>
>> Bests,
>>
>> Eric
>>
>> Le 16/10/2009 02:02, Nikos Balkanas a écrit :
>>
>> Hi,
>>
>> In group sendsms-user:
>>
>> forced-smsc
>> default-smsc
>>
>> You can also specify smsc-id in sendsms URL:
>>
>> &smsc=<smscid>
>>
>> Hope this helps,
>> Nikos
>>
>> ----- Original Message ----- From: "Monchanin Eric"
>> <[email protected]> <[email protected]>
>> To: <[email protected]> <[email protected]>
>> Sent: Friday, October 16, 2009 1:27 AM
>> Subject: Routing Question
>>
>>
>> Hi to all,
>>
>> I am having a little issue with my dual setting mbuni / kannel.
>>
>> I configured 3 different SMSC in Kannel, 2 for USA and 1 for Europe.
>> Mbuni can use those 3 SMSC to send mm1 notifications to the handsets, but
>> as you may know, Mbuni doesn't specificy the smsc in the sendsms request.
>> Mbuni also allows to configure only ONE sendsms-user
>>
>> So, I needed to do a little bit of routing in Kannel.
>>
>> I had no trouble to make the distinction between USA and Europe, using the
>>
>> smsc allowed-prefix setting.
>> allowed-prefix = +1;1 for USA
>> denied-prefix = +1;1 for Europe
>>
>> Now the problem I have is with my 2nd connection to USA, the smsc group is
>>
>> almost configured in the same way, and since Mbuni doesn't route (no smsc,
>>
>> and only one sendsms-user)
>>
>> The only thing I could think of is that this particular connection should
>> only be used by a particular sendmms-user, NOT the one used by Mbuni.
>>
>> Is there a way to filter the users that will be able to use the smsc, or
>> force my "mbuni" user to select only between a few smsc (something like
>> allowed-smsc for instance)
>>
>>
>> I hope I'm clear enough :),
>>
>> Bests,
>>
>> Eric
>>
>>
>>
>>
>>
>> --
>>   Skycore LLC
>> 119 Braintree St. STE 512
>> Allston, MA 02134 Eric Monchanin
>>   [email protected]
>> (+1) 617-314-7688 [email protected]
>> (+33) 6-22-96-71-10
>>
>>
>>
>> --
>>   Skycore LLC
>> 119 Braintree St. STE 512
>> Allston, MA 02134 Eric Monchanin
>>   [email protected]
>> (+1) 617-314-7688 [email protected]
>> (+33) 6-22-96-71-10
>>
>>
>>
>> --
>>   Skycore LLC
>> 119 Braintree St. STE 512
>> Allston, MA 02134  Eric Monchanin
>>   [email protected]
>> (+1) 617-314-7688  [email protected]
>> (+33) 6-22-96-71-10
>>
>
>
>
> --
>   Skycore LLC
> 119 Braintree St. STE 512
> Allston, MA 02134  Eric Monchanin
>   [email protected]
> (+1) 617-314-7688  [email protected]
> (+33) 6-22-96-71-10
>

Reply via email to