Archive

Archive for the ‘UCXN’ Category

Warning: The /common file system is mounted read only

May 22, 2012 Leave a comment

Interesting one…..

Had an issue yesterday where we identified a Cisco bug (CSCti52867) relating to any of the following IBM MCS servers

MCS-7816-I4,

MCS-7825-I4

MCS-7828-I4

When logging into the CLI instead of getting the standard Admin prompt the following information was presented which encouraged me to investigate further

java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)

        at java.io.RandomAccessFile.open(Native Method)

        at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)

        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.restoreIndex(ciscoRollingFileAppender.java:100)

        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.setFile(ciscoRollingFileAppender.java:43)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:196)

        at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:155)

        at org.apache.log4j.xml.DOMConfigurator.setParameter(DOMConfigurator.java:530)

        at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:182)

        at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:140)

        at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:153)

        at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:415)

        at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)

        at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)

        at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:666)

        at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616)

        at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:584)

        at org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:687)

        at sdMain.main(sdMain.java:602)

java.lang.NullPointerException

        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.updateIndex(ciscoRollingFileAppender.java:117)

        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.nextFileName(ciscoRollingFileAppender.java:92)

        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.append(ciscoRollingFileAppender.java:74)

        at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)

        at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)

        at org.apache.log4j.Category.callAppenders(Category.java:187)

        at org.apache.log4j.Category.forcedLog(Category.java:372)

        at org.apache.log4j.Category.info(Category.java:674)

        at sdMain.main(sdMain.java:616)

log4j:ERROR No output stream or file set for the appender named [CLI_LOG].

   Welcome to the Platform Command Line Interface

    WARNING:

        The /common file system is mounted read only.

        Please use Recovery Disk to check the file system using fsck.

The solution to this issue cab be found at the following location

https://supportforums.cisco.com/docs/DOC-12955

Bascially you need to do the following

  1. Perform Backup of CUCM & UCXN  or Relevant UC Servers
  2. Use the Cisco Recovery Disc and perform a file system check (Note: If errors are found a rebuild and restore is required)
  3. Apply Disk Exerciser Utility
  4. Apply Server Firmware

Cheers

The Voice Man

Advertisements
Categories: CUCM, UCXN

Upgrading Exchange 2003/2007 to Exchange 2010 with Cisco Unity

May 15, 2012 Leave a comment

Hi All

Recently we have been required to complete some additional research into customers looking to upgrade their Exchange 2003/2007 servers to Exchange 2010. They still have the full blown Cisco Unity which heavily integrates into AD and Exchange, therefore what is required to upgrade and maintain the integrity of the Cisco Unity environment?

Cisco have a great document which explains how this is achieved and allows for the migration of user mailboxes from the Exchange 2003/2007 message store to the Exchange 2010 message store to be on going, meaning that all mailboxes do not have to be moved all at once, Cisco Unity can manage sending the VM’s to both exchange versions allowing for more in depth testing and smarter migrations

Check this out

Using MS Exchange 2010 with Cisco Unity

Cheers

The Voice Man

Reporting on Cisco Unified Communications Software

October 24, 2011 Leave a comment

Hi All

So you have implemented a new Cisco Unified Communications environment and would like to get some detailed reporting about the installation, configuration and system performance. Some of these applications have built in basic reporting options and of course you can use the RTMT (Real Time Monitoring Tool) to get more information out of the system, however there is another product which produces great detailed documents about the configuration and performance of the enviroment. The product Uplinx Report Tool for Cisco Unified Communications (www.uplinx.com)

This product can report on the following systems

– Cisco Unified Communication Manager

– CUCM Audit (change) report

– Cisco Unified Presence Server CUPS

– Cisco Unity Connection CUC

– Cisco Emergency Responder CER

– Unified Contact Center Express UCCX 8

– Microsoft Exchange 2007/2010 UM role

– Phone Inventory Audit (Change) report

– Phone Inventory report including Serial number, model, MAC, MWI, status, location, switch neighbour details.

For more information check out the datasheet at the following link

http://www.uplinx.com/RT/ReportTool_Datasheet.pdf

Enjoy…..

The Voice Man

Cisco Unified Communications Backup Software

October 19, 2011 Leave a comment

Hi All

I have had a lot of questions surrounding the backup process required for Cisco Unified Communications software including Communications Manager, Unity Connection and Presence.

Each of these pieces of software require an SFTP location to backup to. There are a number of SFTP software applications out there but one that I use all the time during deployments and implementions is by CoreFTP called mini-sftp-server.

CoreFTP have developed a mini FREE version of there server based product and this is great for quickly and easily backing up the CUCM, UCXN or Presence server you have just deployed and ensures all of the configuration settings created are backed up.

The software is easy to use just run it up and enter a Username, Password and Location for the backup files and click start, you now have a portable SFTP server. Just reflect these credentials into your Cisco CUCM, UCXN or Presence servers to complete the process. Please ensure that you have all your desktop firewalls etc turned off as these can sometimes interfere with the connection process

Please note: As a permanent backup solution it is always best to install a fully featured licensed SFTP server application, however the software discussed here is ideal for completing a quick and convenient backup of these solutions

Below is a link and a screenshot of this software

http://www.coreftp.com/server/download/msftpsrvr.exe

 

Enjoy….

The Voice Man

UCXN – Stopping Toll Fraud and Breaches of a Unity Connection System

October 18, 2011 Leave a comment

Hi All

The following restriction tables can be applied to a Unity Connection system to ensure that the UCXN system can’t make outbound calls, this is key to reducing malicious activities like Toll Fraud or IDD calling without IDD access on a Cisco Unity Connection deployment.

Please note the default parameters for these restrictions in most deployments are  using US numbering plans therefore the below restrictions apply for all Australian based sources.

Default Transfer – Call Patterns (in order)
0001* Block
01* Block
002* Block
003* Block
005* Block
007* Block
* Allow
Default FAX – Call Patterns (in order)
0001* Block
01* Block
002* Block
003* Block
005* Block
007* Block
* Allow
Default outdial – Call Patterns (in order)
0001* Block
01* Block
002* Block
003* Block
005* Block
007* Block
* Allow
Default Alt ext – Call Patterns (in order)
0001* Block
01* Block
002* Block
003* Block
005* Block
007* Block
* Allow
CS Default system Transfer – Call Patterns (in order)
0001* Block
01* Block
002* Block
003* Block
005* Block
007* Block
* Allow

Applying these restriction does have some drawbacks, the main one being that users of the system cant make outbound transfers through the system however most clients and or deployments I have seen dont want this as a feature.

Enjoy….

The Voice Man