Client acquired several 2N Helios IP Force door phones with integrated cameras with the intention of using them to open door locks nearby. In addition to the normal DTMF triggering method, they wanted to have the ability to unlock them without calls to the door in progress. The plan was to use the Helios automation features to respond to CUCM device Service URL button pushes.
The Helios units require the "Enhanced Integration" or "gold" license to use the automation features.
Navigate to
System | License and check the
License Status area to confirm you have it available.
In my environment we will be using the first relay on the Helios device to trigger an electronic door lock. We need to flip the Helios relay for 5 seconds, which will unlock the door, and then flip it back to allow the lock to re-engage.
Navigate to
Hardware | Switches and the
Switch 1 tab.
Confirm
"Switch Enabled" is checked.
Confirm
Switch Mode is
Monostable. This means it will flip on and stay on for X amount of seconds, then flip off.
Set
Switch-On Duration to however many seconds you need the switch on.
Assuming you have already wired the door lock to activate via this switch, you can press the
Test the Switch button here and verify it works.
Navigate to
Services | AutomationPick a function tab and confirm
"Function Enabled" is checked
On row
ID 1, change
OBJECT TYPE to
Event.HttpTrigger. On the same row in the
PARAMETERS field enter
"Name=opendoor"
This now defines a trigger for a function that the Helios IP Force will perform when it handles an HTTP request. The word
"opendoor" on the HTTP URL is what triggers this particular function.
Now make your function actually do something. Our something is pretty simple.
On row
ID 2, change the
OBJECT TYPE to
Action.ActivateSwitch. On the same row in the
PARAMETERS field enter
Switch=1;Event=1.
The
Event=1 parameter means do something when the event on row 1 happens (our
opendoor HTTP trigger above).
The
Switch=1 parameter means do something to the switch number 1 on your Helios unit (different units may or may not have the same number of switches).
The
Action. ActivateSwitch is similar to pressing the
Test the Switch button above. Depending on how your switch is configured (i.e.
Monostable) defines what
ActivateSwitch actually does.
Again, because the HttpTrigger (opendoor) happens on row one (ActivateSwitch and Event=1), switch number one is turned on (ActivateSwitch and Switch=1) for five seconds (Switch-On Duration) and then turned back off (Switch Mode is Monostable).
In a browser enter
http://<IP address of Helios endpoint>/enu/trigger/opendoorNavigate to
Status | Events to see the Helios responding and check your work. You should see
switch=1 changing to true and then five seconds later to
false.
If this works, you can now have CUCM users (receptionists, safety staff, etc.) perform this function from a button on a phone.
In CUCM navigate to
Device | Device Settings | Phone ServicesAdd a new service using the
Service Category "Web Link" and the
Service Type "Standard IP Phone Service"
In CUCM navigate to
Device | Phone and find the phone that will press a button to open the door.
Choose
Subscribe / Unsubscribe Services from
Related Links. Choose the
Service you created above.
On the same device, add a Service URL button and configure with the subscribed service.
Pressing that button should now trigger the HTTP Event and function that turns on the Helios switch 1, opening the attached door.
