Mini UCS is finally here

Mini UCS is finally here, it has been long rumoured but has finally arrived. Data sheet does a better job of explaining it than me


http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-6300-series-fabric-interconnects/datasheet-c78-732207.html

JTAPI Testing

Hi Guys

Super useful app is available from cisco to test JTAPI and make sure that your JTAPI setup username/password etc is 100 percent correct. It's available here:

https://developer.cisco.com/site/collaboration/call-control/jtapi/documentation/index.gsp

(Random collection) Random collection of bugs I uncovered during an upgrade from 8.5 to 10.5

- WORKFLOW does not get copied over with a DRS (no reason codes etc)
- Bug with headsets and 79XX handsets means transfers will not work correctly
- ITL will have issues  (show itl in the console)
-  watch out for JTAPI IPv6 issues causing problems with RMCM logging in
- there is an issue when doing UCCX switch version from 8.5 to 10.5
(shared memory on UCS server look for bug with that mentioned)
- CUIC login fails
- database sync has failed when going from SU3 to SU4 for 8.5

Cisco Workflow for Cisco Agent Desktop (CAD) does not get copied during DRS restore or upgrade with UCCX

Hi Guys

as per the post title, Cisco Workflow information does not get copied across with a DRS restore or a UCCX Upgrade, totally crap so be careful when your doing a UCCX upgrade

Hit this bug during a UCCX upgrade from 8.5 to 10.5

https://tools.cisco.com/bugsearch/bug/CSCtz07348

Basically you need to be sure when using JTAPI that your common device phone profile does not have IPv6 Addressing enabled, otherwise JTAPI will try and use IPv6 by default. This can cause error messages such as:

"Login failed due to a configuration error. Please ask your system administrator to associate your phone with the RM JTAPI Provider user ID according to the instructions in the administrators guide"


Another thing that can cause this issue is extension mobility, so if your sure your phone is associated to the user etc, check your common device profile for IPv6 addressing mode as well as checking for Extension mobility