RE: Handheld Phone debug output http://developer.cisco.com/c/message_boards/find_category?p_l_id=2371355&mbCategoryId=0 2013-05-23T09:11:14Z 2013-05-23T09:11:14Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=10086868 2013-01-09T17:08:43Z 2013-01-09T17:08:43Z

Sounds like known issue: CSCtz35941 - Midlet: HttpConnection request blocks UI input This should be resolved in later firmware, starting with 1.4(3)SR1

David Staudt 2013-01-09T17:08:43Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=10042579 2013-01-08T18:30:57Z 2013-01-08T18:30:57Z

Can you provide a few more details about the specific implementation you are looking to build? If you are referring to the XML services display, this simply formats/displays specific XML documents - there is no scripting or other 'dynamic' capability, beyond refreshing the entire page via Refresh header. If you are talking about using the Java midlet capabilities, please let us know which API components you are looking to use, and what you require from 'long poll' functionality.  It should be possible to use the midlet HTTP request object to call a URL, providing a lengthy timeout to wait for the server to respond, i.e. the Ajax/long-poll pattern.

David Staudt 2013-01-08T18:30:57Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=6476733 2012-09-11T18:25:01Z 2012-09-11T18:25:01Z

Unfortunately the source code is not available for distribution.

David Staudt 2012-09-11T18:25:01Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=6087014 2012-07-12T22:51:15Z 2012-07-12T22:51:15Z

After some testing we've found that the 7926 skin will work with the following:   - Netbeans 7.1.2 (latest) - Oracle Wireless Toolkit 3.0 (latest is 3.0.5)   Two caveats of note:   - The 'complete' Netbeans installation includes the Mobility features, and automatically installs the complete WTK 3.0.5.  It may be possible to also install the WTK 3.0 side-by-side, but care must be taken to install the 7926 skin files only in the WTK 3.0 SDK area.  In our setup we installed the base Netbeans 7.1.2, then added the Mobility plugin and installed the standalone WTK 3.0. - After adding the 7926 skin files to the WTK 3.0 directory structure, the 'Java ME SDK 3.0 Device Manager' tray icon must be 'Exit'-ed before restarting Netbeans and performing the 'Manage Emulators/Refresh' sequence.   We are evaluating further updates to the skin to work with WTK 3.0.5, but the above at least allows use of the latest Netbeans.

David Staudt 2012-07-12T22:51:15Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=5495571 2012-04-20T19:18:47Z 2012-04-20T19:18:47Z

Is the default emulator/skin working?  Only the 7926 skin is failing?

David Staudt 2012-04-20T19:18:47Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=5149720 2012-02-14T20:22:16Z 2012-02-14T20:22:16Z

With the advent of Android based devices (Cius) and their excellent on-board app programmability, it seem that the extensive work needed to enable J2ME on additional 'legacy' devices will likely never make it above the line.  I'm not aware of any upcoming announcements...

David Staudt 2012-02-14T20:22:16Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=5146835 2012-02-13T19:02:54Z 2012-02-13T19:02:54Z

Per the linked page, that feature set requires Location API for J2ME (JSR 179).  Unfortunately our devices do not support any extended JSRs built-in.

David Staudt 2012-02-13T19:02:54Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=5131544 2012-02-10T21:21:14Z 2012-02-10T21:21:14Z

See the Emulator Skin Guide (and the Midlet SDK .zip) here:   http://developer.cisco.com/web/jmapi/docs   This will give you a 'pretty close' UI/layout/button approximation of the 7925/26, useful for Netbeans and Oracle J2ME IDEs.   J2ME applications can be multi-threaded, and can run in the background (with some limitations and caveats), see:   http://developers.sun.com/mobility/learn/midp/lifecycle/#execution   Not aware of any J2ME API for low-level wi-fi subsystem query/manipulation.  Note the Cisco midlet implementation covers only a few of the core JSRs - see the developer guide.

David Staudt 2012-02-10T21:21:14Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2942579 2011-01-19T20:49:24Z 2011-01-19T20:49:24Z

Can you confirm the phone model and firmware version in use?  Can you confirm the minimum volume setting for the device, and if modifying it has any effect?

David Staudt 2011-01-19T20:49:24Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2907169 2011-01-15T03:35:37Z 2011-01-15T03:35:07Z

The  bad news is that per the JMAPI doc, the following URIs are supported via platformRequest():     -RTP Streaming URIs: Initiating and terminating RTP audio streams to/from the phone -Enhanced Dial URI: Initiating new calls and controlling the user interface for a call -SendDigits URI: Injecting DTMF digits into active calls   [b]not[/b] including Vibrate. The good news is that midp itself has an API for vibrate: [color=#333333][b]javax.microedition.lcdui.Display[/b] class[/color] [color=#333333][b]vibrate(int duration) method[/b][/color] [color=#333333]The other bad news is that the 792x phones currently do not support the API.  Feedback on use-case and business impact, as always, appreciated so we can feed back to engineering.[/color]

David Staudt 2011-01-15T03:35:07Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2897025 2011-01-13T00:26:38Z 2011-01-13T00:26:38Z

Since the devices are by definition network connected, the streaming audio support is going to be the main mechanism for providing rich app audio.   There are of course sound fles on the device, but so far these have not been exposed to midlets for use.  It's something that is possible - say via URIs - your feedback on the business impact and desired access mechanism appreciated.   Similarly with extra audio codecs, currently only the PCM/wav codec is exposed to midlets via the media player, though the device has more onboard for use with telephony (e.g. 729.)  A compelling use-case (and customer opportunity) would be helpful towards prioritizing enhancements in this area.

David Staudt 2011-01-13T00:26:38Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2894754 2011-01-12T03:09:58Z 2011-01-12T03:09:58Z

Midlet support is present in 1.4.1, though access to the midlet docs and developer support is still limited to registered members of developer.cisco.com for now (hence not announced in the public release notes.)

David Staudt 2011-01-12T03:09:58Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2892216 2011-01-11T23:08:39Z 2011-01-11T23:08:39Z

The phone's local web server has some information - including the primary DN - at /DeviceInformationX (xml format).  Note however that the phones can have more than one DN, and only the primary is listed on the page.  More specific info can be retrieved from UCM using the AXL API and the device's name/MAC, but would require a separate service running somewhere.

David Staudt 2011-01-11T23:08:39Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2877713 2011-01-06T06:59:43Z 2011-01-06T06:59:43Z

UCM CTI APIs (TAPI and JTAPI) can send XSI commands to the phone - for example sendData() in JTAPI.  However, you will need to know the public IP reachable address of the UCM CTI Manager, in the same way you would need to know the phone's IP.     Assuming you can overcome this (say by port-forwarding to the CTI-Manager you want), you could send a CiscoIPPhoneExecute to the phone via JTAPI, and if the URL to execute matches a midlet provisioned on the phone it should (might, have not tested this) launch it.

David Staudt 2011-01-06T06:59:43Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=2371355&messageId=2877688 2011-01-06T06:37:45Z 2011-01-06T06:37:45Z

By default the phone is configured to reset all tracing (i.e. back to 'error' level), is it possible you reset the phone between tracing sessions?  If you so you may need to re-configure tracing and/or make the settings persist.

David Staudt 2011-01-06T06:37:45Z