[cisco-voip] too many MWI ports?

Lelio Fulgenzi lelio at uoguelph.ca
Thu Sep 3 17:19:13 EDT 2009


Sorry, I was thinking of reducing the number of MWI ports without making the other changes. Just wondering. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Wes Sisk" <wsisk at cisco.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Thursday, September 3, 2009 5:15:20 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] too many MWI ports? 

MWI refresh and broadcast messages are the primary triggers I know of. 

Reducing the number of ports will not matter if you increase delay and concurrent calls. though with that combination fewer ports will be used for MWI so you might as well re-allocate them to answering calls. 

/wes 

On Thursday, September 03, 2009 2:45:46 PM , Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 



Thanks Wes. Think I need to make these changes even with fewer MWI ports? I'm wondering if MWI refresh is also affected by this? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Wes Sisk" <wsisk at cisco.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Thursday, September 3, 2009 2:39:40 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] too many MWI ports? 

Numerous cases about this. first attempt to fix was 
CSCsf99708 MWI message optimization 

net result CM cannot process messages as fast as unity can send them (due to thread context switching inside the ccm process). 

workaround is: 
"In Connection Administration on the Port Group page, there is a group 
of MWI settings. You might try the "Delay Between Requests" or 
"Maximum Concurrent Requests" settings." 

decrease number of concurrent requests and increase delay between requests. 

/Wes 



On Thursday, September 03, 2009 2:09:09 PM , Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 



so i just sent out a VM to a distribution list and phones registered to the same subscriber as the voice mail ports got a fast buy instead of dial tone with "high traffic" message. 

the only thing I can think of is that because all my voice mail ports are set to MWI enable, the process of trying to send out 4000 MWIs (via 140 ports) caused the subscriber to hiccup. 

is this expected behaviour? is too many MWI ports a bad thing? 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


_______________________________________________
cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090903/2c99a303/attachment.html>


More information about the cisco-voip mailing list