Hello Rodrigo, Sorry that you will get this message twice, but I forgot to send it to the user list instead of to you personally.
I'd like other people to be able to read this too, they might also have an idea. No, I don't think that is what i mean. The SMSC is what I can provide myself, when I configure the SMPP SMSC right? For example, I have this for my SMS Center: # SMSC SMPP = SMS CENTER group = smsc smsc = smpp smsc-id = MQUBE host = anakin.mqube.us port = 16911 [ etc etc ] Now, when a message is recieve through this SMSC, I will get MQUBE as smsc id. If I am correct of course. But, our SMS gateway provider connects several networks. They support Cingular, Nextel, Boost & Verizon. So when an end user sends a SMS to our shortcode, we need to know what carrier he uses. Verizon uses a double opt-in for example, so that's why we need to know. Maybe I am wrong, please let me know :) Thanks for your help so far! Kind regards, Roland. On 24 November 2004, 16:55:34, Rodrigo wrote: RAC> What you call carrier_id is "smsc-id" inside Kannel. (Take a look at the RAC> smsc group configuration). When Kannel receives a SMS, it passes your script RAC> the "smsc-id" name in the %i variable. When you push a SMS, you should use RAC> that same name, this time setting the "smsc" CGI variable, so Kannel knows RAC> which connection to use.
