SMS To Multiple Numbers
I currently have version 14.2.4 of ServersCheck Monitoring Software paired with a Huawei E3272 modem in COM mode. ServersCheck is able to interface with the E3272 modem and send texts however if I try to set more than one phone number to receive texts, nothing happens. What I have set in the SMS options is +1203XXXXXXX,+1914XXXXXXX and in both options "the default SMS number(s)" and "yes to this number(s)" both only work when one phone number is present.
Has anyone else noticed this issue or has maybe found a solution?
As a side note, hopefully this will help out other people, I purchased the Huawei E3272s-150 off of eBay and used a T-Mobile SIM. It turns out that AT&T was incompatible with the Huawei E3272s-150. The modem came with HiLink installed without COM mode enabled. I ended up needing to downgrade the firmware to E3272s_Update_21.420.07.00.00 and find the correct COM drivers. I needed the flash code generated by a program called Universal Master Code Calculator Final 2013 in order to flash the update. This tutorial http://blog.le-vert.net/?p=196 outlines everything well and https://routerunlock.com has links to these files. You can also use Putty in serial mode to send AT commands to the modem.
Has anyone else noticed this issue or has maybe found a solution?
As a side note, hopefully this will help out other people, I purchased the Huawei E3272s-150 off of eBay and used a T-Mobile SIM. It turns out that AT&T was incompatible with the Huawei E3272s-150. The modem came with HiLink installed without COM mode enabled. I ended up needing to downgrade the firmware to E3272s_Update_21.420.07.00.00 and find the correct COM drivers. I needed the flash code generated by a program called Universal Master Code Calculator Final 2013 in order to flash the update. This tutorial http://blog.le-vert.net/?p=196 outlines everything well and https://routerunlock.com has links to these files. You can also use Putty in serial mode to send AT commands to the modem.
Comments
this was found as a bug and was reported internally. rest assured that our development team is already working on it. An update will be released once we have the fix.