Unfortunately detecting a locked port is typically not that easy.
If a port is not responding to incoming calls (RNA) then it is unlikely Unity will be able to generate an event message in response to the incoming call. There may be other tell-tale event messages in such circumstances but they'd vary greatly depending on the root cause of the unresponsiveness. If the port is locked in an offhook state then the phone system wouldn't even offer a new call to it.
In either case, you might look for ports that Unity believes have been busy on a single call for an extended period of time. I believe this shows up in event ID 584 (or 553 for very old version of Unity),
We are currently experiencing this issue on our Unity 4.0(5) box. I have setup EMS to notify me of the 584 event which is good for making me aware of a port lockup but how do I determine the cause/resolution?? This has occurred since we brought this instance up in September. Sometimes we will go a week without the issue, sometimes it will happen multiple times in a week. I have also noticed that there are times the port will have actually cleared itself by the time I look at it and there are also cases when 2 ports have locked (never more then 2).
We have two Unity 4.0(4)SR1 instances that to my knowledge have yet to encounter this issue.
Any suggestions on researching or resolving this issue would be greatly appreciated. Also, is there a way to have a port auto-reset should the problem occur?
Your best bet will probably be to have a TAC case opened. To find the root cause of a locked port it is very helpful to have diagnostics that cover the last successful call to that port. Seeing the transition from working to non-working in the diag file can usually tell us what is happening.
I don't believe there is a way to have ports auto-reset. Again, the major problem here is that there is no good way for Unity to self-diagnose and identify a locked port. The good news is that if your ports are locked in such a way that they sometimes clear themselves then most likely they can also be cleared by manually resetting the port either in the Unity Status Monitor or in CCM. This indicates a very different scenario than port locks which can only be cleared by restarting Unity.
Here are a few things Id look for
- verify whether the locked ports can be reset through Unity Status Monitor
- use Port Status Monitor (tools depot) to identify what Unity thinks is happening on a locked port (it could be Unity never receives a disconnect from CCM and youve got a conversation or set of Call Handlers that runs through a continuous loop. In such a case you either need to find out why a hang up event is never received from CCM or you need to structure you Call Handlers so they always eventually lead to GoodBye and hangup.
- collect Skinny and Call Control (macro) diags from Unity along with detailed CCM traces that span a port transitioning from working to locked. Work with TAC to identify what went wrong.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...