Hi, Just as I suspected. You restarted bearerbox before receiving the DLR. It has nothing to do with connection/reconnection. How is poor bearerbox going to guess which was the original SMS? The match is stored in memory, which you purged when restarting the process.
BR, Nikos ----- Original Message ----- From: Elton Hoxha To: Nikos Balkanas Cc: Alvaro Cornejo ; kannel users Sent: Saturday, March 07, 2009 4:41 PM Subject: Re: MO-AT delivery report non returns Hi, here are the access.log records 2009-03-04 23:10:56 Sent SMS [SMSC:internal1] [SVC:a] [ACT:] [BINF:] [FID:2231470089] [from:77777] [to:355672509006] [flags:-1:0:-1:-1:31] [msg:121:heldsfffff ffffffffffffffffffffffssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssworld] [udh:0:] 2009-03-04 23:10:56 Receive DLR [SMSC:internal1] [SVC:a] [ACT:] [BINF:] [FID:2231470089] [from:77777] [to:355672509006] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [ud h:0:] Also I`m pasting the reference number of the delivery report that was pending in SMSC queue: 234982379117 Attached are the bearerbox logs Thanks guys Elton 2009/3/7 Nikos Balkanas <[email protected]> Hi, Please help me with something. Your access log says that it received the matching DLR (same FID, destination number) at 20:49:58, and yet you send us an excerpt from your bearerbox failing to match it at 20:51:22, almost 2' later? What happened in between? It's not even the same message, is it? Please post consistent access + bearerbox logs. BR, nikos ----- Original Message ----- From: Elton Hoxha To: Alvaro Cornejo Cc: kannel users Sent: Saturday, March 07, 2009 12:40 PM Subject: Re: MO-AT delivery report non returns Hi guys, I`m attching the conf file and bearerbox logs. Also the access.log records are: 2009-03-04 20:49:48 Log begins 2009-03-04 20:49:58 Sent SMS [SMSC:internal1] [SVC:a] [ACT:] [BINF:] [FID:2224527139] [from:77777] [to:355672509006] [flags:-1:0:-1:-1:31] [msg:121:heldsfffff ffffffffffffffffffffffssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssworld] [udh:0:] 2009-03-04 20:49:58 Receive DLR [SMSC:internal1] [SVC:a] [ACT:] [BINF:] [FID:2224527139] [from:77777] [to:355672509006] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [ud h:0:] Thanks Elton On Fri, Mar 6, 2009 at 10:18 PM, Alvaro Cornejo <[email protected]> wrote: Please post your complete config file and a complete log of the transaction send of message and the dlr transaction |-----------------------------------------------------------------------------------------------------------------| 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 Fri, Mar 6, 2009 at 1:49 PM, Elton Hoxha <[email protected]> wrote: > Hi, > > > while the delivery report is in the queue (after a disconnection of kannel > with SMSC) and the connection is re-established, the SMSC makes its own > retry to deliver the report to kannel, but kannel cannot handle to send it > to my application. > > 2009-03-04 12:22:06 [5885] [7] DEBUG: SMPP[internal1] handle_pdu, got DLR > 2009-03-04 12:22:06 [5885] [7] DEBUG: DLR[internal]: Looking for DLR > smsc=internal1, ts=2155185733, dst=355672509006, type=1 > 2009-03-04 12:22:06 [5885] [7] WARNING: DLR[internal]: DLR from > SMSC<internal1> for DST<355672509006> not found. > 2009-03-04 12:22:06 [5885] [7] ERROR: SMPP[internal1]: got DLR but could not > find message or was not interested in it id<2155185733> dst<355672509006>, > type<1> > > I tried all the msg-id-type values, like 1, 2 3 > > Thanks > Elton >
