[cisco-voip] Unity Broadcast / private distribution list

[Brian Henry]

That is the difference though, it will light up for PDL but not BM.  If you  do BM in unified you will not even receive it in your inbox, so it is pretty quick but with no way of really knowing.

________________________________

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Mon 1/29/2007 10:05 PM
To: Brian Henry; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity Broadcast / private distribution list


We've used a public distribution list in the past and MWIs get lit up. I believe we are on 4.0(4) though.

	----- Original Message ----- 
	From: Brian Henry <mailto:Brian.Henry at apptis.com>  
	To: Lelio Fulgenzi <mailto:lelio at uoguelph.ca>  ; cisco-voip at puck.nether.net 
	Sent: Monday, January 29, 2007 9:58 PM
	Subject: RE: [cisco-voip] Unity Broadcast / private distribution list

	Did they change the way BM work in 4.2?
	 
	4.0(5)
	Broadcast messages do not light message waiting indicators on your phone, nor do they cause you to hear a distinctive dial tone when you pick up the receiver-as may occur when you receive other new messages. In addition, broadcast messages do not trigger message notifications for any alternative devices-such as a pager or cell phone-that you may have set up in the Cisco Unity Assistant. 
	 

________________________________

	From: cisco-voip-bounces at puck.nether.net on behalf of Lelio Fulgenzi
	Sent: Mon 1/29/2007 4:42 PM
	To: cisco-voip at puck.nether.net
	Subject: Re: [cisco-voip] Unity Broadcast / private distribution list
	
	
	Sorry, just to put things into perspective, we have 3600 users on two systems, and as long as we time it properly things go without a hitch. If you can time it so that the MWI process isn't competing with users, then so much the better.
	 
	 
	--------------------------------------------------------------------------------
	Lelio Fulgenzi, B.A.
	Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
	(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
	...there's no such thing as a bad timbit...
	

		----- Original Message ----- 
		From: Lelio Fulgenzi <mailto:lelio at uoguelph.ca>  
		To: Melvin Fong <mailto:mfong at pacific.edu>  ; cisco-voip at puck.nether.net 
		Sent: Monday, January 29, 2007 4:39 PM
		Subject: Re: [cisco-voip] Unity Broadcast / private distribution list

		I don't think the delivery time is that big a deal. And someone told me because it is exchange, there's really only one copy of it. MWI is what takes time and ports.
		It also triggers a large number of people dialing in. There is a tool available that staggers MWI, but all we do is schedule it for delivery sometime just before or just after work. Lunch time is a good time as well since people are leaving and arriving back at their desks at various times.
		 
		Monitor your port usage and reassign as required (if you are using some as AA ports).
		 
		 
		--------------------------------------------------------------------------------
		Lelio Fulgenzi, B.A.
		Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
		(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
		^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
		...there's no such thing as a bad timbit...
		

			----- Original Message ----- 
			From: Melvin Fong <mailto:mfong at pacific.edu>  
			To: cisco-voip at puck.nether.net 
			Sent: Monday, January 29, 2007 4:21 PM
			Subject: [cisco-voip] Unity Broadcast / private distribution list

			Does anyone know where I can find documentation for how long it would
			take to send out a broadcast or private distribution message on a system
			with about 2k users. I know that it would depend on people accessing
			system leaving/getting messages.  I need some numbers to give our risk
			management.   Thanks
			_______________________________________________
			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/20070129/89d4d600/attachment.html