PDA

View Full Version : porting an important number to Voip.ms



masfenix
Jul 27th, 2012, 07:31 PM
I have a important business line with Bell that I want to port to Voip.MS. My concern is that I do not want to lose the number in any condition. So does anyone have any advice on how to do this smoothly and correctly? I will be opening a new Voip.ms account (because my personal one has my home address while the business number has a different address).

So what should I be doing when opening a new account? Here is what I know


Name and address must match
I should NOT let the losing providor know I am porting

wilsonlam97
Jul 27th, 2012, 07:50 PM
I have a important business line with Bell that I want to port to Voip.MS. My concern is that I do not want to lose the number in any condition. So does anyone have any advice on how to do this smoothly and correctly? I will be opening a new Voip.ms account (because my personal one has my home address while the business number has a different address).

So what should I be doing when opening a new account? Here is what I know


Name and address must match
I should NOT let the losing providor know I am porting


Also have your account number ready and you should be good to go.

Avatar
Jul 27th, 2012, 08:45 PM
I have a important business line with Bell that I want to port to Voip.MS. My concern is that I do not want to lose the number in any condition. So does anyone have any advice on how to do this smoothly and correctly? I will be opening a new Voip.ms account (because my personal one has my home address while the business number has a different address).

So what should I be doing when opening a new account? Here is what I know


Name and address must match
I should NOT let the losing providor know I am porting


For important business line, I'll suggest Anveo. Reliability is solid for Anveo compare to VOIP.MS. The Toronto servers has been down for a few times already. That said, VOIP.ms is still a good provider for residential users with lots of features and services.

Porting your phone number is a straight forward process. There's actually a wiki for this on their site.

PianoGuy
Jul 27th, 2012, 09:55 PM
I'd agree with this. VoIP.ms' reliability has been very shaky lately, and the staff seem to be all talk and no action. I wouldn't trust an important business number to VoIP.ms. Anveo is a good contender though; their network is better designed and has fewer points of failure.

JamesA1
Jul 27th, 2012, 10:14 PM
I think the reliability of voip.ms has been quite good, even compared to the business-to-business voip companies we use for our office systems.

When porting a number, you can set up the DID in advance on voip.ms so that calls will go through correctly the instant that Bell makes the switch in their computers. That's still no guarantee that Bell won't screw something up, but if all goes properly it should take only a few seconds to make the switch (plus the 2-6 weeks lead time, of course).

silvy
Jul 28th, 2012, 01:32 PM
I've been using voip.ms for my business for the past 2 years. I have non-stop headaches and I've come to expect my phones to give me a problem regularly (which means at least once a day). It's sad that if I have a day or 2 without an issue, I consider it a good day. I'm so desperate to get away from them that I'm in talks with Rogers to switch to their hosted IP voice simply because I know I'll be able to call them. Sure, it will cost me probably an extra $1000 a year..but worth it, IMO. Moral of my story, I wouldn't recommend voip.ms if your phones being reliable with good support is important to you.

larrysy
Jul 31st, 2012, 08:45 AM
I just initiated a port from Bell to VOIP.ms - FOC was supposed to be on Aug 3 but Bell released my number prematurely by 5 days. I can make outgoing calls from VOIP.ms with the new number but cannot receive incoming calls. It seems that the new routing has to propagate through all different providers before I can receive incoming calls. Mine is just a residential number, so it's not critical. However, beware of the possibility that you will be left with several days unable to receive incoming calls.

BingoRingo
Jul 31st, 2012, 07:22 PM
I just initiated a port from Bell to VOIP.ms - FOC was supposed to be on Aug 3 but Bell released my number prematurely by 5 days. I can make outgoing calls from VOIP.ms with the new number but cannot receive incoming calls. It seems that the new routing has to propagate through all different providers before I can receive incoming calls. Mine is just a residential number, so it's not critical. However, beware of the possibility that you will be left with several days unable to receive incoming calls.

Your DID (number) cannot be used for outgoing calls, you can put whatever you want in the caller ID field, you can even make calls without a DID. The DID is only for incoming calls, and usually there should not be any delay between disconnection and reconnection with the new provider. I would doublecheck your settings.