Obi200 Call forwarding on busy worked once
SteveInWA:
Making some changes on the local web browser interface, and making other changes on the OBiTALK interface, makes a mess. The OBiTALK settings will normally overwrite the locally-made settings, but, in some cases, you can end up with them being out of sync. The red exclamation marks simply let you know that you changed a value from the default; it doesn't mean anything is wrong.
If you really want to clean this up, I'd suggest starting over.
Delete your OBi device from the OBiTALK web portal and wait a few minutes for OBiTALK to remotely access the device.Unplug the power and Ethernet cables from the device.Find the recessed reset switch on the bottom of the device. On the OBi 2xx series, there is a raised bump with a hole in it. Set the device on a flat service, upside down. Using a paper clip, gently depress and hold in the recessed button. You should feel a slight click.While continuing to hold in the button with one hand, plug in just the power cord with the other hand. Wait at least 10 seconds, then remove the paper clip. Wait a couple minutes.Your OBi is now restored to factory defaults.Now, add it back to the OBiTALK web portal. following the **5 procedure.Set up your service provider(s) as needed. If you are using a major SIP VoIP provider that OBi supports, scroll down to the bottom of the OBiTALK service provider selection page, and click "OBiTALK compatible service providers", and select your provider from the list. This will load a pre-configured settings template for that service provider.From now on, do not make changes on the local UI. Make all changes from the OBiTALK web portal, using it's "Expert configuration" mode if needed.
drgeoff:
Quote from: static1120 on September 22, 2017, 09:12:17 am
I have been doing changes on the device and on the OBIexpert configurations but I can get them to play nicely with each other, I know I may be overlooking something fairly simple
You overlooked the 'NOT' in the title of the post I referred you to. Clearly you failed to either read or comprehend that post.
static1120:
Thank you both for your help, regarding the issue I am having, in response to drgeoff, sorry I did look at your post, but I simply had already messed around with both configurations by the time I saw the post and was trying to clean up the mess I made (new user error)
Thanks for the detailed info Steve
I went ahead and cleaned up the mess I did using Steves guide, deleted device from obitalk
Reset device to factory, then Re-added device using the **5 code
After doing so I got it back up and did changes only trough obitalk
Went down to voice services, SP1 and under calling features deselected Obitalk to be able to select the call forward on busy checkbox, and entered the number (1XXXXXXXXXX) I tried (XXX-XXX-XXXX) and (XXXXXXXXXX) but they all still end up giving me the previous issue, when I call the primary number the second time I only hear a beep on the main line, and the call does not roll-over to the other number that needs to be called.
I am still trying to figure out why I got it to work once and I have not been able to get it to work anymore :'(
SteveInWA:
It doesn't make sense that you'd set up call forwarding on the OBi. That's something that should be handled either by the Syn248 gateway, or via a service provider (e.g. a VoIP service).
Google Voice is NOT a free VoIP trunk. It's a full-featured, inbound call forwarding and voicemail/text message management system. It's going to have conflicts trying to interact with forwarding from the OBi to another number (azrobert's claims to the contrary).
It's a shame that you bought the AT&T system, instead of a bunch of true IP phones, that could function with either a true VoIP PBX or a cloud-based PBX-like service. But, given that you have to work with what you bought, I'd suggest dumping Google Voice and whatever service is providing your landline, and getting as many SIP VoIP DIDs and channels as you need from a SIP VoIP service provider (e.g. Callcentric, voip.ms, Phonepower), then using one OBi 200 per analog port on the 248, or buy a OBi 202 to support two analog ports.
azrobert:
You need to specify the trunk you want to use for the call forward.
sp1(1xxxxxxxxxx)
This really isn't a call forward, it's bridging the call. You use your service provider to make a new call then connect the inbound call to the target. The target will see your service provider's CallerID, not the original inbound CallerID.
Navigation
[0] Message Index
[#] Next page
[*] Previous page