Gildas Perrot wrote:
> group = smsc
> smsc-id = A
> ...
> group = sendsms-user
> username = operator_A
> password = foo
> forced-smsc = A
> operator_A routed to B SMSC account. Is it due to to the fact I didn't put
> "denied-smsc-id" directives in smsc groups ?
Just setting the smsc-id variable in a "group = smsc" block does not
in any way constrain which messages can be sent through that smsc. It
just means that all messages received from that smsc will have that
smsc-id, and it will also be set in replies generated to those
messages (unless overridden). These ids then have to be used in
conditions like accepted-smsc in sms-service groups or
preferred-smsc-id in smsc groups to achieve something useful. (This is
explained in the user guide under "SMSC Group Variables".)
> If true, is there another way to do that specific routing since I am going
> to have a lot of smsc accounts, and I don't want to specify all of them in a
> "denied-smsc-id" directive.
If you want to only allow messages with a certain smsc-id, it's of
course easier to use allowed-smsc-id instead of denied-smsc-id.
