Routing rule for destination address for Mo SMS

[GoogleCodeExporter]

SMSC should be flexible to allow adding routing rule depending on destination 
number.

For example SMS is sent to number 1234, and administrator configured routing 
rule for 1234 to be routed over SMPP to Connection1, SMSC should send SMS to 
corresponding ESME via SMPP

Original issue reported on code.google.com by [email protected] on 23 Mar 2012 at 11:23

[GoogleCodeExporter]

Hi,

SMSC should also have the feature to be able to route a shortcode [ 1234 ] to a 
normal MSISDN like [ 93700XXXXX ] . 

Original comment by [email protected] on 9 Apr 2012 at 3:06

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

More like vice versa as well - sms sent to long numbers should be translated 
into SMPP accounts / other long numbers.


# international address is passed thru (without +)
#
# eat the plus regardless the prefix after that
#long code to short code mapping for election
<92700000XXXXX>{s/2727}:ACCEPT;
<226610010>{&}:ACCEPT;
<2266>{&}:ACCEPT;
<91002>{&}:ACCEPT;
<2299>{s/92XXXXXXXX}:ACCEPT;

Original comment by [email protected] on 9 Apr 2012 at 3:07

• Added labels: ****
• Removed labels: ****