Showing posts with label Cisco Callmanager. Show all posts
Showing posts with label Cisco Callmanager. Show all posts

Tuesday, 6 November 2007

Dual Mode Phones take their first big leap

Woohoo cheers Cisco!

On the front page of their site they have a news post with a little gem in it. We're finally going to see the first SCCP load for a non-Nokia phone (For the record, the E60, E61 and E65 are utter crap - don't buy one!).

The featured device is a HP iPAQ 600 series phone based on Microsoft Mobile. Hopefully this will pave the way towards more and more Microsoft based devices running in harmony with Cisco CallManager:


I definitely can't wait! Imagine a device that is the pinnacle of mobility and productivity in the future. The following features would be nice!
  • Dual Mode (Wireless and GSM)

  • Push Email

  • GPS

  • Touch functionaity

  • MP3 player (DVB based TV onboard would be cool too!)

  • Camera with flash

Nice one Cisco!

Sunday, 28 October 2007

The aftermath of DMA

Another day, another dollar or so they say. Today we completed a migration of Callmanager 4 to Callmanager 5 using the DMA tool, with largely successful results. We did however, run into issues which caused the project to be delayed.

So what did we learn?

I tested using the DMA tool on a dummy system in our attempt to see what could break during the process - and during the process I found no problems. Great! What we didn't really bank on was some issues with the installation of CM5 with the real customer's DMA file. The problem that occurred caused the CM installation to crash and at first we thought it was a problem relating to delete.CSV being present in the DMA tar file; but using the tar tool to remove it didn't solve the issue. It turned out to be a problem relating to the new 7937 Cisco phone, and a typo in one of the XML files. We got Cisco TAC on the case and their brilliant engineers got us to the install day.

After the DMA had completed we did find several other (small) problems but were easily sidestepped:
  • It was impossible to delete some old device pools because the device defaults claimed they were assigned to the device pools- but they weren't...
  • The Subscriber is having problems replicating databases even though the system health check says all is well.
  • Various auto generated device profiles could not be deleted because they were assigned to phones that didn't exist.

Overall the whole process was very successful, but it took a while to complete and we came up against some problems which were definitely "show stoppers". DMA is a fantastic tool, but for all budding upgrades out there -plan, test, plan, test.

Test!