Personnel

Contact Person: Rob Tuck
Software Development: Rob Tuck
Hardware Development: Rick Crispin

Schedule for Voicemail -> email interface

This section of the schedule pertains only to providing voicemail to email capabilities to faculty and students. This is an initial stage of the internal VOIP-based extension system scheduled for deployment by September 2007.

9/15/06: Decide if T1 is "possible"
9/15/06: select digium cards
10/6/06: spec, order, and install Asterisk server (est. cost $2000)
10/13/06: install Asterisk software and student voicemail extensions
1. extensions need to be established
2. user instructions needed
3. maintainer instructions needed
4. Asterisk cards needed to support at least 3 lines
10/20/06: install faculty voicemail extensions
1. extensions need to be established
2. user instructions needed
3. maintainer instructions needed
4. Asterisk cards needed to support one additional line lines
10/27/06: student voicemail testing complete
1. student centrex phones disconnected
2. set message with verizon
3. update RU data
10/27/06: install 5-10 faculty/staff VOIP phones for alpha test
11/10/06: faculty voicemail testing complete
1. faculty centrex phones disconnected
2. set message with verizon
3. update RU data

Costs

We need to keep track of all costs requiired and savings obtained to establish this new phone service.

Billing

We need to couple the Asterisk records to the SAS billing info. This requires serious software development and constrains when a full internal VOIP will be ready.

Notes

Establishing voicemail -> email is being done at a much faster pace than anticipated. Other commitments may need to be reduced.

The initial test setup should use a dedicated set of 4 lines in a hunt group to handle student/faculty voicemail (6450 -> 6451 -> 0592 -> 2685). The last line (2685) will always be busy. Peak student and faculty use must be measured as well as the number of callers who get a busy signal. The last number in the group of four will allow us to keep track of how many calls are refused by a three line service - the fourth line is only for data collection. Acceptable rejection rates (e.g., 1%, 5%, 10%) need to be established rejection rates need to be monitored and reported.

VOIP phones must be able to run on the same connection network as a work station.

Initial test for "typical" VOIP will use four lines in a dedicated hunt group (6430 -> 3167 -> 2558 -> 4787). Unlike the voicemail setup all lines will be availalbe. We need to keep call records but will not be able to record rejection rates since there is no "always-busy" line at the end of the hunt group.

Student extensions

Each student gets a dedicated extension
It remains the same during their stay at Rutgers
All student numbers will begin with a 9
- only Loree phones begin with a 9 (9343 and 9347)
- a possible extension format is 9yab
  - y is the last digit of the year they enter
  - ab is arbitrary - conflicts need to be checked.

Faculty and staff keep their extensions

The last four digits of their current phone number willbecome their extension

Logistics of phone line location

all calls will ultimately go through 445-2001
initially call forwarding will be used to make that number to ring in Core

Logistics of voice mail

How long should voice mail be kept - 1 month?
Should we have a quota on voice mail - 1 GB?

Attendant protocols

we need to record a voice with instructions
enter the extension
spell the last name
contact the operator - what to ring (2001?)

Open Issues

Virtual phones?

Incoming caller ID

Outgoing caller ID

Private list of all cell phone numbers

POE: power over ethernet

Known Problems

OTRS queue is needed
Voice mail playback is garbled using VOIP phone
call is delayed 2-3 rings compared to partner system
Echo on VOIP phones
- 9/26/06: does not affect VOIP/VOIP calls, only affects VOIP/POTS calls.
- 9/26/06: tuning Asterisk software makes significant improvement
auto attendant not present, spelling name fails, 0 doesn't go to operator
- 9/26/06: # to invoked attendent disabled