Porting Procedures?

[myvoip07]

I use a 2-line Panasonic 5.8GHz cordless phone and the GT 286 is directly connected to 1 line on the Panasonic with 2 handsets. I use dry dsl and haven't had a chance to figure out if i can use 1 line of the internal home wiring to connect voip.

[christcorp]

Well I swapped out the Grandstream for my Packet8 adapter. I can dial out and it sounds fine. Just have to wait til this afternoon and see how the incoming is after the number ports.

After that, I guess it will be time to call up Packet8 and make sure my account with them is canceled. Looking forward to the port. Never had any real problems with Packet8; but it has appeared that the VoipO line has had better quality. I've taken the adapter to Mexico and Belize and it worked fine. I see a lot of good things coming with VoipO. Later... Mike.....

[christcorp]

Well, a little after 10am, I called home on the VoipO adapter, and my daughter answered the phone. That means that the port went through. It rang 3 times, so that also means that the adapter seems to be able to handle my home phones hooked up. I will do some experimenting with it tonight to make sure it doesn't become overloaded.

Thanks for the prompt porting Tim and VoipO team. I faxed/emailed VoipO my paperwork on July 9th. That means it took 16 days to complete the port. Plus, with Tim/VoipO keeping me abreast of the progress, I am very satisfied that if this is the norm when public customers come onboard, that they will be very pleased. Excellent job. Later.... Mike....

[N9MD]

Tim -- please have your people call my people ... er-r-r-r- ... that is, have them check out TT#NXO-321510.

Just in case others might have encountered a similar problem, here's the gist:

I recently converted to the Founders' Annual Account Plan. My correct VOIPo# 973-302-xxxx is shown under the secure.voipo.com log-in. An incorrect VOIPo# 973-208-yyyy (NJ area code) is listed on the billing.voipo.com webpage. I did originally have VOIPo# 561-208-yyyy (FL area code) as my main DID# with VOIPo. Tim graciously allowed me to port the FL # to another provider last year, when it was found that I could not register VOIPo on my PAP2T-NA in my Boca Raton home with Comcast as the broadband connection.

To add to the stew, I am now in the midst of porting my constantly used home NJ # from VT to VOIPo.

So, I'm hoping to avoid any confusion by correcting the billing.voipo.com info to reflect my actual current VOIPo #. And I don't want my FL DID# working thru Comcast to evaporate.

-- Cliff

[VOIPoTim]

Ticket already updated

Tim -- please have your people call my people ... er-r-r-r- ... that is, have them check out TT#NXO-321510.

Just in case others might have encountered a similar problem, here's the gist:

I recently converted to the Founders' Annual Account Plan. My correct VOIPo# 973-302-xxxx is shown under the secure.voipo.com log-in. An incorrect VOIPo# 973-208-yyyy (NJ area code) is listed on the billing.voipo.com webpage. I did originally have VOIPo# 561-208-yyyy (FL area code) as my main DID# with VOIPo. Tim graciously allowed me to port the FL # to another provider last year, when it was found that I could not register VOIPo on my PAP2T-NA in my Boca Raton home with Comcast as the broadband connection.

To add to the stew, I am now in the midst of porting my constantly used home NJ # from VT to VOIPo.

So, I'm hoping to avoid any confusion by correcting the billing.voipo.com info to reflect my actual current VOIPo #. And I don't want my FL DID# working thru Comcast to evaporate.

-- Cliff