Atlantic Telecom vs voip.ms

I set up a voice.ms account yesterday and configured that account using an Obi202 today. I was running into difficulties with the configuration so-called "customer services" for support and was told that voip.ms does not recommend obi talk and I could not get configuration help other than through the receipt of a pretty technical pdf sheet that they provided a link to. When I asked which devices they do support I was told "Can't recommend a device as I'm not a user or haven't used them all". In short, the voip.ms service agents are so ill-trained they know zippo about the devices that work on the service that employs them. The alternative is that they are instructed to avoid answering. I gave up on that customer service rep (Fred) and sought the help I needed through other online forums, which I found. After configuring the service, I made my first call on the voip.ms line (which is through their Vancouver 2 exchange) to my cellphone, my cellphone indicated the incoming call was from Russia so I placed a support ticket with voip and asked two questions. The first was: What do I need to do to reflect that the call was placed from the Vancouver area, not Russia? The second was: Is voip was a Russian based service? Neither of my questions were answered by the support agent (John) but I did get some lame excuse about why Russia might be shown as the origin of the call. That excuse did not sound plausible. Of the $20 I uploaded to my voip account yesterday, $10.10 was consumed in setting up which includes a month's outgoing calls, which is pretty reasonable. However, a voip service that mistakenly indicates I'm placing calls from Russia will result in so many calls not being answered that the service is not worth having. That, along with the quite derisory quality of customer service I received, and the risk of voip.ms being a Russian based company with whatever potential security issues that might attach to that circumstance, means I'm dropping them today like a hot potato.