This document was generated from CDN thread
Created by: Nawin Khunkitti on 27-04-2009 08:55:12 AM
Hello,
I'm using CallManager 7. I want to make a phonelock application but the way is not that easy. I have to use JTAPI for listening a button press especially service button to make sure that the application will work eventhough the users press service button to exit the app. How to make this key listening? and Is there any way to listen other buttons as well? Actually, I tried to use CiscoTermButtonPressedEv object but don't know what exactly how to use. Any example code will be very appreciated. Thank you
PS. Sorry for my bad english
Subject: RE: Button press listening by JTAPI
Replied by: Chikeobi Njaka on 27-04-2009 01:38:46 PM
Hello,
I'm using CallManager 7. I want to make a phonelock application but the way is not that easy. I have to use JTAPI for listening a button press especially service button to make sure that the application will work eventhough the users press service button to exit the app. How to make this key listening? and Is there any way to listen other buttons as well? Actually, I tried to use CiscoTermButtonPressedEv object but don't know what exactly how to use. Any example code will be very appreciated. Thank you
PS. Sorry for my bad english
I don't think JTAPI monitoring is the way to go. Specifically, it will not be particularly scalable. There are also problems with finding ways around 411 and 911 type calls which (at least in the US) *must* be allowed to go through.
Consider changeing the calling search space of the phone when it it locked. This of course means the phone must be reset going in and out of lock and you must recall and save the specific search space when locking so it can be restored when unlocking.
Subject: RE: Button press listening by JTAPI
Replied by: Stephan Steiner on 24-06-2009 06:12:45 PM
You will only get button events for the regular phone buttons (0 - 9, *, #).. not the rest.
There are a couple approaches to locking - many have been outlined here or in the netpro forum for developers (probably most in the netpro part).
For instance.. use Extension Mobility.. log out and have the logged out profile limited to making calls to the switchboard.
If that's too complex, how about simply taking the ability to make calls when the phone is "locked"? E.g. change the css to none for the phone.. and viola, nobody will make outgoing calls anymore. You can also lock down the services by simply removing them.
I've also seen people use JTAPI for a solution. Monitor phones, and for locked ones, immediately terminate a call as soon as you see one being set up.
And here's yet another one I have dreamed up: Push a "this phone is locked screen" on the phone when it is locked. Configure the service so that when it leaves the foreground or is closed, is sends a notification to your application, which immediately repushes the application on the foreground, thus preventing people from having enough time to actually make a call or do much else. This is time sensitive though.. your app needs to be quick.
Personally, I'd go for the "reconfigure phone so that even if you get your hands on it, it is not very useful".. use extension mobility where possible since it means no effort on your part, and use axl to reconfigure the phone if extension mobility is not possible.
