<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I would have to agree with Grey Man, a pilot project is one way to
start up.<br>
<br>
I would also seriously recommend buying some consulting time from an <br>
experienced Asterisk PBX vendor/dealer/consultant.<br>
<br>
The cost is negligible in light of the scope of your project.<br>
<br>
A pilot project will only give you a glimpse of what is required.<br>
<br>
You have to have a design that incorporates your eventual build out.<br>
A pilot by itself is not going to give you that. You will need help from<br>
a source that can bring their experience to help you tip toe around the<br>
potential land mines you can encounter.<br>
<br>
regards,<br>
<br>
John Signorello<br>
Managing Partner<br>
ispbx.com<br>
866 GO ISPBX<br>
<br>
Grey Man wrote:
<blockquote
cite="mid:3dd5666c0805140600ic9fcc1bke2f63a73c2a736a7@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, May 13, 2008 at 12:17 PM, Matthew Ratliff
<a class="moz-txt-link-rfc2396E" href="mailto:mratliff@nauticalthinking.com"><mratliff@nauticalthinking.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'll be doing a new Asterisk deployment soon, and would like to gather your thoughts.
Here are some items that need to be kept in mind:
Support 800 phones (400 of which are analog)
Concurrent calls ... ? but need to guess high so that the server can handle this.
Voicemail will be required along with sending voice mail attachments to email server.
Flash panel for switchboard operator.
Needs to be a distributed server design for redundancy and fail-over.
Will need to be integrated into an existing PBX until each building is switched over to use the Asterisk servers.
If calling 911 from a building among multiple buildings, how can EMS find that person based upon the call?
What type of data line should be used in this setup? T1?
The physical network will support QOS and the like, so that is not an issue.
What type of design/setup do you recommend for this? How about server resources...ie...CPU, RAM, Disk space.
How about backups? Does imaging work best if a server were to fail?
Any thing else you can think of?
</pre>
</blockquote>
<pre wrap=""><!---->
If this is a project for your work and it's your first Asterisk
deployment then definitely don't go the big bang approach in the way
you've outlined. If you do you could well be out of that job in 6
months!
The first thing I'd recommend you do is find 10 or 20 people who are
suitable as early adopters. The set up a single Asterisk server and
give the early adopters a SIP phone each thats in addition to their
normal desk phone and ask them to see how they go using the SIP phones
for calls to each other, external calls and whatever else would make
sense. Then 6 months and a lot of learning/experience/frustration
later you'll know whether to get answers to your original questions or
not.
Regards,
Greyman.
_______________________________________________
-- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a>
</pre>
</blockquote>
</body>
</html>