Keyboard.asp Questions

Version 1
    This document was generated from CDN thread

    Created by: ASHISH PATEL on 16-09-2009 04:05:30 PM
    Hi
     
    I have a customer where
     
    Their users want to use a keyboard to do a directory search from the phone. So they wrote a keyboard application using the Ip Phone Services SDK example using keyboard.asp application.
     
    They have two questions around this.
     
    Q1) The application itself is based upon the example keyboard.asp application provided in the ip phone services sdk.
    The performance problem stems from the fact that each key press that you make on the touch screen causes at postback to the server. So ideally we would wish to build a version that stored up the key presses and then did the submit when they have finished typing. But I can't see a way of achieving this by the xml interface?
     
     
    Q2) The 2nd issue I have is that I would like the number keypad to be inactive when the touch screen application is running (but all other keys working).
     
    Would a keyboard midlet me a better fit?
     
    Thanks
     
    ashish

    Subject: RE: Keyboard.asp Questions
    Replied by: David Staudt on 16-09-2009 07:11:46 PM
    Unfortunately today, an onscreen touch keyboard is impractical in several ways via XML services.  In addition to the limitations you mention, there is an issue where the TCP connection pool on the phone becomes quickly exhausted, as each HTTP request is Connection: close.
     
    Once midlet development is opened up, such a feature will be much easier to implement robustly.

    Subject: RE: Keyboard.asp Questions
    Replied by: ASHISH PATEL on 16-09-2009 09:10:51 PM
    Thanks for the answer David could you comment on this
    "Q2) The 2nd issue I have is that I would like the number keypad to be inactive when the touch screen application is running (but all other keys working). "
     
    I think this is not supported as the control/call plane is always given priority over the application plane is that a correct statement?
     
    Thanks
    ashish

    Subject: RE: Keyboard.asp Questions
    Replied by: David Staudt on 16-09-2009 10:00:31 PM
    There is no ability to map a keypad key to one of the CiscoIPPhoneGraphicFileMenu touch areas, so I'm not sure the keypad behaviour is defined. 
     
    What happens if you press a number key when this menu is being displayed?  Does the phone attempt to start a call?  If so, I'm not aware of any way to disable this.

    Subject: RE: Keyboard.asp Questions
    Replied by: ASHISH PATEL on 16-09-2009 10:05:23 PM
    Hi David
     
    The customer wants to stop users from entering any keypad presses during the time they have access to the keyboard application on the phone.
     
    Currently pressing the keypad on the phone leads to random events such as opening the settings access page, sometimes the services page, sometimes pressing the keypad number e.g. 1.  So the events are random and hence they wanted to know if you could disable the keypad through a command while the keypad.asp application is running on the phone?
     
    Thanks,
     
    ashish

    Subject: RE: Keyboard.asp Questions
    Replied by: David Staudt on 17-09-2009 12:18:03 AM
    That sounds...weird.  So while the CiscoIPPhoneGraphicFileMenu is displaying, pressing the keypad keys performs these random things?  Does the same number key always result in the samebehaviour - i.e. pressing '1' always kicks off the Settings service, for example?
     
    Can you try the latest firmware load for the phone model you're using.  If you still see this issue let me know the model/firmware version.

    Subject: RE: Keyboard.asp Questions
    Replied by: ASHISH PATEL on 17-09-2009 09:53:07 AM
    Hi David
     
    Sorry I checked with the customer the behaviour is not what I said - the behaviour is as expected
     
    "The issue that I raised with the keypad buttons is not a bug as such. The behaviour does make sense in that if you hit say "1" it types the first letter on the keyboard, "2" the 2nd, etc. We only wanted to suppress this behaviour which you have advised is not possible."
     
    Thanks
     
    ashish