[cisco-voip] Help:Proposing hardware, software and licesnsing

[James Buchanan]

Hello,

 

For 3), you will need DLUs (device licenses). 

For 4), don't forward to configure this with voice code and DSPs.

For 5), I'd stay far away from the CE-500 switches. The CPU utilization
goes through the roof when under load.

For IPCC Express, you will need an additional MCS.

As far as Unity versus Unity Connection, it really depends upon the
number of mailboxes and depends on whether or not you need to integrate
with Microsoft Exchange or Domino for unified messaging. If you do not
have this need, Unity Connection is the way to go.

 

Of course, this is without any knowledge of the number of phones needed
for your organization.

 

Thanks,

 

James

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Syed Khalid Ali
Sent: Friday, July 25, 2008 2:55 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Help:Proposing hardware, software and licesnsing

 

Hi,
 
Luckily I have been asked by my manager to propose harware, software and
licenses for an IPT solution.
 
Need suggestions on the list below that I have come up with:
 
1- MCS 7816-H3 Appliance with CCM 6.1 x 2
2- Cisco 2851 with SRST x 1
3- Cisco 7940/1 and 7911 IP phones
4- Cisco 2811 with 4-port FXO  x 2 (for initial setup, later they will
move to PRIs)
5- Catalyst 3560 or 2960 or CE-500/520 PoE switches (whatever comes in
budget)
6- VG224 for Analog Phones
 
a- Now what else I am missing in the licensing part. 
 
b- For IPCC exress 5.0+, will I need an additional MCS.
 
c- Should I go with Unity or Unity Connection.
 
d- Any thing else that I missed!
 
 
Regards,
 
Khalid 
 
 
 
 
 
 
 

________________________________

Explore the seven wonders of the world Learn more!
<http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBR
E> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080725/8ae81eb2/attachment.html>