[cisco-voip] Unity not using newly added VM ports

[Ryan Ratliff]

Sounds like your problem is not with Unity but with CallManager.   If  
you are on CM 3.3 or earlier make sure port 32 is CFNA, CFB to port  
33 and so on.  If you are on CM 4.x make sure your line group  
includes the new vm ports.

Also make sure ports 33+ show registered in CallManager.
-Ryan

On Jun 8, 2006, at 11:10 AM, Peter Pauly wrote:

I'm running Unity 4.0(3) SR 1 and just expanded the number of voice mail
ports from 32 to 96. The licensing application shows that
LicVoicePortsMax is 96. In the Manage Integrations app, I added the
additional ports and checked all the boxes. I also added ports in Call
Manager. Unity has been rebooted since the ports were added, but it
still won't use the additional ports. I max out the 32 ports a few times
during the day and get a busy signal. Status Monitor shows only the old
ports being used. The new ports are displayed but are idle.

The only odd thing about my installation is that I have two
integrations, ports 1-8 are on Centrex. Ports 9 and up are on Call  
Manager.

Is there some trick to get Unity to start using the new ports? Did I
leave something out?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip