Cius Add-On v1.0 library compatibility with sipcius.9-2-2-49 and prior? http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=5428828 2013-05-23T20:23:00Z 2013-05-23T20:23:00Z Greg Marquez http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5530644 2012-04-27T16:50:06Z 2012-04-27T16:50:06Z

A follow-on question: What is the best/easiest way to detect what version firmware a Cius device is running on, either programmatically or by using the Cius UI? The reason I'm asking is that I'd like to test my app on both "versions" of the firmware (pre-9.2.3 and post 9.2.3), but all of our hardware devices have already updated themselves to post-9.2.3. I'd like to use either a device or the emulator to verify that my code works with pre-9.2.3, but for that I need to either "downgrade" a Cius device to pre-9.2.3, or to verify that the emulator I'm using is indeed pre-9.2.3. In trying to verify if my emulator is emulating pre-9.2.3, I've tried using the android/Cius GUI to go to Settings->About Phone. There I find a model number ("cius2_addon"), android version ("2.2"), kernel version ("2.6.29-002610g0097074-dirtydigit@digit #20"), and build number ("cius2_addon-eng 2.2 MASTER eng. root.20110810.155907 test-keys"), but how do I correlate these to the "firmware version"? One of our post-9.2.3 Cius hardware devices show Model Number 'CIUS-7", Android version "2.2.2", kernel version "2.6.31.6-mrstcius-build-user@cius-build-machine #1", build number "FRG83G.9.2.3.143"...additionally, it has a "Cisco Load Infromation" section that the emulator doesn't have, containing Active load "sipcius.9-2-3-143" and last upgrade "Mar 21, 2012 816:46 AM" I just need a way to test on a pre-9.2.3 device or emulator...is there a way to temporarily "downgrade" a Cius device with the previous load? Or is there a way to verify that the emulator version I am using is simulating a pre-9.2.3 device? Thanks! - Greg Marquez, SLA Corp.

Greg Marquez 2012-04-27T16:50:06Z Pete C http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5430155 2012-04-10T17:48:24Z 2012-04-10T17:48:24Z

Thank you, David. I will try the procedure discussed in the blog post you cited.

Pete C 2012-04-10T17:48:24Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5431297 2012-04-10T16:39:40Z 2012-04-10T16:39:40Z

In case you missed it, this blog post has information regarding the change and how to work with it: http://developer.cisco.com/web/cius-developer/blogroll/-/blogs/cisco-telephony-manager-updates?_33_redirect=http%3a%2f%2fdeveloper.cisco.com%2fweb%2fcius-developer%2fblogroll%3fp_p_id%3d33%26p_p_lifecycle%3d0%26p_p_state%3dnormal%26p_p_mode%3dview%26p_p_col_id%3dcolumn-1%26p_p_col_count%3d1

David Staudt 2012-04-10T16:39:40Z Pete C http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5428827 2012-04-10T03:54:36Z 2012-04-10T03:50:17Z

Recently, the Cius Add-On v1.0 library package was made available. The v1.0 package changed the CiscoTelephonyManager() signature and initialization flow.   Previously v0.5 was in use and working to use the CiscoTelephonyManager API on Cius firmware sipcius.9-2-2-49 and prior. Now, it appears that using the v1.0 library will only work on the newer Cius load: sipcius.9-2-3-143 and later.   The CiscoTelephonyManager API object does not initialize on Cius firmware sipcius.9-2-2-49 and prior. Is there a way to either: 1) Use the v1.0 jar library with Cius load: sipcius.9-2-2-49 and prior? 2) Dynamically load either the v0.5 jar or v1.0 jar at runtime based on the    Cius device load?         // Cisco Cius Add-On v0.5 usage.         try         {             ctm = new CiscoTelephonyManager( context, mHandler );         }         catch ( CiscoTelephonyManagerBindFailed e )         {             Log.w(TAG, "Fail init: CiscoTelephonyManager", e );             e.printStackTrace();             return false;         }         // Cisco Cius Add-On v1.0 usage.         ctm = (CiscoTelephonyManager) context.getSystemService(             CiscoTelephonyManager.CISCO_TELEPHONY_MANAGER );         if ( ctm == null )         {             Log.w(TAG,                "Fail init: getSystemService: CISCO_TELEPHONY_MANAGER null" );             return false;         }

Pete C 2012-04-10T03:50:17Z