Problem on UC540 - can call internal extensions but have no audio - public phone numbers work fine
I don't normally get in to IP telephony, but I have an interesting problem going on. About 2 years ago I acquired a customer with an IP-based phone system. Per usual, I'll grab configs of all network equipment upon getting access to the devices, which I did in this case. A few days ago, I was notified that the phones stopped working at a remote site (inbound, outbound, internal, and external), and after checking out the problem, I noticed that some of the configuration for the VPN tunnel was never in place. The IP in option 150 of the DHCP service was not assigned to the VPN tunnel, so after adding this to the tunnel, the phones got their configuration, and I see a lot of traffic to this IP for SCCP traffic. The users now can receive and make external calls. Unfortunately, there is no audio for internal calls (just dialing extensions) - the phones ring, though. Per the configuration from a couple years ago, this IP had never been configured for the tunnel. I'm wondering what else may be missing.
There are 3 locations total, and the other two function correctly. However, voice is traversing a VPN tunnel between two ASA's for the partly broken location, while the other location that is working is connected to the host site via MPLS. From what I've read, this is likely a codec problem, and I believe this is under "voice class codec 1", but this codec is working between two sites already.
In the attached configuration, the site not working has extensions 211 and 212. The other remote site that is working has extensions 202, 203, 205, 208, and 214. The host site is 201, 204, 206, 207, 209, and 213.
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.