Rus Yates-Aylott

The correct way is to create a bespoke callflow using an 'extension' number. This does not need to be a number. It can be a random tesxt string. On the bar at the top click on the little edit icon (where you can name the callflow) Next, check the box that says 'Make this callflow available to the Main Number' Now go ahead and create/save your callflow. Back on SmartPBX, navigate to Main Number Incoming Call Routing. You will now see a 4th routing option where you can select your bespoke callflow.

Yes. If the evice settings in the Callflow App are not set to inherit those of the overall account, then the device will be prevented from dialling out until a user with appropriate privileges logs in. By default, it is good practice to set the account level to internal and emergency only.

We have achieved this via a bespoke callflow set up to provide feature codes that toggle the 'Forced On' or 'Forced Off' attributes of a ToD element. Hope this is useful

This is most easily achieved via the Yealink configuration file. Any DSS key can be programmed as follows, to provide BLF key presence etc. This will show the status of the monitored user as well as provide the ability to answer the phone by pressing the key and also make contact with the monitored party in the way a speed dial key might. You will need to ensure the Yealink has *23 set up as directed pickup also. Config as follows: ### BLF Keys - LED Status - Pickup(*23 or equivalent must be enabled as feature code on PBX) - Place Call - Replaces x's and y with valid data for key and account linekey.x.label = <BLF label 1> #line = account on which the user exists linekey.x.line = y linekey.x.pickup_value = *23 linekey.x.type = 16 ### Value must be valid extension number linekey.x.value = <BLF ext 1>

We can page Yealink phones individually using the *0 paging feature code (*0nnnn where nnnn is the extension number) By default the yealinks will auto-answer but Polycoms will not ( I suspect that to be a setting on the polycom somewhere) If you have 2 devices registered against the extension (user) it is a race as to which one answers and although the other(s) may attempt to auto-answer the call will only connect to one device. This is why paging groups would be so useful.... However, the issue we have experienced is that phones in the group WILL answer but there is no audio. We did a wireshark trace and could see audio being sent, It just wasn't being received. Anyone else experienced or resolved this? If multi-cast works, can someone detail how to set this up for Yealinks and Polycom phones. Thanks

On the paging side of things... We can page Yealink phones individually using the *0 paging feature code (*0nnnn where nnnn is the extension number) By default the yealinks will auto-answer but Polycoms will not ( I suspect that to be a setting on the polycom somewhere) If you have 2 devices registered against the extension (user) it is a race as to which one answers and although the other(s) may attempt to auto-answer the call will only connect to one device. This is why paging groups would be so useful.... However, the issue we have experienced is that phones in the group WILL answer but there is no audio. We did a wireshark trace and could see audio being sent, It just wasn't being received. Anyone else experienced or resolved this?