Problems configuring OBi110 to work with FPL
Posted: 01/25/2015
Hi all,
I am new to VoIP, after some researching online decided on the OBi ATA, specifically the 110 model. I purchased the VoIP Unlock Key, started configuring the device for use with FPL (for obvious reasons ).
Using the FPL "Updated OBi100 Guide" just get the device to enable inbound calls, as I could not make outbound calls, until I configure the OBi110 using OBiTalk Portal. This worked for a while until somehow it stopped working the next day. With some help from the OBiTalk forums, I changed the Google Voice to SP2, keeping FPL as SP1, as this was done using the Updated OBi100 Guide.
This worked for a day, until I need to move the ATA to another Ethernet port in another room, removing the setup would have powered down the ATA, or something happened that the device stopped working, unable to make (outbound) calls. After some thorough re-config of the device on OBiTalk portal, the setup works again.
However I still have at least 2 concerns:
1. Dropping Caller ID. No matter how many times I have to re-entered the Caller ID, (my name) on the device IP address, it did not "stick", or not for long. I saw the CID appears on my POTS phone, then disappeared!. Checking back the configured OBi100 IP address setting, the entered CID was gone, after a couple minutes!
2. DigitMap not registered as recommended by FPL. The Guide recommends:
DigitMap: (911|[2-‐9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|*98|[6-‐7]x*xxxxxxxxxxx.)
Somehow the device can't seem to keep this config, always reverted back to:
(*95|*98|*xx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.)
Without understanding the meaning behind the 2 strings, I can vaguely guess the FPL e911 service, as advertized included in the $50 package, would not work.
I intend to port over my existing POTS phone number to replace the new "IP" number, but hesitate because that would defeat the purpose (to keep the 911 calling capability).
Help!
I am new to VoIP, after some researching online decided on the OBi ATA, specifically the 110 model. I purchased the VoIP Unlock Key, started configuring the device for use with FPL (for obvious reasons ).
Using the FPL "Updated OBi100 Guide" just get the device to enable inbound calls, as I could not make outbound calls, until I configure the OBi110 using OBiTalk Portal. This worked for a while until somehow it stopped working the next day. With some help from the OBiTalk forums, I changed the Google Voice to SP2, keeping FPL as SP1, as this was done using the Updated OBi100 Guide.
This worked for a day, until I need to move the ATA to another Ethernet port in another room, removing the setup would have powered down the ATA, or something happened that the device stopped working, unable to make (outbound) calls. After some thorough re-config of the device on OBiTalk portal, the setup works again.
However I still have at least 2 concerns:
1. Dropping Caller ID. No matter how many times I have to re-entered the Caller ID, (my name) on the device IP address, it did not "stick", or not for long. I saw the CID appears on my POTS phone, then disappeared!. Checking back the configured OBi100 IP address setting, the entered CID was gone, after a couple minutes!
2. DigitMap not registered as recommended by FPL. The Guide recommends:
DigitMap: (911|[2-‐9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|*98|[6-‐7]x*xxxxxxxxxxx.)
Somehow the device can't seem to keep this config, always reverted back to:
(*95|*98|*xx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.)
Without understanding the meaning behind the 2 strings, I can vaguely guess the FPL e911 service, as advertized included in the $50 package, would not work.
I intend to port over my existing POTS phone number to replace the new "IP" number, but hesitate because that would defeat the purpose (to keep the 911 calling capability).
Help!