abuzooz Posted February 9, 2023 Report Posted February 9, 2023 Hi All, I was reading on how to disable/enable call waiting for users, I found this article but I have no idea where should I add this to deactivate call waiting for a user. if someone can guide or show an example this would be much appreciated Thanks Yazan
MattForrest Posted March 6, 2023 Report Posted March 6, 2023 Hi Yazan, Can't advise if this works in 4.x but it doesn't work in 5.0 / 5.1 - advised it was a community contribution and it hasn't been fully pulled through to 5.x / isn't supported. Frustrating really as the back end is all still present in 5.x and it can be configured, but it simply doesn't work. There is a callflow element for this too which allows the feature to be toggled on/off and you can set the scope - it can either be user based or device based. You will need to create the callflow through the API as the callflow elements isn't exposed in the Callflows app. The flow element needs the below - you can change scope from 'device' to 'user' depending on weather you want this as device based or user based. flow": { "data": { "action": "toggle", "scope": "device" }, "module": "call_waiting", "children": {} } If you create the callflows then toggle call waiting, if you then perform a GET on the user or device (depending on what you have the scope set as) you will see a call_waiting element has been added to the associated document. However, like I said, on 5.x when you call the user or device, there is no change to the call behaviour despite the above changes to the user/device doc being made. If you are on 4.x it may work, but should you go to 5.x at any point it is likely to stop working. Matt
abuzooz Posted March 12, 2023 Author Report Posted March 12, 2023 Thank you @MattForrest, I solved it on the client side as I gave it to get it resolved on the backend side. I am going to test the above callflow to see if it works as I am still on Kazoo 4.3 Appreciated Yazan
tomas_ Posted January 30 Report Posted January 30 Hi, did you found out anything about disabling call waiting in the backend? Br - Tomas
abuzooz Posted January 30 Author Report Posted January 30 Hi @tomas_ Not really, we managed this on the client side
tomas_ Posted January 30 Report Posted January 30 I see, thanks for your answer. Guess we'll embed this into the preflow script we already use.
MattForrest Posted January 30 Report Posted January 30 @tomas_ just out of interest how are you looking to achieve this server side using a preflow? Server side call waiting would be much better than having to handle this device by device, especially if a user has multiple devices.
tomas_ Posted January 30 Report Posted January 30 (edited) Hi @MattForrest! We have a PHP script which is setup to run as preflow on the account, invoked by Pivot (made in Callflows app). This script can for intance handle presences (connected to calendar services, with a voice saying that a user is in a meeting and when he/she will be back, etc). I guess it would not be that hard to add functionality to check if any of the user's devices is in use and then disconnect the call with a busy tone / response. More info here:https://docs.2600hz.com/dev/applications/callflow/doc/preflow/https://docs.2600hz.com/dev/applications/pivot/doc/https://docs.2600hz.com/dev/applications/pivot/doc/kazoo/hangups/ Edited January 30 by tomas_ (see edit history)
esoare Posted January 31 Report Posted January 31 Would love to see a "Forward on Busy" at the User level to be enacted, for those clients that don't want a second call, and don't want to "reject or DND" at the Device level!
Recommended Posts