Determining Our Needs
Now that we have examined some of the options, we need to determine what our needs are. Requirements will vary quite a bit from site to site. Something to keep in mind is that, although the previous choices are distinct, they can be mixed in an Asterisk installation. We can have VoIP providers and POTS lines, as well as a PRI if we desire. It's very common to have this type of setup. For example, if we have an office in another country, we can call them using VoIP but all local calls could use POTS. It is important to understand the calls our system will be making and where they will be going, so that we can arrange for the necessary services and ensure that the calls are routed accordingly. If we have an existing telephony system, we can take a look at the calls it's making just now and our current costs so that we can determine what technologies will be of most use to our system's users.
Now is the time to begin documenting what our plan is. If Asterisk is to replace an existing system, then we should start by writing down all the current lines coming into our incumbent PBX. Once that is done, we need to look at our requirements.
First, we need to determine how many lines are needed. Telephone providers can generate a usage report that will tell us the maximum concurrent connections we have experienced in the last month. While they are able to do this, many providers are not very happy to run such a report. However, without that information we have nothing to gauge our needs other than gut feelings.
If we need more channels than we have, someone will get a busy/congested signal. Therefore, we should plan to have the maximum number of channels we have used plus a reasonable cushion. 125 percent of our current maximum is usually a reasonable cushion, this allows for instant 20-25 percent growth so that we can accommodate a sudden increase in calls without the system failing over, causing busy signals. If we do increase calling to this level for a relatively long period, we must consider an increase in lines to prevent congestion. These numbers are a guideline and they can change depending on circumstances. In a call center where the main business purpose is to make and receive calls, 150 percent may be a more satisfactory figure. We also should take into account the time it takes to get new lines set up from our local operator. If a significant event that generates a large number of calls occurs, we should have the capacity to handle this or be able to increase the capacity quickly.
Now that we have a number of lines, we need to determine the technology to use for each line. VoIP is usually the cheapest, especially for long-distance calls. PRI is usually the most reliable, and for incoming calls is often cheaper than VoIP.
While pricing the options, we need to remember that POTS lines usually have a single phone number only, while a PRI can have hundreds of phone numbers. If we are a business that receives only a few calls, but needs the calls to have different phone numbers, then a PRI probably makes the most sense. Also, with a PRI we can trunk more effectively, which may become essential.
Although a PRI can have hundreds of phone numbers, there is a charge for each number each month. Called DID (Directed Inward Dialing) numbers, these virtual numbers are usually sold in blocks of 10-20. If we do not order enough to begin with, it is usually not difficult to get new DIDs ordered. Often they can be available the same week, depending on the phone company. We assign these numbers to individual devices or groups of devices ourselves, once we have them allocated.
This means we can decommission or reallocate numbers as necessary. We may have campaign DIDs that are reassigned to different groups depending on the current campaign, personal DIDs for key staff, or our main DID, which would probably be assigned to a group of people responsible for handling these calls.
We should take this opportunity to write down what lines we want, what phone numbers we need, and get quotes if it differs from the currently installed PSTN connections.
No comments:
Post a Comment