![]() |
|
|
|
|
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes | |
|
|
||||
|
|
#31 |
|
Join Date: Jun 2002
Posts: 17
|
Submitted port request Feb14. Current phone provider Teksavvy. Voip.ms indicated their carrier is currently swamped with port request. Anyone else experiencing this kind of delay?
|
|
|
| Sponsored Links | |||
Advertisement | |||
|
|
#32 |
|
Join Date: Nov 2008
Location: Alberta
Posts: 796
|
Unfortunately yes - I did a port at the beginning of the year to what was probably the same carrier. The delay is most annoying, but it's worth the wait since if the carrier is who I think it is, it's one of the better ones.
|
|
|
|
|
#33 |
|
Rookie
Join Date: Apr 2011
Posts: 6
|
I am new to VOIP MS in the past month and I am thinking of dumping my Bell land line. I also have Bell DSL internet. I know if I port my number, I initiate the request with VOIP MS.
My questions is if I want to dry loop my internet and then port my number, what is the correct order of operations? Thanks in advance. |
|
|
|
|
#34 |
|
Join Date: Mar 2007
Posts: 64
|
What I did (and I'm not saying my case is the same as yours)...
Initially I obtained a new DID from voip.ms. Then, after setting up voip.ms to have mailboxes etc for the new DID, I call forwarded my Bell number to the new DID. At this point, seeing I am a Rogers client I could disconnect the Bell network at the demarc. from the house wiring, and attach an ATA to the house wiring, leaving all the other phones as is. I have just submitted a porting request to have the number moved from Bell, and, once that is done I will cancel the temporary DID. In your case, the only challenge I would see is the need for the DSL modem to stay attached to the Bell network. |
|
|
|
|
#35 |
|
Rookie
Join Date: Apr 2011
Posts: 4
|
I ported from Telus landline to Voip.ms
It took me 7 days. Last edited by hugh; 2011-04-19 at 11:48 AM. Reason: removed off topic portion. please stay on topic |
|
|
|
|
#36 |
|
Join Date: Nov 2005
Posts: 16
|
Ported my number as well as a colleague from Vonage.
In my case, I chose a date (22 days in the future) so that I could cancel close to my next billing date with Vonage. Got approved within 2 business days. But after 14 days ( 10 business days), my port request was rejected by voip.ms carrier asking for latest authorization. Once your re-start, it takes another 2 business days to get approved but they were able to meet the original cutover date. If you follow this route, keep an eye out and act fast if you face any obstacle. In my colleagues case, took exact 7 days (5 business days) to get ported over. You dont need to call vonage to cancel. They will send you a cancellation email with what you owe them. |
|
|
|
|
#37 |
|
Rookie
Join Date: Apr 2011
Posts: 6
|
Thank you for the replies. My porting concern is that I can't loose my current DSL connection with Bell. So I am not sure if I can do a dry loop request when I have an active phone line (that will be ported) to ensure I have DSL before I do my port request with Voip MS.
Can anyone post a similar experience? |
|
|
|
|
#38 |
|
Rookie
Join Date: Mar 2011
Location: Toronto
Posts: 14
|
You don't need to do a "dry loop request when I have an active phone line (that will be ported)". Once your number is ported, you will no longer have a phone line with Bell. But you will still have Internet with them. In other words, a dry loop. You might want to call Bell once the number gets ported (this should be your 1st call to Bell about porting), and make sure they understand that you don't want them to make any changes to your DSL. That's what I did. And I got a confirmation number for our conversation.
|
|
|
|
|
#39 |
|
Veteran
Join Date: Jun 2007
Location: /dev/null
Posts: 2,669
|
I just ported a Rogers and a Primus TBB DID, and in both cases I had a 10-day FOC reply within one day. I ported my first Primus TBB number two years ago and it took a lot longer.
In a few days I will be porting a business line and a toll-free DID from Bell, so it'll be interesting to see how quickly those come over. |
|
|
|
|
#40 | |
|
Rookie
Join Date: Apr 2011
Posts: 6
|
Quote:
|
|
|
|
|
|
#41 |
|
Rookie
Join Date: Mar 2011
Location: Toronto
Posts: 14
|
Yes, that is what I am saying. I can't guarantee that you will have the same experience, but my guess is that you will. You don't have much choice anyway, because you don't want to make any changes on the Bell side before your number is successfully ported. The only precaution I suggest you take is to call Bell once the porting has happened, and tell them that you want to continue as a DSL customer and not to touch your DSL.
|
|
|
|
|
#42 |
|
Rookie
Join Date: Mar 2011
Location: VoIP.ms Employee
Posts: 27
|
The cooperation of losing provider, by replying to requests promptly, is one of the most important factors, however in my personal opinion the most important factor to calculate the porting time is the ratecenter of the number, as that decides what carrier your VoIP provider may assign to handle the port on their behalf.
Most big VoIp providers use several major carriers if possible, to have a bigger porting coverage. This leads to working with different types of quality on each carrier's own LNP department too. In previous months there was a specific carrier in Canada, amongst several we work with, that started lagging on their support and overall quality. This led to some ports (of numbers from ratecenters that only this carrier was able to port at the time) taking several weeks. In the past month we found other major carriers to work with, that allowed to finally leave this specific carrier whose quality was much less than expected by our standards while being able to offer the same pricing. Now all carriers used by VoIP.ms for Canadian ports can usually port a number within one week, or in five business days. There can be faster ports of course, but right now all canadian ports should take only up to a week unless there is a rejection from losing provider of course. I hope this clears up some of the inconsistencies in the porting times that previously occurred. Peter Sahui |
|
|
|
|
#43 |
|
Join Date: Dec 2005
Location: Oshawa
Posts: 497
|
posted in the other voip.ms thread, but i ported from rogers in 5 days,
__________________
50PX75U, (rogers') 8300HDPVR, 42PD50, Macbook Pro Imac 3.2ghz, Apple TV2, Iphone4, Time Capsule, VOIP Line, |
|
|
|
|
#44 |
|
Rookie
Join Date: Apr 2011
Posts: 1
|
Started the port last week from Rogers. Got a message next day about a FOC date. Today is my FOC date but as of 10 am it hasnt happened yet. Hopefully soon as Im excited to play with it. Soo many options. I grabbed a temp DID so when the port goes it will auto forward to the other DID so no downtime (hopefully)
Update: We are emailing you regarding an order you have in our system for the following DID(s): 613523**** Status for your port has been updated to the following: New Status: Completed Description: Port Completed - Number is now on VoIP.ms network. Updated by Brian on 2011-05-03 at 11:41:15 Woo hoo Last edited by Spikie; 2011-05-03 at 11:44 AM. |
|
|
|
|
#45 |
|
Rookie
Join Date: Apr 2011
Posts: 6
|
I am sorry if this a really basic questions but I am still a VOIP MS newbie.
I currently have a 647 DID and my original home # has a port request set to be completed tomorrow. Once VOIP MS associates it to my account, what do I need to do to get it up and running? (on Voip MS portal and ATA) Can I keep both DID's (not that I need to) Thanks in advance. |
|
|
![]() |
| Tags |
| bell home phone, voip.ms |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|