Hello, Can brackets be used to create call parks without any adverse effect?  The documentation I found stated 1 or 2 X's can be used and a range up to 100 numbers can be created but nothing about any other wildcard usage.  As a test, I created a call park range 111[01]X and found I was able to access the full 20 slots as anticipated. I'd prefer that 1 entry rather than creating 2 entries 1110X and 1111X.  Has anyone else tried this and encountered an issues? The reason I'm looking for this type of wildcard solution is to reduce the amount of call parks created in our call park redesign to meet requirements to implement a new operator console software solution.  We have 240+ sites and 8 nodes. CUCM version 10.5 Thanks ... View more

My company just purchased a few new phones and would like to install them in our lab. We purchased the 7841, 8811, and 8851.  So, far we’ve been unsuccessfully getting any of those phones to register. Currently we are running our test environment with CUCM 8.6.2.23900-10. So, far we’ve tried these steps: Attempt 1:     Installed device pack - cmterm-devicepack8.6.2.26149-1.cop.sgn     Restarted the server (even though I understand on restarting the TFTP Server is necessary)     Configured the phone.     The phone powers up, displays our tested network address but only displays “Phone is registering”.     Start/Stopped the TFTP Server = phone is registering Attempt 2:     Installed the individual .cop file for the 8800 series of phones - cmterm-88xx-sip.10-2-2-16.cop.sgn     Restarted the server     Configured the phone     Reset all the settings on the phone.     The phone powers up, displays our tested network address but only displays “Phone is registering”.     Start/Stopped the TFTP Server = phone is registering Attempt 3:     Installed device pack - cmterm-devicepack8.6.2.26152-1.cop.sgn     Restarted the server     Configured the phone.     Same result = the phone powers up, displays our tested network address but only displays “Phone is registering”. The previous models of phones still register properly – examples 6945 and 9971. The Compatibility Matrix shows I’m using a newer release than the one stated. Is there a step I’m missing?   ... View more