Nisan Bloch wrote:
Hi
We have a queue load balancer in front of Kannel, that through a
statusbox monitors Kannel, and knows extended information about each
gateway that kannel is connected to. This way we can control the throughput
of any of the Kannel connections, as well as load balance
Rory Campbell-Lange schrieb:
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!
yeah, Kannel performs very well ;))
I've
Alexander Malysh wrote:
hmm, sleep is very bad (imho). In this sleep time you can maybe handle 100
delivery receipts instead just sleeping. It would be great to add abstracted
bandwidth calculation code to kannel and then send only if bandwidth allow
this.
so sleeping makes only sense if
Alexander Malysh [EMAIL PROTECTED] wrote:
Hi Bruno,
Am Donnerstag, 19. Juni 2003 16:03 schrieb Bruno Rodrigues:
Stipe Tolj [EMAIL PROTECTED] wrote:
Bruno Rodrigues wrote:
You need to sleep right after sending the message for it to work.
We can have configuration code in smsccon
Rory Campbell-Lange wrote:
The only error codes I'm getting are:
2003-06-06 20:42:53 [8] ERROR: SMPP[orangelong]: SMSC returned error
code 0x0045 in response to submit_sm.
according to SMPP specs this is considered to be a *general* error for
a submit_sm PDU. (seee SMPP v3.4, p. 113).
Andreas Fink wrote:
AT2 module sleeps anyway and waits for ACK from modem before proceeding.
So adding sleeps there is not making any sense unless you wana limit it to have only
1 message every minute or such.
ok, I wasn't aware of it right now. That's fine with me then.
Stipe
[EMAIL
Thanks for the help, Alex and Andreas.
I've had a look at the specs. Thanks for the pointer, Andreas.
You are right, Alex. I'm not suffering from throttling problems. I have
no 0x0058 errors in my logs, despite sometimes sending Kannel over
100 messages in a second on some occasions --
|There's no way to make it more elegant!||The SMPP specs dont allow for anything else. Nice would be
to stop sending if we |got "throttle" and resume when we get some kind of
"resume" message but there is |no such message. Kannel does the only valid thing
which is wait a bit and try |again.
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
Hi Andreas
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 = 0x8004
2003-06-06 07:30:08 [6] DEBUG: command_status: 0 = 0x
2003-06-06
Rory Campbell-Lange wrote:
My smsbox/bearerbox setup has been working flawlessly for about a month.
However recently I have had to restart the system after a number of
messages are shown as queued but not sent. On restarting bearerbox the
messages flood through.
The problems start with a
My smsbox/bearerbox setup has been working flawlessly for about a month.
However recently I have had to restart the system after a number of
messages are shown as queued but not sent. On restarting bearerbox the
messages flood through.
The problems start with a message I sent myself at 7.30am in
12 matches
Mail list logo
