Hi, thanks for the DLR, yeah... i wasn't aware that was a dlr because i didn't enable any DLR but the SMSC sent me that, from other source i think, i've change the config to define smsc-id and it works :) , i also tested with ur fix on latest cvs without defining smsc-id and it works too :) thanks a lot :)
-man- ----- Original Message ----- From: "Bruno David Simões Rodrigues" <[EMAIL PROTECTED]> To: "Abd Rahman Johari" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, May 03, 2002 8:39 AM Subject: Re: More Info: Problem with EMI2, latest cvs > On Fri, 2002-05-03 at 00:21, Abd Rahman Johari wrote: > > more info regarding this issue, if the SMSC doesn't send any message, the > > kannel was okay and i can send out sms, > > but if the kannel starts to receive message from SMSC, it will just die with > > the following error, i wonder what has happened here, > > since i have just got into this kind of problem couple days ago. I've tested > > with early release of kannel and all of them face the same problem. > > You are not receiving a message (O-52) but a deliver report (O-53) and > deliver reports expect you to have a smsc-id defined on configuration. > > To avoid this problem, I've changed the code to use "name" variable if > smsc-id is undefined. > > Please check newest cvs and see if it works ok. > > > About the unsupported EMI XSer, just ignore them. My smsc, after last > upgrade, sends-me that XSER too.. > > It's a "single-shot indicator" and its value is the default, and the > field shouldn't be there, but cmg doesn't accept it as a "bug". > (XSER = 0D0100) > > > > >
