I cross-checked, this is already the case. Note that SMS-MO do make their
way to the get-url but only DLRs are getting buffered.

On Tue, Sep 30, 2014 at 7:22 PM, Alvaro Cornejo <cornejo.alv...@gmail.com>
wrote:

> Hi
>
> Check sms routing group /smsc-id it should match that of the route used
>
> Regards
>
> Alvaro
>
>
> |-----------------------------------------------------------------------------------------------------------------|
> 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.com
>
> On Mon, Sep 29, 2014 at 5:02 PM, ha...@aeon.pk <ha...@aeon.pk> wrote:
>
>> Hi,
>>
>> My DLRs are being buffered at Kannel and not hitting the URL specified in
>> dlr_url paratmeter in SQLBOX while sending SMS. Can someone please help to
>> figure out what's wrong? I am using following statement:
>>
>> INSERT INTO `kannel`.`send_sms`
>> (momt,charset,coding,sender,receiver,msgdata,smsc_id,sms_type,dlr_mask,dlr_url)
>> VALUES ('MT','','','03xxyyyyyyy','03aabbbbbbb','Hello. This is test DLR
>> message.','my-smsc','2','63','
>> http://127.0.0.1/testdlr/dlr.php?dlrid=3&status=%d')
>>
>> The DLR is received by kannel/bearerbox successfully but kannel status
>> window shows it as buffered. It never hits the URL specified.
>>
>> Is there some CGI parameter I am missing? The dlr.php file is on the
>> right path specified in the URL.
>>
>> Regards,
>> Hamza
>>
>> On Fri, Jun 13, 2014 at 11:41 PM, [Digital^Dude] ® <
>> millennium....@gmail.com> wrote:
>>
>>> In your sendsms url just append dlr-url e.g.
>>>
>>> http://kannel.host.com:xxxx/sendsms.cgi?user...&dlr-mask=x&dlr-url=[url
>>> encoded form of url]
>>>
>>> As you receive a dlr response, this dlr-url will be hit. Assuming your
>>> dlr-url was the following:
>>>
>>> http://another.host.com/myapi.py?status=%d&mID=123&tStamp=....
>>>
>>> You can grep for "mID=123" and view its status in the web server logs of
>>> another.host.com
>>>
>>
>>
>

Reply via email to