Hello, Thank You for the response. I didn't have the user assigned on the device, which I did now, and also added the Digest User. But it still doesn't look like anything changed.
On the phone display it is showing as "Failed to connect to server - "Call Manager IP Address"
I logged into the phone using the IP address it got via DHCP, configured the signaling protocols, Gateway, Proxy etc. But nothing is helping. Only after configuring those I started getting the message on the phone "Failed to connect". Before then it would not show anything.
I got the AudioCodes 420HD phone registered to the CUCM.
I did successful ping tests from the Call Manager to the phone and back.
The phone came with a firmware for Lync, which dd not give the option to input digest credentials, instead had Lync Sign in options which didn't work.
Below is what I did as a whole if it helps someone in the future.
Configured the phone as a Thrid Party SIP device(Basic) on the Call Manager. Configured the Line.
Downloaded the latest Generic Firmware for 420HD phones, from AudioCodes website, and uploaded it to the phone using its GUI.
Once the phone came up with the new load, it had the option to input the user credentials under Configuration --> Quick Setup --> Line Settings. In my case I had the extension number as Display Name, User ID, Authentication Username and Password. Configure the End User on the CUCM before this.
Go to Voice Over IP --> Signaling Protocols --> SIP Proxy and Registrar --> Use SIP Proxy - Enable it, Proxy IP Address or Host Name: Enter the CUCM IP Address. Use SIP Registrar - Enable: Registrar IP Address or Host Name: Enter CUCM IP Address, Submit(Save).
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...