I am trying to upgrade a MeetingPlace AppServer in standalone mode from the release 184.108.40.206 to the release 220.127.116.11 but when I run the upgrade file after the version validation I get and DNS error saying that the validation fails trying to resolve the FQDN of the MeetingPlace and the IP-Address of the MeetingPlace, but I have lookup at the logs and I found that the DNS server replys to the request of the MeetingPlace in a correct way.
I'm running into the same issue, wondering if anyone can post a resolution or some tips. I've verified that both the Host (A) and Reverse (PTR) records are present and correct in my DNS. I can get on the MP server itself and do an nslookup on both the hostname with or without domain name and on the IP and I get the correct response back. Can't figure out why I keep running into this error.
Any clue what logs files I should be looking at and where they are? The UpgradeLog.log in the /root folder doesn't give any clues, just a bunch of successes then it says the upgrade was terminated by user.
I had no idea it was that picky with regard to DNS. Turned out to be a mismatch between the PTR record and the hostname. Hostname was something like CUMPAppSrv and the PTR record had it as cumpappsrv. Changed the hostname to all lowercase and got past that part of the installation no problem.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...