I got a ticket reporting that a courtesy phone in a lobby was no longer working. Which is why Contact Center so often makes me wanna cry. A useful skill set to have as an engineer is to recognize when communication between devices has broken down. Welcome back step upgrade. Switch versions on the secondary, repeat the process above, pour another glass of whatever is left. 
| Uploader: | Mosho |
| Date Added: | 28 January 2010 |
| File Size: | 35.58 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 99847 |
| Price: | Free* [*Free Regsitration Required] |
What if, for whatever perfectly legitimate reason that completely boggles the mind of any sane administrator, the user needs to have a brand new extension and a brand new phone added to this process.
Then check and see of your server makes the cut. This document may make your head spin a little, but first look for the version of UCCX you want to go with, in our case 8.
X show network eth0 confirm the changes.
UCCX – Just another day at the office…
But I currently live in 9. Home Who writes this stuff and why? Of course upgrades always go as planned, right? CUCM could not find a potential match for the destination directory number in any partition in the CSS of the translation pattern.
lixense
You call the user and have her log in, expecting accolades and words of supreme gratitude and instead you are confronted with this beautiful piece of snark, beginning with the phrase The specified extension is not associated with the ID: Voice engineering breeds much in the way of paranoia, so I also recommend downloading lciense scripts and prompts, just in case you get the additional fun of rebuilding the server from scratch.
In this case, our sample server meets the hard drive specs GB drivesbut is going to need an extra two gig of RAM to make the leap into hyperspace.
Category: UCCX
Historical reports tells you how exceptional you are with an Exceptional Error. I find the upgrade research process far more entertaining if you approach it like a less than ideal scavenger hunt — a poorly planned, slightly brutal game of talent and luck- mixed with just a pinch of despair.
You check resources in UCCX and you see the fruits of your awesome work reflected in the updated extension now showing for said user.
Switch versions on the primary. When I power on the what-should-be-happier server, however, I am woefully disappointed when all is not right in Whoville.
Cisco UCCX 11.5 + CUCM 11.5 Integration
I decided it was time to talk to my excellent friends over at TAC. Standard disclaimer, I put this list together from various calls with TAC asking for documentation and clarification on the process for each application and what to expect.
Wait for services to start.
And they have my email address. After a little digging, I found that this phone was put in place to be a PLAR private line automatic ringdown phone, and when users picked up the handset they were greeted with an unfriendly fast busy instead of being courteously and automatically connected to the proper extension. In our example case, we do make the cut — our version of UCCX 7. If you noticed this issue because you are exceptional and your Historical Reports makes wild unsubstantiated claims that no data exists, just check out the solution under No Data Available in the Historical Reports in this link because there are a few more hoops to jump through: And by we, I mean he.
Go ahead and check one more time, confirm that you really are seeing the updated extension in UCCX. Then try another reboot of the pair, attempt license load once more with fingers more tightly crossed than before, and then proceed to happy dance.
Step one is once again to determine your hardware compatibility. Did I mention read the docs? Shut down the server because seriously, who needs that kind of negativity in life?
Error occurred while performing the operation. Among other things, you will still need to review the release notes for each application, check for COP file requirements, check the prerequisites for each proposed version, and confirm phone firmware compatibility. The cluster information and subscriber configuration does not match. This is probably because I started out in voice completely unfamiliar with the product- and also because the application developers may or may not have been smoking crack.
Back to the story though- I gracefully take down the secondary server and pull out lcense sticks of 1 gig memory and put in 2 sticks of 2 gig memory. When I presented the process to my virtualization guruhe concluded it would not work for our configuration, we would have to use some PowerCLI magic instead.
Tue Oct 18 Log into the server, install license file, note the error message about OVA template issues.
Comments
Post a Comment