Fisamo
Premium
join:2004-02-20
Apex, NC
 ·VOIPo
·AT&T CallVantage
| reply to MillsapsPE
While you're posting the porting rules, it may be helpful to add a list of features that will cause a port to fail.
•RingMaster/Distinctive Ring: I found out the hard way that this service will cause a port to fail. Those with this service have more than one phone# assigned to your line, and when the second or third numbers are dialed, a the line rings with a different pattern (e.g. double short ring or short-long-short ring).
•DSL Flag: If you have ever had DSL on your phone line, you must be certain that the DSL service is canceled and your telephone provider has adjusted your account accordingly. Sometimes, even after canceling DSL, the account flag is not removed.
•Local Carrier Freeze: I'm not exactly sure if it's called a Local Carrier Freeze, but similar to a PIC freeze with your long distance carrier, I'm certain you can tell your local telco to not change your service provider without explicit authorization from you. (Certainly, slamming is just as illegal for local service as it is for long distance service, so the local service must have the same protection options as long distance service.) The only way to remove this block from your line is to call your telco and ask them to remove it.
If any of these items are 'active' on your local telco account, you need to call your telco and be certain that they are inactivated on your account. Even then, you may not be able to initiate a port until the beginning of the following billing cycle.
If I missed any, or if anyone knows the correct term for a local carrier freeze, please add it to the thread! 
--
{Earthlink 5M/384 cable (TWC) - Moto Surfboard 4220} - {Home network - WRT54G (HyperWRT 2.0b3 f/w)} - {ATTCV VoIP - Centillium MTA-1 (f/w 6.23L)} |
