A customer admin must be assigned to the project to work with the ScopServ Project Manager. This admin will be responsible for the following:
Extension List with names, physical locations, DID's, email addresses (please
identify who will get a voicemail box and who will not) must be provided by the Customer contact.
Phone Line due dates and circuit
numbers and point of contact with telephone carrier
If <Insert Name Here> is not
purchasing or porting lines to ScopServ then ScopServ is not responsible
for ordering or provisioning new or existing PSTN lines and due dates must
be managed by the customer. ScopServ will provide
technical advice regarding line provisioning upon request.
If the End User is purchasing
or porting lines to ScopServ, then ScopServ will require a copy of the latest customer invoice from the existing carrier and authorization to port or out any
existing phone numbers. Portability orders typically take 5 business days to implement.
A cutover date must be agreed upon between the ScopServ representative and
the Customer’s administrator.
DID numbers and call routing
information
Floor plan with names and extension
numbers identified on the plans
Any special requirements for the
phone system like ACD information or other desired applications as in IVR
with written scripts to pre-record IVR prompts before the cutover.
Customer will need to provide IP
information for the new phone system:
Will
a voice VLAN be required? If yes then the following applies
Static
IP LAN address for each VLAN on managed switches
Static
IP LAN address for data VLAN (VLAN 1)
Static
IP LAN addresses for voice VLAN will be assigned during installation (VLAN 20).
Proposed subnet 172.16.12.0 255.255.252.0 (host range 172.16.12.1=>172.16.12.15.254)
Subnet
mask for private and public IP addresses
Default
gateway for private and public IP addresses
Static
route information for private and public IP addresses
Fully qualified domain name for ScopTEL
server
FQDN
added to both public and private DNS A Records
DNS server information
Mail server IP address and fully
qualified domain name of mail server
MX record must exist for customer’s
email domain
Existing network topology diagram
The customer will need to configure
DHCP scope option 66 on their DHCP server to point to the ScopTEL IP
address (this is the TFTP option and it is required to provision the IP
phones).Option 66 Example: http://<ip address of server>:5555/tftpboot/
If the ScopTEL server will be installed on Customer Premises and a third party firewall will be implemented then firewall ports must be forwarded from any third party firewall to
the phone system IP address. ScopServ will not be
responsible any for third party firewall configuration. Any SIP ALG's enabled on the firewall must be disabled and UDP Timeouts must be configured to the firewall's maximum value (typically 1800 seconds).
| 22/tcp |
SSH |
| 5555/tcp |
GUI |
| 5060/udp |
SIP signalling |
| 5061/tcp |
SIP signalling |
| 10000-20000/udp |
SIP RTP |
| 4569/udp |
IAX2 protocol |
| 123/udp |
NTP protocol |
The existing router will also need
new routes to be configured to reach the new voice VLAN. ScopServ will not be responsible for third party router configuration.
If ITSP VoIP trunking or remote IP
phones will be used the server will require a dedicated public IP address
and Internet connection to ensure an appropriate MOS. The bandwidth
requirements for this link must be determined by the number of
simultaneous speech path requirements.
ScopServ will also need to set up
training dates for Customer staff prior to the cutover.