 | Obi110 breaks POTS call waiting When my POTS line is routed through the Obi110, pressing 'flash' for call waiting leads to a dial tone instead of switching to the incoming call. What setting do I need to change in the Obi110 for POTS call waiting to work properly? |
|
 PX EliezerPremium join:2008-08-09 Hutt River kudos:13 | Maybe this will help. »www.obitalk.com/forum/index.php?topic=4926.0 |
|
 hardlyPremium join:2004-02-10 USA | reply to JTS33 It may be that this could apply:
»[Voip.ms] Receiving a second call using the FLASH command |
|
 | reply to JTS33 Alternatively, there is also a parameter in the Phone port settings Calling Features area called, "HookFlashHandling." The default setting is: Handle Hook Flash Locally Set this to: Send Hook Flash to PSTN
Parameter setting descriptions from the OBi Device Admin Guide: »www.obihai.com/docs/OBiDeviceAdminGuide.pdf
Handle Hook Flash Locally This is the normal setting, where the device intercepts all the hook flash events detected on the PHONE port, and acts on them accordingly, such as: - Hold current call and start second dial tone for 3-way calls - Start a 3-way conference - End call with 2nd conferencee in a 3-way conference - Swap between two calls in a call-waiting situation
Send Hook Flash Signal to PSTN Device does not act on hook flash events detected on the PHONE port. It either ignores hook flash events OR regenerates similar hook flash events on the PSTN line if the phone user is currently in a call using the PSTN line service when the hook flash event happens. This option may be useful in cases where the user has traditional call-waiting or 3-way calling services on his PSTN line service; hence he can control those PSTN supplementary services using hook flash signals. However, the OBi in this case would automatically disable its own call-waiting function on the PHONE port, and the user would have no means to tell OBi to make 3-way calls.
Note that an alternative way to let the OBi generate a hook flash signal to the PSTN line is to use a double hook flash event by hook flashing twice within 700 ms. See the description of the parameter EnableDoubleHookFlash in this table. With this enabled, you can still let the device handle normal hook flash event locally and preserve the call-waiting and 3-way calling functionality.
This option is only available in OBi110 |
|
 hardlyPremium join:2004-02-10 USA | reply to JTS33 It's a feature . . . |
|
 Reviews:
·AcroVoice
3 edits | reply to PX Eliezer This did not work for me, but it seems the double hook flash is a setting (already enabled) instead of actually pressing Flash twice in quick succession. |
|
|
|
 Reviews:
·AcroVoice
1 edit | reply to ShermanObi said by ShermanObi:Alternatively, there is also a parameter in the Phone port settings Calling Features area called, "HookFlashHandling." The default setting is: Handle Hook Flash Locally Set this to: Send Hook Flash to PSTN Thanks, this worked.
Note that an alternative way to let the OBi generate a hook flash signal to the PSTN line is to use a double hook flash event by hook flashing twice within 700 ms. See the description of the parameter EnableDoubleHookFlash in this table. With this enabled, you can still let the device handle normal hook flash event locally and preserve the call-waiting and 3-way calling functionality.
This option is only available in OBi110 It appears the EnableDoubleHookFlash setting is enabled by default, but for whatever reason does not work for me.
What's the benefit of having the hook flash event locally? Is it so if you have multiple lines of service, you can do call waiting and 3-way calling between different lines? |
|
 | When working with a PSTN analog circuit call, once you send a hook-flash event to the CO, your PSTN session will be 'altered' by the CO and the OBi will have less (or no) control to perform supplementary services on its own, e.g. place a call on hold, get a second dial tone (call conferencing) / answer the incoming call (call waiting).
Since the OBi110 handles multiple services, comprised of SIP+GV+OBiTALK VoIP sessions and PSTN analog circuit calls, the OBi110 is like a CO, in its own right, and can be smart about how it handles hook-flash events initiated by attached phones, e.g. The OBi knows to send a single hook-flash to the VoIP service and double hook-flash to the LINE port (PSTN).
So, like the admin guide says, "This may be useful in cases where the user has traditional call-waiting or 3-way calling services on his PSTN line service; hence he can control those PSTN supplementary services using hook flash signals. However, the OBi in this case would automatically disable its own call-waiting function on the PHONE port, and the user would have no means to tell OBi to make 3-way calls."
The OBi110 can have up to 2 independent commercial VoIP services, OBiTALK P2P service as well as an analog service connected to the LINE port. Using the double hook-flash is the only way to maintain supplementary services (call waiting, 3-way calling) support in both the PSTN and VoIP worlds.
You might want to open a ticket with Obihai tech support to see why double hook-flash is not working for you. |
|
 | reply to JTS33 said by JTS33:It appears the EnableDoubleHookFlash setting is enabled by default, but for whatever reason does not work for me.
What's the benefit of having the hook flash event locally? Is it so if you have multiple lines of service, you can do call waiting and 3-way calling between different lines? I suspect that the firmware in your phone is enforcing a minimum spacing between the flashes that exceeds the OBi's default timeout. For the Phone port, try changing DoubleHookFlashTimeMax from 700 to 1500 or even 2000.
In addition to the features already mentioned, a local hook flash is useful for functions not available on your POTS. For example, you probably don't have call transfer. So, if you're on a POTS call and need to walk the dog, flash, dial your mobile (using VoIP), answer the mobile then hang up the analog phone. The OBi will bridge the calls, so you can continue your conversation while you are out. |
|
 Reviews:
·AcroVoice
| reply to ShermanObi said by ShermanObi:You might want to open a ticket with Obihai tech support to see why double hook-flash is not working for you. Thanks for the explanation! I wonder if it's my Panasonic DECT 6.0 cordless phone system, as it seems others aren't experiencing this issue. Although it does work connected directly to POTS or using "Send Hook Flash to PSTN."
I did notice that there appears to be a longer delay before the call switches over (compared to if the phone system was connected directly to POTS). And if I switch over to a second caller and the second caller hangs up before I press Flash, I can't get back to the first caller anymore (who remains on Hold). |
|
 Reviews:
·AcroVoice
| reply to Stewart said by Stewart:said by JTS33:It appears the EnableDoubleHookFlash setting is enabled by default, but for whatever reason does not work for me.
What's the benefit of having the hook flash event locally? Is it so if you have multiple lines of service, you can do call waiting and 3-way calling between different lines? I suspect that the firmware in your phone is enforcing a minimum spacing between the flashes that exceeds the OBi's default timeout. For the Phone port, try changing DoubleHookFlashTimeMax from 700 to 1500 or even 2000. In addition to the features already mentioned, a local hook flash is useful for functions not available on your POTS. For example, you probably don't have call transfer. So, if you're on a POTS call and need to walk the dog, flash, dial your mobile (using VoIP), answer the mobile then hang up the analog phone. The OBi will bridge the calls, so you can continue your conversation while you are out. Thanks, I'll try increasing DoubleHookFlashTimeMax and see if that does the trick. |
|