How to convert a MXP 1000 with SCCP M2.x Firmware to a MXP 1000 with F9.x Firmware. *This process will describe how to convert an MXP 1000 with Mx.x firmware which is an SCCP  firmware version   to a F9 firmware which will provide the H323 and SIP capabilities to the MXP 1000. *This process can be used in the event that a customer may have use and registered an MXP 1000 to their Cisco  Unified Communications Manager as SCCP while in CUCM version 7.1.x or below. *This Process will enable users to have the MXP1000 act as a H323 Client in UCM 8.x and higher and therefore able   to communicate with other UCM endpoints as normal. -Proceed to download the TANDBERG SCCP Upgrade Tool Ver 1.1, you can download the following tool from   http://ftp.tandberg.com/pub/software/endpoints/cisco_call_manager_series/ -Proceed to download the desired firmware, for the purposes of this document we used   s50000f9_1.pkg -Proceed to obtain an F9 Key by contacting the Cisco Licensing Department -Once you have a F9 key,  proceed to open the TANDBERG SCCP Upgrade Tool Ver 1.1 -Using the top panes on the tool we will navigate and highlight the desire firmware, in our case we   navigated and selected the s5000f9_1.pkg file. -Next we proceeded to enter the IP address of the MXP 1000 Unit under the IPAddress columm -Next we proceeded to enter the password, this should be the telnet password (if any exist), enter   this password under the Password Columm -Next we proceeded to enter the Release Key under the Release Key columm. -Next proceed to press the Upgrade button, If all goes well the upgrade should start on the MXP 1000 -Once the upgrade has been completed the unit will reboot and the unit will be now running the F9 Version. -In order for the MXP 1000 to interoperate with UCM 8.x you will need configure the MXP 1000 as an H323 client in UCM 8.x - How to properly Configure an MXP 1000 as an H323 client to be used with UCM 8.x -Go to System Configuration -Select the H323 Tab H323 Configuration Callsetup Mode : Call manager CallManager Extention: The correspondent UCM DN Number CallManager Address: The appropriate UCM IP Address -Change the H.323 Ports selection to Static -Leave the rest as default, select save -Proceed with the next Section                                                         How to add a MXP 1000 as an H323 Client in UCM 8.6.x -Go to the UCM Administration Page -Go to Device then select Phone -Proceed to select Phone Type options and select   H323 Client. -Proceed to enter the IP address of the MXP 1000 in the Device Name Field as well as   selec the appropriate Device Pool, Calling Search Space location and other UCM   require selections, select save. -Proceed to enter the Directory number information for the MXP 1000 and other required UCM information, select save. -Proceed to test ... View more

                              How to transfer Opends VCS data to TMS for recovery purposes. Scenario: Let's assume customer has had a harddrive failure and has lost its opends data/provisioning data in its TMS Server and now has to build a new TMS server but needs to recover its provisioning information and would like to do this by using the data that is currently residing in VCS opends server. Resolution: We will copy the opends data residing on a VCS server and use it on a TMS server with the purposes of building a new TMS provisioning directory using the data that resides on the VCS server. Environment: - TMS 13.x - VCS  6.1 Tools Needed: - Putty - WinSCP Access Needed: - Root Access to VCS - RDP Access to the TMS server Restart or Reboot Server Required: - Yes, TMS Server only Possible Errors: - Could wipe all opends/provisioning data in the VCS Server - Unable to replicate from the TMS to the VCS Before continuing the following should apply: - The new TMS Server has not been replicated to the VCS. - The new TMS server ldap and replication password has not been changed from the default value of TANBDERG. - It is preferred for the new TMS server to have the same host name / IP address as the old TMS server. - The VCS server should be able to ping the TMS Server by its hostname only - The VCS server still contains data from the last time TMS successfully replicated to the VCS. Steps to resolve scenario: 1. First, we need to verify that opends data exist in the VCS server. a. Login to the VCS server via SSH and as root and by typing the following command as root on the VCS: #ldapsearch -x -h localhost -D "cn=Directory Manager" -w TANDBERG -b dc=provisioning "(objectclass=*)" b. The above command will return ldap data contained in the opends.  For example, you will find provisioned users information. c. Once confirmed provisioning data is in the Opends in the VCS server we, proceed to next step. 2. Proceed to change the replication and ldap password to the default value of TANDBERG. a. Enter the following commands as root in the VCS Server.  #tmsagent_ldap_passwd #tmsagent_replication_passwd 3. Proceed to open WinSCP and enter the VCS Server information (root credentials) 4. Proceed to browse to /mnt/harddisk/app/opends/db/ and copy the userRoot directory from the VCS to the TMS server desktop. 5. Proceed to open the task manager application and end all java.exe processes 6. Proceed to access the TMS server via RDP and navigate to C:\Program Files\TANDBERG\TMS\Provisioning\OpenDS-2.0\db\ 7. Once in the C:\Program Files\TANDBERG\TMS\Provisioning\OpenDS-2.0\db\ directory proceed to rename the userRoot directory to userRoot_old 8. Proceed to copy the userRoot directory that you extracted from the VCS server to the following directory:   C:\Program Files\TANDBERG\TMS\Provisioning\OpenDS-2.0\db\ 9. You should now have userRoot_old and userRoot directory 10. Proceed to restart the TMS server 11. Verify the TMS server has fully come up including all services   12. Proceed to navigate to System, Provisioning,Directory and verify      your provisioning information. Note: All provisioning information resided in VCS should now be part of the TMS provisioning directory. 13. Proceed to access the VCS Server and purge the opends Data by  entering the following command:   tmsagent_destroy_and_purge_data   14. The above command should return in the last line OK. 15. Proceed to access the TMS gui and change the ldap configuration password and the ldap replication password to another value and select save.   16. Proceed to enable replication to the VCS This document was created by Cesar Fiestas ... View more

