Re: Selecting which smsc to use from HTTP interface
It works now :) Gracias Alvaro! On 12/07/2011 09:42 p.m., Alvaro Cornejo wrote: You need to add allowed-smsc denied-smsc parameters in your smsc config |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jul 12, 2011 at 9:03 PM, Alejandro Mejia Evertszame...@gua.net wrote: Hello guys, I'm a little confused with the smsc parameter when sending a message from HTTP, as I have 2 smsc configured (oper1 and oper2). Both serve same country prefix, so I thought I was able to route the message to a specific smsc-id using http://x.x.x.x/cgi-bin/sendsms.bla+bla+bla...smsc=oper2 Messages allways get routed through oper1 I was reading this under UG: If you want to use SMS push services, requesters should then set the smsc request parameter, or 'sendsms-user' groups should be defined like this: group = sendsms-user username = operator_A password = foo forced-smsc = A group = sendsms-user username = operator_B password = bar forced-smsc = B Is it possible to select which smsc to use as I'm trying to do with HTTP's param smsc? or do I have to route using the method described on UG? Thanks in advance for your help, Alejandro
Selecting which smsc to use from HTTP interface
Hello guys, I'm a little confused with the smsc parameter when sending a message from HTTP, as I have 2 smsc configured (oper1 and oper2). Both serve same country prefix, so I thought I was able to route the message to a specific smsc-id using http://x.x.x.x/cgi-bin/sendsms.bla+bla+bla...smsc=oper2 Messages allways get routed through oper1 I was reading this under UG: /If you want to use SMS push services, requesters should then set the smsc request parameter, or 'sendsms-user' groups should be defined like this:/ /group = sendsms-user username = operator_A password = foo forced-smsc = A group = sendsms-user username = operator_B password = bar forced-smsc = B/ Is it possible to select which smsc to use as I'm trying to do with HTTP's param smsc? or do I have to route using the method described on UG? Thanks in advance for your help, Alejandro
Re: Selecting which smsc to use from HTTP interface
You need to add allowed-smsc denied-smsc parameters in your smsc config |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jul 12, 2011 at 9:03 PM, Alejandro Mejia Evertsz ame...@gua.net wrote: Hello guys, I'm a little confused with the smsc parameter when sending a message from HTTP, as I have 2 smsc configured (oper1 and oper2). Both serve same country prefix, so I thought I was able to route the message to a specific smsc-id using http://x.x.x.x/cgi-bin/sendsms.bla+bla+bla...smsc=oper2 Messages allways get routed through oper1 I was reading this under UG: If you want to use SMS push services, requesters should then set the smsc request parameter, or 'sendsms-user' groups should be defined like this: group = sendsms-user username = operator_A password = foo forced-smsc = A group = sendsms-user username = operator_B password = bar forced-smsc = B Is it possible to select which smsc to use as I'm trying to do with HTTP's param smsc? or do I have to route using the method described on UG? Thanks in advance for your help, Alejandro
