Thanks for the comments. It would appear that the "hackers" are only looking for the first standard port 5060 and not looking for 5062. That may be why only Voipo is affected as line 1. I will take your suggestions and see if that works.

I've used voip with Quantumvoice for over three years and never had this problem using the standard port configuration. I may just switch my Voipo line to #2 and my voip.ms line to #1 to see if the problem follows the line or service. An interesting experiment.