A few users complained they have echo whem calls to PSTN. I noticed that Echo TailLength of the 6608 PRI on the CCM is 32ms, actually the maxium is 64.I think change this may fix the problem. But is there any disadvange to change the default to 64? Thanks
Under older 6608 code, the above URL showed the only tools you had on 6608 to help eliminate echo. Under newer code with CallManager 3.3(3)SR2 (I think) and above, Cisco has integrated the same DSP code that's used on IOS routers to eliminate echo (sometimes referred to as Echo Beach). You can tell if your CallManager version came with the newer code if 64ms is available as the max echo tail length as opposed to 32ms.
With the new echo cancellation code, convergence is fast enough that there is no real downside to setting the ECAN tail length to the max and leaving it there.
Supposedly, higher echo canceller taillengths cause longer training times, meaning the echo heard on the first few seconds of a call that the echo canceller cannot cancel would last longer. Although I have recently heard from Cisco that the latest algorymths get around this and that there is no longer any reason to not max out the taillength number.
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.