Module-LAB-ScopTEL-System-Networking-LAB
System Networking Lab – Table 1
In
this diagram each system operates independently to supply network
services to the phones on its LAN interface. The phones are powered by a
Power over Ethernet switch.
|
Hostname
|
WAN address
|
LAN address
|
DNS Server
|
Ext Prefix
|
Site Prefix
|
Firewall Mode
|
|
1000.scopserv.local
|
192.168.100.1/24
|
172.16.1.1/16
|
172.16.1.1
|
1XXX
|
801
|
Gateway/Firewall
|
|
2000.scopserv.local
|
192.168.100.2/24
|
172.16.2.1/16
|
172.16.2.1
|
2XXX
|
802
|
Gateway/Firewall
|
|
3000.scopserv.local
|
192.168.100.3/24
|
172.16.3.1/16
|
172.16.3.1
|
3XXX
|
803
|
Gateway/Firewall
|
|
4000.scopserv.local
|
192.168.100.4/24
|
172.16.4.1/16
|
172.16.4.1
|
4XXX
|
804
|
Gateway/Firewall
|
|
5000.scopserv.local
|
192.168.100.5/24
|
172.16.5.1/16
|
172.16.5.1
|
5XXX
|
805
|
Gateway/Firewall
|
|
6000.scopserv.local
|
192.168.100.6/24
|
172.16.6.1/16
|
172.16.6.1
|
6XXX
|
806
|
Gateway/Firewall
|
The WAN ports are plugged into a switch so they can communicate
over a Layer 2 network so there is no need to route between subnets
Each system operates in Gateway/Firewall mode in order to NAT each
systems LAN to each WAN interface
The NAT option allows each system to provide DHCP on each phone
subnet to simplify configuration
Each system listens on both interfaces for VoIP traffic using the built
in SBC (Session Border Controller)
The network and dial plans must be built in order to route VoIP traffic
between system extensions
Each system has a unique Site Prefix in order steer VoIP traffic to each
fully qualified host name
Incoming calls will have the Site Prefix added to CLID on ingress to
make a callback easier
Console – nmtui
If there is no DHCP server on the network the server will not get an IP address.
Using the command ‘nmtui’ omitting any quotes an IP address can be set statically and then used to login to the GUI.
Use the tab key on the keyboard to select Edit a connection
Use the tab key on the keyboard to select the desired interface and press Enter
Use the tab key and keyboard arrows on the keyboard to select elements.
The Default is Automatic (DHCP)
To edit this connection Tab to <Automatic> and press Enter
Tab to Manual and press Enter
Keep using the keyboard to enter any static configurations, then tab or use arrows to select OK and press Enter
After pressing Enter use the <Back> button to exit nmtui
Console – service network restart
From the root prompt type ‘service network restart’ omitting any quotes to restart the network with the new static IP address.
GUI|Login
Using the IP address of the server and the default management port :5555 login to the server using an Internet Browser
Example:
The default admin username is 'admin'
The default admin password is 'admin'
On your first login you will be required to change the default admin password.
Server Module – Configuration Wizard
Since each system is a new install after the first admin login you will be prompted to run the ScopServ Initial Server Configuration Wizard.
Before proceeding make sure you have your server’s serial number handy so you can activate all of the menus and proceed with the configuration wizard.
If you have the serial number proceed with the wizard by pressing Next.
Server Module – EULA
By clicking on Next on the EULA page you are agreeing to the terms of the ScopServ End User License Agreement.
Server Module – Listen Port
The default GUI listening port is 5555.
Proxy information can be entered if the required Internet connection uses a proxy.
To send voicemail or fax to email using a third party email server tick the ‘Smart Relay’ check box and fill in the credentials needed to connect to the external email server.
Click Next to proceed.
Server Module – Registration Details
Enter the Serial Number purchased from ScopServ and system details.
Click Next.
Server Module – Admin Password Change
In the field it is recommended to change the default admin password.
Since this is a lab environment leave the default password and click Next.
Server Module – NTP Server
Choose your Time Zone and check the box to sync time with an NTP time server.
Enter the IP or FQDN address of the NTP server.
Click Next.
Server Module – Network Configuration
Set the Fully Qualified Domain Name (FQDN) for the local system from the System Networking Lab – Table 1.
Set the network configuration as static for the local system using the information from the System Networking Lab – Table 1.
Set the DNS server information for the local system using the information from the System Networking Lab – Table 1.
NOTE: The system is a fully capable DNS server and can resolve
DNS for the network but a third party DNS server can also be used.
Press Next.Server Module – High Availability
Skip any required High Availability Settings.
Press Next.
Server Module – Firewall Type
You will set the Firewall configuration later.
Choose No Firewall.
Click Next.
Server Module – Locale
Choose the language type that best suits your country profile to set the local tones and cadences configuration that best suits your local telco.
The Server is behind NAT option is configured if the server is
behind a third party NAT router. This setting manipulates SIP traffic
to work behind the NAT router using the internal Session Border
Controller (SBC)
For each local system use the Hostname using the information from the System Networking Lab – Table 1
NOTE: If the server is behind NAT then ensure that any external
firewall port forwards the TCP/UDP ports to the static IP address of
the server.
Port examples:
5060-5061/tcp SIP signaling
10000-20000/udp SIP RTP traffic
4569/udp IAX2 signaling and RTP traffic
22/tcp SSH management
5555/tcp ScopTEL GUI
123/udp NTP
Server Module – Apply Changes and Reboot
Review changes and tick on Apply Changes.
Click Finish.
Reboot Server when prompted.
Network Configuration – Network Interfaces
On a new installation it may be necessary to add an eth1 interface in order to configure the WAN interface.
From the Configuration>Network>Interfaces tree check to see if both eth0 and eth1 interfaces already exist.
If the eth1 interface is already configured then from the Configuration>Network>Interfaces tree click on edit eth1.
If the eth1 interface is not configured, then from the Configuration>Network>Interfaces tree click on Add a new
Interface.
Network Configuration – WAN Interface
Substitute the IP address and subnet mask and MAC address for
the system you are working on using the information table on page 1.
When finished click Add or Save depending on whether you must add eth1 or it is already configured.Network Configuration – LAN Interface
In this example the eth0 configuration from the lab exercise system is 1000.scopserv.local and the eth0 LAN interface is 172.16.1.1/16.
Edit the eth0 interface and substitute the IP address and subnet mask
and MAC address for the system you are working on using the information
table.
When finished click on Save.
Network Configuration – Hostname
In this example the hostname configuration from the lab exercise system is 1000.scopserv.local and you will use the eth0 LAN address as the DNS server address which is also the DNS Server information from page 1.
Edit the default Hostname and when finished click on Save.
Network Configuration – Firewall Wizard
Click on each box listed to allow inbound traffic for each required service and click Next.
There is no need to deny any Outbound
Services in the lab so click on Next.
On the last step make sure to click on the the Apply Changes? [x] box and then click Finish to save the configuration.
Network Configuration – DNS Configuration Wizard
From the DNS tree click on Configuration
From the drop down list select the Wizard. Local Domain scopserv.local.
Click Next.Network Configuration – DNS Configuration Wizard
Enter a View Name in the text box that corresponds with the server in this network.
1000local was chosen for this system.
Click Next
Click a checkbox into Apply Changes and click Finish
Click Close.
Network Configuration – DNS A Records - Table 2
Each server has a unique Fully Qualified Host Name (FQDN) on the network.
Each server will communicate with the others by using DNS A records.
A DNS record for each other system needs to be entered into the default zone for each server on the network.
Use this table to enter each A record for other systems on this network.
Notice that each A record will resolve to the WAN address of each server. This is because each LAN address is behind NAT and will not be accessible by other servers.
|
A Record
|
IP address
|
Reverse DNS
|
|
1000.scopserv.local
|
192.168.100.1
|
1000.scopserv.local
|
|
2000.scopserv.local
|
192.168.100.2
|
2000.scopserv.local
|
|
3000.scopserv.local
|
192.168.100.3
|
3000.scopserv.local
|
|
4000.scopserv.local
|
192.168.100.4
|
4000.scopserv.local
|
|
5000.scopserv.local
|
192.168.100.5
|
5000.scopserv.local
|
|
6000.scopserv.local
|
192.168.100.6
|
6000.scopserv.local
|
Network Configuration – DNS Zone Configuration
Click on Zones.
Edit the scopserv.local zone.
Choose Record Type IPv4 Address (A).
Enter the Host name.
Enter the IPv4 address.
Make sure to use the data from the DNS A Records Table for each system.Network Configuration – DNS A Record Configuration
NOTE that the default A record for the local system is already created by the DNS Configuration Wizard and uses the LAN address of the server.
Make sure each other A record is configured before proceeding to the next module.
Network Configuration – DHCP Subnet – Table 3
Use this table to create the DHCP server configuration for each system on the network.
Note that each scope belongs to a class B subnet so it can service more than 254 IP addresses. In real scenarios a larger subnet might be necessary to provide DHCP to thousands of IP phones.
The Default Gateway belongs to the LAN address of each server so the DHCP client will NAT outbound to reach subnets that are not local.
Primary DNS is the local server which is configured with A records for each other server.
The TFTP server for each subnet is the LAN address of the local server which will use the Automatic Provisioning System to manage the configuration files for each IP Phone.
The NTP server for each subnet is the LAN address of the local server and the local server will act as a Network Time Protocol (NTP) server on each local subnet.
Edit the default DHCP Server configuration.
Network Configuration – DHCP Subnet Configuration
Enable the DHCP Server.
Check Dynamically update the DNS Server? [x].
Choose the Domain DNS Zone scopserv.local from the dropdown list.
Click Save when done.
Click on Add to add a new subnet
Select Interface LAN from the dropdown list.
Using the DHCP table enter the Start and End IP address and Gateway information for the local server.
When done click on the DNS Configuration tab.
Enter scopserv.local into the Domain Name field.
Using the DHCP table enter the LAN address of the local server.
When done click on the DHCP Options tab.
Using the DHCP table enter the FQDN of the local server into the TFTP Server Name and Time Server (NTP) fields.
Enter -18000 (GMT-5) into the Time Offset (in seconds) field to
configure the DHCP clients into time zone EST (or applicable time zone).
When done click on Add.
Network Configuration – General Services Startup
From the tab General>Bootup Services click on Edit and put a checkbox next to Network, Firewall, DHCP Server, DNS Server.
Apply Change when done.
Network Configuration – Network Commit
Server Configuration – Date and Time Configuration
From the Server menu Edit the Date and Time Configuration.
Check the box to Use Time Server (NTP)? [x].
Choose the Time Zone applicable for your Time Zone (America/Montreal in this example).
Click on the Time Server tab when done.
Check the box to Act as a Time Server?[x]
Enter time.nrc.ca as the Primary Server
Enter Allowed Network 172.16.0.0/16 for each server on the network to allow NTP requests from any client on this subnet
Click Save when done
Server Configuration – Server Bootup Services
From the tab Server Bootup Services Edit the Bootup Services and check the option to start all services as shown in this example.
Click Apply Change when done.
Network Configuration – Reboot Server
From the tab Server>General click on Reboot Server to apply and start all services.
Telephony Configuration – Pre-Requisites
Objects like telephony extensions, Class of Service, and Outgoing Lines require that other objects exist before they can be properly and efficiently configured. Configuring these objects in the correct sequence will make first time installation much more efficient and promote a better understanding of each object’s intended function. It is best practice not to use Upper Case characters or Special characters when entering object names.
Here is a basic checklist to perform when setting up a new server for the first time:
Edit Telephony Modules
Edit Feature Codes
Commit
Edit Services Startup
Interfaces Card Detect (optional but at least one physical interface must exist in order to provide a DAHDI timing source for Asterisk)
Create Interfaces
Create Incoming lines
Create Outgoing Line(s)
Verify Class of Service objects
Security Settings
Create Extensions
Commit and Services Restart
Telephony Configuration – Edit Telephony Modules
It is essential that pre-requisite modules be enabled prior to anything being configured on the server. This is to ensure that only required VoIP protocols and PSTN hardware modules are loaded during startup.
Edit and save the values for tab Configuration>Telephony>Configuration>Telephony Modules.
After saving Commit all changes
|
Include all default values
Analog Interfaces (DAHDIl)
Digital Interfaces (DAHDI)
SIP Channels
IAX Channels
Virtual Fax
Emergency Lines
Queues and Agents
Conferences
IVR Report/Logging
Scheduler
Asterisk Manager
Jabber (XMPP) Channels
T.38 Fax (UDPTL)
PassthroughServer Module – Telephony 2.5 Version Switcher
Telephony version 2.5 and Asterisk 1.8 are required for the latest features and support.
The Version Switcher easily switches between various releases.
From the tab Server>Packages Manager>Versions Information.
Click to Toggle Version to scopserv-telephony25.
Click to Commit changes.
Telephony Module – Edit Services
You must enable the services you require.
Typically all services are enabled.
Click on Edit Services to select the required services on boot.Telephony Module – Edit Services
Click each checkbox to enable Start at bootup.
Apply Change when done.
Telephony Module – SIP VoIP Interfaces – Table 4
For each system create each other dynamic SIP VoIP Interface so a Specific friend can register to this system.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server Username
|
Server
Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
1000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
802to801
|
802to801
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
803to801
|
803to801
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
804to801
|
804to801
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
805to801
|
805to801
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
806to801
|
806to801
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
For each system create each other Specific SIP VoIP Interface to register to the Dynamic friend.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server
Username
|
Server Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
1000.scopserv.local
|
2000.scopserv.local
|
Specific
|
801to802
|
801to802
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
3000.scopserv.local
|
Specific
|
801to803
|
801to803
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
4000.scopserv.local
|
Specific
|
801to804
|
801to804
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
5000.scopserv.local
|
Specific
|
801to805
|
801to805
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
1000.scopserv.local
|
6000.scopserv.local
|
Specific
|
801to806
|
801to806
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
Telephony Module – SIP VoIP Interfaces – Table 5
For each system create each other dynamic SIP VoIP Interface so a Specific friend can register to this system.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server Username
|
Server
Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
2000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
801to802
|
801to802
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
803to802
|
803to802
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
804to802
|
804to802
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
805to802
|
805to802
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
806to802
|
806to802
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
For each system create each other Specific SIP VoIP Interface to register to the Dynamic friend.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server
Username
|
Server Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
2000.scopserv.local
|
1000.scopserv.local
|
Specific
|
802to801
|
802to801
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
3000.scopserv.local
|
Specific
|
802to803
|
802to803
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
4000.scopserv.local
|
Specific
|
802to804
|
802to804
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
5000.scopserv.local
|
Specific
|
802to805
|
802to805
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
2000.scopserv.local
|
6000.scopserv.local
|
Specific
|
802to806
|
802to806
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
Telephony Module – SIP VoIP Interfaces – Table 6
For each system create each other dynamic SIP VoIP Interface so a Specific friend can register to this system.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server Username
|
Server
Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
3000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
801to803
|
801to803
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
802to803
|
802to803
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
804to803
|
804to803
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
805to803
|
805to803
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
806to803
|
806to803
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
For each system create each other Specific SIP VoIP Interface to register to the Dynamic friend.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server
Username
|
Server Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
3000.scopserv.local
|
1000.scopserv.local
|
Specific
|
803to801
|
803to801
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
2000.scopserv.local
|
Specific
|
803to802
|
803to802
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
4000.scopserv.local
|
Specific
|
803to804
|
803to804
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
5000.scopserv.local
|
Specific
|
803to805
|
803to805
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
3000.scopserv.local
|
6000.scopserv.local
|
Specific
|
803to806
|
803to806
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
Telephony Module – SIP VoIP Interfaces – Table 7
For each system create each other dynamic SIP VoIP Interface so a Specific friend can register to this system.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server Username
|
Server
Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
4000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
801to804
|
801to804
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
802to804
|
802to804
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
803to804
|
803to804
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
805to804
|
805to804
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
806to804
|
806to804
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
For each system create each other Specific SIP VoIP Interface to register to the Dynamic friend.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server
Username
|
Server Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
4000.scopserv.local
|
1000.scopserv.local
|
Specific
|
804to801
|
804to801
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
2000.scopserv.local
|
Specific
|
804to802
|
804to802
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
3000.scopserv.local
|
Specific
|
804to803
|
804to803
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
5000.scopserv.local
|
Specific
|
804to805
|
804to805
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
4000.scopserv.local
|
6000.scopserv.local
|
Specific
|
804to806
|
804to806
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
Telephony Module – SIP VoIP Interfaces – Table 8
For each system create each other dynamic SIP VoIP Interface so a Specific friend can register to this system.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server Username
|
Server
Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
5000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
801to805
|
801to805
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
802to805
|
802to805
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
803to805
|
803to805
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
804to805
|
804to805
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
806to805
|
806to805
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
For each system create each other Specific SIP VoIP Interface to register to the Dynamic friend.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server
Username
|
Server Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
5000.scopserv.local
|
1000.scopserv.local
|
Specific
|
805to801
|
805to801
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
2000.scopserv.local
|
Specific
|
805to802
|
805to802
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
3000.scopserv.local
|
Specific
|
805to803
|
805to803
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
4000.scopserv.local
|
Specific
|
805to804
|
805to804
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
5000.scopserv.local
|
6000.scopserv.local
|
Specific
|
805to806
|
805to806
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
Telephony Module – SIP VoIP Interfaces – Table 9
For each system create each other dynamic SIP VoIP Interface so a Specific friend can register to this system.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server Username
|
Server
Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
6000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
801to806
|
801to806
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
802to806
|
802to806
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
803to806
|
803to806
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
804to806
|
804to806
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
NA Specific Registers to Dynamic
|
Dynamic
|
805to806
|
805to806
|
Sc0pS3rv
|
FALSE
|
TRUE
|
DEFAULT
|
Friend
|
For each system create each other Specific SIP VoIP Interface to register to the Dynamic friend.
|
System
|
Default Host/IP
|
Host Mode
|
General
Username
|
Server
Username
|
Server Password
|
Register As user Agent
|
Enable Proxy Settings
|
From User
|
Type
|
|
6000.scopserv.local
|
1000.scopserv.local
|
Specific
|
806to801
|
806to801
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
2000.scopserv.local
|
Specific
|
806to802
|
806to802
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
3000.scopserv.local
|
Specific
|
806to803
|
806to803
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
4000.scopserv.local
|
Specific
|
806to804
|
806to804
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
|
6000.scopserv.local
|
5000.scopserv.local
|
Specific
|
806to805
|
806to805
|
Sc0pS3rv
|
TRUE
|
TRUE
|
DEFAULT
|
Friend
|
Telephony Module – Add New VoIP Accounts
Click Add a new VoIP Account from Interfaces>VoIP Accounts
Telephony Module – Dynamic Host Mode VoIP Accounts
Create a dynamic SIP Friend for each server referencing SIP VoIP Interfaces – Table 4-9.
In this example you are configuring server 1000.scopserv.local with a Dynamic entry of 802to801 so the remote server 2000.scopserv.local can register to 1000.scopserv.local.
You will have to create a dynamic entry for all other systems on the network to allow registrations to this local server.
Type is SIP.
Trunk Type is Friend to allow calls in both directions.
Enter the remote Hostname into the Name field.
When done click on the Server tab.
This example shows the Server tab requirements for Host Mode Dynamic
Host Mode Dynamic sets the SIP registration credentials for other systems with VoIP accounts set to Host Mode specific to allow the remote system to register to this account.
Since we are not allowing only incoming registrations
. from a specific Host/IP the Default Host/IP can be left blank.
The default Port is 5060 and can be left blank.
The Enable Proxy Settings checkbox must be checked and the From User Default info will appear in the CLID of incoming calls.
The From User must be left at the Default setting
Click Add when done.Create a specific SIP Friend for each server referencing SIP VoIP Interfaces – Table 4-9.
This example shows the General tab requirements for Host Mode specific.
Host Mode specific sets the SIP registration credentials to
register to Host Mode Dynamic VoIP accounts on other servers in the
network.
Since we must register the local system 1000.scopserv.local to 2000.scopserv.local will use an account name of 801to802.
Type is SIP.
Trunk Type is Friend to allow calls in both directions.
When done click on the Server tab.This example shows the Server tab requirements for Host Mode Specific.
Host Mode Specific sets the SIP registration credentials to register to Host Mode Dynamic VoIP accounts on other servers in the network.
Since we must register 1000.scopserv.local to other servers a Specific VoIP account must be created for this local server
Enter the remote Hostname into the Host/IP field to route SIP registrations to the remote server
Register as User Agent must be checked
The default Port is 5060 and can be left blank
The Enable Proxy Settings checkbox must be checked and the From User Default info will appear in the CLID of incoming calls
The From User must be left at the Default setting
Click Add when done
Telephony Module – VoIP Interface Summary
This example shows the completed VoIP Interface section for server 1000.scopserv.local.
Data fill each other server with the information from the SIP VoIP Interfaces – Table 4-9.
Telephony Module – Dial Plan Summary
Custom Dial Plan Strings
|
X
|
matches any digit from 0-9
|
|
Z
|
matches any digit form 1-9
|
|
N
|
matches any digit from 2-9
|
|
[1237-9]
|
matches any digit or letter in the brackets (in this example, 1,2,3,7,8,9)
|
|
.
|
wildcard, matches one or more characters
|
|
!
Examples
|
wildcard, matches zero or more characters immediately
|
|
NXXXXXX
|
matches a normal 7 digit telephone number
|
|
1NXXNXXXXXX
|
matches an area code and phone number preceded by a one
|
|
9011.
|
matches any string of at least five characters that starts with 9011, but it does not match the four-character string 9011 itself.
|
|
#
|
matches a single # keypress
|
Telephony Module – Incoming Lines – Table 11
For each system create an Incoming Line from each other Trunk
|
System
|
Incoming Line Type
|
Extensions (Pattern)
|
Trunk
|
Options Schedule
|
Advanced Options Class of Service
|
CallerID Enable Presentation indicator
|
|
1000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
802to801
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
1000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
803to801
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
1000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
804to801
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
1000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
805to801
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
1000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
806to801
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
Telephony Module – Incoming Lines – Table 12
For each system create an Incoming Line from each other Trunk
|
System
|
Incoming Line Type
|
Extensions (Pattern)
|
Trunk
|
Options Schedule
|
Advanced Options Class of Service
|
CallerID Enable Presentation indicator
|
|
2000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
801to802
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
2000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
803to802
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
2000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
804to802
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
2000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
805to802
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
2000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
806to802
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
Telephony Module – Incoming Lines – Table 13
For each system create an Incoming Line from each other Trunk
|
System
|
Incoming Line Type
|
Extensions (Pattern)
|
Trunk
|
Options Schedule
|
Advanced Options Class of Service
|
CallerID Enable Presentation indicator
|
|
3000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
801to803
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
3000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
802to803
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
3000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
804to804
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
3000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
805to805
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
3000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
806to806
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
Telephony Module – Incoming Lines – Table 14
For each system create an Incoming Line from each other Trunk
|
System
|
Incoming Line Type
|
Extensions (Pattern)
|
Trunk
|
Options Schedule
|
Advanced Options Class of Service
|
CallerID Enable Presentation indicator
|
|
4000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
801to804
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
4000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
802to804
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
4000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
803to804
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
4000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
805to804
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
4000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
806to804
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
Telephony Module – Incoming Lines – Table 15
For each system create an Incoming Line from each other Trunk
|
System
|
Incoming Line Type
|
Extensions (Pattern)
|
Trunk
|
Options Schedule
|
Advanced Options Class of Service
|
CallerID Enable Presentation indicator
|
|
5000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
801to805
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
5000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
802to805
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
5000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
803to805
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
5000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
804to805
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
5000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
806to805
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
Telephony Module – Incoming Lines – Table 16
For each system create an Incoming Line from each other Trunk
|
System
|
Incoming Line Type
|
Extensions (Pattern)
|
Trunk
|
Options Schedule
|
Advanced Options Class of Service
|
CallerID Enable Presentation indicator
|
|
6000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
801to806
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
6000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
802to806
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
6000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
803to806
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
6000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
804to806
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
|
6000.scopserv.local
|
Map to Local Extension
|
[123456]XXX
|
805to806
|
default
|
System Default
|
Presentation Allowed, Not Screened
|
Telephony Module – Incoming Dial Plan
For each server a new Incoming Line must be built for each Dynamic VoIP Interface using the Incoming Lines Table 10-16.
An Extensions (Pattern) can be used to simplify incoming DNIS lookups if Type Map to Local Extensions is used.
Choose the incoming Dynamic trunk from the Trunk drop down list.
Click on the CallerID tab when you have configured the Type, Extensions (Pattern), Trunk.
Click on the CallerID tab when you have configured the Type, Extensions (Pattern), Trunk.
Enable Presentation indicator and choose Presentation Allowed, Not Screened from the drop down list.
Using the same Extensions (Pattern) keep adding Trunks until all incoming Dynamic Trunks have been added.
Telephony Module – Incoming Dial Plan Summary
Here is the Incoming Line summary for 1000.scopserv.local.
Telephony Module – Outgoing Line Dial Plan - Table 17
For each system create an Outgoing Line to each other system prefix and include each outgoing line in each extension's Class of Service
|
|
Telephony Module – Outgoing Line Dial Plan - Table 18
For each system create an Outgoing Line to each other system prefix and include each outgoing line in each extension's Class of Service
|
|
Telephony Module – Outgoing Line Dial Plan - Table 19
For each system create an Outgoing Line to each other system prefix and include each outgoing line in each extension's Class of Service
|
|
Telephony Module – Outgoing Line Dial Plan - Table 20
For each system create an Outgoing Line to each other system prefix and include each outgoing line in each extension's Class of Service
|
|
Telephony Module – Outgoing Line Dial Plan - Table 21
For each system create an Outgoing Line to each other system prefix and include each outgoing line in each extension's Class of Service
|
|
Telephony Module – Outgoing Line Dial Plan - Table 22
For each system create an Outgoing Line to each other system prefix and include each outgoing line in each extension's Class of Service
|
|
Telephony Module – Outgoing Lines Dial Plan Summary
An Outgoing Line for each remote server must be built for each local server based on the Outgoing Line Dial Plan – Table 17-22.
The Outgoing Line Custom Dial Plan determines which VoIP Interface to use by recognizing digits dialed to steer the call to the desired server.
For example when the digits dialed from system 1000.scopserv.local are 8022001 the server recognizes 802 as the prefix for the 801to802 VoIP Interface and passes 2001 to server 2000.scopserv.local. 2000.scopserv.local then matches the incoming digits 2001 to local extension 2001 causing the phone to ring.
The same rules remain true for any VoIP (SIP, IAX2, Skinny) or TDM (ISDN PRI) trunk that supports DNIS routing.
Here is the configured Outgoing Lines summary for 1000.scopserv.local.
Telephony Module – Outgoing Lines Dial Plan Configuration
Click Add a New Outgoing Line.
Give the Outgoing Line an alphanumeric name (no upper case or special characters).
Select the correct outgoing Trunk that matches the dial plan.
When done Click on the Dial String tab.
Choose Type Custom Dial String from the drop down list.
Since Dial Plans rely on X the Dial String includes the site prefix and the wild card upper case XXXX.
Number of digit to strip 3 strips the first 3 digits from the
outgoing call sending only the last 4 digits allowing the remote server
to do a dial plan lookup and steer the call to a matching extension
using the Incoming Lines Dial Plan.
When done click on the Dial Options tab and use the Outgoing
Line Dial Plan – Table 17-22. Note that the Dial Options are common for
each server.
When done Click Add.Telephony Module - Manager > Class of Service default
Newly installed 2.5 systems include all Outgoing Lines in the default Class of Service for all tenants.
You should check the Class of Service to make sure each newly created Outgoing Line is allowed for the Class of Service assigned to each extension.
Add a new Class if you need to create a custom Class of Service.
Telephony Module – Security
SIP Phones are SIP User Agents.
For security, SIP User Agents must register to the SIP Registrar via username and password authentication.
It is typical for the SIP protocol ports to be open or forwarded to the ScopTEL server if a third party Firewall is implemented.
When the SIP ports are exposed on the Firewall it is common for hackers to attempt brute force attacks on the server. Such attacks systematically request authentication using common dial plan Extensions and trivial passwords.
Examples of such brute force attacks:
Extension range 1000-3000
Systematic Password attempts using passwords 1000-3000
Systematic Password attempts using passwords 0000, 1234, 1111, 4321, 123456, 7654321
Therefore if a secure password policy is used it will prevent the overall majority of hackers from registering a SIP Extension or SIP Trunk with the server for fraudulent purposes.
Examples of secure SIP password policy
Minimum password length of 8 alpha numeric characters.
No Dictionary words
Minimum 2 Upper Case characters used
Minimum 2 numerals used
Passwords should be unique for each extension
The same policy enforcement should be in effect when configuring Voicemail Passwords except Voicemail Passwords cannot contain Alpha characters and must be numeric.
A poorly implemented Voicemail Password Policy can allow a hacker access to thru dial capabilities from a mailbox configured to allow outdial capabilities.
Therefore Voicemail Passwords must be strict regardless of inconvenience caused to end users.
Voicemail Password should never match the extension number. Example: Extension 100, Voicemail Password 100
Voicemail Password should never be trivial.
Examples: 0000, 1234, 1111, 4321, 123456, 7654321
Telephony Module – Security Here are the recommended Settings.
The SIP and IAX2 Password Policy is set independently of the Global Voicemail Password Policy.
If the Options to automatically fix invalid password?[x] is
checked then non-compliant passwords will be made compliant after a
commit (recommended).
Telephony Module – Extensions
Typical Extensions types are:
SIP Extension (IP Extension using the SIP protocol)
IAX2 Extension (IP Extension using the IAX2 protocol)
Zap Extension (analog FXS extension using Sangoma or Digium cards. Sangoma and Digium cards should not coexist in the same server)
Voicemail Extension (Voicemail box only)
HotDesk Extension
A HotDesk Extension is an Extension that logs into a physical Extension using the HotDesk Feture Code, HotDesk Extension number and required password.
By logging into a physical Extension the HotDesk Extension can make and receive calls from any extension which allows the HotDesk Feature Code in its assigned Class of Service. Caller ID incoming and outgoing will be automatically manipulated to display HotDesk user information.
Virtual Extension
A Virtual Extension is a very advanced Extension type which allows a user to login to the ScopTel GUI and use the Realtime Monitor and customize Call Detail Reports and other types of reports.
Advanced options can be configured to ring multiple destinations and automatically forward copies of voicemail messages to multiple extensions
User Options for Virtual Extensions include Follow Me, Camp-On, Personal IVR destinations
Custom Forwarding Rules can be defined for:
Call Forward Immediate • Call Forward Busy
Call Forward No Answer
Call Forward Unavailable (forward when physical extension is offline)
It is possible to Immediate Forward a Virtual Extension to make an Application available within an IVR context for inbound PSTN callers.
Ring Group Extension
A Ring Group Extension automatically Immediately Forward it’s calls to configured Follow Me destinations
Advanced options can be configured to ring multiple destinations and automatically forward copies of voicemail messages to multiple extensions
User Options for Virtual Extensions include Follow Me, Camp-On, Personal IVR destinations
Custom Forwarding Rules can be defined for:
Call Forward Immediate
Call Forward Busy
Call Forward No Answer
Call Forward Unavailable (forward when physical extension is offline)
It is possible to Immediate Forward a Virtual Extension to make an Application available within an IVR context for inbound PSTN callers.
Shared Extension
A Shared Extension can be configured so that multiple extensions can ring when the pilot DN is dialed but depending on the busy status of the extension(s) one or more extensions can ring but the busy extension will not ring
Telephony Module – Add Multiple Extensions Wizard
You can extensions manually or use the Add Multiple Extensions Wizard.
Add Multiple Extensions Wizard can also be used to create a single extension.
Click on Add Multiple Extensions.
Telephony Module – Add Multiple Extensions Wizard
Type is SIP.
Extension(s) create a range of 3 extension numbers applicable to the system you are configuring in the network.
In this example 1000.scopserv.local is being configured with extensions 1000, 1001, 1002.
Class of Service default.
No Phone Template is being used.
Click Next.Enable the Voicemail option.
Click Next.
Leave all the default values.
Click Next.
NOTE: Act as an Operator will ring any extension with this option checked when a caller dials 0 from a voicemail prompt. After you create all extensions edit one of the extensions and check this option to enable the Voicemail Operator.
Check off the following options (you will have to scroll down the active window for all options):
Enable Message Waiting Indicator (MWI).
Allow sender to hit 0 to reach operator.
Allow sender to review/re-record message before saving?
Allow to Compose a message.
Allow to Callback from Voicemail.
Leave all other options at default.
When done click Next.Phone Options.
The phones in the lab will not be behind NAT so leave unchecked. For example you would enable this option if the phone was being used by a telecommuter behind a NAT firewall. This setting enables SBC backend settings per extension.
Choose the options in the screenshot.
Do not click Next.
Do not click Next.
This is a continuation of Phone Options settings.
SIP Alert (Auto Answer/Distinctive Ring) options are checked to enable a
phone to receive an internal page. In this screenshot a Polycom phone
was selected from the Device drop down list and is configured to receive
incoming pages.
When done click Next.
User Options.
Enable Call Forward on No Answer Voicemail from
Do not click Next.
User Options continued.
Enable Incoming and Outgoing Calls using the On the drop down list. Demand Call Recording drop down list.
When done click Next.
User Informations
The Full Name is also used by the Voicemail IVR to lookup the
extension by name when a caller uses the Voicemail Directory feature.
Click Next when you have finished entering a name for each Extension.Check the Apply Changes box.
Click Finish.
Telephony Module – Commit Changes
From the Telephony General page click on Commit to write all the changes.
When the Commit is complete reboot the server.
Related Articles
Module 19 - ScopTEL IP PBX Software - Quality-of-Service-Training
The use of IP as a foundation for converged networks has raised several issues for both enterprise IT departments and ISPs. IP and Ethernet are connectionless technologies and do not guarantee bandwidth. The protocol will not differentiate network ...Module 23 - ScopTEL - Configuring LDAP and Directories
Background and Pre-Requisites Minimum package version scopserv-server-6.20.0.0.20210211-1.nodist.scopserv.noarch Supported Handsets: Yealink, Polycom (version 3+ firmware), Snom What is LDAP ? LDAP (Lightweight Directory Access Protocol) as its name ...Module 4 - ScopTEL IP PBX Software - PSTN Interfaces and Gateways
Gateways A VoIP gateway is as a bridge between: Interfaces: (T1/E1, FXO, FXS) Protocols: SIP, Cisco SCCP/Skinny, MGCP (legacy protocol), and H.323 (legacy protocol) CODECS (media): GSM (13 Kbps), iLBC (15 Kbps), G.711 (64 Kbps), G.722 (48/56/64 ...General-Presentation-ScopTEL-ENGLISH
ScopServ – The Company ScopServ is a Canadian firm founded in 2004, specializing in information technology. It designs high-end corporate applications and holds the intellectual property rights for its products and solutions. A strong actor in ...Module 14 - ScopTEL IP PBX Software - Managing ACD
Automatic Call Distribution (ACD) | Background Automatic Call Distribution queues put callers into a queue and typically play Music on Hold or custom announcement messages to keep them informed or relaxed while they wait for an agent to become ...