MattForrest

@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.

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