Call to messageGateway.Find(config) with invalid COM-port hangs
When calling messageGateway.Find(config) with and invalid COM-port, the call hangs.
Is it possible to avoid this? Some user will undoubtably try it...
This is a bit tricky. The COM port exists but is not a valid port for the modem.
So when the library sends the AT command, there is no response after waiting for 30 seconds for each command.
We have patched it such that if during connection set up, there is no OK response, the library will raise a "Invalid COM port" exception.
In case you have already downloaded version 220.127.116.11, please download it again and try. The exception will be raised after 30 seconds.