Thanks very much for your message, Stipe. Upon enquirey it appears that the target SMPP host only allows 6 messages a second to pass through on our service. I was trying to send 150 messages in less than a second!
I've slowed down the sending system. However, is there a way of throttling the number of messages sent in a second or automatically retrying requeued messages when sending clients try to send too many messages in a few moments? Thanks for your time, Rory On 08/06/03, Stipe Tolj ([EMAIL PROTECTED]) wrote: > Rory Campbell-Lange wrote: > > Is this a response? > > > > 2003-06-06 07:30:08 [6] DEBUG: SMPP PDU 0x81358a0 dump: > > 2003-06-06 07:30:08 [6] DEBUG: type_name: submit_sm_resp > > 2003-06-06 07:30:08 [6] DEBUG: command_id: 2147483652 = 0x80000004 > > 2003-06-06 07:30:08 [6] DEBUG: command_status: 0 = 0x00000000 > > 2003-06-06 07:30:08 [6] DEBUG: sequence_number: 4992 = 0x00001380 > > 2003-06-06 07:30:08 [6] DEBUG: message_id: "0647D504" > > 2003-06-06 07:30:08 [6] DEBUG: SMPP PDU dump ends. > > > > If so does the submit_sm_resp come from the service provider (the SMPP server > > at Orange?). Is there any way of flushing a queue with messages that havne't got a > > response? As I mentioned, the messages ended up being sent after I restarted > > bearerbox. > > the problem is that the submit_sm_resp are not send from the SMPP > server side and Kannel interprets this as temporary problem with the > SMSC and keeps the message in it's queue. > > Best way would be to ask your SMSC provider why they don't seem to > send the submit_sm_resp PDUs. -- Rory Campbell-Lange <[EMAIL PROTECTED]> <www.campbell-lange.net>
