Differences between CM 5X and 6X - Light informational inquiry
I've been working with CM 5X for a while now and am starting to get into 6X. Can anyone tell me what their experience has been with working with 6X as compared to 5X? Any major differences in administration? Disaster recovery?
Re: Differences between CM 5X and 6X - Light informational inqui
Just to add some input. These always get confused.
Recording means recording is supported. Still need a 3rd party recording server and need phones that have the dual-RTP stream capability. See the administration guide for the supported phones. Usually 79x1 and up phones.
Intercom is actually paging to ONE phone. If the phone is on the phone (hehe) the page can be "wispered" so only the IP phone can hear the page. The person they are talking to can't hear it. Like auto answer to speakerphone from previous CCM versions, need a phone that has a free line button (ie, 7940, 7960, etc.) 7906, 7911, etc with only one button is not supported.
Another big one is AAC / ILBC codecs. AAC is higher fidelity voice. 22KHz, 16Bit instead of 8K, 8 bit. All using the same 80Kbps transfer rate. Need the newer phones to support it (7942, 7962, 45, 65, etc.) ILBC is a codec that is supposed to be more, say, Internet friendly. Tolerates more jitter, latency, etc. Also need those newer phones.
Do not disturb: A real do not disturb
what else is good.
Programmable line keys. A line key can be programmed to take on just about any (one) function. Line, Speed Dial, BLF, hold, transfer, etc.
Upgrading from 5.x to 6.0 is a little "different" since the database changed significantly.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.