Problems with porting to Google Voice.
RFord:
Bandwidth.com seems to run out of 954 Area Codes from time to time. If you keep checking, more 954 will become available. Also, they should be able to port your 954-353-xxxx, even though it doesn't show up on their list. I was able to port a T-Mobile number 954-73X-XXXX to GV sometime ago:
http://www.localcallingguide.com/lca_prefix.php?ocn=982E&npa=954®ion=FL
Stewart:
Something seems very strange about your Localphone VM problem. While I can certainly imagine a problem with the U-Verse RG that corrupts a SIP CANCEL request and causes an unanswered call to continue to ring her phone, that should have nothing to do with Localphone's sending the caller to voicemail. If the caller continued to hear ringing, IMO that had to be a problem with the Localphone configuration or with their service. As I mentioned earlier, the setting for voicemail-on-no-answer is in an obscure place (Internet Phone -> Call Forwarding). Can you retest if that is working now?
I am reasonably certain that Localphone does not route calls differently based on IP address, so moving the OBi overseas won't change anything. However, they may route a call differently based on the caller's number, because of various tariffs related to intra- vs. inter-state and intra- vs. inter-LATA. Also, it's possible that if the general problem with FL routing is fixed, the special 4-digit prefix may be discontinued or repurposed. So, you should be prepared to adjust the OBi configuration if needed. That should not be hard to do, either through the OBiTalk portal, directly via port forwarding, or by remote access to her desktop and running a browser from there.
carl:
Quote from: Stewart on April 24, 2012, 11:32:00 am
Something seems very strange about your Localphone VM problem. While I can certainly imagine a problem with the U-Verse RG that corrupts a SIP CANCEL request and causes an unanswered call to continue to ring her phone, that should have nothing to do with Localphone's sending the caller to voicemail. If the caller continued to hear ringing, IMO that had to be a problem with the Localphone configuration or with their service. As I mentioned earlier, the setting for voicemail-on-no-answer is in an obscure place (Internet Phone -> Call Forwarding). Can you retest if that is working now?
Forwarding to another number or forwarding directly to the voice mail works without problems. A few months ago, when i was setting up my Localphone service, I posted a.o. about the voice mail problems. I Will contact Localphone again in order to find out about any possible changes, in the past they were not able to help me. Localphone voice mail is a bit strange anyway since you cannot access it from another phone. The only way is to use *1571 from the phone connected to your registered ATA. Yes, you can access it via the computer but since I cannot use the LP softphone or X lite etc ( those mysterious gateway issues) that's not an option for me. I recorded a message for the callers with an alternate number to reach me, but it is a bit of an issue with those using my overseas DID.
carl:
I called Amex and charged back the $ 20.- for the port. I will think about trying it once again in a few days . If that does not work I just let the number go. GV does strange things sometimes.
jimates:
Read the porting info at Anveo http://www.anveo.com/faq.asp?code=faq_did_portin
3 to 5 weeks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page