|
Porting Rules and VoIP |
Porting rules only apply to RBOCs, CLECS, and ILECs. This includes big telephone companies, cell providers like Sprint Wireless, Verizon Wireless, and CLECs like Level 3. VOIP providers aren't usually CLEC's, (even though they should be), thus they aren't necessarily subject to any porting rules. Most VoIP Providers don't own any telephones lines of their own, but lease them from a CLEC like Level 3. So complaining to the FCC about a VOIP company not releasing your number to port to another VoIP, or not successfully porting it to themselves, won't get the Subscriber far at all. If the VoIP serving The Subscriber isn't a CLEC, they aren't subject to porting rules, and the FCC isn't likely to deal with it, as the VOIP company is the actual "customer" for the phone number, not the End User. The End User/Subscriber has no rights to port an assigned VOIP number under portability laws, after they port a number to a VoIP therefore. The CLEC owns the number, and the VOIP company is the customer, therefore the Subscriber can never expect to port an assigned VOIP number anywhere again, according to the portability rules. Numbers the Subscriber can expect to be ported: If The Subscriber has a phone number in their own name from an ILEC, RBOC, or cell provider, the Subscriber can port it to a VOIP provider who really ports it to the CLEC that they are using in the Subscriber's area. Incoming calls after porting will go to the CLEC's UNE-L switch, which is connected to the VoIP provider. The Subscriber's number and the CLEC's exchange must be in the same rate center, or the Subscriber can't port it. The CLEC being used must have a "Point of presence" in the same area where the Subscriber's number is located. If the Subscriber's number and The Subscriber's VOIP provider's CLEC are in the same point of presence, and the number is a working number, there is a good chance that the number can be ported. What can go wrong, if this is the case? The answer: Plenty! Many CLECs are slow to port their numbers, as they have no incentive to do so. The Subscriber's VOIP provider might be slow to initiate the port with the CLEC they use in the Subscriber's city, or the CLEC who services The Subscriber locally for The Subscriber's VOIP provider might be slow to accept the port request. 3 different companies, all moving at a different pace, are involved in porting a number to a VOIP service. Any one of them can cause problems or move slowly. The Subscriber's VOIP provider might cause the problem, or it might be The Subscriber's present telco, or it might be The Subscriber's local CLEC! The name on The Subscriber's phone bill has to match the Subscriber's VOIP bill or no port, also, the Subscriber can't port a VOIP assigned number, or a disconnected number. Just don't ask! It's not the VOIP provider's fault! Exceptions and mistakes do happen. Rules are meant to be broken as the old saying goes. Some people have ported a VOIP assigned number elsewhere but it's a rarity and won't happen often. A VOIP company can "give up" their rights to a number if they want to but I wouldn't expect that to happen very often. What I've tried to do here is write how it's "supposed" to work, not how it may actually work for anyone. Good luck! |
|||||||||
|
|
||||||||||
|
||||||||||







