Hi Have you tried urlencoding your dlr?
Which store have you setup in kannel for dlr? if it is a database, can you check how reccords are stored and which values it has? They should still be there since kannel has not received any "valid"dlr. Else you can temporarily set kannel storage to a database and look at how it is storing the pair destination/id. Regards Alvaro On 12/7/12, Ali Kashif <syedalikas...@gmail.com> wrote: > Dear Alvaro, > > i am passing the internal message id, obtained from send-url. with %I code. > > i think issue is something different, and i suspect that is something with > http generic SMSC > > now look at this > i changed the generic SMSC to kannel. > here is the conf. > > #################### > # http smsc with system type kannel > #################### > group = smsc > smsc = http > *system-type = kannel* > smsc-id = localpars > log-file = "/var/log/kannel/httpkannel.log" > host = 172.18.4.100 > port = 8998 > send-url = "http://localhost/asd.php"; > connect-allow-ip = "*.*.*.*" > reroute-dlr = true > smsc-username = user > smsc-password = password > status-success-regex = "" > status-permfail-regex = "failure" > status-tempfail-regex = "retry later" > > ################################ > # My php file received this data > ################################ > Array > ( > username=user > [password] => password > [to] => +9xxxxxxxx > [text] => test rerout message test > [from] => 21234A > [mclass] => 1 > [coding] => 0 > [charset] => UTF-8 > [binfo] => 11223 > [smsc] => localpars > [dlr-url] => 3b6555b1 > [dlr-mask] => 19 > ) > > ################################ > > now system type kannel do not send the internal message id in send-url > > so i looked at kannel access log. > > and got the message id . > > > ######################################### > # My Kannel Access log > ########################################## > > 2012-12-07 14:44:04 Sent SMS [SMSC:localpars] [SVC:ali-KSA] [ACT:] > [BINF:11223] *[FID:a548e4db-7400-43e1-892d-f51858bdb11c]* [META:?smpp?] > [from:21234A] [to:+9xxxxxxxx] [flags:1:0:-1:-1:19] [msg:24:test rerout > message test] [udh:0:] > > > > > ################################ > # when the message is received at http SMSC following is generated in http > smsc log, with system-type= kannel, but when the system type is changed to > generic, there is nothing like this in log file, infact the log file is > totally silent when an incomming message is received, and it silently > passed data to send-url. > ################################ > > 2012-12-07 14:44:04 [22045] [8] DEBUG: DLR[internal]: Adding DLR > smsc=localpars, ts=a548e4db-7400-43e1-892d-f51858bdb11c, src=21234A, > dst=+9xxxxxxxxx, mask=19, boxc=ali-KSA > > > ################################ > # now i passed the message ID to my url to inject dlr and it worked > perfectly > > http://172.18.4.24:8998/sms?username=user&password=password&dlr-mask=1&to=9xxxxxxxxxxxx&dlr-mid=a548e4db-7400-43e1-892d-f51858bdb11c > > > ################################ > > > > and finally here is the http smsc log file which says DLR is received and > processed. > > ####################################### > 2012-12-07 14:46:11 [22045] [7] DEBUG: HTTP[localpars]: Got request `/sms' > 2012-12-07 14:46:11 [22045] [7] DEBUG: HTTP[localpars]: Received an HTTP > request > 2012-12-07 14:46:11 [22045] [7] DEBUG: DLR[internal]: Looking for DLR > smsc=localpars, ts=a548e4db-7400-43e1-892d-f51858bdb11c, dst=9xxxxxxxx, > type=1 > 2012-12-07 14:46:11 [22045] [7] DEBUG: DLR[internal]: created DLR message > for URL <a548e4db> > 2012-12-07 14:46:11 [22045] [7] DEBUG: HTTP[localpars]: Received DLR for > DLR-URL <a548e4db> > 2012-12-07 14:46:11 [22045] [7] DEBUG: HTTP[localpars]: Sending reply > ####################################### > > > > so i think there is something to do with smsc http with system type > generic. (not sure at all...) > > > i hope this will explain my concerns. > > > Thanks > Ali > > > On Fri, Dec 7, 2012 at 5:32 PM, Alvaro Cornejo > <cornejo.alv...@gmail.com>wrote: > >> Hi the issue is that kannel uses its own id for each MT creating a >> unique dest-number/id. >> >> When you submit the dlr you are using your own ID, therefore kannel >> have a no match pair dest_number/id. >> >> Regards >> >> Alvaro >> >> On 12/7/12, Ali Kashif <syedalikas...@gmail.com> wrote: >> > Dear users, >> > >> > my goal is to manually inject DLR to kannel. >> > for this is have created a http generic smsc with send-url, i am >> > getting >> > proper data in my php file. >> > >> > after parsing my message data in need to inject DLR back to my http >> > smsc, >> > ,but when i try that i face "Unknown DLR, not accepted" >> > >> > here is my http smsc conf and the data i am receiving in my php and the >> URL >> > to inject DLR, >> > >> > can anyone advise me what wrong i am doing? >> > >> > ############# >> > # My generic SMSC >> > ############# >> > group = smsc >> > smsc = http >> > system-type = generic >> > smsc-id = localpars >> > log-file = "/var/log/kannel/generic.log" >> > port = 8998 >> > send-url = " >> > >> http://localhost/asd.php?date=%t&unified_sender=%Q&unified_receiver=%q&message=%a&localsmsc=%i&dlr-mask=%d&service=%n&binfo=%B&sender=%P&receiver=%p&mid=%I&dlr-url=%R&coding=%c&charset=%C&FID=%F&mclass=%m >> > " >> > connect-allow-ip = "*.*.*.*" >> > reroute-dlr = true >> > smsc-username = user >> > smsc-password = pass >> > status-success-regex = "" >> > status-permfail-regex = "failure" >> > status-tempfail-regex = "retry later" >> > >> > >> > >> > ######################### >> > # data received in my php file >> > ######################### >> > Array >> > ( >> > [date] => 2012-12-07 07:47:20 >> > [unified_sender] => 21234A >> > [unified_receiver] => +9XXXXXXXXX >> > [message] => test rerout message >> > [localsmsc] => localpars >> > [dlr-mask] => 19 >> > [service] => ali >> > [binfo] => 11223 >> > [sender] => 21234A >> > [receiver] => +9XXXXXXXX >> > [mid] => 6f0087b5-7d98-4175-95e2-fd637dff63ba >> > [dlr-url] => 6f0087b5 >> > [coding] => 0 >> > [charset] => UTF-8 >> > [FID] => 6f0087b5 >> > [mclass] => 1 >> > ) >> > >> > ############################## >> > # URL which should injects the DLR >> > ############################## >> > >> > >> > >> http://172.18.4.24:8998/sms?username=user&password=pass&dlr-mask=1&dlr-mid=6f0087b5-7d98-4175-95e2-fd637dff63ba&to=+9xxxxxxxxx >> > >> > or >> > (without + in to parameter) >> > >> http://172.18.4.24:8998/sms?username=user&password=pass&dlr-mask=1&dlr-mid=6f0087b5-7d98-4175-95e2-fd637dff63ba&to=9xxxxxxxxx >> > >> > >> > >> > ############################## >> > # http smsc log when i call above URL >> > ############################## >> > 2012-12-07 08:07:06 [22756] [7] DEBUG: HTTP[localpars]: Got request >> `/sms' >> > 2012-12-07 08:07:06 [22756] [7] DEBUG: HTTP[localpars]: Received an >> > HTTP >> > request >> > 2012-12-07 08:07:06 [22756] [7] DEBUG: DLR[internal]: Looking for DLR >> > smsc=localpars, ts=6f0087b5-7d98-4175-95e2-fd637dff63ba, dst= 9xxxxxxx, >> > type=1 >> > 2012-12-07 08:07:06 [22756] [7] WARNING: DLR[internal]: DLR from >> > SMSC<localpars> for DST< 923219473162> not found. >> > 2012-12-07 08:07:06 [22756] [7] ERROR: HTTP[localpars]: Got DLR but >> > could >> > not find message or was not interested in it >> > id<6f0087b5-7d98-4175-95e2-fd637dff63ba> dst< 9xxxxxxx>, type<1> >> > 2012-12-07 08:07:06 [22756] [7] DEBUG: HTTP[localpars]: Sending reply >> > >> > >> > >> > >> > Thank >> > Ali >> > >> >> >> -- >> >> |-----------------------------------------------------------------------------------------------------------------| >> 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 >> > -- |-----------------------------------------------------------------------------------------------------------------| 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
