We had a similar situation the difference is we had the instance on two different servers instead of two different ports. The solution for us was to store the DLR's in a database instead of allowing kannel to handle them internally. Our issue was that the response would come in on the other bind and it didn't know about he DLR on the other server. So on DLR was triggered. Once we moved the DLR's to a database and had them ignore the SMSC ID then the deliver_sm could come back on either server and either server could find the DLR and send it. I hope this helps.
--Eric On Thu, Jul 12, 2012 at 12:45 PM, neo nortan <[email protected]>wrote: > > Please help > i have configure two instances of kannel on two different ports.both are > working fine, messages or going properly and dlrs are also recieving > properly in sent_sms table. but not able to understand after sending some > message one or two messages get stuck, not getting dlrs of these message > while messages are delivered properlyand there is one more record is > showing in DLR table. > > thanx > regards > > > <http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline.htm@Middle?> > Follow *Rediff Deal ho > jaye!<http://track.rediff.com/click?url=___http://dealhojaye.rediff.com?sc_cid=rediffmailsignature___&cmp=signature&lnk=rediffmailsignature&newservice=deals> > * to get exciting offers in your city everyday.