Overview SMART is a POWERFUL Output log parser and analyzer capable of parsing and analyzing single or multiple SIP, H323 and Q931 logs files from various platforms such as Cisco Telepresence Video Communication Server, Cisco Unified Communications Manager, Cisco Telepresence Systems, Cisco IOS and others. Thus, SMART reduces painful, consuming and critical log analyzing time for the engineer while providing accurate parsing as well as reporting. Features Cisco Unified Communications     Manager  Intelligent SIP parsing capabilities Cisco Unified Communications Manager Intelligent   H323 parsing capabilities Cisco Unified Communications Manager Intelligent   Q931 parsing capabilities Cisco IOS Q931 Intelligent parsing capabilities Cisco IOS Intelligent SIP Log tracing   capabilities Cisco Telepresence Video Communication Server  SIP  Log Tracing capabilities Cisco Telepresence Video Communication Server   H323 Log Tracing capabilities Cisco Telepresence System SIP Log Tracing   capabilities Cisco Cius SIP parsing capabilities. Quick Find (multiple search criteria within the   log or logs) Powerful Call Flow and Media Reporting SMART Inspector feature (double click on any  line  and new screen opens with the actual file content, matching location of   the line selected by the user) Log screen Print SMART Report Print SMART supports .txt, .log, .dat  and most  text  file formats  Detail Screen Print Single and all row copy feature Access to the PolarisOne database Compare Files (SMART will be able to compare   xconfig and IOS configuration files) Auto Self Update and or upgrades (no need to   search for new updates or upgrades files) Easy Installation (interactive process) How to use     -Gather the trace log for example:      *In the event of wanting to analize SIP or H323 logs from UCM, use RTMT to gather the sdi ccm traces      *In the event of wanting to analize H323 logs from an IOS device please use the correct debug commands       to properly capture this information      *In the event of wanting to analize SIP logs from Cisco VCS version 5.x, 6.x, use Netlog 2 SIP     -Save your output trace log as .txt     -Open SMART     -Select the platform that the trace log was taken from     -Open or drag and drop your trace log file     -Let SMART handle the rest Installation SMART requires the following hardware and software in  order to properly install and run, -1 GHz x86 processor -512 MB of RAM -512 MB Hard Disk space available -Microsoft Windows  Professional -Microsoft Windows Vista -Microsoft Windows 2000 -Microsoft Windows 7 *.NET Framework 3.5 is required. You can download SMART her or by going to www.telepresencebridge.com/smart ... View more