Angel Fradejas wrote: > > >>Not true in multi-operator links. > > > >if your multi-operator incoming link tells you the original SMSC the > >message comes from (passing the %i) then youre back in business. If > >you implement mnc and mcc and the multi-operator link doesnt tell you > >this, you're back to square one, hence the original smsc name is as > >good as mnc and mcc. > > Better a practical (and simplified) example: > > you have only one link > > group = smsc > smsc-id = custom_driver_whatever > smsc = custom_type > > The protocol of this link tells you (in one way or another) the operator > originating the MO. Your %i will be "custom_driver_whatever". > > Hope this clarifies.
yep, if you do receive messages from different networks over one link, which is what you think of, the %i only tells the sms-service that it has arrived from this smsc. In this case I suggest you're backend system should know the prefix of the MO message, hence your backend system has to figure out from which network the request is coming by parsing the prefix number value. Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG M�nsterstr. 248 40470 D�sseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
