you need to take care of only 1st alarm. Presence server require the messages to be authenticated otherwise the presence won't work. set the default subzone to "check credentials" or "treat as authenticated".
from one of the screenshot i see that it gives a policy response error..making above changes will fix that issue.
The "Legacy TMS Agent mode" warning is because you are still running TMS agent in legacy mode instead of using TMSPE (the new way of provisioning). Don't have to worry too much about this as you can still run the Legacy TMS Agent mode on x7.1. however we strongly recommend to use the TMSPE .
regarding alarm 3&4 since you are using default passwords thats the reason you are getting this alarms.
regarding the call issue i just see that it is matching to dial to MCU search rule but that just have pattern string as 39589 and it says stop..is there any other search after this also ? or it just ends there?
As you can see in my search rule capture before, dial to MCU we set to highest priority with stop to make sure the call wouldn't match to other search rule.
the problem is MCU prefix and ID that registered to VCS sometimes cannot be called even though in search history inform that the call match with search rule dial to MCU, but when we update MCU config and test dial again to the same destination prefix, the call is succeed.
is the problem occur because software bug / wrong configuration ?..this is the first time I work with Codian MCU so we doesn't know the behavior of this MCU.
If you have any suggestion / experiencing same issue, it will be great..:)
Unreachable destination could indicate that there is a firewall between your VCS and the MCU, preventing the VCS to connect to the MCU on TCP port 1720.
To further troubleshoot this issue, I would recommend that you start a diagnostics log on the VCS (With Network log level set to DEBUG) and place a test call towards the MCU. When the call attempt fails, stop the diagnostics log, open it in a text editor and search for the IP address of your MCU throughout the log. If you see any "TCP connection failed" entries for the MCU's IP address this would indicate a firewall/ACL rejecting the connection attempt from the VCS towards the MCU.
If you are not able to identify the issue yourself, I'd recommend you raise a TAC case and provide the diagnostics log along with a description of the issue.
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...