We are running a pilot of Cisco's IP telephony project, with Unity as our voice mail platform. The install was done by a consultant, but I'm the man ultimately responsible for the system in our organization.<br><br>I got back from lunch today and voice mail was unavailable - dialing the pilot number gave a fast busy. I got on the Unity console and looked at the status URL, and found that the Unity service was stopped.<br><br>Starting it brought everything back just fine.<br><br>Then, just a few minutes ago it happenned again. This time, however, the status page showed the Unity service was up, even though we were getting fast busy signals when calling the numbers.<br><br>The only change I made today was to unplug and plug back in a fiber link between two of our three Catalyst switches (a 4006, a 5500, and a 6509). They are all wired together in a triangle via gigabit fiber. When I unplugged the link the first time, the Unity perhaps lost connectivity for at most 20-30 second before the spanning tree algorithm did its thing and all was back up.<br><br>And it was plugging that link back in that seemed to kill it the second time. Again, there should have been no loss of connectivity there (maybe a few seconds at the most).<br><br>I see in our NT Application log for the Unity service the following Warning message at about the times we experienced the problems:<br><br>AvCiscoTsp device 1: Disconnected from CallManager 10.64.16.41<br>(also for devices 2, 3, and 4 - we have a 4-port license)<br><br>and then within a second in the log:<br><br>AvCiscoTsp device 1: Reconnected to CallManager 10.64.16.41<br><br>So it seems like it got reconnected just fine. I don't know why it would be giving a busy when I call. As I said, the second time this happenned the Unity service still appearred to be running fine. Via the status URL, I stopped and started it and everything came back.<br><br>I believe our consultant said we were using TSP version 28, which I guess is not considered the most stable production version (24 is?). We upgraded to that for some other problem, which didn't get fixed anyway, so there likely is not a problem to downgrade.<br><br>It looks like we're using Unity 2.4 Build 2.4.5.73<br><br>If there is anything else I can describe or provide that would be helpful in diagnosis, please let me know.<br><br>I am going to probably try and reproduce the problem to see if it is consistent. We were about to start rolling into production with this IP phone system; I suppose it is better that this cropped up now rather than next week.<br><br>thanks!<br><br>johnS<br><br>
