|
Home > Archive > Voice over IP Cisco > August 2006 > What controls how quickly MWI is resynced?
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]
| Author |
What controls how quickly MWI is resynced?
|
|
| Robert Kulagowski 2006-08-22, 1:11 pm |
| In a 72 port Unity 4.2(1) system, how come going to UTIM and performing
a "Resync Now" doesn't use all 72 ports? All the ports are available
for MWI, but from watching the PortStatusMonitor it's only using Port 72
for the most part, and port 70 and 71 infrequently, so the resync (after
a failover to the secondary) seems to be taking a very long time. (At 17
minutes and still counting according to the eventvwr.)
| |
| Matt Slaga \(US\) 2006-08-22, 1:11 pm |
| Check your port configuration in Unity. You have the ability to only
allow certain ports to send MWI, which is probably configured.
I would advise against allowing all 72 ports for MWI however. If your
CEO decides to send a corporate-wide broadcast, the server may have to
light x thousand phones which could make unity inoperable until it was
complete.
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Robert
Kulagowski
Sent: Tuesday, August 22, 2006 12:18 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] What controls how quickly MWI is resynced?
In a 72 port Unity 4.2(1) system, how come going to UTIM and performing
a "Resync Now" doesn't use all 72 ports? All the ports are available
for MWI, but from watching the PortStatusMonitor it's only using Port 72
for the most part, and port 70 and 71 infrequently, so the resync (after
a failover to the secondary) seems to be taking a very long time. (At 17
minutes and still counting according to the eventvwr.)
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
| |
| Simon, Bill 2006-08-22, 1:11 pm |
| We see no difference between enabling two MWI ports and enabling ten.
In both cases, it only seems to use two when performing a resync. I
assume it is due to some other bottleneck in Unity that has nothing to
do with the MWI ports.
Robert Kulagowski wrote:
> In a 72 port Unity 4.2(1) system, how come going to UTIM and performing
> a "Resync Now" doesn't use all 72 ports? All the ports are available
> for MWI, but from watching the PortStatusMonitor it's only using Port 72
> for the most part, and port 70 and 71 infrequently, so the resync (after
> a failover to the secondary) seems to be taking a very long time. (At 17
> minutes and still counting according to the eventvwr.)
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
| |
| Lelio Fulgenzi 2006-08-22, 1:11 pm |
| I can confirm that. We have multiple MWI ports configured but still only see one or two ports being used at once.
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I can eat fifty eggs." "Nobody can eat fifty eggs."
----- Original Message -----
From: Simon, Bill
To: Robert Kulagowski
Cc: cisco-voip@puck.nether.net
Sent: Tuesday, August 22, 2006 1:32 PM
Subject: Re: [cisco-voip] What controls how quickly MWI is resynced?
We see no difference between enabling two MWI ports and enabling ten.
In both cases, it only seems to use two when performing a resync. I
assume it is due to some other bottleneck in Unity that has nothing to
do with the MWI ports.
Robert Kulagowski wrote:
> In a 72 port Unity 4.2(1) system, how come going to UTIM and performing
> a "Resync Now" doesn't use all 72 ports? All the ports are available
> for MWI, but from watching the PortStatusMonitor it's only using Port 72
> for the most part, and port 70 and 71 infrequently, so the resync (after
> a failover to the secondary) seems to be taking a very long time. (At 17
> minutes and still counting according to the eventvwr.)
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Robert Kulagowski 2006-08-22, 1:11 pm |
| Matt Slaga (US) wrote:
> Check your port configuration in Unity. You have the ability to only
> allow certain ports to send MWI, which is probably configured.
Unity and UTIM are both configured so that all 72 ports are available
for MWI. But again, in Port Status Monitor, I could see that only port
72 was being used for the most part, with 70 and 71 with almost no
activity. Total time to resync was over 1 hour.
> I would advise against allowing all 72 ports for MWI however. If your
> CEO decides to send a corporate-wide broadcast, the server may have to
> light x thousand phones which could make unity inoperable until it was
> complete.
Not an issue in our environment.
| |
| Ortiz, Carlos 2006-08-22, 7:12 pm |
| We are around 1000 phones and the Resyncs seem to take a couple of hours
in our case. Anyone know if it's possible to speed this up?
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Tuesday, August 22, 2006 1:43 PM
To: Simon, Bill; Robert Kulagowski
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] What controls how quickly MWI is resynced?
I can confirm that. We have multiple MWI ports configured but still only
see one or two ports being used at once.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I can eat fifty eggs." "Nobody can eat fifty eggs."
----- Original Message -----
From: Simon, Bill <mailto:bills@tns.its.psu.edu>
To: Robert Kulagowski <mailto:bob@smalltime.com>
Cc: cisco-voip@puck.nether.net
Sent: Tuesday, August 22, 2006 1:32 PM
Subject: Re: [cisco-voip] What controls how quickly MWI is
resynced?
We see no difference between enabling two MWI ports and enabling
ten.
In both cases, it only seems to use two when performing a
resync. I
assume it is due to some other bottleneck in Unity that has
nothing to
do with the MWI ports.
Robert Kulagowski wrote:
> In a 72 port Unity 4.2(1) system, how come going to UTIM and
performing
> a "Resync Now" doesn't use all 72 ports? All the ports are
available
> for MWI, but from watching the PortStatusMonitor it's only
using Port 72
> for the most part, and port 70 and 71 infrequently, so the
resync (after
> a failover to the secondary) seems to be taking a very long
time. (At 17
> minutes and still counting according to the eventvwr.)
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Simon, Bill 2006-08-22, 7:12 pm |
| We have over 7000 VMO subscribers and it takes 8 hours. Resyncing MWI =
is a huge deal for us, and one we have never been satisfied with. We =
are unable to implement Cisco's failover recommendation of resyncing MWI =
nightly due to the length of time it takes. It is a big headache. HELP!
Ortiz, Carlos wrote:
> We are around 1000 phones and the Resyncs seem to take a couple of hours =
> in our case. Anyone know if it=92s possible to speed this up?
> =
> =
> =
> ------------------------------------------------------------------------
> =
> *From:* cisco-voip-bounces@puck.nether.net =
> [mailto:cisco-voip-bounces@puck.nether.net] *On Behalf Of *Lelio Fulgenzi
> *Sent:* Tuesday, August 22, 2006 1:43 PM
> *To:* Simon, Bill; Robert Kulagowski
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] What controls how quickly MWI is resynced?
> =
> =
> =
> I can confirm that. We have multiple MWI ports configured but still only =
> see one or two ports being used at once.
> =
> =
> =
> -------------------------------------------------------------------------=
-------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "I can eat fifty eggs." "Nobody can eat fifty eggs."
> =
> ----- Original Message -----
> =
> *From:* Simon, Bill <mailto:bills@tns.its.psu.edu>
> =
> *To:* Robert Kulagowski <mailto:bob@smalltime.com>
> =
> *Cc:* cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> =
> *Sent:* Tuesday, August 22, 2006 1:32 PM
> =
> *Subject:* Re: [cisco-voip] What controls how quickly MWI is resynced?
> =
> =
> =
> We see no difference between enabling two MWI ports and enabling ten.
> In both cases, it only seems to use two when performing a resync. I
> assume it is due to some other bottleneck in Unity that has nothing to
> do with the MWI ports.
> =
> =
> Robert Kulagowski wrote:
> performing
ble[vbcol=seagreen]
> Port 72
> (after
> (At 17
> =
> -- =
> Bill Simon - bills@tns.its.psu.edu <mailto:bills@tns.its.psu.edu> -
> (814) 865-2270
> http://tns.its.psu.edu/
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =
-- =
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
| |
| Stu Packett 2006-08-22, 7:12 pm |
| The way the MWI sync works is Unity goes through each person's Exchange
Inbox looking for a particular Exchange 'message class' or Unity
voicemail.
Since I manage the Exchange system as well, I think I may have an answer
as to why 2 ports or 50 ports don't make a difference. I'm no expert in
Exchange or Unity, but just throwing this out there in case a guru has
some comments. Exchange has these threads (MAPI sessions) that it hands
out to applications like Outlook and Unity. I think Exchange and/or
Unity is limiting the amount of threads that can be used when it does
MWI syncs so it won't bring the Exchange server to a halt. I think the
magic number is around 250 threads per account. For us, we have users
with over 10,000 emails in their Inbox and I too increased the MWI sync
ports, but didn't seem to make a big difference and it may be because
the amount of threads or 'MAPI sessions' that the Unity service account
is limited to 250.
I may have the terminology of threads or MAPI sessions wrong, but it's
something similar to that.
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ortiz, Carlos
Sent: Tuesday, August 22, 2006 3:05 PM
To: Lelio Fulgenzi; Simon, Bill; Robert Kulagowski
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] What controls how quickly MWI is resynced?
We are around 1000 phones and the Resyncs seem to take a couple of hours
in our case. Anyone know if it's possible to speed this up?
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Tuesday, August 22, 2006 1:43 PM
To: Simon, Bill; Robert Kulagowski
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] What controls how quickly MWI is resynced?
I can confirm that. We have multiple MWI ports configured but still only
see one or two ports being used at once.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I can eat fifty eggs." "Nobody can eat fifty eggs."
----- Original Message -----
From: Simon, Bill <mailto:bills@tns.its.psu.edu>
To: Robert Kulagowski <mailto:bob@smalltime.com>
Cc: cisco-voip@puck.nether.net
Sent: Tuesday, August 22, 2006 1:32 PM
Subject: Re: [cisco-voip] What controls how quickly MWI is
resynced?
We see no difference between enabling two MWI ports and enabling
ten.
In both cases, it only seems to use two when performing a
resync. I
assume it is due to some other bottleneck in Unity that has
nothing to
do with the MWI ports.
Robert Kulagowski wrote:
> In a 72 port Unity 4.2(1) system, how come going to UTIM and
performing
> a "Resync Now" doesn't use all 72 ports? All the ports are
available
> for MWI, but from watching the PortStatusMonitor it's only
using Port 72
> for the most part, and port 70 and 71 infrequently, so the
resync (after
> a failover to the secondary) seems to be taking a very long
time. (At 17
> minutes and still counting according to the eventvwr.)
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
--
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|