Re: Queuing Messages

2016-05-24 Thread amalysh
Hi,

more infos would be great. Version, which SMSC module, what is the config, etc.

Without infos, nobody can help you.

Alex

> Am 19.05.2016 um 13:02 schrieb Amelye Chatila :
> 
> Hello,
> 
> Messages get queued, we found that it is because of an I/O Error below
> 
> smsc-one.log 
>  
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: I/O error or other 
> error. Re-connecting. 
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: Couldn't connect to 
> SMS center (retrying in 10 seconds). 
>  
> bearerbox.log 
>  
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued. 
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
> 
> Routing failed means can not find the smsc but the smsc is up. The only 
> solution we have so far is to restart.
> 
> The issue why the queue is not emptied when the bind is up again? Is this I/O 
> Error a connection error to SMSC?
> 
> Thank you!
> 



Re: Queuing Messages

2016-05-23 Thread Manas Mohanty
Hi,

We are also facing this issue. No clue how to resolve this. Only solution
is to restart but restart loss messages in queue. We are using
gateway-1.4.4.

On Thu, May 19, 2016 at 4:32 PM, Amelye Chatila  wrote:

> Hello,
>
> Messages get queued, we found that it is because of an I/O Error below
>
> smsc-one.log
>
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: I/O error or other
> error. Re-connecting.
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: Couldn't connect to
> SMS center (retrying in 10 seconds).
>
> bearerbox.log
>
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
>
> Routing failed means can not find the smsc but the smsc is up. The only
> solution we have so far is to restart.
>
> The issue why the queue is not emptied when the bind is up again? Is this
> I/O Error a connection error to SMSC?
>
> Thank you!
>


Queuing Messages

2016-05-19 Thread Amelye Chatila
Hello,

Messages get queued, we found that it is because of an I/O Error below

smsc-one.log

2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: I/O error or other
error. Re-connecting.
2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: Couldn't connect to
SMS center (retrying in 10 seconds).

bearerbox.log

2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.

Routing failed means can not find the smsc but the smsc is up. The only
solution we have so far is to restart.

The issue why the queue is not emptied when the bind is up again? Is this
I/O Error a connection error to SMSC?

Thank you!