Kurt Harnish Posted February 21, 2014 Report Share Posted February 21, 2014 From the customer Call transfer – we have encountered this situation several times. We use the attended transfer feature where the receptionist puts a call on hold, presses a “one touch” key to dial the desired party in house, announces the call, and then presses the transfer button twice to complete the transfer. If another outside call starts ringing during this process, when Jolene hits the transfer button twice, the new incoming call gets disconnected and the call on hold that was supposed to be transferred remains on hold (is not transferred). SNOM ONE Version 5.1.3 SNOM 720 with 8.7.3.25 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 21, 2014 Report Share Posted February 21, 2014 Okay, let me try to understand: The problem is reproducible? Attended transfer, then where exactly does the call come it? This might be a issue with the user interface of the phone. The PBX cannot "see" what is being pressed on the phone and when. Call waiting is an easily forgotten test case between every button press, also in the call transfer scenario. Easy workaround is to disable call waiting; not sure if that is really addressing the problem. Quote Link to comment Share on other sites More sharing options...
Kurt Harnish Posted February 24, 2014 Author Report Share Posted February 24, 2014 I would rather not disable call waiting if possible. The call is coming in from the outside via a hunt group. When the are ready to transfer the call another call comes in and they press the transfer button twice it puts the attended transfer gets put back on hold and they lose the outside call from the hunt group. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 24, 2014 Report Share Posted February 24, 2014 Well, how can the PBX help here. This sounds like a problem with the user interface of the phone. When the user presses a button on the phone, this does not mean that the PBX receives a message. Actually the PBX only gets the result of the transfer (or hangup) request. Maybe you can try a different phone type to see if the behavior is different/sufficient. Quote Link to comment Share on other sites More sharing options...
Chappo Posted February 25, 2014 Report Share Posted February 25, 2014 The setting you need to adjust is the following - http://wiki.snom.com/Settings/always_show_active_call This setting is used to configure the default behaviour in call waiting scenarios. Default value on will keep the active call on the display, regardless of any incoming calls. All user actions such as hold or transfer will effect the active call. Disabling this setting will display the latest incoming call (all actions will be applied to the call displayed) Quote Link to comment Share on other sites More sharing options...
Kurt Harnish Posted February 26, 2014 Author Report Share Posted February 26, 2014 I'm not sure if the active call setting is what we want but I will test it. I will post this to the SNOM phone forum as well since you are no longer SNOM? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 27, 2014 Report Share Posted February 27, 2014 I think the solution with the setting on the phone sounds like a good solution. It does not block call waiting per se; it just makes sure that you still deal with the current call and not with the incoming call. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.