RE: [BUG] failure to send DLR with SMPP
"Oded Arbel" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
> -----Original Message----- > From: Alan McNatty [mailto:[email protected]] > I experience the same problem but haven't been working on it lately > (dlr's on back burner at present). I have patched local copy to get > working though, my patch does something simple like ... > > from handle_pdu - deliver_sm > > > if ( pdu->u.deliver_sm.destination_addr > != NULL ) > > tmp_addr = pdu->u.deliver_sm.destination_addr; > > else > > tmp_addr = pdu->u.deliver_sm.source_addr; > > So rather than changing the dlr_find I have not did that - simply commented that the change to dlr_find() which has no correlation with SMPP caused this bug to surface > we work around a smpp > bug from smsc > by building the *right* pdu (it is really a break in protocol standard > so IMHO this is the better place to do it). I didn't understand your patch - are you suggesting that getting the receiver of the original message in the "source_addr" field of the DLR report is not compliant with the SMPP protocol ? -- Oded Arbel m-Wise mobile solutions [email protected] +972-9-9581711 (116) +972-67-340014 ::.. The biggest lies: 23. Now, I'm going to tell you the truth > > Cheers, > Alan > > On Wed, 2002-09-25 at 05:00, Oded Arbel wrote: > > Hi list. > > > > we found a problem with SMPP in one of out connections - > when a deliver_sm of type DLR is received, Kannel will fetch > a dlr with the sms.receiver set to the destination_addr from > the deliver_sm. at least on the connection we checked, this > is wrong as the deliver_sm message has the source_addr set to > the MSISDN of the receiver of the original message and the > destination_addr set to the sender of the original address - > as if the message is an MO in response to the MT we sent. of > course, the result is that in the created DLR message, the > sender and receiver numbers are identical and so smsbox > rejects the message. > > I think it can only happen in the CVS version of Kannel, as > only lately a change has been made to the DLR scheme to > remeber also the sender of the original message and fill it > in the DLR message. > > > > Did anyone else encounter this problem, and do you think > its safe to fix it by changing the call to dlr_find() to use > source_addr instead of destination_addr - the dlr_find() > function does not do anything interesting with that value, > except putting it into the receiver field of the DLR msg. > > > > -- > > Oded Arbel > > m-Wise mobile solutions > > [email protected] > > > > +972-9-9581711 (116) > > +972-67-340014 > > > > ::.. > > Wasting time is an important part of living. >