I Agree With you, i have ever meet this problem more terrible, submit_sm_resp always send seq_number 0x0 to each submit_sms. I ask the SMSC operator to fix this problem, because based on SMPP 3.3/3.4 spec, seq_number on submit_sm_rep should be correspondence to seq_number on submit_sm sent by ESME
Thx > Hi Jean, > > I think this is not a Kannel problem, but a SMSC one. Set loglevel > to 0 and check your kannel log to trace the PDU´s sequence numbers. > Maybe the SMSC loses the PDU correlativity, and that is why Kannel > warns you. If this is what is happening, the operator should fix this. > > Best regards, > > Rodrigo. > > On 8/11/05, Jean <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> We are experiencing problems with sequence numbers that get out of sync. >> >> We have experimented with changing throughput and max-pending-submits, >> but >> this does not always seem to resolve the issue. >> >> Has anyone had similar problems and found a solution? >> >> The bearerbox log message we receive is: >> 2005-08-10 16:20:37 [1648] [8] WARNING: SMPP[XXXXX]: SMSC sent >> submit_sm_resp with wrong sequence number 0x0000318b >> >> Our configuration for this SMSC is: >> >> # >> # Group: smsc >> # >> priority=3 >> system-type=smpp >> system-id> group=smsc >> smsc-id=XXXXX >> smsc=smpp >> service-type> #msg-id-type=1 >> source-addr-ton=1 >> source-addr-npi=1 >> source-addr-autodetect=0 >> host=XXXXXXXX >> smsc-username=XXXXX >> port=31000 >> smsc-password=XXXXXX >> throughput=6 >> max-pending-submits=50 >> data-coding-scheme=-1 >> reconnect-attempts=1000 >> interface-version=34 >> message-retry-attempts=100 >> dest-addr-npi=1 >> dest-addr-ton=1 >> transceiver-mode=1 >> reconnect-delay=60 >> denied-prefix=XXXXXXXX >> allowed-prefix> denied-smsc-id=XXXXXXX >> preferred-smsc-id=XXXXXX >> enquire-link-interval=60 > >
