Hi Eric, I don't know mbuni at all. If it's a big problem to pass smsc-id or use two sendsms users you could try apply prefix-based routing:
in example: +1xxxxx -> US SMSC1 001xxxxx -> US SMSC2 If the SMSC2 does not accept 001xxxx prefix, change it to +1 using 'unified-prefix' in the smsc configuration. unified-prefix = "+1,001" Many VoIP providers uses this method to route calls via different trunks (cheaper or more expensive) Regards, Cezary ----- Original Message ----- From: Monchanin Eric To: Nikos Balkanas Cc: [email protected] Sent: 16 October 2009 12:02 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 ?
