We just ran across an issue with this, we were installing a bunch of them and discovered that they were all coming up at 10/half. All of the existing doc states that the devices do auto by default, but in this release note, where they give the possible values, they show 0x00000044 as the setting for auto. They ship with a setting of 0x00000000, which according to the doc, and our experience, is 10/half. Also, once you change the settings, you have to power cycle the unit to get them to change, resets will not do it. There also does not seem to be any documentation besides the release notes for 3.2, it would be nice to have an admin guide.
Correction - they did not all come up at 10/half, while they all had the same software and settings, about a quarter of them did the autonegotiation - and adignan, I notice you specified the Admin Guide - the latest doc I find online is for 3.0, and the TAC engineer I harrassed about this said they were not planning on issuing new documentation. Is it really out there somewhere, or were you looking at the release notes?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...