I am setting up about 10 Cisco 7975 phones |
|||
 |
UC500.comCisco Communication Manager Express, UC520, SMB VOIP reference and community |
|
|
UC500.comCisco Communication Manager Express, UC520, SMB VOIP reference and community |
7975/7970 UC500 and conferencing
I now have proof this is a big problem. I'm running a BU provided engineering release IOS at a customer site to see if we can get 7 7975 and 2 7945s to work with the UC500. Anyone out there considering a high-end deployment with the UC and 7975/7970 should be warned to hold on tight and be ready to engage the BU.....I've been working on this with TAC and the BU for over 2 months. Quite a happy customer...
Final Connect Corp
www.finalconnect.com
If you configured the BLFs
If you configured the BLFs for Presence, then the line button would stay red, if the line is not available.
-Dapunisher
A+. Network+, MCP, CCNA, CCVP
Geek Chic! ----> www.WeGeek.com
I have all kinds of 7975 problems
I THINK IT IS TOO MUCH PHONE FOR THE UC500.
Final Connect Corp
www.finalconnect.com
It doesn't matter what type
It doesn't matter what type of phones you use, as long as you stay within the limits of the UC520 or ISR's CME version.
It doesn't matter if it's a 7902 or a 7985, a phone is a phone as long as CME is concerned. 10x7975 are as taxing for CME as are 10x7902.
I just tested it, and you
I just tested it, and you right. It is strange though. I would say its by design. Maybe they fixed it in a newer version?
CCNA, JNCIA
That is how it works on all Cisco Phones
If the device holding the ephone-dn is unregistered the CME uses the CFNA setting of the DN. In this case it sounds like that is configured for voicemail.
A Monitor DN is not really "Owned" by the phone it occupies. It is there to Monitor or watch the behavior of a specific DN. If you shared the line instead of using a Monitor line, the behavior would be different.
Ted