Hello, I am still digging around this issue.
In the changelog for kannel 1.5.0 it says that since version 1.4.3 Fixed weak DLR resolving for some SMSC types. I tried to search in redmine for what has changed but I didn't find anything. I would like to see if the changes might my problem. Another question would you 1.5.0 in a production environment? -- Oscar On Thu, Feb 3, 2011 at 8:23 AM, Oscar Cassetti <oscar.getstr...@gmail.com> wrote: > If it can help or add any other information the SMSC center has said > > "As I can see from your traces you have messageid mapped to wrong message:" > > Is there a memory corruption going on or something? > > -- > Oscar Cassetti > > > > > > > On Wed, Feb 2, 2011 at 8:21 PM, Oscar Cassetti > <oscar.getstr...@gmail.com> wrote: >> Hello, >> >> I am having some problem to figure out why some delivery reports are >> mapped incorrectly >> in kannel. For instance if I submit the following message >> from = 1234567890 >> to = 0987654321 >> text = blah blah >> >> when the delivery report is received the message is mapped to a different >> from number and to number but same text (say) >> >> from = 222222222 >> to = 4444444444 >> text = blah blah >> >> Now the message to 44444444 does exist but the text would be totally >> different. >> >> This happens occasionally and I am not sure if this is problem related >> to kannel >> or to SMSC that I use. I tried to increase the level to debug but I did not >> spot >> the problem. I really don't where the mapping is happening. >> >> I am currently connecting to SMSC via SMPP using two connection one for >> sending >> the messages and one for receiving the delivery reports. >> >> I am using Mysql as dlr-storage >> >> Below a example of what I caught in the logs >> >> 2011-02-02 16:07:04 Sent SMS [SMSC:mySMSC] [SVC:mySMSC] [ACT:] [BINF:] >> [FID:xxxxxxxx] [from:123457890] [to:0987654321] [flags:-1:0:-1:-1:31] >> [msg:126:1030 blah blah blah] [udh:0:] >> 2011-02-02 16:07:04 Receive DLR [SMSC:mySMSC] [SVC:mySMSC] [ACT:] >> [BINF:] [FID:xxxxxxxxxx] [from:123457890] [to:0987654321] >> [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] >> >> (Here the wrong mapping) >> >> 2011-02-02 16:14:41 Receive DLR [SMSC:mySMSC] [SVC:mySMSC] [ACT:] >> [BINF:] [FID:xxxxxxxxxx] [from:2222222222] [to:44444444444] >> [flags:-1:-1:-1:-1:1] [msg:129:id:71020217070660233 sub:001 dlvrd:001 >> submit date:1102021707 done date:1102021707 stat:DELIVRD err:000 >> text:1030 blah blah] [udh:0:] >> >> >> Below the configuration for the smsc. >> >> #Sender section >> >> group = smsc >> smsc = smpp >> smsc-id = "mySMSC" >> denied-smsc-id = "OTHER_SMSC_1", "OTHER_SMSC_2", "OTHER_SMSC_3" >> allowed-smsc-id = "mySMSC" >> host = smpp3.mySMSC.com >> port = 1234 >> smsc-username = "USERNAME" >> smsc-password = "PASSWORD" >> system-type = "SMPP" >> interface-version = 34 >> alt-addr-charset = GSM >> msg-id-type = 0x03 >> max-pending-submits = 50 >> connection-timeout = 30 >> denied-prefix = "87;86;85;84;83;" >> log-file = "/opt/kannel/logs/mySMSC.log" >> log-level = 1 >> >> #Receiver section >> >> group = smsc >> smsc = smpp >> smsc-id = "mySMSC" >> denied-smsc-id = "uk_ls", "cardboard", "hsl" >> allowed-smsc-id = "mySMSC" >> host = smpp3.mySMSC.com >> port = 0 >> receive-port = 1234 >> smsc-username = "USERNAME" >> smsc-password = "PASSWORD" >> system-type = "SMPP" >> interface-version = 34 >> alt-addr-charset = GSM >> msg-id-type = 0x03 >> connection-timeout = 30 >> log-file = "/opt/kannel/logs/mySMSC-rcv.log" >> log-level = 1 >> >> Thanks for any advice. >> >> -- >> Oscar Cassetti >> >
