Hi Dan, I don't see any errors in my bearerbox.log file. Here's a sample of what I see:
2015-10-27 14:51:26 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:51:26 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:26 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:51:26 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:51:35 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:35 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:51:36 [22127] [9] DEBUG: boxc_receiver: sms received 2015-10-27 14:51:36 [22127] [9] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:36 [22127] [8] DEBUG: sms_router: handling message (0x26be190 vs 0x26be190) 2015-10-27 14:51:36 [22127] [8] DEBUG: Routing failed, re-queued. 2015-10-27 14:51:36 [22127] [8] DEBUG: sms_router: handling message (0x26be190 vs 0x26be190) 2015-10-27 14:51:36 [22127] [8] DEBUG: Routing failed, re-queued. 2015-10-27 14:51:36 [22127] [8] DEBUG: sms_router: time to sleep 30.00 secs. 2015-10-27 14:51:36 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:51:47 [22127] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2015-10-27 14:51:47 [22127] [2] DEBUG: HTTP: Created HTTPClient area 0x26c21a0. 2015-10-27 14:51:47 [22127] [3] DEBUG: HTTP: Destroying HTTPClient area 0x26c21a0. 2015-10-27 14:51:47 [22127] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2015-10-27 14:51:50 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:50 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:51:51 [22127] [9] DEBUG: boxc_receiver: sms received 2015-10-27 14:51:51 [22127] [9] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:51 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:51:52 [22127] [9] DEBUG: boxc_receiver: heartbeat with load value 0 received 2015-10-27 14:51:55 [22127] [8] DEBUG: sms_router: gwlist_len = 2 2015-10-27 14:51:55 [22127] [8] DEBUG: sms_router: handling message (0x26be190 vs 0x26be190) 2015-10-27 14:51:55 [22127] [8] DEBUG: Message routed successfully. 2015-10-27 14:51:55 [22127] [8] DEBUG: sms_router: handling message (0x26c2d60 vs 0x26c2d60) 2015-10-27 14:51:55 [22127] [8] DEBUG: Message routed successfully. 2015-10-27 14:51:56 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:56 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:51:56 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:51:56 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:51:56 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:51:56 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:52:05 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:52:05 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:52:06 [22127] [9] DEBUG: boxc_receiver: sms received 2015-10-27 14:52:06 [22127] [9] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:52:06 [22127] [8] DEBUG: sms_router: handling message (0x26bf730 vs 0x26bf730) 2015-10-27 14:52:06 [22127] [8] DEBUG: Routing failed, re-queued. 2015-10-27 14:52:06 [22127] [8] DEBUG: sms_router: handling message (0x26bf730 vs 0x26bf730) 2015-10-27 14:52:06 [22127] [8] DEBUG: Routing failed, re-queued. 2015-10-27 14:52:06 [22127] [8] DEBUG: sms_router: time to sleep 30.00 secs. 2015-10-27 14:52:06 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:52:20 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:52:20 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:52:21 [22127] [9] DEBUG: boxc_receiver: sms received 2015-10-27 14:52:21 [22127] [9] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:52:21 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:52:22 [22127] [9] DEBUG: boxc_receiver: heartbeat with load value 0 received 2015-10-27 14:52:25 [22127] [8] DEBUG: sms_router: gwlist_len = 2 2015-10-27 14:52:25 [22127] [8] DEBUG: sms_router: handling message (0x26bf730 vs 0x26bf730) 2015-10-27 14:52:25 [22127] [8] DEBUG: Message routed successfully. 2015-10-27 14:52:25 [22127] [8] DEBUG: sms_router: handling message (0x26c1850 vs 0x26c1850) 2015-10-27 14:52:25 [22127] [8] DEBUG: Message routed successfully. 2015-10-27 14:52:26 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:52:26 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:52:26 [22127] [9] DEBUG: boxc_receiver: got ack 2015-10-27 14:52:26 [22127] [10] DEBUG: send_msg: sending msg to box: <127.0.0.1> 2015-10-27 14:52:26 [22127] [10] DEBUG: boxc_sender: sent message to <127.0.0.1> 2015-10-27 14:52:26 [22127] [9] DEBUG: boxc_receiver: got ack When looking at the service provider's logs, MT's are successful, but MO's are failing. I'm beginning to wonder if it's a capacity issue. If that were the case, would there be any indication? On Tue, Oct 27, 2015 at 10:19 AM, Jesus D Irausquin V <jdirausq...@gmail.com > wrote: > If the SMSC server is disconnected you should see something like: > > ERROR: connect to <xxx.xx.xx.xx> failed > ERROR: System error 110: Connection timed out > ERROR: error connecting to server `xxx.xx.xx.xx' at port `zzzzz' > ERROR: SMPP[SMSC_ID]: Couldn't connect to server. > ERROR: SMPP[SMSC_ID]: Couldn't connect to SMS center (retrying in 10 > seconds). > DEBUG: Connecting to <xxx.xx.xx.xx> > > Regards. > > 2015-10-27 9:34 GMT-04:30 Lester Freamon <oneonezeroonedotd...@gmail.com>: > >> Hi Dan, >> >> I ran a Ping against our service provider's SMSC server (over VPN) for 9 >> minutes yesterday and had no packet drops. I will look into changing the >> log-level to zero. Would you recommend looking for any particular errors or >> statuses in the logs? >> >> >> On Tue, Oct 27, 2015 at 9:32 AM, Jesus D Irausquin V < >> jdirausq...@gmail.com> wrote: >> >>> Hello Lester, >>> Maybe the log-file bearerbox.log (with log-level = 0) can be helpful. >>> This looks like a connectivity issue... Are you sure this isn't a VPN >>> problem? Try to keep a ping to the SMSC or telnet SMSC port. >>> Regards. >>> Dan >>> >>> 2015-10-26 12:55 GMT-04:30 Lester Freamon < >>> oneonezeroonedotd...@gmail.com>: >>> >>>> Hello, >>>> >>>> I have several Kannel setups in place but this one in particular is >>>> causing me some headaches. According to the provider, they attempt to send >>>> us a message but the connection gets terminated before an acknowledgement >>>> was received. In the provider's logs, we see the message as being sent, in >>>> the smsbox.log files, I don't see any "Starting to service..." statements >>>> for messages that fail. It seems we're simply not receiving them. >>>> >>>> What's strange is the frequency in which this issue manifests. Looking >>>> at the logs, I cannot discern any pattern -- it's just randomly working, >>>> and then not. >>>> >>>> I have tried adjusting the timeout to 60 seconds (60000 in the conf), >>>> but the issue still persists. >>>> >>>> This connection is over VPN, but after some investigation, VPN doesn't >>>> appear to be causing the issue. >>>> >>>> Is there a particular set of troubleshooting steps I should follow to >>>> determine the root cause? >>>> >>>> We're using Kannel bearerbox II version 1.4.3 if that's helpful. >>>> >>>> Thank you. >>>> >>> >>> >>> >>> >> > > >
