Cisco Unified Application Environment Developer Forums

« Back to Developers

How to lock the IP phone

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Hi,
 
I am writing a few applications on the IP hard phone and one or two applications of those require security.
So how can I lock the phone. I intend to provide a lock button or something on the phone, not sure yet. But following this request from the user on the phone, the phone should be completely locked until a valid passowrd is given.
Whereas I can plan the first and the last part of the flow i.e. how to invoke lock and how to validate the password, can someone please provide me information on how to lock the phone. Intention is to disable all the buttons on IP hard phone. Pressing any button shoule popup the password screen.
Any help is much appreciated.
 
Thanks.

This type of request comes up every so often, and usually the need for total restriction is always tempered by the need for 911 - as this should be available at all times to anyone.  The indicated solution usually is to use the AXL SOAP API with your application to change the available calling search space on the device, so that the phone can only call 911.
 
You could also implement this so that the app used the Extension Mobility API to login a dummy E/M user, who had CSS for 911 only, had a special set of services that only pointed to the unlock app, etc.
 
Beyond the more or less standard admin config options - dial plan changes, E/M, line provisioning, services provisioning: available via AXL - there is no mechanism to take direct control of the physical buttons on the device.

This type of request comes up every so often, and usually the need for total restriction is always tempered by the need for 911 - as this should be available at all times to anyone.  The indicated solution usually is to use the AXL SOAP API with your application to change the available calling search space on the device, so that the phone can only call 911.
 
You could also implement this so that the app used the Extension Mobility API to login a dummy E/M user, who had CSS for 911 only, had a special set of services that only pointed to the unlock app, etc.
 
Beyond the more or less standard admin config options - dial plan changes, E/M, line provisioning, services provisioning: available via AXL - there is no mechanism to take direct control of the physical buttons on the device.


Hi David,
 
Can you please elaborate more on the CSS for device? I think we need to use the UpdatePhone step in CUAE, right? Once I change the CSS of the device, to acheive the target functionality, there shouldnt be a need to logout from the device for the change to take effect?
 
Thanks,
Chandan

Dear David,
                  plz let us know the details about how to lock an ip phone without using EM service,  which axl functions you have used for  ip phone lock application. Can we implement security code mechanism while the phone is idle for one minute, but how let us know the technical details of the required axl functions etc.
 
Thanks

AXL <updatePhone> would be the right request, sending a new <callingSearchSpaceName> which CSS has been configured in UCM to dial 911/operator only.
 
Triggering this after 1 minute idle can best be accomplished via a CTI API (TAPI or JTAPI) to monitor the phone's call events in real time.  When your app detects that all calls have been idle for > 1 minute, execute the AXL change as above
 
 
 

Dear David,
If i call the xml service having the axl request of <>updatephone> as an idle url after setting the idle time of 60 seconds, is it possible

Thanks for ur suggestion

I had forgotten that the Idle URL had a configurable timer - that would be a potentially simpler approach emoticon

Dear David,
Would you let me know, how to implement phone locking with CME and can we use axl in order to do so,
Thanks

Not exactly sure what is your requirement but please take a look this post in Cisco Support Community see if this is what you are looking for.

https://supportforums.cisco.com/thread/294826

Thanks !