Unity 4.0(4) SR1 intermittently not answering

Unanswered Question
Mar 15th, 2007

I am running 4.0(4) SR1. I have 72 ports total licensed and and the first 62 are for taking messages, the rest for MWI and message notification. Intermittently when calling a subscriber phone, the phone will keep ringing and not forward to Unity on a no answer. Has anyone here had this intermittent issue? It isn't just with a single subscriber, it is various subscribers. Any suggestions on where to look? Not a Unity guy so looking for a little guidance. Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
jbarcena Thu, 03/15/2007 - 13:49

There is a bug were the Unity ports will hang on Unity 4.0(4) if they are answering many calls, the fix is to either upgrade to Unity 4.0(5) or restart the Unity ports from CCM one by one or all at a time by restarting the unity server.



uberwolfe Thu, 03/15/2007 - 13:53

I will look into that further. When you say restart Unity servers or just Unity itself?

jbarcena Thu, 03/15/2007 - 13:56

Stop/Start Unity from the system tray should be enough, although I normally recommend to reboot the server, at the end is up to you.

uberwolfe Thu, 03/15/2007 - 14:02

OK was just verifying this. I had already stopped and started Unity from the system tray. I will try restarting the ports from CCM. If anyone else has an idea or anything different, suggestions are appreciated. Thanks to you guys.

Tommer Catlin Thu, 03/15/2007 - 14:05

what is your TSP version on Unity? Upgrade if they are not the most recent. Sounds like a TSP problem.

Tommer Catlin Thu, 03/15/2007 - 14:10

Your TSP version on Unity 4.04 is going to be on the server

At the console go to Unity Tools and Unity Integration manager (UTIM)

The TSP version will be listed where it is connected to CCM or integrated

Tommer Catlin Thu, 03/15/2007 - 14:26

yeah, I can't help ya there then. Because TSP software version should be in numbers like 7.x 8.x The most recent TSP version is 8.1.3 you can download from CCO.

Are you using Unity Connection or Unity 4.04 or both?

eschulz Thu, 03/15/2007 - 15:41

TSP versioning gets a bit wacky on ESes. This is because the TSP code is actually built with Connection. The same TSP is then used with both Connection and Unity. For regular releases, the versioning on the TSP files are restamped to provide something meaningful, e.g. 8.1(3). With TSP ESes, that restamping doesn't always happen. Thus you're left with a version number that looks sort of like a Connection ES version.

Anyway, long story short... The 1.2(1.0)ES4 TSP is actually our 8.1(3)ES1.


eschulz Thu, 03/15/2007 - 15:44

Stepping back from the rest of the thread here, can you clairify this "the phone will keep ringing and not forward to Unity"?

If the call is not forwarding to Unity then the issue likely lies with the phone system.



This Discussion