>Since the smsc_id in the MO is set by the driver, and this only applies >to custom/proprietery or future drivers, I think that setting the smsc_id >of the MO to something that represents the mcc/mnc will suffice (maybe a >concatenation of their values), and is a good solution.
Yes Oded, that was an option I evaluated too. But then you have all of your routing rules (allowed-smsc-id, preferred-smsc-id, denied-smsc-id) invalidated (as MO smsc_id is copied to MT), or extremely bloated (you would have to declare every mcc-mnc combination) or you would have to mess around later in the application handling the MO to output a X-Kannel-SMSC header to correct it. >So my opinion is that if the implementation is clean - it will do no >harm and potentioally can do good. Thx, Oded. Angel Fradejas Mediafusin Espa a, S.A. [EMAIL PROTECTED] www.mediafusion.es Tel. +34 91 252 32 00 Fax +34 91 572 27 08
