It will depend on how you control your message status and/or traffic routing.
You can just use your message id and the dlr status. This might be enough to check your db for the message that needs to be updated. I use also the smsc-id to know the real smsc my message went through since I use "generic or virtual" routes when calling kannel and some additional parameters of my own to validate some other things. Regards Alvaro On Thu, May 7, 2009 at 12:38 PM, Eduardo Raad <[email protected]> wrote: > Alvaro, > > Which parameter do you think is the best to pass my local message ID to the > HTTP generic SMSC? May I use binfo? > > Eduardo > > On Thu, May 7, 2009 at 9:55 AM, Alvaro Cornejo <[email protected]> > wrote: >> >> Hi Eduardo >> >> I think you don't need to do all that unless you want to store your >> provider ID. >> >> You can add your own ID on the dlr-url you send to your provider. When >> they send their dlr you get your own id and you can use that id to >> match your dlr table. >> >> Also depending on your provider, you can ask them to include their >> message ID in your dlr-url so you can grab that id from your dlr >> >> is that what you want? >> >> Regards >> >> Alvaro >> >> On Thu, May 7, 2009 at 9:43 AM, Eduardo Raad >> <[email protected]> wrote: >> > Hey guys, I think this should probably be sent to the developers list >> > but >> > here it goes: >> > >> > Most of the HTTP gateways out there use a callback URL to send DLR >> > updastes. >> > Some of them include a message ID in the HTTP response (mostly the body) >> > so >> > we can enable a URL where the gateway posts back DLR updates using that >> > message ID. >> > >> > What about creating a callback function into the HTTP generic SMSC >> > interface >> > that: >> > >> > - Captures the HTTP response from the SMSC/Gateway >> > - Parses it using Regex >> > - Generates an HTTP call to a callback URL configured by the user, >> > including >> > this captured message body/parameters >> > - This way we would a option for DLR support into the HTTP generic SMSC >> > >> > I recently connected to a gateway that behaved like this: Replied to the >> > requests by HTTP generic SMSC with a message ID. Then updated the >> > message >> > status to a callback URL I provided to them. I needed a way to capture >> > the >> > message ID from the reply so I could create a database record for them >> > to >> > update. >> > >> > My solution was to create a web application that acted as a proxy >> > between >> > the HTTP generic SMSC and the gateway, so I captured the message status >> > before returning the actual response to Kannel. This my end up being >> > problematic as there is an extra HTTP call for each message and an >> > additional point of failure. >> > >> > Let me know if someone is interested in doing this :) >> > >> > Eduardo >> > >> > -- >> > Eduardo Raad >> > Gerente General >> > Metromovil >> > >> > móvil + 593 93978888 >> > oficina + 593 42329455 x 1099 >> > >> > Av. 10 de Agosto 511 y Chimborazo >> > Edificio Equinoxcorp, Piso 3 >> > Guayaquil, Ecuador >> > >> >> >> >> -- >> >> |-----------------------------------------------------------------------------------------------------------------| >> 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 > > > > -- > Eduardo Raad > Gerente General > Metromovil > > móvil + 593 93978888 > oficina + 593 42329455 x 1099 > > Av. 10 de Agosto 511 y Chimborazo > Edificio Equinoxcorp, Piso 3 > Guayaquil, Ecuador > -- |-----------------------------------------------------------------------------------------------------------------| 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
