Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas
Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
After doing a bunch of troubleshooting with a Bigpond 320U myself, I eventually found that swapping the username/password (i.e. username in the password field and vice versa) in the LTE interface config got it working. IIRC that was on a much earlier version of the 6.0 branch so they may have fixed it in a later release, but it would be worth giving that a try. I might even re-test later this afternoon with 6.18 if I get a chance. Cheers, Andrew. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au Important Notice: The contents of this email are intended solely for the named addressee and are confidential; any unauthorised use, reproduction or storage of the contents is expressly prohibited. If you have received this email in error, please delete it and any attachments immediately and advise the sender by return email or telephone. Deakin University does not warrant that this email and any attachments are error or virus free.
Hi Andrew, This device is on a Telstra corporate account, so there is no username and password - the full config for the PPP interface is: /interface ppp-client add add-default-route=yes allow=pap,chap,mschap1,mschap2 apn=telstra.extranet \ comment="Telstra 4G (USB) uplink" data-channel=3 default-route-distance=1 \ dial-command=ATDT dial-on-demand=no disabled=no info-channel=2 \ keepalive-timeout=30 max-mru=1500 max-mtu=1500 modem-init="" mrru=disabled \ name=telstra-uplink null-modem=no password="" phone="" pin="" port=usb1 \ profile=default use-peer-dns=yes user="" Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Andrew Van Slageren Sent: Tuesday, 26 August 2014 1:26 PM To: MikroTik Australia Public List Subject: Re: [MT-AU Public] SMS send timeouts After doing a bunch of troubleshooting with a Bigpond 320U myself, I eventually found that swapping the username/password (i.e. username in the password field and vice versa) in the LTE interface config got it working. IIRC that was on a much earlier version of the 6.0 branch so they may have fixed it in a later release, but it would be worth giving that a try. I might even re-test later this afternoon with 6.18 if I get a chance. Cheers, Andrew. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au Important Notice: The contents of this email are intended solely for the named addressee and are confidential; any unauthorised use, reproduction or storage of the contents is expressly prohibited. If you have received this email in error, please delete it and any attachments immediately and advise the sender by return email or telephone. Deakin University does not warrant that this email and any attachments are error or virus free. _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, No luck setting the info channel to 3 (the same as the data channel) - the PPP session connects, but still only get about a 50-60% success rate sending messages :( Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Thomas, Just to check whether it is serial port/channel conflict, try disabling ppp and see if that allows txt to pass through more reliably. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 1:40 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, No luck setting the info channel to 3 (the same as the data channel) - the PPP session connects, but still only get about a 50-60% success rate sending messages :( Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, No luck there, I disabled the PPP client interface and only managed to send 2 messages out of 5 tries. To eliminate any problems with this particular hardware, at another of our sites, we have an OmniTIK U-5HnD with the same model of Sierra Wireless dongle attached - I've tried using that to send some messages, and am seeing similar results from that too. Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Thursday, 28 August 2014 9:03 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Just to check whether it is serial port/channel conflict, try disabling ppp and see if that allows txt to pass through more reliably. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 1:40 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, No luck setting the info channel to 3 (the same as the data channel) - the PPP session connects, but still only get about a 50-60% success rate sending messages :( Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
That is strange indeed. Unless anyone else has further ideas, perhaps we can send a question to MT to ask what are the possible causes of that timeout behaviour. If you want to follow that path, please do this: 1) power cycle router 2) disable ppp 3) send a few test txt to show some working some failing 4) make supout file 5) send supout to support@duxtel.com Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Thursday, 28 August 2014 9:23 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, No luck there, I disabled the PPP client interface and only managed to send 2 messages out of 5 tries. To eliminate any problems with this particular hardware, at another of our sites, we have an OmniTIK U-5HnD with the same model of Sierra Wireless dongle attached - I've tried using that to send some messages, and am seeing similar results from that too. Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Thursday, 28 August 2014 9:03 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Just to check whether it is serial port/channel conflict, try disabling ppp and see if that allows txt to pass through more reliably. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 1:40 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, No luck setting the info channel to 3 (the same as the data channel) - the PPP session connects, but still only get about a 50-60% success rate sending messages :( Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, Thanks, I'll forward you the supout file in a few mins Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Thursday, 28 August 2014 9:48 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts That is strange indeed. Unless anyone else has further ideas, perhaps we can send a question to MT to ask what are the possible causes of that timeout behaviour. If you want to follow that path, please do this: 1) power cycle router 2) disable ppp 3) send a few test txt to show some working some failing 4) make supout file 5) send supout to support@duxtel.com Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Thursday, 28 August 2014 9:23 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, No luck there, I disabled the PPP client interface and only managed to send 2 messages out of 5 tries. To eliminate any problems with this particular hardware, at another of our sites, we have an OmniTIK U-5HnD with the same model of Sierra Wireless dongle attached - I've tried using that to send some messages, and am seeing similar results from that too. Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Thursday, 28 August 2014 9:03 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Just to check whether it is serial port/channel conflict, try disabling ppp and see if that allows txt to pass through more reliably. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 1:40 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, No luck setting the info channel to 3 (the same as the data channel) - the PPP session connects, but still only get about a 50-60% success rate sending messages :( Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 1:11 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, If you can access by ppp, then LTE /should/ work OK but it is never an exact science - sometimes even modem firmware can make a difference. Maybe try setting info channel to the same as data channel - for modems that only have one channel available, this seems to work ok (just that access to 'info' is not available when data session I online) If you can manage that, then maybe it will leave channel 2 available for your txt actions? Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 12:22 PM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I had not seen that paragraph yet - when it does fail, it takes about 2 seconds to time out, so I guess that points to something during the AT command exchange. I need the data channel to remain connected given the primary use of this device as OOB access - but I can see that the PPP session has been up for a few hours now, and during that time I have been able to sometimes send and sometimes not send messages, so I'm not sure if the two are directly related. I've been using port usb1 and channel 2 for sending messages and the PPP client is configured to use channel 3 for data and channel 2 for info messages. As a thought, I have got "/port firmware set ignore-directip-modem=yes" set because I've never been able to get the native LTE interface type to work - would there be any value in persevering with trying to get LTE working (if so, can you point me in the direction of a guide on how to set it up)? Cheers, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 11:57 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts OK, How long does it take to fail, when it does play up? Did you note this paragraph in the wiki docs: Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange. What port are you using for txt? Is it possible, for example, that you are using the same port as data channel and data channel is attempting to dial up ppp session every few seconds so that txt only works during the in-between times when ppp dialler gives up and releases data channel for a few seconds before retry? Or something like that? ;) As far as I am aware, you don't need to have data channel connected to send TXT - just needs SIM registered to an available telco. Cheers! Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 10:51 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Mike, I get the same problem when entering the send SMS command straight into the Mikrotik terminal, so looks like the API is behaving correctly and it is a problem with the SMS tool: [me@myrouter] > /tool sms send port=usb1 channel=2 phone-number=<my mobile> message="This is a test" failure: timeout Thanks, Thomas -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 26 August 2014 10:30 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] SMS send timeouts Hi Thomas, Have you decided yet whether it is an API timeout or a sms timeout? I suspect the latter (from the way it looks in the log) but your reference to 'the API returns a timeout error' throws me :-} Cheers, Mike. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Tuesday, 26 August 2014 9:36 AM To: MikroTik Australia Public List Subject: [MT-AU Public] SMS send timeouts Hi all, I'm trying to set up a Nagios box to send SMS alerts using an RB751U-2HnD which has a Telstra 4G USB device (Sierra Wireless 320U) connected to the USB port. At the moment, we use the SMSGlobal API (which was down for most of yesterday afternoon) to send notifications from Nagios, which has the major downside of relying on the internet connection from our Nagios box being alive and of course, relies on the API provider being online as well. The RB751U-2HnD is already in place (it is currently used to provide OOB access into the network - permanently connected to the telstra.extranet APN for a public IP with DynDNS set up so that it can be found), so I figured it would be easy to add this functionality in. So far, I've got a PHP script written that will (via a Mikrotik API call) send an SMS out about 60% of the time - the rest of the time, the API returns a timeout error (also logged to the Mikrotik log - eg "gsm,error sms send failed: timeout"). This happens completely randomly, sometimes I can send 10 messages in a row without a problem, then have another 10 that fail - other times, I can send 10 messages and have every second one fail. A basic solution would be to simply catch the error in the PHP script and try to send again, but I'd like to see if I am missing anything in the Mikrotik config first. Currently running version 6.10 and I can't see anything in the changelog since then that references SMS. Relevant config sections: /tool sms set channel=2 port=usb1 receive-enabled=yes secret=smspassword /port set 0 name=usb1 /port firmware set ignore-directip-modem=yes /interface ppp-client info 0 modem-status: call in progress pin-status: no password required functionality: full manufacturer: Sierra Wireless, Incorporated model: AirCard 320U revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41 serial-number: redacted current-operator: Telstra (cellid redacted) access-technology: Evolved 3G (LTE) signal-strengh: -85 dBm frame-error-rate: n/a Has anyone come against this problem before? Cheers, Thomas _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
participants (3)
-
Andrew Van Slageren
-
Mike Everest
-
Thomas Jackson