|
Home > Archive > Voice over IP Cisco > November 2007 > Unity Failover
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| I need some pointers here please. Have Unity, 4.0(5) installed with
failover. Now we had some replication problems earlier which tac help
us sort out so currently the secondary server is active. When we try
to failback to the primary, VM does not work and logs from event
viewer tells me failover back to primary succeeded but:
For more information, click: http://www.CiscoUnitySupport.com/find.php "
22/11/ 2007 08:14:41 CiscoUnity_Arbiter Warning
Run
1039 N/A unity1 "Port 2 has received an incoming call. This port is
configured to not answer incoming calls, so the call will be ignored.
For more information, click: http://www.CiscoUnitySupport.com/find.php "
22/11/ 2007 08:14:30 CiscoUnity_Arbiter Warning
Run
1039 N/A unity1 "Port 2 has received an incoming call. This port is
configured to not answer incoming calls, so the call will be ignored.
For more information, click: http://www.CiscoUnitySupport.com/find.php "
22/11/ 2007 08:14:27 CiscoUnity_NodeMgr Informa
tion Run
1047 N/A unity1 "Service AvCsMgr is active.
For more information, click: http://www.CiscoUnitySupport.com/find.php "
22/11/ 2007 08:14:27 CiscoUnity_Scheduler Infor
mation Run
1004 N/A unity1 "The Failover service (AvCsNodeMgr) is activating the
Scheduler.
For more information, click: http://www.CiscoUnitySupport.com/find.php "
22/11/ 2007 08:14:26 CiscoUnity_TSP Information
None 101 N/A unity1 "Cisco
Unity-CM TSP device 76 (Cisco Unity port 72): Connected to Cisco
CallManager 10.100.1.12:2000.
The cisco Unity-CM TSP version is 8.1(3)."
22/11/ 2007 08:14:26 CiscoUnity_TSP Information
None 101 N/A unity1 "Cisco
Unity-CM TSP device 74 (Cisco Unity port 70): Connected to Cisco
CallManager 10.100.1.12:2000.
Like i said i am new to unity so any help will be greatly appreciated
Thnx
| |
| Erick Bergquist 2007-11-23, 1:11 pm |
| It looks like it failed back to the primary server, but the Voicemail
ports on the primary server are not registered in Call Manager so the
calls to voicemail are using the VM ports on the failover server which
are registered.
You can confirm this by going into CCMadmin, then looking at the
Voicemail ports to see which ones are registered.
You may need to stop/start Unity on the primary server to get them
registered and working again (or reboot the server) - maybe something
did not fallback cleanly.
On Nov 23, 2007 6:38 AM, Lemon <lemon@lemon.za.net> wrote:
> I need some pointers here please. Have Unity, 4.0(5) installed with
> failover. Now we had some replication problems earlier which tac help
> us sort out so currently the secondary server is active. When we try
> to failback to the primary, VM does not work and logs from event
> viewer tells me failover back to primary succeeded but:
>
>
> For more information, click: http://www.CiscoUnitySupport.com/find.php "
> 22/11/2007 08:14:41 CiscoUnity_Arbiter Warning Run
> 1039 N/A unity1 "Port 2 has received an incoming call. This port is
> configured to not answer incoming calls, so the call will be ignored.
>
> For more information, click: http://www.CiscoUnitySupport.com/find.php "
> 22/11/2007 08:14:30 CiscoUnity_Arbiter Warning Run
> 1039 N/A unity1 "Port 2 has received an incoming call. This port is
> configured to not answer incoming calls, so the call will be ignored.
>
> For more information, click: http://www.CiscoUnitySupport.com/find.php "
> 22/11/2007 08:14:27 CiscoUnity_NodeMgr Information Run
> 1047 N/A unity1 "Service AvCsMgr is active.
>
> For more information, click: http://www.CiscoUnitySupport.com/find.php "
> 22/11/2007 08:14:27 CiscoUnity_Scheduler Information Run
> 1004 N/A unity1 "The Failover service (AvCsNodeMgr) is activating the
> Scheduler.
>
> For more information, click: http://www.CiscoUnitySupport.com/find.php "
> 22/11/2007 08:14:26 CiscoUnity_TSP Information None 101 N/A unity1 "Cisco
> Unity-CM TSP device 76 (Cisco Unity port 72): Connected to Cisco
> CallManager 10.100.1.12:2000.
>
> The cisco Unity-CM TSP version is 8.1(3)."
> 22/11/2007 08:14:26 CiscoUnity_TSP Information None 101 N/A unity1 "Cisco
> Unity-CM TSP device 74 (Cisco Unity port 70): Connected to Cisco
> CallManager 10.100.1.12:2000.
>
>
> Like i said i am new to unity so any help will be greatly appreciated
>
> Thnx
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Jonathan Charles 2007-11-24, 1:11 pm |
| In normal operation, when the primary is active, all of the voicemail
ports are registered. When the secondary is active, the primary vmail
ports unregister (to prevent calls from going to the primary, cuz
those ports are first in the hunt group).
Make sure none of the service accts that unity uses are domain admins
(for some reason this causes failover to freak out, especially on
win2k3).
Jonathan
On Nov 23, 2007 8:32 AM, Erick Bergquist <erickbee@gmail.com> wrote:
> It looks like it failed back to the primary server, but the Voicemail
> ports on the primary server are not registered in Call Manager so the
> calls to voicemail are using the VM ports on the failover server which
> are registered.
>
> You can confirm this by going into CCMadmin, then looking at the
> Voicemail ports to see which ones are registered.
>
> You may need to stop/start Unity on the primary server to get them
> registered and working again (or reboot the server) - maybe something
> did not fallback cleanly.
>
>
>
> On Nov 23, 2007 6:38 AM, Lemon <lemon@lemon.za.net> wrote:
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
|
|
|
|
|