UC Series User Manual (For Version 1.x)
1 Overview
1.1 Introduction
The UC300 series delivers a multi-functional business office telephony system designed for small to medium enterprises. The series integrates functions such as IP phone, fax, and voice recording, and is compatible with multiple service platforms such as Cisco CallManager, Broadsoft, Huawei IMS and Asterisk, and terminals. The products are highly reliable, easy to install and deploy, and offer a brand-new experience in mobile offices and communications.
The UC300 delivers a full-featured IP Telephony solution. By supporting intelligent communication functions such as mobile phone extensions, instant multi-party conferences, call history, click-to-dial, and customer information management, it not only facilitates seamless communication between enterprise employees and customers, but also provides a solid basis for enterprises to analyze core business data.
1.1.1Features
Specification
Item | Description |
System Capacity | Up to 800 extension registers 100 concurrent calls with G.729 codec 300 concurrent calls with G.711 codec |
Network Interface | 1×10/100M LAN port |
USB Port | 1×USB 2.0 for external storage or disaster recovery system |
External Storage | 1×SD slot, support up to 128G |
Telephony Interface | FXS/FXO interface, Optional |
RAM | DDR3 1GB |
Storage | 16GB Onboard Flash |
Power Consumption | 12V/0.8A 9.6W Maximum |
Failover Function | 4 FXO +1FXS or 1FXO+1FXS model |
PBX
- Supported codecs: ADPCM, G.711(A-Law & u-Law), G.722, G.723.1(pass through),G.726, G.729,GSM, iLBC(optional) among others.
- Support for analog interfaces such as FXS/FXO(PSTN/POTS)
- SIP and IAX2 support
- Incoming and outgoing routes with support for dial pattern matching
- Hardware detection interface
- Support for paging and intercom
- Web-based operator panel
- DISA(Direct Inward System Access)
- Call detail record(CDR) report
- Billing and consumption report
- Distributed DialPlan with dundi
- Call recording, Call parking, call queues, Voicemail, Conference
- Echo canceller
- Callback support
- Flexible and configurable IVR
- Support for PIN sets
- Support for time conditions
- VoIP provider configuration
- Support for follow-me
- Support for ring group
- Support for video-phones
- Channel usage reports
Email - Mail server with multi-domain support
- Based in Postfix for high email volume
- Remote SMTP Module
- Web based email client
- Support for quotas
- Antispam support
- Support for mail relay
- Email list management
FAX - Fax to email application
- Fax visor with downloaded PDFs
- Can be integrated with Winprint Hylafax
- Fax send through Web Interface
- Fax to email customization
- Access control for fax client
General - System resources monitor
- Backup Restore Validation
- Network configurator
- Heartbeat Module
- Configurable server date, time and timezone
- Backup/restore support via Web
- Automatic Backup Restore
- Server shutdown from the web
- DHCP server for dynamic IP
- Access control to the interface based on ACLs
1.1.2 Model
UC300 series supports multiple models with varying amounts of FXO ports and FXS ports, as shown in the Table 1-1-1.
Table 1-1-1 product models
Mode | Network port | FXO Ports | FXS Ports | USB | SD |
UC300-A11EM1 | 1 x 10/100M Ethernet | 1 | 1 | 1 | 1 |
UC300-A41EM1 | 1 x 10/100M Ethernet | 4 | 1 | 1 | 1 |
1.1.3Appearance
Figure 1-1-1UC300-A11EM1 front panel
Figure 1-1-2 UC300-A11EM1 back panel
Figure 1-1-3 UC300-A14EM1 front panel
Figure 1-1-4UC300-A14EM1 back panel
Table 1-1-2LED description
LED Label | Function | Status | Indication | |
PWR | Power Status | Slow blinking (Green 1s and Flash 1s) | Starting up | |
Off | Power off | |||
RUN | System Status | Keep Blinking(Green 2s and Flash 0.1s) | Work normally | |
Off | System failure | |||
Fast blinking (Green 0.1s and Flash 0.1s) | Work abnormally | |||
Blinking(Green 0.3s and Flash 0.3s) | Factory Reset | |||
LAN | LAN Data Status | On | Connected but no data transmitting | |
Blink | Data transmitting | |||
Off | Disconnected | |||
1-4 ( SLOT 1/2 ) | SLOT 1/2 Status | FXS / FXO | Green | Channel available |
Off | Channel failure |
1.2 Physical
Weight: 530g
Size: 130*130*40mm
Operating Temperature: 0 °C ~40 °C
Storage Temperature: -20 °C ~ 65 °C
Humidity: 10~90% Non-Condensing
1.3 Compatible Endpoints
l Any SIP compatible IP Phone (Desktop Phones and Soft Phones for Windows, Linux, iOS and also Android platforms). Desktop phone examples include: CooFone Series IP Phones provided by OpenVox, and also Cisco, Grandstream, Yealink, Polycom, Snom, Akuvox, Escene, Favil, HTek etc. Soft Phone examples include 3CX, CooCall, Linphone, X-Lite, Zoiper etc.
l IAX compatible endpoints, for example, CooFone IP Phones provided by OpenVox and also Zoiper softphone.
l Analog Phones and Fax Machines
l Web Extensions (WebRTC)
1.4 Log in to the Web GUI
Step 1 Use a CAT5 cable to connect the device to the local network where the PC is connected, or connect the device directly to the PC.
Step 2 Dial “**89” to obtain device IP address by an analog telephone, the device defaults to a fixed IP address: 172.16.101.1
Step 3 Make sure that the PC and the device are on the same network segment.
Step 4 Enter the device IP address in the browser address bar (e.g. 192.168.2.218);
Step 5 You can enter the login interface for device configuration by selecting your role and entering a password on the login interface. The default administrator password is admin.
Getting Started
Figure 1-1-5 Login interface
Website login
Default IP: 172.16.101.1
Username: admin
Password: admin
1.4.3 Web GUI overview
The web management interface of the UC300 includes three areas: System button area, Menu bar, and Configuration area.
Figure 1-1-6 Web GUI layout
Table 1-3 Web management interface layout
Item | Description |
(1) System button area | Contains buttons such as Reboot, Logout. Product information; and displays the identity of the current login user. |
(2) Menu bar | Displays submenus for your selection when the mouse pointer is moved onto a menu. The selection result is displayed in the configuration area. |
(3) Configuration area | View or modify or view configuration. |
2 Features
2.1 System
2.1.1Dashboard
The option "Dashboard" of menu "System" in UC300 is a visualization tool that shows a general view of the system and gives a faster access to administrative actions in order to allow the user an easy administration of the server such as "System Resources", "Processes Status", "Hard Drives". Below a short description of each one.
2.1.1.1 Dashboard
System Resources: Here shows general information about the system where UC300 is running.
Figure 2-1-1 System Resource
Processes Status: It shows the enabled and disabled processes. Here you can start, stop and restart these processes.
Figure 2-1-2 Processes Status
Hard Drives: Hard Drives shows the free and used space of the hard drives installed on your server.
Figure 2-1-3 Hard Drives
Performance Graphic: It allows to check out the history of CPU and Memory usage as well as simultaneous calls over the time.
Figure 2-1-4 Performance Graphic
Communication Activity: This applet shows the number of extensions, trunks and calls currently on sip server.
Figure 2-1-5 Communication Activity
Calls: It is a history of calls with time and duration related to the extension of the logged user.
Figure 2-1-6 Calls
2.1.1.2 Dashboard Applet Admin
The option "Dashboard Applet Admin" from menu "System" in UC300 allows enabling or disabling the visibility of the applets in the Dashboard.
Navigate to System > Dashboard > Dashboard Applet Admin:
Figure 2-1-7 Dashboard Applet Admin
2.1.2 Network
2.1.2.1 Network Parameters
The option “Network” of the Menu “System” in UC300 series lets us view and configure the network parameters of the server.
Navigate to System > Network > Network Parameters to set network parameters according to the installed network environment.
Figure 2-1-8 Network Parameters Interface
This corresponds to the general network parameters of the server.
Table2-1-1 Description of Network Parameters
Item | Description |
Host (Ex. host.example.com) | Server Name, for example: pbx.subdomain.com |
Primary DNS | IP Address of the Primary Domain Name Server (DNS) |
Default Gateway | IP Address of the Port of Connection (Default Gateway) |
Secondary DNS | IP Address of the Secondary or Alternative Domain Name Server (DNS) |
To edit any of these parameters, click on the button .
Here also shows a list of available Interfaces on the server. Below the details.
Table2-1-2 Description of Edit Network Parameters
Item | Description |
Device | Name of the Ethernet interface |
Type | The type of IP address that the Interface has, which could be STATIC when the IP address is fixed or DHCP when the IP address is obtained automatically from a DHCP server. |
IP | IP Address assigned to the Interface |
Mask | The Network Mask assigned to the Interface |
MAC Address | Physical Address of the network Interface |
HW Info | Additional information about the network Interface |
Status | Shows the physical status of the Interface, if it’s connected or not |
To edit the parameters Type, IP or Mask, click on the name of the device. The rest of parameters cannot be changed.
Figure 2-1-9 Network setting interface
2.1.2.2 DHCP Server
DHCP (Dynamic Host Configuration Protocol) is a standardized network protocol used on Internet Protocol (IP) networks for dynamically distributing network configuration parameters, such as IP addresses for interfaces and services.
With DHCP, computers/IP phones request IP addresses and networking parameters automatically from UC300 WAN/LAN port which saves administrators a lot of time when compared with having to configure these settings manually.
The option "DHCP Server" allows configuring UC300 series so it can assign IP addresses in the network.
Navigate to System > Network > DHCP Server:
Figure 2-1-10 DHCP Server interface
Here the description of each field.
Table2-1-3 Description of DHCP Server
Item | Description |
Status | It indicates if the DHCP service is enabled or disabled. |
Starting IP Address | This will be the beginning of the IP range that the server will provide. |
Ending IP Address | This will be the ending of the IP range that the server will provide. |
Lease time | Amount of time the IP address will be assigned to devices in the network. |
DNS 1 | This address is the Primary DNS that the server will provide. |
DNS 2 | This address is the Secondary DNS that the server will provide. |
WINS | It is the IP of the WINS Server that will be given to Windows machines. |
Gateway | This is the address the server will provide as Gateway. |
To save changes just click on the button . The service can be started by clicking on .
2.1.2.3 DHCP Client List
This module shows a list of DHCP clients and leased IP addresses.
Navigate to System > Network > DHCP Client List and you will see a list of all devices receiving their IP address from the UC300 system.
Figure 2-1-11 DHCP Client List interface
To see the leased time of each address, click on "View Details".
Figure 2-1-12 View Details
2.1.2.4 Assign IP Address to Host
With this option you can assign an IP address to a specific device through MAC address. When the device requests an IP address, the DHCP server will provide it according to the MAC address. All the associations created by the user are shown in a list.
Navigate to System > Network > Assign IP Address to Host.
Figure 2-1-13 Assign IP Address to Host
To create a new association, click button. Fill out the required information and click on button.
Figure 2-1-14 Add Assign IP Address
The following table shows the description of each field:
Item | Description |
Host Name | Name that you want to assign to the device |
IP Address | IP Address you want to use for the device |
MAC Address | MAC number of the device |
2.1.3 Users
2.1.3.1 Users
The option “Users” allows creating and modifying users who will have access to the UC300 series Web Interface.
Navigate to System > Users > Users to create new users.
Figure 2-1-15 Users Interface
The users belong to a group which gives them privileges on UC300 series Web Interface. They can be associated with an extension and email. Click on a user to see, delete or edit the information of the user.
To create a new user, click on the button and fill out the required information.
Figure 2-1-16 Create New User
Click to save the configuration.
2.1.3.2 Groups
The option “Groups” allows you to create and modify all groups that will have access to the UC300 series Web Interface. There are 3 default groups of users as follows:
- Administrator
- Operator
- Extension
Figure 2-1-17 Groups Interface
Each one of these groups represents different levels of access to the UC300 Web Interface. These levels are associated with a set of menus to which a given user will have access. The various access permissions to the menus are better illustrated in the following table:
Table2-1-4 Groups
Menu | Administrator | Operator | Extension |
System | |||
System Info | Yes | Yes | No |
PBX Configuration | Yes | No | No |
Network | Yes | No | No |
User Management | Yes | No | No |
Shutdown | Yes | No | No |
Operator Panel | |||
Flash Operator Panel | Yes | Yes | No |
Voicemails | |||
Asterisk Recording Interface | Yes | Yes | No |
Fax | |||
Virtual Fax List | Yes | Yes | No |
New Virtual Fax | Yes | No | No |
Reports | |||
CDR Report | Yes | Yes | No |
Channels Usage | Yes | Yes | No |
Billing | |||
Rates | Yes | No | No |
Billing Report | Yes | No | No |
Destination Distribution | Yes | No | No |
Trunk Configuration | Yes | No | No |
Extras | |||
SugarCRM | Yes | Yes | Yes |
Calling Cards | Yes | Yes | Yes |
Downloads | |||
Softphones | Yes | Yes | Yes |
Fax Utilities | Yes | Yes | Yes |
To create a new group, click on the button and fill out the required information.
Figure 2-1-18 Create New Group
And then click to save the configuration.
2.1.3.3 Group Permissions
The option “Group Permission” of the Menu “System” in UC300 lets us determine the menus to which each group of users will have access.
The list below shows the names of the UC300 menus; you should select the ones that each group should have permission to access, and then click the “Apply” button.
Follow this procedure:
Step1 Go to System > Users > Group Permissions, click to select one of groups: Administrator, Operator and Extension. Then click the button .
Figure 2-1-19 Group Permissions Interface
Step 2 Click the button to save the configuration.
2.1.4 Analog
Figure 2- 1-20 general Configuration
Table2-1-5 Instruction of General
Options | Definition | ||||||
Tone duration |
| ||||||
Codec | Set the global encoding : mulaw, alaw. | ||||||
Impedance | Configuration for impedance. | ||||||
Flash/Wink | Turn on/off Flash/wink. | ||||||
Min flash time | Min flash time.(in milliseconds). | ||||||
Max flash time | Max flash time.(in milliseconds). | ||||||
“#”as Ending Dial Key | Turn on/off Ending Dial Key. |
Figure 2- 1-21 Fax
Table 2-1-6 Definition of Fax
Options | Definition |
Rate | Set the rate of sending and receiving. |
Ecm | Enable/disable T.30 ECM (error correction mode) by default. |
Figure 2-1-22 Echo
Figure 2- 1-23 Country
Table2-1-7 Definition of Country
Options | Definition |
Country | Configuration for location specific tone indications. |
Ring cadence | List of durations the physical bell rings. |
Dial tone | Set of tones to be played when one picks up the hook. |
Ring tone | Set of tones to be played when the receiving end is ringing. |
Busy tone | Set of tones played when the receiving end is busy. |
Call waiting tone | Set of tones played when there is a call waiting in the background. |
Congestion tone | Set of tones played when there is some congestion. |
Dial recall tone | Many phone systems play a recall dial tone after hook flash. |
Record tone | Set of tones played when call recording is in progress. |
Info tone | Set of tones played with special information messages (e.g., number is out of service.) |
Figure 2- 1-24 Caller ID
Figure 2-1-25 Hardware gain
Table2-1-8 Instruction of Hardware gain
Options | Definition |
FXO Rx gain | Set the FXO port Rx gain. Range: from -150 to 120. |
FXO Tx gain | Set the FXO port Tx gain. Range: from -150 to 120. |
FXS Rx gain | Set the FXS port Rx gain. Range: -35, 0 or 35. |
FXS Tx gain | Set the FXS port Tx gain. Range: -35, 0 or 35. |
Figure 2- 1-26 CallerID detect
Table 2-1-9 Instruction of CallerID detect
Options | Definition |
Use Callerid | Turn on/off callerid detect function |
Hide Callerid | Turn on/off callerid detect function |
Figure 2- 1-27 silence detect
Table 2-1-10 Definition of Silence detect
Options | Definition | |
Silence detect | Turn on/off silence detect function | |
Silence threshold | What we consider silence: the lower, the more sensitive, eg:250 is 250ms. Range: 100 to 500(100 to 500ms), default: 250 | |
Silence length | How many silence threshold of silence before hanging up(eg: 16 is 250ms*16=4s). Range: 2 to 1020 (200ms to 512s), default: 80(20s) | |
Silence framesize | Rx threshold | Range:-20 dBm0 to -40 dBm0, default: 20(-20 dBm0), all values are understood to be negative. |
Tx threshold | Range:-20 dBm0 to -40 dBm0, default: 20(-20 dBm0), all values are understood to be negative. |
Figure 2-1-28 Busy detect
Table 2-1-11 Instruction of Busy detect
Options | Definition |
Busy detect | Turn on/off busy detect function |
Busy count | How many busy tones to wait for before hanging up. The default is 3, but it might be safer to set to 6 or even 8. |
Busy country | Set the busy detect country |
2.1.5 Shutdown
This option allows for the shutdown and rebooting of the IP-PBX series. Upon choosing whichever of the two options, you will be prompted to confirm the action.
Navigate to System > Shutdown
Figure 2-1-29 Shutdown Interface
2.1.6 Preferences
2.1.6.1 Language
The option “Language” of the Menu “Preferences” in UC300 lets us configure the language for the UC300 Web Interface.
Select the language from the list and click on the “save” button.
Figure 2-1-30 Language setting
2.1.6.2 Date/Time
The option “Date/Time” of the Menu “Preferences” in UC300 lets us configure the Date, Hour and Timezone for the UC300 Web Interface.
Select the new date, hour and timezone and click on the “Apply changes” button.
Navigate to System > Preferences > Date/Time to deploy time server.
Figure 2-1-31 Date/Time Interface
2.1.6.3 Currency
The option "Currency" of the menu "Preferences" lets us change the currency for Reports in UC300 Web Interface.
Select a currency from the available options and click on the button.
Figure 2-1-32 Currency Setting interface
2.1.7 Licenses
Each product has its own Licenses UID, and the default Max SIP Number is 30. But we can expand the Max SIP Number to 300. If you have the need for this, please copy the products information about MAC, the serial number, and sent to contact our sales staff (sales@openvox.cn), then you will get the Licenses file. Finally you could upload Licenses to realize your needs.
Figure 2-1-33 License interface
2.1.8 SSH Settings
By default, SSH is disabled on the device. Generally, it is recommended that the SSH be disabled.
To enable SSH, navigate to System > SSH Settings, switching the enable to the on.
Figure 2-1-34 SSH Settings interface
2.1.9 Capture
The UC300 series have been supplied a network packets capture in the web for ease of user to analysis, capture and monitor the network status, RTP flows, protocol analysis and so on.
Figure 2-1-35 Capture interface
2.1.10Backup/Restore/Update
The option "Backup/Restore/Update" of the menu "System" allows you to back up and restore the configuration of UC300 series. If you have made a backup any time before this will appear in the list. To download a backup from the list, just click on the name of the tar file.
2.1.10.1 Configurations Files
Figure 2-1-36Currency Setting
2.1.10.2 Factory Reset
Figure 2-1-37 Factory Reset
2.1.10.3 Firmware Update
Figure 2-1-38 Firmware Update
2.1.10.4 Fax/Voice Mail/Voice Record
Figure 2-1-39 Fax/Voice Mail/Voice Record
2.1.11 About
Navigate to System >About, lets us view some information of UC300 series about firmware version and other useful information.
Figure 2-1-40 About the features information
2.2 Email
2.2.1 Domains
The option “Domains” of the Menu “Email” in UC300 lets us view and create domains in the email server.
Figure 2-2-1 Domains Interface
Create Domain
To add a domain, click on the button. A form will be shown where you will input the name of the new domain.
Delete a Domain
Clicking on the name of a domain will bring us to a screen that shows a button.
2.2.2 Accounts
The option “Accounts” of the Menu “Email” in UC300 lets us view and configure the email accounts for each of the domains specified in the server. Select a domain to see the existing accounts.
Figure 2-2-2 Account information
View, Edit and Delete
Clicking on the name of the account will bring us to a screen that shows the data of the account.
Here you can Edit or Delete the account. The name of the account cannot be modified.
Create an Account
To add a new account, select the domain under which it will be created and click on the “Create Account” button. A form will appear in which you will input the information for the following fields:
Table2-2-1 Description of Create an Account
Item | Description |
Email Address | This is the text that comes before the @ symbol |
Quota | The maximum space that this email account can use for the storage of emails on the server. The space is measured in kilobytes, so please be aware of this when the quota amounts are assigned for each user. |
Password | The password of the email account |
Retype password | Confirmation of the password of the email account |
2.2.3 Relay
By default, the email server doesn’t receive emails for accounts that are not found in the domains. The purpose of this is to prevent the server from being used for spam applications or trash and to prevent the unnecessary utilization of system resources. But there are some cases where it is necessary to activate this option for certain networks, such as, the internal network of a company. This way, the users can use the email server in UC300 to send emails to destinations that are outside of the domain of the system. In the option “Relay” it is specified the networks in which UC300 allows you to connect and use the server to send emails. The networks should be inputted as IP/MASK. For example: 127.0.0.1/32
Figure 2-2-3 Relay Interface
2.2.4 Webmail
The option “Webmail” of the Menu “Email” in UC300 lets us check the emails of the configured domains.
Figure 2-2-4 Webmail login Interface
Enter the username and password of the email account, and click on the “Login” button.
Figure 2-2-5 Webmail Interface
2.2.5 Antispam
The option "Antispam" from "Email" allows configuring the level of acceptation of emails that are not "Spam".
Figure 2-2-6 Antispam Interface
To activate Antispam is necessary, make sure the "Spamassassin" service is turned on. The option "status" allows turning on or turning off the service.
To mark the level of catch for Spams, just move the slider to the desired level.
The antispam politics to configure are:
Mark Subject:
Mark the Subject of email by the value of text Field.
Spam Capture:
Activate "Sieve" service to send all Spam to the "Spam folder" per each email account.
Activate action to remove Spams per email account and remove older emails given a specific time.
The options are:
Delete Spam for more than one week: Allow remove all Spam from "Spam" folder which have been more than one week in that folder.
Delete Spam for more than two week: Allow remove all Spam from "Spam" folder which have been more than two weeks in that folder.
Delete Spam for more than one month: Allow remove all Spam from "Spam" folder which have been more than one month in that folder.
This process is done every day.
2.2.6 Remote SMTP
The Module Remote SMTP allows adding a SMTP Server generally used to send messages from a mail client of a different mail server.
The fields to configure a Remote SMTP Server are:
Figure 2-2-7 Remote SMTP
Table2-2-2 Definition of Remote SMTP
Item | Definition |
Status | Status of connection SMTP Server. |
SMTP Server | Remote email server. |
Domain | Domain of SMTP Server. |
Port | Port to establish the connection with SMTP Server. |
User | Username of email account from SMTP Server. |
Password | Password of email account from SMTP Server |
TLS Enable | To enable certificates of TLS (Transport Layer Security). Some SMTP servers like Gmail requires these certificates. |
2.2.7 Email list
The module "Email List" allows creating list of mails using the software Mailman. You must have at least one domain created in your server.
When you click on this module initially it will show you all the current lists of mail created by us. Here you can create a new email list or delete an existing one. You can also use the filter to show the lists of a specific domain.
Figure 2-2-8 Email list interface
Creating a New Email List
To create a new list, click on button. If there isn't an existing Mailman Admin User, you'll have to configure it (you must have a Mailman admin created in order to run the mailman service). Enter an email and password for the administration of the Mailman. Then enter the New List Settings such as the domain (you should have at least one domain created in UC300 ), the name of the list, the administrator and password. When finish click on button (The administrator will receive an email with the password of the list)
Figure 2-2-9 Creating New Email List
Note: If there's an existing Mailman Admin already, you'll only need to enter the New List Settings.
Removing an Email List
To remove a list, just select the list and click on "Delete" button.
2.2.8 Email stats
The module "Email Stats" shows statistic graphics of the quantity of incoming emails.
The message "Nothing to show yet" means that UC300 doesn't have the enough information to show these statistics.
Figure 2-2-10 Email Status interface
2.2.9 Vacations
The "Vacations" module sends automatic replies while you are not available.
This module can be used for example:
- holiday
- lunch
- weekends
Figure 2-2-11 Vocation Interface
2.3 Fax
2.3.1 Virtual Fax
2.3.1.1 Virtual Fax List
The option “Virtual Fax List” of the Menu “FAX” in UC300 lets us verify the list of all the virtual faxes, including the status of each one.
Figure 2-3-1 Virtual Fax List interface
Also, clicking on the virtual fax's name displays its information:
Here you can Edit and Delete the Virtual Fax.
2.3.1.2 New Virtual Fax
The option “New Virtual Fax” from the Menu “FAX” in UC300 lets us create a new virtual fax. You should have previously created an IAX extension in "PBX => PBX Configuration => Extensions => Generic IAX2 Device".
Figure 2-3-2 New Virtual Fax
To create a new virtual fax, enter the name, e-mail, extension, secret code, country code and area code for the virtual fax (these are the mandatory fields). After this information is added, click on the button to save the virtual fax or to leave without saving.
2.3.1.3 Send Fax
The option "Send Fax" of the menu "Fax" in UC300 allows sending faxes to one or more numbers. Here you can enter the text you want to send and click on button.
Figure 2-3-3 Send fax with text information
Also, you can send files in the format .pdf, .tiff and .txt
Figure 2-3-4 Send fax with File Upload
2.3.1.4 Fax Queue
The option "Fax Queue" from the Menu "FAX" in UC300 shows the list of faxes that are awaiting its turn to be sent. All the jobs have an ID and a status so you can monitor the sending of the faxes. If you want to cancel a job, just select the job and click on button.
Figure 2-3-5 Fax Queue interface
2.3.2 Fax Master
The option "Fax Master" of the Menu "FAX" in UC300 lets us input the email address of the administrator of the Fax, and this email will receive notifications of the messages received, errors and other activities of the Fax Server.
Figure 2-3-6Fax Master Interface
2.3.3 Fax Clients
The option "Fax Clients" of the Menu "FAX" in UC300 lets us input the IPs that have permission to send faxes through UC300 .
Figure 2-3-7 Fax Client interface
Proceed to input the IPs, one IP per line and click on the button.
It is recommended that you input the IP 127.0.0.1 and localhost in the configuration because some processes might need to use them.
2.3.4 Fax Viewer
The option "Fax Viewer" of the Menu "Fax" shows a list with all the faxes that have been sent and received in the virtual Faxes. You can download the faxes if you click on the name of the file.
Figure 2-3-8 Fax Viewer interface
By the default all the files are shown, but you can filter according to company name, company fax, fax date or type fax.
Figure 2-3-9 Fax Viewer show filter
2.3.5 Email Template
The option "Email Template" of the menu "Fax" allows editing the configuration parameters of the sending of faxes to the email.
Figure 2-3-10 Fax Template interface
To edit the parameters, click on "Edit Parameters" button. Below an explanation of the editable fields:
Table 2-3-1 Definition of Email Template
Item | Description |
From (Email Address) | The email of the sender of the fax |
From (Name) | The name of the sender of the fax |
Subject | Write here the title of the email. By default it is specified the name of the PDF file. |
Body | Here you can write a description of the email. By default it is specified the Company Name, Company Number and Name PDF. |
2.4 PBX
2.4.1 PBX Configuration
The option “PBX Configuration” of the Menu “PBX” lets us configure extensions, trunks, routes, dialplan, queues, IVR and so on for UC300 series.
In the left part, we can observe that we have different options for configuration.
Basic
Extensions
Figure 2-4-1Add an Extension interface
Click one of extensions number:
Figure 2-4-2 Extension parameter interface
Table 2-4-1 Definition of Extension parameter
Item | Description |
Edit Extension | |
Display Name | The CallerID name for calls from this user will be set to this name. only enter the name , NOT the number. |
CID Num Alias | The CID Number to use for internal calls, if different from the extension number. This is used to masquerade as a different user. A common example is a team of support people who would like their internal CallerID to display the general support number(a ringgroup or queue). There will be no effect on external calls. |
SIP Alias | If you want to support direct sip dialing of users internally or through anonymous sip calls, you can supply a friendly name that can be used in a addition to the users extension to call them. |
Extension Options | |
Outbound CID | Override the callerid when dialing out a trunk. Any setting here will override the common outbound callerid set in the trunk admin. Format: “caller name” <#######> Leave this filed blank to disable the outbound callerid feature for this user. |
Asterisk Dial Options | Cryptic Asterisk Dial Options, check to customize for this extension or un-check to use system defaults set in Advanced Options. These will not apply to trunk options which are configured with the trunk. |
Ring Time | Number of seconds to ring prior to going to voicemail. Default will use the value set in Advanced Settings. If no voicemail is configured this will be ignored. |
Call Forward Ring Time | Number of seconds to ring during a Call Forward Busy or Call Forward Unavailable call prior to continuing to voicemail or specified destination. Setting to Always will not return, it will just continue to ring. Default will use the current Ring Time. If voicemail is disabled and there is not destination specified, it will be forced into Always mode. |
Outbound Concurrency Limit | Maximum number of outbound simultaneous calls that an extension can make. This is also very useful as a Security Protection against a system that has been compromised. It will limit the number of simultaneous calls that can be made on the compromised extension. |
Call Waiting | Set the initial/current Call Waiting state for this user’s extension |
Internal Auto Answer | When set to Intercom, calls to this extension/user from other internal users act as if they were intercom calls meaning they will be auto-answered if the endpoint supports this feature and the system is configured to operate in this mode. All the normal white list and black list settings will be honored if they are set. External calls will still ring as normal, as will certain other circumstances such as blind transfers and when a Follow Me is configured and enabled. If Disabled, the phone rings as a normal phone. |
Call Screening | Call Screening requires external callers to say their name, which will be played back to the user and allow the user to accept or reject the call. Screening with memory only verifies a caller for their callerid once. Screening without memory always required a caller to say their name. Either mode will always announce the caller based on the last introduction saved with that callerID. If any user on the system uses the memory option, when that user is called, the caller will be required to re-introduce themselves and all users on the system will have that new introduction associated with the caller’s CallerID. |
Pinless Dialing | Enabling Pinless Dialing will allow this extension to bypass any pin codes normally required on outbound calls. |
Emergency CID | This callerid will always be set when dialing out an Outbound Route flagged ad Emergency. The Emergency CID overrides all other CallerID settings. |
Queue State Detection | If this extension is part of a Queue will attempt to use the user’s extension state or device state information when determining if this queue member should be called. In some uncommon situations such as a Follow-Me with no physical device, or some virtual extension scenarios, the state information will indicate that this member is not available when they are. Setting this to ‘Ignore-State’ will make the Queue ignore all state information thus always trying to contact this member. Certain side affects can occur when this route is taken due to the nature of how Queues handle Local channels, such as subsequent transfers will continue to show the member as busy until the original call is terminated. In most cases, this SHOULD BE set to ‘Use State’. |
Assigned DID/CID | |
DID Description | A description for this DID, such as “Fax”. |
Add Inbound DID | A direct DID that is associated with this extension. The DID should be in the same format as provider (e.g. full number, 4digits for 10x4, etc). |
Add Inbound CID | Add a CID for more specific DID+CID routing. A DID must be specified in the above Add DID box. In addition to standard dial sequences, you can also put Private, Blocked, Unknown, Restricted, Anonymous and Unavailable in order to catch these special cases if the Telco transmits them. |
Device Options | |
Secret | Password (secret) configured for the device. Should be alphanumeric with at least 2 letters and numbers to keep secure. |
dtmfmode | The DTMF signaling mode used by this device, usually rfc2833 for most phone. |
canreinvite | Re-Invite policy for this device, see Asterisk documentation for details. |
context | Asterisk context this device will send calls to. Only change this is you know what you are doing. |
host | Host settings for this device, almost always dynamic for endpoint. |
trustrpid | Whether Asterisk should trust the RPID settings from this device. Usually should be yes for CONNECTEDLINE( ) functionality to work if supported by the endpoint. |
sendrpid | Whether Asterisk should send RPID (or PAI) info to the device. Usually should be enabled to the settings used by your device for CONNECTEDLINE( ) functionality to work if supported by the endpoint. |
type | Asterisk connection type, usually friend for endpoint. |
nat | NAT seting, see Asterisk documentation for details. Yes usually works for both internal and external devices. Set to No if the device will always be internal. |
port | Endpoint port number to use, usually 5060. Some 2 ports devices such as ATA may used 5061 for the second port. |
qualify | Setting to yes (equivalent to 2000 msec) will send an OPTIONS packet to the endpoint periodically (default every minute). Used to monitor the health of the endpoint. If delays are longer then the quality time, the endpoint will be taken offline and considered unreachable. Can be set to a value which is the msec threshold. Setting to no will turn this off. Can also be helpful to keep NAT pinholes open. |
qualifyfreq | Frequency in seconds to send qualify messages to the endpoint. |
transport | This sets the allowed transport settings for this device and the default (Primary) transport for outgoing. The default transport is only used for outbound message until a registration takes place. During the peer registration the transport type may change to another supported type if the peer requests so. In most common cases, this does not have to be changed as most devices register in conjunction with the host=dynamic setting. If you are using TCP and/or TLS you need to make sure the general SIP Settings are configured for the system to operate in those modes and for TLS, proper certificates have been generated and configured. If you are using websockets (such as WebRTC) then you must select an option that includes WS. |
avpf | Whether to Enable AVPF. Defaults to no. the WebRTC standard has selected AVPF as the audio video profile to use for media streams. This is not the default profile in use by Asterisk. As a result the following must enabled to use WebRTC. |
icesupport | Whether to enable ICE support. Defaults to no. ICE ( Interactive Connectivity Establishment) is a protocol for network address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. This option is commonly enabled in WebRTC setups. |
dtlsenable | Whether to enable DTLS for this peer. Defaults to no. |
dtlsverify | Whether to verify that the provided peer certificate is valid. Defaults to no. |
dtlssetup | Behavior on DTLS incoming and outgoing connections, defaults to actpass. |
dtlscertfile | Path to certificate file to present. |
dtlsprivatekey | Path to private key for certificate file. |
encryption | Whether to offer SPTR encrypted media (and only SRTP encrypted media) on outgoing calls to a peer. Calls will fail with HANGUPCAUSE=58 if the peer does not support SRTP. Defaults to no. |
callgroup | Callgroup(s) that this device is part of, can be or more callgroups, e.g. ‘1,3-5’ would be in groups 1,3,4,5. |
pickupgroup | Pickupgroup(s) that this device can pickup calls from, can be one or more groups, e.g. ‘1.3-5’ would be in groups 1,3,4,5. Device does not have to be in a group to be able to pickup calls from that group. |
disallow | Disallowed codecs. Set this to all to remove all codecs defined in the general settings and then specify specific codecs separated by ‘&’ on the ‘allow’ setting, or just disallow specific codecs separated by ‘&’. |
allow | Allow specific codecs, separated by the ‘&’ sign and in priority order. E.g. ‘ulaw&g729’. Codecs allowed in the general settings will also be allowed unless removed with the ‘disallow’ directive. |
dial | How to dial device, this should not be changed unless you know what you are doing. |
accountcode | Accountcode for this device. |
mailbox | Mailbox for this device. This should not be changed unless you know what you are doing. |
vmexten | Asterisk dialplan extension to reach voicemail for this device. Some devices use this to auto-program the voicemail button on the endpoint. If left blank, the default vmexten setting is automatically configured by the voicemail module. Only changed this on devices that may have special needs. |
deny | IP Address range to deny access to, in the form of network/netmask. |
permit | IP Address range to allow access to, in the form of network/netmask. This can be a very useful security option when dealing with remote extensions that are at a known location (such as a branch office) or with a known ISP range for some home office situations. |
Dictation Services | |
Email Address | The email address that completed dictations are sent to. |
Language | |
Language Code | This will cause all messages and voice prompts to use the selected language if installed. |
Recording Options | |
Inbound External Calls | Recording of inbound calls from external sources. |
Outbound External Calls | Recording of outbound calls from external sources. |
Inbound Internal Calls | Recording of calls received from other extensions on the system. |
Outbound Internal Calls | Recording of calls made to other extensions on the system. |
On Demand Recording | Enable or disable the ability to do on demand (one-touch) recording. The overall calling policy rules still apply and if calls are already being recorded they can not be paused. |
Record Priority Policy | Call recording policy priority relative to other extensions when there is a conflict between an extension wanting recording and the other not wanting it. The higher of the two determines the policy, on a tie the global policy (caller or callee) determines the policy. |
Voicemail | |
Voicemail Password | This is the password used to access the Voicemail system. This password can only contain numbers. A user can change the password you enter here after logging into the Voicemail system (*98) with a phone. |
Email Address | The email address that Voicemails are sent to. |
Pager Email Address | Page/mobile email address that short Voicemail notifications are sent to. |
Email Attachment | Option to attach Voicemail to email. |
Play CID | Read back caller’s telephone number prior to playing the incoming message, and just after announcing the date and time the message was left. |
Play Envelope | Envelope controls whether or not the Voicemail system will play the message envelope (date/time) before playing the voicemail message. This setting does not affect the operation of the envelope option in the advanced voicemail menu. |
Delete Voicemail | If set to “yes” the message will be delete from the voicemailbox (after having been emailed). Provides functionality that allows a user to receive their voicemail via email alone, rather than extension handset. CAUTION: must have attach voicemail to email set to yes otherwise your messages will be lost forever. |
VM Options | Separate options with pipe( | ) Ie: review=yes|maxmessage=60 |
VM Context | This is the voicemail context which is normally set to default. Do not change unless you understand the implications. |
VmX Locater | |
VmX Locater™ | Enable/ disable the VmX locater feature for this user. When enabled all settings are controlled by the user in the user portal (ARI). Disabling will not delete any existing user settings but will disable access to the feature. |
Use When | Menu options below are available during your personal voicemail greeting playback. Check both to use at all times. |
Voicemail Instructions | Uncheck to play a deep after your personal voicemail greeting. |
Press 0 | Pressing 0 during your personal voicemail greeting goes to the operator. Uncheck to enter another destination here. This feature can be used while still disabling VmX to allow an alternative operator extension without requiring the VmX feature for the user. |
Press 1 | The remaining options can have internal extensions, ringgroups, queues and external numbers that may be rung. It is often used to include your cell phone. You should run a test to make sure that the number is functional any time a change is made so you don’t leave a caller stranded or receiving invalid number messages. |
Press 2 | Use any extensions, ringgroups, queues or external numbers. Remember to re-record your personal voicemail greeting and include instructions. Run a test to make sure that the number is functional. |
Optional Destinations | |
No Answer | Optional destination call is routed to when the call is not answered on an otherwise idle phone. If the phone is use and the call is simply ignored, then the busy destination will be used. |
CID Prefix | Optional CID prefix to add before sending to this no answer destination. |
Busy | Optional destination the call is route to when the phone is busy or the call is rejected the user. This destination is also used on an unanswered call if the phone is in use and the user choose not pickup the second call. |
CID Prefix | Optional CID prefix to add before sending to this busy destination. |
Not Reachable | Optional destination the call is routed when the phone is office, such as a softphone currently off or a phone unplugged. |
CID Prefix | Optional CID prefix to add before sending to this not reachable destination. |
Feature codes
Figure 2-4-3 Feature code admin interface
Outbound Routes
Figure 2-4-4 Outbound Routes interface
Table2-4-2 Definition of Outbound Routes
Item | Definition |
Route Settings | |
Route Name | Name of this route. Should be used to describe what type of calls this route matches (for example, 'local' or 'longdistance'). |
Route CID | Optional Route CID to be used for this route. If set, this will override all CIDS specified except: l extension/device EMERGENCY CIDs if this route is checked as an EMERGENCY Route l trunk CID if trunk is set to force it's CID l Forwarded call CIDs (CF, Follow Me, Ring Groups, etc) l Extension/User CIDs if checked |
Override Extension | If checked the extension's Outbound CID will be ignored in favor of this CID. The extension's Emergency CID will still be used if the route is an Emergency Route and the Extension has a defined Emergency CID. |
Route Password | Optional: A route can prompt users for a password before allowing calls to progress. This is useful for restricting calls to international destinations or 1-900 numbers. A numerical password, or the path to an Authenticate password file can be used. Leave this field blank to not prompt for password. |
Route Type | Optional: Selecting Emergency will enforce the use of a device's Emergency CID setting (if set). Select this option if this route is used for emergency dialing (ie: 911). Optional: Selecting Intra-Company will treat this route as an intra-company connection, preserving the internal CallerID information instead of the outbound CID of either the extension or trunk. |
Music On Hold | You can choose which music category to use. For example, choose a type appropriate for a destination country which may have announcements in the appropriate language. |
Time Group | If this route should only be available during certain times then Select a Time Group created under Time Groups. The route will be ignored outside of times specified in that Time Group. If left as default of Permanent Route then it will always be available. |
Route Position | Where to insert this route or relocate it relative to the other routes. |
Additional Settings | |
Call Recording | Controls or overrides the call recording behavior for calls coming into this DID. Allow will honor the normal downstream call recording settings. Record on Answer starts recording when the call would otherwise be recorded ignoring any settings that say otherwise. Record Immediately will start recording right away capturing ringing announcements, MoH, etc. Never will disallow recording regardless of downstream settings. |
PIN Set | Optional: Select a PIN set to use. If using this option, leave the Route Password field blank. |
Dial Patterns that will use this Route | A Dial Pattern is a unique set of digits that will select this route and send the call to the designated trunks. If a dialed pattern matches this route, no subsequent routes will be tried. If Time Groups are enabled, subsequent routes will be checked for matches outside of the designated time(s). Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the patterns specified by the subsequent columns, then this will be prepended before sending to the trunks. Prefix: Prefix to remove on a successful match. The dialed number is compared to this and the subsequent columns for a match. Upon a match, this prefix is removed from the dialed number before sending it to the trunks. Match pattern: The dialed number will be compared against the prefix + this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks. CallerID: If CallerID is supplied, the dialed number will only match the prefix + match pattern if the CallerID being transmitted matches this. When extensions make outbound calls, the CallerID will be their extension number and NOT their Outbound CID. The above special matching sequences can be used for CallerID matching similar to other number matches. |
Dial patterns wizards | These options provide a quick way to add outbound dialing rules. Follow the prompts for each. Lookup local prefixes This looks up your local number on ww.localcallingguide.com (NA-only), and sets up so you can dial either 7, 10 or 11 digits (5551234, 6135551234, 16135551234) to access this route. Upload from CSV Upload patterns from a CSV file replacing existing entries. If there are no headers then the file must have 4 columns of patterns in the same order as in the GUI. You can also supply headers: prepend, prefix, match pattern and callerid in the first row. If there are less than 4 recognized headers then the remaining columns will be blank. |
Trunk Sequence for Matched Routes | The Trunk Sequence controls the order of trunks that will be used when the above Dial Patterns are matched. For Dial Patterns that match long distance numbers, for example, you’d want to pick the cheapest routes for long distance (ie, VoIP trunk first) followed by more expensive routes (POTS lines). |
Optional Destination on Congestion | If all the trunks fail because of Asterisk ‘CONGESTION’ dial status you can optionally go to a destination such as a unique recorded message or anywhere else. This destination will NOT be engaged if the trunk is reporting busy, invalid numbers or anything else that would imply the trunk was able to make an ‘intelligent’ choice about the number that was dialed. The ‘Normal Congestion’ behavior is to play the ‘ALL Circuits Busy’ recording or other options configured in the route Congestion Messages module when installed. |
Trunk
Figure 2-4-5 Add trunk interface
Figure 2-4-6 Add SIP Trunk
Table2-4-3 Definition of add a SIP trunk
Item | Definition |
General Setting | |
Trunk Name | Descriptive Name for this trunk |
Outbound CallerID | CallerID for calls placed out on this trunk Format: <#######>. You can also use the format: “hidden” <#######> to hide the CallerID sent out over Digital lines if supported (SIP/IAX). |
CID Options | Determines what CIDs will be allowed out this trunk. IMPORTANT: EMERGENCY CIDs defined on an extension/device will ALWAYS be used if this trunk is part of an EMERGENCY Route regardless of these settings. Allow Any CID: all CIDs including foreign CIDS from forwarded external calls will be transmitted. Block Foreign CIDs: blocks any CID that is the result of a forwarded call from off the system. CIDs defined for extensions/users are transmitted. Remove CNAM: this will remove CNAM from any CID sent out this trunk Force Trunk CID: Always use the CID defined for this trunk except if part of any EMERGENCY Route with an EMERGENCY CID defined for the extension/device. Intra-Company Routes will always transmit an extension’s internal number and name. |
Maximum Channels | Controls the maximum number of outbound channels (simultaneous calls) that can be used on this trunk. To count inbound calls against this maximum, use the auto-generated context: as the inbound trunk's context. (see extensions_additional.conf) Leave blank to specify no maximum. |
Asterisk Trunk Dial Options | Asterisk Dial command options to be used when calling out this trunk. To override the Advanced Settings default, check the box and then provide the required options for this trunk |
Continue if Busy | Normally the next trunk is only tried upon a trunk being ‘Congested’ in some form, or unavailable. Checking this box will force a failed call to always continue to the next configured trunk or destination even when the channel reports BUSY or INVALID NUMBER. |
Disable Trunk | Check this to disable this trunk in all routes where it is used. |
Dialed Number Manipulation Rules | These rules can manipulate the dialed number before sending it out this trunk. If no rule applies, the number is not changed. The original dialed number is passed down from the route where some manipulation may have already occurred. This trunk has the option to further manipulate the number. If the number matches the combined values in the prefix plus the match pattern boxes, the rule will be applied and all subsequent rules ignored. Upon a match, the prefix, if defined, will be stripped. Next the prepend will be inserted in front of the match pattern and the resulting number will be sent to the trunk. All fields are optional. Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the patterns specified by the subsequent columns, then this will be prepended before sending to the trunks. Prefix: Prefix to remove on a successful match. The dialed number is compared to this and the subsequent columns for a match. Upon a match, this prefix is removed from the dialed number before sending it to the trunks. Match pattern: The dialed number will be compared against the prefix + this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks after removing the prefix and appending the prepend digits You can completely replace a number by matching on the prefix only, replacing it with a prepend and leaving the match pattern blank. |
Dial Rules Wizards | Always dial with prefix is useful for VoIP trunks, where if a number is dialed as “5551234”, it can be converted to “16135551234”. Remove prefix from local numbers is useful for ZAP and DAHADI trunks, where if a local number is dialed as “1615551234”, it can be converted to “555-1234”. Setup directly assistance is useful to translate a call to directory assistance. Lookup numbers for local trunk This looks up your local number on www.localcallingguide.com (NA-only), and sets up so you can dial either 7or 10 digits (regardless of what your PSTN is) on a local trunk (where you have to dial 1+area code for long distance, but only 5551234 (7-difit dialing) or 6135551234 (10-digit dialing) local calls. Upload from CSV Upload pattern from a CSV file replacing existing entries. If there are no headers then the file must have 3 columns of pattern in the same order as in the GUI. You can also supply headers: prepend. Prefix and match pattern in the first raw. If there are less than 3 recognized headers than the remaining columns will be blank. |
Outbound Dial Prefix | The outbound dialing prefix is used to prefix a dialing string to all outbound calls placed on this trunk. For example, if this trunk is behind another PBX or is a Centrex line, then you would put 9 here to access an outbound line. Another common use is to prefix calls with 'w' on a POTS line that need time to obtain dial tone to avoid eating digits. Most users should leave this option blank. |
Outgoing Settings | |
Trunk Name | Give this trunk a unique name. example: myiaxtel |
PEER Details | Modify the default PEER connection parameters for your VoIP provider. You may need to add to the default lines listed below, depending on your provider. WARNING: Order is important as it will be retained. For example, if you use the \"allow/deny\" directives make sure deny comes first. |
Incoming Settings | |
USER Context | This is most often the account name or number your provider expects. This USER Context will be used to define the below user details. |
USER Details | Modify the default USER connection parameters for your VoIP provider. You may need to add to the default lines listed below, depending on your provider.. WARNING: Order is important as it will be retained. For example, if you use the \"allow/deny\" directives make sure deny comes first. |
Register String | Most VoIP providers require your system to REGISTER with theirs. Enter the registration line here. example: username:password@switch.voipprovider.com. Many providers will require you to provide a DID number, ex: username:password@switch.voipprovider.com/didnumber in order for any DID matching to work. |
Figure 2-4-7 Add DAHDI Trunk
Table2-4-4 Definition Add DAHDI Trunk
Item | Definition |
General Setting | |
Trunk Name | Descriptive Name for this trunk |
Outbound CallerID | CallerID for calls placed out on this trunk Format: <#######>. You can also use the format: “hidden” <#######> to hide the CallerID sent out over Digital lines if supported (SIP/IAX). |
CID Options | Determines what CIDs will be allowed out this trunk. IMPORTANT: EMERGENCY CIDs defined on an extension/device will ALWAYS be used if this trunk is part of an EMERGENCY Route regardless of these settings. Allow Any CID: all CIDs including foreign CIDS from forwarded external calls will be transmitted. Block Foreign CIDs: blocks any CID that is the result of a forwarded call from off the system. CIDs defined for extensions/users are transmitted. Remove CNAM: this will remove CNAM from any CID sent out this trunk Force Trunk CID: Always use the CID defined for this trunk except if part of any EMERGENCY Route with an EMERGENCY CID defined for the extension/device. Intra-Company Routes will always transmit an extension’s internal number and name. |
Maximum Channels | Controls the maximum number of outbound channels (simultaneous calls) that can be used on this trunk. Inbound calls are not counted against the maximum. Leave blank to specify no maximum. |
Asterisk Trunk Dial Options | Asterisk Dial command options to be used when calling out this trunk. To override the Advanced Settings default, check the box and then provide the required options for this trunk |
Continue if Busy | Normally the next trunk is only tried upon a trunk being ‘Congested’ in some form, or unavailable. Checking this box will force a failed call to always continue to the next configured trunk or destination even when the channel reports BUSY or INVALID NUMBER. |
Disable Trunk | Check this to disable this trunk in all routes where it is used. |
Dialed Number Manipulation Rules | These rules can manipulate the dialed number before sending it out this trunk. If no rule applies, the number is not changed. The original dialed number is passed down from the route where some manipulation may have already occurred. This trunk has the option to further manipulate the number. If the number matches the combined values in the prefix plus the match pattern boxes, the rule will be applied and all subsequent rules ignored. Upon a match, the prefix, if defined, will be stripped. Next the prepend will be inserted in front of the match pattern and the resulting number will be sent to the trunk. All fields are optional. Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the patterns specified by the subsequent columns, then this will be prepended before sending to the trunks. Prefix: Prefix to remove on a successful match. The dialed number is compared to this and the subsequent columns for a match. Upon a match, this prefix is removed from the dialed number before sending it to the trunks. Match pattern: The dialed number will be compared against the prefix + this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks after removing the prefix and appending the prepend digits You can completely replace a number by matching on the prefix only, replacing it with a prepend and leaving the match pattern blank. |
Dial Rules Wizards | Always dial with prefix is useful for VoIP trunks, where if a number is dialed as “5551234”, it can be converted to “16135551234”. Remove prefix from local numbers is useful for ZAP and DAHADI trunks, where if a local number is dialed as “1615551234”, it can be converted to “555-1234”. Setup directly assistance is useful to translate a call to directory assistance. Lookup numbers for local trunk This looks up your local number on www.localcallingguide.com (NA-only), and sets up so you can dial either 7or 10 digits (regardless of what your PSTN is) on a local trunk (where you have to dial 1+area code for long distance, but only 5551234 (7-difit dialing) or 6135551234 (10-digit dialing) local calls. Upload from CSV Upload pattern from a CSV file replacing existing entries. If there are no headers then the file must have 3 columns of pattern in the same order as in the GUI. You can also supply headers: prepend. Prefix and match pattern in the first raw. If there are less than 3 recognized headers than the remaining columns will be blank. |
Outbound Dial Prefix | The outbound dialing prefix is used to prefix a dialing string to all outbound calls placed on this trunk. For example, if this trunk is behind another PBX or is a Centrex line, then you would put 9 here to access an outbound line. Another common use is to prefix calls with 'w' on a POTS line that need time to obtain dial tone to avoid eating digits. Most users should leave this option blank. |
DAHDi Identifier | DAHADi channels are referenced either by a group number or channel number (which is defined in chan_dahadi.conf). The default setting is g0(group zero) |
Figure 2-4-8 Add IAX2 Trunk
Table 2-4-5 Definition of Add IAX2 Trunk
Item | Definition |
General Setting | |
Trunk Name | Descriptive Name for this trunk |
Outbound CallerID | CallerID for calls placed out on this trunk Format: <#######>. You can also use the format: “hidden” <#######> to hide the CallerID sent out over Digital lines if supported (SIP/IAX). |
CID Options | Determines what CIDs will be allowed out this trunk. IMPORTANT: EMERGENCY CIDs defined on an extension/device will ALWAYS be used if this trunk is part of an EMERGENCY Route regardless of these settings. Allow Any CID: all CIDs including foreign CIDS from forwarded external calls will be transmitted. Block Foreign CIDs: blocks any CID that is the result of a forwarded call from off the system. CIDs defined for extensions/users are transmitted. Remove CNAM: this will remove CNAM from any CID sent out this trunk Force Trunk CID: Always use the CID defined for this trunk except if part of any EMERGENCY Route with an EMERGENCY CID defined for the extension/device. Intra-Company Routes will always transmit an extension’s internal number and name. |
Maximum Channels | Controls the maximum number of outbound channels (simultaneous calls) that can be used on this trunk. To count inbound calls against this maximum, use auto-generated context: from-trunk-[trunkname] as the inbound trunk’s context. (see extesions_additional .conf)Leave blank to specify no maximum. |
Asterisk Trunk Dial Options | Asterisk Dial command options to be used when calling out this trunk. To override the Advanced Settings default, check the box and then provide the required options for this trunk. |
Continue if Busy | Normally the next trunk is only tried upon a trunk being ‘Congested’ in some form, or unavailable. Checking this box will force a failed call to always continue to the next configured trunk or destination even when the channel reports BUSY or INVALID NUMBER. |
Disable Trunk | Check this to disable this trunk in all routes where it is used. |
Dialed Number Manipulation Rules | These rules can manipulate the dialed number before sending it out this trunk. If no rule applies, the number is not changed. The original dialed number is passed down from the route where some manipulation may have already occurred. This trunk has the option to further manipulate the number. If the number matches the combined values in the prefix plus the match pattern boxes, the rule will be applied and all subsequent rules ignored. Upon a match, the prefix, if defined, will be stripped. Next the prepend will be inserted in front of the match pattern and the resulting number will be sent to the trunk. All fields are optional. Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the patterns specified by the subsequent columns, then this will be prepended before sending to the trunks. Prefix: Prefix to remove on a successful match. The dialed number is compared to this and the subsequent columns for a match. Upon a match, this prefix is removed from the dialed number before sending it to the trunks. Match pattern: The dialed number will be compared against the prefix + this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks after removing the prefix and appending the prepend digits You can completely replace a number by matching on the prefix only, replacing it with a prepend and leaving the match pattern blank. |
Dial Rules Wizards | Always dial with prefix is useful for VoIP trunks, where if a number is dialed as “5551234”, it can be converted to “16135551234”. Remove prefix from local numbers is useful for ZAP and DAHADI trunks, where if a local number is dialed as “1615551234”, it can be converted to “555-1234”. Setup directly assistance is useful to translate a call to directory assistance. Lookup numbers for local trunk This looks up your local number on www.localcallingguide.com (NA-only), and sets up so you can dial either 7or 10 digits (regardless of what your PSTN is) on a local trunk (where you have to dial 1+area code for long distance, but only 5551234 (7-difit dialing) or 6135551234 (10-digit dialing) local calls. Upload from CSV Upload pattern from a CSV file replacing existing entries. If there are no headers then the file must have 3 columns of pattern in the same order as in the GUI. You can also supply headers: prepend. Prefix and match pattern in the first raw. If there are less than 3 recognized headers than the remaining columns will be blank. |
Outbound Dial Prefix | The outbound dialing prefix is used to prefix a dialing string to all outbound calls placed on this trunk. For example, if this trunk is behind another PBX or is a Centrex line, then you would put 9 here to access an outbound line. Another common use is to prefix calls with 'w' on a POTS line that need time to obtain dial tone to avoid eating digits. Most users should leave this option blank. |
Outgoing Setting | |
Trunk Name | Give this trunk a unique name. example: myiaxtel |
PEER Details | Modify the default PEER connection parameters for your VoIP provider. You may need to add to the default lines listed below, depending on your provider. WARNING: Order is important as it will be retained. For example, if you use the \"allow/deny\" directives make sure deny comes first. |
Incoming Setting | |
USER Context | This is most often the account name or number your provider expects. This USER Context will be used to define the below user details. |
USER Details | Modify the default USER connection parameters for your VoIP provider. You may need to add to the default lines listed below, depending on your provider.. WARNING: Order is important as it will be retained. For example, if you use the \"allow/deny\" directives make sure deny comes first. |
Registration | |
Register String | Most VoIP providers require your system to REGISTER with theirs. Enter the registration line here. example: username:password@switch.voipprovider.com. Many providers will require you to provide a DID number, ex: username:password@switch.voipprovider.com/didnumber in order for any DID matching to work. |
Figure 2-4-9 Add ENUM Trunk
Table 2-4-6 Definition of Add ENUM Trunk
Item | Definition |
Trunk Name | Descriptive Name for this trunk |
Outbound CallerID | CallerID for calls placed out on this trunk Format: <#######>. You can also use the format: “hidden” <#######> to hide the CallerID sent out over Digital lines if support (SIP/IAX). |
CID Options | Determines what CIDs will be allowed out this trunk. IMPORTANT: EMERGENCY CIDs defined on an extension/device will ALWAYS be used if this trunk is part of an EMERGENCY Route regardless of these settings. Allow Any CID: all CIDs including foreign CIDS from forwarded external calls will be transmitted. Block Foreign CIDs: blocks any CID that is the result of a forwarded call from off the system. CIDs defined for extensions/users are transmitted. Remove CNAM: this will remove CNAM from any CID sent out this trunk Force Trunk CID: Always use the CID defined for this trunk except if part of any EMERGENCY Route with an EMERGENCY CID defined for the extension/device. Intra-Company Routes will always transmit an extension’s internal number and name. |
Maximum Channels | Controls the maximum number of outbound channels (simultaneous calls) that can be used on this trunk. Inbound calls are not counted against the maximum. Leave blank to specify no maximum. |
Asterisk Trunk Dial Options | Asterisk Dial command options to be used when calling out this trunk. To override the Advanced Settings default, check the box and then provide the required options for this trunk |
Continue if Busy | Normally the next trunk is only tried upon a trunk being ‘Congested’ in some form, or unavailable. Checking this box will force a failed call to always continue to the next configured trunk or destination even when the channel reports BUSY or INVALID NUMBER. |
Disable Trunk | Check this to disable this trunk in all routes where it is used. |
Dialed Number Manipulation Rules | These rules can manipulate the dialed number before sending it out this trunk. If no rule applies, the number is not changed. The original dialed number is passed down from the route where some manipulation may have already occurred. This trunk has the option to further manipulate the number. If the number matches the combined values in the prefix plus the match pattern boxes, the rule will be applied and all subsequent rules ignored. Upon a match, the prefix, if defined, will be stripped. Next the prepend will be inserted in front of the match pattern and the resulting number will be sent to the trunk. All fields are optional. Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the patterns specified by the subsequent columns, then this will be prepended before sending to the trunks. Prefix: Prefix to remove on a successful match. The dialed number is compared to this and the subsequent columns for a match. Upon a match, this prefix is removed from the dialed number before sending it to the trunks. Match pattern: The dialed number will be compared against the prefix + this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks after removing the prefix and appending the prepend digits You can completely replace a number by matching on the prefix only, replacing it with a prepend and leaving the match pattern blank. |
Dial Rules Wizards | Always dial with prefix is useful for VoIP trunks, where if a number is dialed as “5551234”, it can be converted to “16135551234”. Remove prefix from local numbers is useful for ZAP and DAHADI trunks, where if a local number is dialed as “1615551234”, it can be converted to “555-1234”. Setup directly assistance is useful to translate a call to directory assistance. Lookup numbers for local trunk This looks up your local number on www.localcallingguide.com (NA-only), and sets up so you can dial either 7or 10 digits (regardless of what your PSTN is) on a local trunk (where you have to dial 1+area code for long distance, but only 5551234 (7-difit dialing) or 6135551234 (10-digit dialing) local calls. Upload from CSV Upload pattern from a CSV file replacing existing entries. If there are no headers then the file must have 3 columns of pattern in the same order as in the GUI. You can also supply headers: prepend. Prefix and match pattern in the first raw. If there are less than 3 recognized headers than the remaining columns will be blank. |
Outbound Dial Prefix | The outbound dialing prefix is used to prefix a dialing string to all outbound calls placed on this trunk. For example, if this trunk is behind another PBX or is a Centrex line, then you would put 9 here to access an outbound line. Another common use is to prefix calls with 'w' on a POTS line that need time to obtain dial tone to avoid eating digits. Most users should leave this option blank. |
Figure 2-4-10 Add DUNDI Trunk interface
Table 2-4-7 Definition of Add DUNDI Trunk
Item | Definition |
Trunk Name | Descriptive Name for this trunk |
Outbound CallerID | CallerID for calls placed out on this trunk Format: <#######>. You can also use the format: “hidden” <#######> to hide the CallerID sent out over Digital lines if supported (SIP/IAX). |
CID Options | Determines what CIDs will be allowed out this trunk. IMPORTANT: EMERGENCY CIDs defined on an extension/device will ALWAYS be used if this trunk is part of an EMERGENCY Route regardless of these settings. Allow Any CID: all CIDs including foreign CIDS from forwarded external calls will be transmitted. Block Foreign CIDs: blocks any CID that is the result of a forwarded call from off the system. CIDs defined for extensions/users are transmitted. Remove CNAM: this will remove CNAM from any CID sent out this trunk Force Trunk CID: Always use the CID defined for this trunk except if part of any EMERGENCY Route with an EMERGENCY CID defined for the extension/device. Intra-Company Routes will always transmit an extension’s internal number and name. |
Maximum Channels | Controls the maximum number of outbound channels (simultaneous calls) that can be used on this trunk. Inbound calls are not counted against the maximum. Leave blank to specify no maximum. |
Asterisk Trunk Dial Options | Asterisk Dial command options to be used when calling out this trunk. To override the Advanced Settings default, check the box and then provide the required options for this trunk |
Continue if Busy | Normally the next trunk is only tried upon a trunk being ‘Congested’ in some form, or unavailable. Checking this box will force a failed call to always continue to the next configured trunk or destination even when the channel reports BUSY or INVALID NUMBER. |
Disable Trunk | Check this to disable this trunk in all routes where it is used. |
Dialed Number Manipulation Rules | These rules can manipulate the dialed number before sending it out this trunk. If no rule applies, the number is not changed. The original dialed number is passed down from the route where some manipulation may have already occurred. This trunk has the option to further manipulate the number. If the number matches the combined values in the prefix plus the match pattern boxes, the rule will be applied and all subsequent rules ignored. Upon a match, the prefix, if defined, will be stripped. Next the prepend will be inserted in front of the match pattern and the resulting number will be sent to the trunk. All fields are optional. Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the pattern in the prefix and match pattern boxes, this will be prepended before sending to the trunks. Prefix: Prefix to remove upon a successful match. If the dialed number match this plus the match pattern box, this prefix is removed before adding the optional prepend box and sending the results to the trunk. Match pattern: The dialed number will be compared against the prefix plus this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks after removing the prefix and appending the prepend digits You can completely replace a number by matching on the prefix only, replacing it with a prepend and leaving the match pattern blank. |
Dial Rules Wizards | Always dial with prefix is useful for VoIP trunks, where if a number is dialed as “5551234”, it can be converted to “16135551234”. Remove prefix from local numbers is useful for ZAP and DAHADI trunks, where if a local number is dialed as “1615551234”, it can be converted to “555-1234”. Setup directly assistance is useful to translate a call to directory assistance. Lookup numbers for local trunk This looks up your local number on www.localcallingguide.com (NA-only), and sets up so you can dial either 7or 10 digits (regardless of what your PSTN is) on a local trunk (where you have to dial 1+area code for long distance, but only 5551234 (7-difit dialing) or 6135551234 (10-digit dialing) local calls. Upload from CSV Upload pattern from a CSV file replacing existing entries. If there are no headers then the file must have 3 columns of pattern in the same order as in the GUI. You can also supply headers: prepend. Prefix and match pattern in the first raw. If there are less than 3 recognized headers than the remaining columns will be blank. |
Outbound Dial Prefix | The outbound dialing prefix is used to prefix a dialing string to all outbound calls placed on this trunk. For example, if this trunk is behind another PBX or is a Centrex line, then you would put 9 here to access an outbound line. Another common use is to prefix calls with 'w' on a POTS line that need time to obtain dial tone to avoid eating digits. Most users should leave this option blank. |
DUNDi Mapping | This is the name of the DUNDi mapping as defined in the [mappings] section of remote dundi.conf peers. This corresponds to the ‘include’ section of the peer details in the local dundi.conf file. This requires manual configuration of DUNDi to use this trunk. |
Figure 2-4-11 Add CUSTOM Trunk interface
Table 2-4-8 Definition of Add CUSTOM Trunk
Item | Definition |
Trunk Name | Descriptive Name for this trunk |
Outbound CallerID | CallerID for calls placed out on this trunk Format: <#######>. You can also use the format: “hidden” <#######> to hide the CallerID sent out over Digital lines if supported (SIP/IAX). |
CID Options | Determines what CIDs will be allowed out this trunk. IMPORTANT: EMERGENCY CIDs defined on an extension/device will ALWAYS be used if this trunk is part of an EMERGENCY Route regardless of these settings. Allow Any CID: all CIDs including foreign CIDS from forwarded external calls will be transmitted. Block Foreign CIDs: blocks any CID that is the result of a forwarded call from off the system. CIDs defined for extensions/users are transmitted. Remove CNAM: this will remove CNAM from any CID sent out this trunk Force Trunk CID: Always use the CID defined for this trunk except if part of any EMERGENCY Route with an EMERGENCY CID defined for the extension/device. Intra-Company Routes will always transmit an extension’s internal number and name. |
Maximum Channels | Controls the maximum number of outbound channels (simultaneous calls) that can be used on this trunk. Inbound calls are not counted against the maximum. Leave blank to specify no maximum. |
Asterisk Trunk Dial Options | Asterisk Dial command options to be used when calling out this trunk. To override the Advanced Settings default, check the box and then provide the required options for this trunk |
Continue if Busy | Normally the next trunk is only tried upon a trunk being ‘Congested’ in some form, or unavailable. Checking this box will force a failed call to always continue to the next configured trunk or destination even when the channel reports BUSY or INVALID NUMBER. |
Disable Trunk | Check this to disable this trunk in all routes where it is used. |
Dialed Number Manipulation Rules | These rules can manipulate the dialed number before sending it out this trunk. If no rule applies, the number is not changed. The original dialed number is passed down from the route where some manipulation may have already occurred. This trunk has the option to further manipulate the number. If the number matches the combined values in the prefix plus the match pattern boxes, the rule will be applied and all subsequent rules ignored. Upon a match, the prefix, if defined, will be stripped. Next the prepend will be inserted in front of the match pattern and the resulting number will be sent to the trunk. All fields are optional. Rules: X matches any digit from 0-9 Z matches any digit from 1-9 N matches any digit from 2-9 [1237-9] matches any digit in the brackets (example: 1,2,3,7,8,9). wildcard, matches one or more dialed digits Prepend: Digits to prepend to a successful match. If the dialed number matches the pattern in the prefix and match pattern boxes, this will be prepended before sending to the trunks. Prefix: Prefix to remove upon a successful match. If the dialed number match this plus the match pattern box, this prefix is removed before adding the optional prepend box and sending the results to the trunk. Match pattern: The dialed number will be compared against the prefix plus this match pattern. Upon a match, the match pattern portion of the dialed number will be sent to the trunks after removing the prefix and appending the prepend digits You can completely replace a number by matching on the prefix only, replacing it with a prepend and leaving the match pattern blank. |
Dial Rules Wizards | Always dial with prefix is useful for VoIP trunks, where if a number is dialed as “5551234”, it can be converted to “16135551234”. Remove prefix from local numbers is useful for ZAP and DAHADI trunks, where if a local number is dialed as “1615551234”, it can be converted to “555-1234”. Setup directly assistance is useful to translate a call to directory assistance. Lookup numbers for local trunk This looks up your local number on www.localcallingguide.com (NA-only), and sets up so you can dial either 7or 10 digits (regardless of what your PSTN is) on a local trunk (where you have to dial 1+area code for long distance, but only 5551234 (7-difit dialing) or 6135551234 (10-digit dialing) local calls. Upload from CSV Upload pattern from a CSV file replacing existing entries. If there are no headers then the file must have 3 columns of pattern in the same order as in the GUI. You can also supply headers: prepend. Prefix and match pattern in the first raw. If there are less than 3 recognized headers than the remaining columns will be blank. |
Outbound Dial Prefix | The outbound dialing prefix is used to prefix a dialing string to all outbound calls placed on this trunk. For example, if this trunk is behind another PBX or is a Centrex line, then you would put 9 here to access an outbound line. Another common use is to prefix calls with 'w' on a POTS line that need time to obtain dial tone to avoid eating digits. Most users should leave this option blank. |
Custom Dial String | Define the custom Dial String. Include the token $OUTNUM$ wherever the number to dial should go. Example: CAPI/XXXXXXXX/$OUTNUM$ H323/$OUTNUM$@XX.XX.XX.XX:XXXX Vpb/1-1/$OUTNUM$ |
Inbound Call Control
Inbound Routes
Figure 2-4-12 Add incoming Route interface
Table 2-4-9 Definition of Add incoming Route
Item | Definition |
Add incoming Route | |
Description | Provide a meaningful description of what this incoming route is |
DID Number | Define the expected DID Number if your trunk passes DID on incoming calls. Leaving this blank to match calls with any or no DID info. You can also use a pattern match (eg_2[345]X) to match a range of numbers. |
CallerID Number | Define the CallerID Number to be matched on incoming calls. Leave this field blank to match any or no CID info. In addition to standard dial sequences, you can also put Private, Blocked, Unknown, Restricted, Anonymous and Unavailable in order to catch these special cases if the Telco transmits them. |
CID Priority Route | This effects CID ONLY routes where no DID is specified. If checked, calls with this CID will routed to this route, even if there is a route to the DID that was called. Normal behavior is for the DID route to take the calls. If there is a specific DID/CID route for this CID, that route will still take the call when that DID is called. |
Options | |
Alert Info | ALERT_INFO can be used for distinctive ring with SIP devices. |
CID name prefix | You can optionally prefix the CallerID name. ie: If you prefix with “Sales:”, a call from john Doe would display as “Sales: John Doe” on the extension that ring |
Music On Hold | Set the MoH class that will be used for calls that come in on this route. For example, choose a type appropriate for routes coming in from a country which may have announcements in their language. |
Signal RINGING | Some devices or providers require RINGING to be sent before ANSWER. You’ll notice this happening if you can send calls directly to a phone, but if you send it to an IVR, it won’t connect the call. |
Pause Before Answer | An optional delay to wait before processing this route. Setting this value will delay the channel from answering the call. This may be handy if external fax equipment or security systems are installed in parallel and you would like them to be able to seize the line. |
Privacy | |
Privacy Manager | If no CallerID has been received, Privacy Manager will ask the caller to enter their phone number. If an user/extension has Call Screening enabled, the incoming caller will be prompted to say their name when the call reaches the user/extension. |
CID Lookup Source | |
Source | Source can be added in Caller Name Lookup Sources section. |
Fax Detect | |
Detect Faxes | Attempt to detect faxes on this DID. No: No attempts are made to auto-determine the call type; all calls sent to destination below. Use this option if this DID is used exclusively for voice OR fax. Yes: try to auto determine the type of call; route to the fax destination if call is a fax, otherwise send to regular destination. Use this option if you receive both voice and fax calls on this line. |
Language | |
Language | Allows you to set the language for this DID. |
Call Recording | |
Call Recording | Controls or overrides the call recording behavior for calls coming into this DID. Allow will honor the normal downstream call recording settings. Record on Answer starts recording when the call would otherwise be recorded ignoring any settings that say otherwise. Record Immediately will start recording right away capturing ringing, announcements, MoH, etc. never will disallow recording regardless of downstream settings. |
DAHDI Channel DIDs
Figure 2-4-13 Add DAHDI Channel interface
Table 2-4-910 Definition of Add DAHDI Channel
Item | Definition |
Channel | The DAHDI Channel number to map to a DID |
Description | A useful description this channel |
DID | The DID that this channel represents. The incoming call on this channel will be treated as if it came in with this DID and can be managed with Inbound Routing on DIDs |
Announcements
Figure 2-4-13 Announcements interface
Table 2-4-11 Definition of Announcements
Item | Definition |
Description | The name of this announcement |
Recording | Message to be played. To add additional recordings use the “System Recordings” MENU to the left |
Repeat | Key to press that will allow for the message to be replayed. If you choose this option there will be a short delay inserted after the message. If a longer delay is needed it should be incorporated into the recording. |
Allow Skip | If the caller is allowed to press a key to skip the message |
Return to IVR | If the announcement came from an IVR and this box is checked, the destination below will be ignored and instead it will be return to the calling IVR. Otherwise, the destination below will be taken. Don’t check if not using in this mode. The IVR return location will be to the last IVR in the call chain that was called so be careful to only check when needed. For example, if an IVR directs a call to another destination which eventually calls this announcement and this box is checked, it will return to that IVR which may not be the expected behavior. |
Don't Answer Channel | Check this to keep the channel from explicitly being answered. When checked, the message will be played and if the channel supports that. When not checked, the channel is answered followed by a 1 second delay. When using an announcement from an IVR or other sources that have already answered the channel, that 1 second delay may not be desired. |
Blacklist
Figure 2-4-14 Blacklist interface
Table 2-4-12 Definition of Blacklist
Item | Definition |
Number/CallerID | Enter the number/CallerID you want to block |
Description | Enter a description for the number you want to block |
Block Unknown/Blocked Caller ID | Check here to catch Unknown/Blocked CallerID |
CallerID Lookup Sources
Figure 2-4-15 CallerID Lookup Sources
Table 2-4-13 Definition of CallerID Lookup Sources
Item | Definition |
Source Description | Enter a description for this source |
Source type | Select the source type, you can choose between: OpenCNAM: Use OpenCNAM [http://www.opencnam.com/] Internal: use astdb as lookup source, use phonebook module to populate it ENUM: Use DNS to lookup caller names, it uses ENUM lookup zones as configured in eunm.conf HTTP: It executes an HTTP GET passing the caller number as argument to retrieve the correct name MySQL: It queries a MySQL database to retrieve caller name |
Cache results | Decide whether or not cache the results to astDB; it will overwrite present values. It does not affect Internal source behavior. |
Use Professional Tier | OpenCNAM’s Professional Tier lets you do as many real-time CNAM queries as you want, for a small fee. This is recommended for business users |
Call Flow Control
Figure 2-4-16 Call flow control interface
Table 2-4-14 Definition of Call flow control
Item | Definition |
Call Flow Toggle Feature Code Index | There are a total of 10 Feature code objects,0-9, each can control a call flow and be toggled using the call flow toggled feature code plus the index |
Description | Description for this Call Flow Toggle Control |
Current Mode | This will change the current state for this Call Flow Toggle Control, or set the initial state when creating a new one. |
Recording for Normal Mode | Message to be played in normal mode (Green/BLF off) To add additional recordings use the “System Recordings” MENU to the left |
Recording for Override Mode | Message to be played in override mode (Green/BLF off) To add additional recordings use the “System Recordings” MENU to the left |
Optional Password | You can optionally include a password to authenticate before toggling the call flow. If left blank anyone can use the feature code and it will be un-protected |
Normal Flow (Green/BLF off) | Destination to use when set to Normal Flow (Green/BLF off) mode |
Override Flow (Red/BLF on) | Destination to use when set to Override Flow (Red/BLF off) mode |
Follow Me
After setting up the extensions, you need to decide if you want UC300 to call another pre-arranged extension, if the extensions called do not answer. This is where we will do it as per the illustration below:
Select the PBX -> PBX Configuration -> Follow Me.
You will be presented with the following screen:
Figure 2-4-17 Follow Me interface
Select the extensions that you want to define (the extension selection is on the right of the screen).
Figure 2-4-18 Follow Me User interface
Table 2-4-15 Definition of Follow Me
Item | Definition |
Edit Follow Me | |
Disable | By default (not checked) any call to this extension will go to this Follow-Me instead, including directory calls by name from IVRs. If checked, calls will go only to the extension. However, destinations that specify FollowMe will come here. Checking this box is often used in conjunction with VmX Locater, where you want a call to ring the extension, and then only if the caller chooses to find you do you want it to come here. |
Initial Ring Time | This is the number of seconds to ring the primary extension prior to proceeding to the follow-me list. The extension can also be included in the follow-me list. A 0 setting will bypass this |
Ring Strategy | Ringallv2: ring Extension for duration set in Initial Ring Time, and then, while continuing call to extension, ring Follow-Me List for duration set in Ring Time. Ringall: ring Extension for duration set in Initial Ring Time, and then, terminate call to extension, ring Follow-Me List for duration set in Ring Time. Hunt: take turns ringing each available extension Memoryhunt: ring first extension in the list, then ring the 1st and 2nd extension, then ring 1st 2nd and 3rd extension in the list….etc. *-prim: these mode act as described above. However, if the primary extension (first in the list) is occupied, the other extensions will not be rung. If the primary is FreePBX DND, it won’t be rung. If the primary is FreePBX CF unconditional, then all will be rung Firstavailable: ring only the first available channel Firstavailable:: ring only the first channel which is not off hook-ignore CW |
Ring Time (max 60 sec) | Time in second that the phones will ring. For all hunt style ring strategies, this is the time for each iteration of phone(s) that are rung |
Follow-Me List | List extensions to ring, one per line, or use the Extension Quick Pick below. You can include an extension on a remote system, or an external number by suffixing a number with a pound (#). Ex:2448089# would dial 2448089 on the appropriate trunk (see Outbound Routing). |
Extension Quick Pick | Choose an extension to append to the end of the extension list above |
Announcement | Message to be played to the caller before dialing this group. To add additional recordings please use the “System Recordings” MENU to the left. |
Play Music On Hold | If you select a Music on Hold class to play, instead of ‘Ring’, they will hear that instead of Ringing while they are waiting for someone to pick up. |
CID Name Prefix | You can optionally prefix the Caller ID name when ringing extensions in this group. Ie: if you prefix with “Sales:”, a call from John Doe would display as “Sales: John Doe” on the extensions that ring |
Alert Info | You can optionally include an Alert Info which can create distinctive ring on SIP phones. |
Call Confirmation Configuration | |
Confirm Calls | Enable this if you’re calling external numbers that need confirmation, eg, a mobile phone may go to voicemail which pick up the call. Enabling this require the remote side push 1 on their phone before the calls is put through. This feature only works with the ringall/ringall-prim ring strategy. |
Remote Announce | Message to be played to the person RECEIVING the call, if ‘Confirm Calls” is enabled. To add additional recordings use the ‘System Recordings” MENU to the left |
Too-Late Announce | Message to be played to the person RECEIVING the call, if the call has already been accepted before they push 1. To add additional recordings use the ‘System Recordings” MENU to the left |
Change External CID Configuration | |
Mode | Default: Transmits the Caller CID if allowed by the trunk. Fixed CID Value: Always transmit the Fixed CID Value below. Outside Calls Fixed CID Value: Transmit the Fixed CID Value below on calls will continue to operate in default mode. Use Dialed Number: Transmit the number that was dialed as the CID for calls coming from outside. Internal extension to extension calls will continue to operate in default mode. There must be a DID on the inbound route for this. This will be BLOCKED on trunks that block foreign Caller ID Force Dialed Number: Transmit the number that was dialed as the CID for calls coming from outside. Internal extension to extension calls will be continue to operate in default mode. There must be a DID on the inbound route for this. This WILL be transmitted on trunks that block foreign CallerID |
Fixed CID Value | Fixed value to replace the CID with used with some of the modes above. Should be in a format of digits only with an option of E164 format using a leading “+”. |
IVR
Figure 2-4-20 IVR interface
Table 2-4-16 Definition of add IVR
Item | Definition |
IVR General Options | |
IVR Name | Name of this IVR |
IVR Description | Description of this ivr |
IVR Options (DTMF) | |
Announcement | Greeting to be played on entry to the IVR. |
Direct Dial | Provides options for callers to direct dial an extension. Direct dialing can be: l Completely disabled l Enabled for all extensions on a system |
Timeout | Amount of time to be considered a timeout |
Invalid Retries | Number of time to retry when receiving an invalid/unmatched response from the caller |
Invalid Retry Recording | Prompt to be played when an invalid/unmatched response is received, before prompt the caller to try again |
Append Announcement on Invalid | After playing Invalid Retry Recording the system will replay mail IVR Announcement |
Return on Invalid | Check this box to have this option return to a parent IVR if it was called from a parent IVR. If not, it will go to the chosen destination. The return path will be to any IVR that was in the call path prior to this IVR which could lead to strange result if there was an IVR called in the call path but not immediately before this. |
Invalid Recording | Prompt to be played before sending the caller to an alternate destination due to the caller pressing 0 or receiving the maximum amount of invalid/unmatched responses (as determined by Invalid Retries) |
Invalid Destination | Destination to send the call to after Invalid recording is played. |
Timeout Retries | Number of times to retry when no DTMF is heard and the IVR choice time out. |
Timeout Retry Recording | Prompt to be played when a timeout occurs, before prompting the caller to try again |
Append Announcement on Timeout | After playing the Timeout Retry Recording the system will replay the main IVR Announcement. |
Return on Timeout | Check this box to have this option return to a parent IVR if it was called from a parent IVR. If not, it will go to the chosen destination. The return path will be to any IVR that was in the call path prior to this IVR which could lead to strange result if there was an IVR called in the call path but not immediately before this |
Timeout Recording | Prompt to be played before sending the caller to an alternate destination due to the caller pressing 0 or receiving the maximum amount of invalid/unmatched responses(as determined by Invalid Retries) |
Timeout Destination | Destination to send the call to after Timeout Recording is played. |
Return to IVR after VM | If checked, upon exiting voicemail a caller will be returned to this IVR if they got a user voicemail |
IVR Entries | |
Return | Return to IVR |
Delete | Check this box to have this option return to a parent IVR if it was called from a parent IVR. If not, it will go to the chosen destination. The return path will be to any IVR that was in the call path prior to this IVR which could lead to strange result if there was an IVR called in the call path but immediately before this. |
Queue Priorities
Figure 2-4-21 Queue Priorities interface
Table 2-4-17 Definition of add Queue Priorities
Item | Definition |
Description | The descriptive name of this Queue Priority instance |
Priority | The Queue Priority set |
Queues
Figure 2-4-22 Queues interface
Table 2-4-18 Definition of add Queues
Item | Definition |
Add Queue | |
Queue Number | Use this number to dial into the queue, or transfer callers to this number to put them into the queue. Agents will dial this queue number plus* to log the queue, and this queue number plus** to log out the queue. For example, if the queue number is 123: 123*=log in 123**=log out |
Queue Name | Give the queue a brief name to help you identify it. |
Queue Password | You can require agents to enter a password before they can log in to this queue. This setting is optional. The password is only used when logging in with the legacy queue no* code. When using the toggle codes, you must use the Restrict Dynamic Agents option in conjunction with the Dynamic Members list to control access. |
Generate Device Hints | If checked, individual hints and dialplan will be generated for each SIP and IAX2 device that could be part of this queue. These are used in conjunction with programmable BLF status as to the current state, the format of this hints is *45ddd*qqq Where *45 is the currently define toggle feature code, ddd is the device number (typically the same as the extension number) and qqq is this queue’s number |
Call Confirm | If checked, any queue member that is actually an outside telephone number, or any extension Follow-Me or call forwarding that are pursued and leave the PBX will be forced into Call Confirmation mode where the member must acknowledge the call before it is answered and delivered. |
Call Confirm Announce | Announcement played to the Queue Member announcing the Queue call and requesting confirmation prior to answering. If set to default, the standard call confirmation default message will be played unless the number is reached through a Follow-Me and this is an alternate message provided in the Follow-Me. This message will override any other message specified. To add additional recordings please use the “System Recordings” MENU. |
CID Name Prefix | You can optionally prefix the CallerID name of callers to the queue. ie: If you prefix with “Sales:”, a call from John Doe would display as “Sales: John Doe” on the extensions that ring. |
Wait Time Prefix | When set to Yes, the CID Name will be prefix with the total wait time in the queue so the answering agent is aware how long they have waited. It will be rounded to the nearest minute, in the form of Mnn: where nn is the number of minutes. If the call is subsequently transferred, the wait time will reflect the time since it first entered the queue or reset if the call is transferred to another queue with this feature set. |
Alert Info | ALERT_INFO can be used for distinctive ring with SIP device. |
Static Agents | Static agents are extensions that are assumed to always be on the queue. Static agents do not need to 'log in' to the queue, and cannot 'log out' of the queue. List extensions to ring, one per line. You can include an extension on a remote system, or an external number (Outbound Routing must contain a valid route for external numbers). You can put a "," after the agent followed by a penalty value, see Asterisk documentation concerning penalties. An advanced mode has been added which allows you to prefix an agent number with S, X, Z, D or A. This will force the agent number to be dialed as an Asterisk device of type SIP, IAX2, ZAP, DAHDi or Agent respectively. This mode is for advanced users and can cause known issues in FreePBX as you are by-passing the normal dialplan. If your 'Agent Restrictions' are not set to 'Extension Only' you will have problems with subsequent transfers to voicemail and other issues may also exist. (Channel Agent is deprecated starting with Asterisk 1.4 and gone in 1.6+.) |
Extension Quick Pick | Choose an extension to append to the end of the static agents list above. |
Dynamic Members | Dynamic Members are extensions or callback numbers that can log in and out of the queue. When a member logs in to a queue, their penalty in the queue will be as specified here. Extensions included here will NOT automatically be logged in to the queue. |
Extension Quick Pick | Chose an extension to append to the end of the dynamic member list above. |
Restrict Dynamic Agents | Restrict dynamic queue member logins to only those listed in the Dynamic Members list above. When set to Yes, members not listed will be DENIED ACCESS to the queue. |
Agent Restrictions | When set to ‘Call as Dialed’ the queue will call an extension just as if the queue were another user. Any Follow-Me or Call Forward states active on the extension will result in the queue call following these call paths. This behavior has been the standard queue behavior on past FreePBX versions. When set to ‘No Follow-Me or Call Forward’, all agents that are extensions on the system will be limited to ring their extensions only. Follow-Me and Call Forward settings will be ignored. Any other agent will be called as dialed. This behavior is similar to how extensions are dialed in ringgroups When set to ‘Extensions Only’ the queue will dial Extensions as described for ‘No Follow –Me or Call Forward’. Any other number entered for an agent that is NOT a valid extension will be ignored. No error checking is provided when entering a static agent or when logging on as a dynamic agent, the call will simply be blocked when the queue tries to call it. For dynamic agents, see the ‘Agent Regex filter’ to provide some validation. |
General Queue Options | |
Ring Strategy | Ringall: ring all available agents until one answers (default) Leastrecent: ring agent which was least recently called by this queue Fewestcalls: ring the agent with fewest completed calls from this queue Random: ring random agent Rrmemory: round robin with memory, remember where we left off last ring pass Rrordered: same as rrmemory, except the queue member where order from config file is preserved Linear: rings agents in the order specified, for dynamic agents in the order they logged in Wrandom: random using the member’s penalty as a weighting factor, see asterisk documentation for specifics. |
Autofill | Starting with Asterisk 1.4, if this is checked, and multiple agents are available, Asterisk will send one call to each waiting agent(depending on the ring strategy). Otherwise, it will hold all calls while it tries to find an agent for the top call in the queue making other calls wait. This was the behavior in Asterisk 1.2 and has no effect in 1.2. See Asterisk documentation for more details of this feature. |
Skip Busy Agents | When set to 'Yes' agents who are on an occupied phone will be skipped as if the line were returning busy. This means that Call Waiting or multi-line phones will not be presented with the call and in the various hunt style ring strategies, the next agent will be attempted. When set to 'Yes + (ringinuse=no)' the queue configuration flag 'ringinuse=no' is set for this queue in addition to the phone's device status being monitored. This results in the queue tracking remote agents (agents who are a remote PSTN phone, called through Follow-Me, and other means) as well as PBX connected agents, so the queue will not attempt to send another call if they are already on a call from any queue. When set to 'Queue calls only (ringinuse=no)' the queue configuration flag 'ringinuse=no' is set for this queue also but the device status of locally connected agents is not monitored. The behavior is to limit an agent belonging to one or more queues to a single queue call. If they are occupied from other calls, such as outbound calls they initiated, the queue will consider them available and ring them since the device state is not monitored with this option. WARNING: When using the settings that set the 'ringinuse=no' flag, there is a NEGATIVE side effect. An agent who transfers a queue call will remain unavailable by any queue until that call is terminated as the call still appears as 'inuse' to the queue UNLESS 'Agent Restrictions' is set to 'Extensions Only'. |
Queue Weight | Gives queue a ‘weight’ option, to ensure calls waiting in a higher priority queue will deliver its calls first if there are agents common to both queues. |
Music on Hold Class | Music (MoH) played to the caller while they wait in line for an available agent. Choose “inherit” if you want the MoH class to be what is currently selected, such as by the inbound route. MoH Only will play music until the agent answers. Agent Ringing will play MoH until an agent’s phone is presented with the call and is ringing. If they don’t answer MoH will return. Ring only makes callers hear a ringing tone instead of MoH ignoring any MoH class selected as well as any configured periodic announcements. This music is defined in the “Music on Hold” Menu. |
Join Announcement | Announcement played to callers prior to joining the queue. This can be skipped if there are agents ready to answer a call (meaning they still may be wrapping up from a previous call) or when they are free to answer the call right now. To add additional recordings please use the “System Recordings” MENU. |
Call Recording | Incoming calls to agents can be recorded. (saved to /var/spool/asterisk/monitor) |
Recording Mode | Choose to ‘Include Hold Time’ in the recording so it starts as soon as they enter the queue, or to defer recording until ‘After Answered’ and the call is bridged with a queue member. |
Caller Volume Adjustment | Adjust the recording volume of the caller. |
Agent Volume Adjustment | Adjust the recording volume of the queue member (Agent). |
Mark calls answered elsewhere | Enabling this option, all calls are marked as ‘answered elsewhere’ when cancelled. The effect is that missed queue calls are *not* shown on the phone(if the phone support it) |
Timing & Agent Options | |
Max Wait Time | The maximum number of seconds a caller can wait in a queue before being pulled out.(0 for unlimited). |
Max Wait Time Mode | Asterisk timeoutpriority. In ‘Strict’ mode, when the ‘Max Wait Time’ of a caller is hit, they will be pulled out of the queue immediately. In ‘Loose’ mode, if a queue stops ringing with this call, then we will wait until the queue stops ringing this queue number or otherwise the call is rejected by the queue member before taking the caller out of the queue. This means that the ‘Max Wait Time’ could be as long as ‘Max Wait Time’+’Agent Timeout’ combined. |
Agent Timeout | The number of seconds an agent’s phone can ring before we consider it a timeout. Unlimited or other timeout values may still be limited by system ringtime or individual extension defaults. |
Agent Timeout Restart | If timeout restart is set to yes, then the time out for an agent to answer is reset if a BUSY or CONGESTION is received. This can be useful if agents are able to cancel a call with reject or similar |
Retry | The number of seconds we wait before trying all the phones again. Choosing “No Retry” will exit the queue and go to the fail-over destination as soon as the first attempted agent time-out, additional agents will not be attempted. |
Wrap-Up-Time | After a successful call, how many seconds to wait before sending a potentially free agent another call (default is 0, or no delay) If using Asterisk 1.6+, you can also set the ‘Honor Wrapup Time Across Queues setting (Asterisk: shared_lastcall) on the Advanced Settings page so that this is honored across queues for members logged on to multiple queues. |
Member Delay | If you wish to have a delay before the member is connected to the caller (or before the member hears any announcement messages), set this to the number of seconds to delay. |
Agent Announcement | Announcement played to the Agent prior to bridging in the caller. Example : ”the Following call is from the Sales Queue” or “This call is from the Technical Support Queue”. To add additional recordings please use the “System Recordings” MENU. Compound recordings composed of 2 or more sound files are not displayed as options since this feature can not accept such recordings. |
Report Hold Time | If you wish to report the caller’s hold time to the member before they are connected to the caller, set this to yes. |
Auto Pause | Auto Pause an agent in this queue (or all queues they are a member of ) if they don’t answer a call. Specific behavior can be modified by the Auto Pause Delay as well Auto Pause Busy/Unavailable settings if supported on this version of Asterisk. |
Auto Pause on Busy | When set to Yes agents devices that report busy upon a call attempt will be considered as a missed call and auto paused immediately or after the auto pause delay if configured |
Auto Pause on Unavailable | When set to Yes agents devices that report congestion upon a call attempt will be considered as a missed call and paused immediately or after that auto pause delay if configured |
Auto Pause Delay | This setting will delay the auto pause of an agent by auto pause delay seconds from when it last took a call. For example, if this were set to 120 seconds, and a new call is presented to the agent 90 seconds after they last took a call, will not be auto paused if they don’t answer the call. If presented with a call 120 seconds or later after answering the last calls, this will have no effect. |
Capacity Options | |
Max Callers | Maximum number of people waiting in the queue (0 for unlimited ) |
Join Empty | Determines if new callers will be admitted to the Queue, if not, the failover destination will be immediately pursued. The options include: l Yes Always allows the caller to join the Queue. l Strict Same as Yes but more strict. Simply speaking, if no agent could answer the phone then don’t admit them. If agents are infuse or ringing someone else, caller will still be admitted. l Ultra Strict Same as Strict plus a queue member must be able to answer the phone ‘now’ to let them in. simply speaking, any ‘available’ agents that could answer but are currently on the phone or ringing on behalf of another caller will be considered unavailable. l No Callers will not be admitted if all agents are paused, show an invalid status for their device, or have penalty values less than QUEUE_MAX_PENALTY (not currently set in FreePBX dialplan). l Loose Same as No except Callers will be admitted if there are paused agents who could become available. |
Leave Empty | Determines if callers should be exited prematurely from the queue in situations where it appears no one is currently available to take the call. The options include: l Yes Callers will exit if all agents are paused, show an invalid state for their device or have penalty values less than QUEUE_MAX_PENALTY(not currently set in FreePBX dialplan) l Strict Same as Yes but more strict. Simply speaking, if no agent could answer the phone then have them leave the queue. If agents are inuse or ringing someone else, caller will still be held. l Ultra Strict Same as Strict plus a queue member must be able to answer the phone ‘now’ to let them remain. simply speaking, any ‘available’ agents that could answer but are currently on the phone or ringing on behalf of another caller will be considered unavailable. l Loose Same as No except Callers will remain in the queue, if there are paused agents who could become available. l No never have a caller leave the Queue until the Max Wait Time has expired. |
Penalty Members Limit | Asterisk: penalty members limit. A limit can be set to disregard penalty settings, allowing all members to be tried, when the queue has too fewer members. No penalty will be weight in if there are only X or fewer queue members. |
Caller Position Announcements | |
Frequency | How often to announce queue position and estimated holdtime (0 to Dis able Announcements). |
Announce Position | Announce position of caller in the queue |
Announce Hold Time | Should we include estimated hold time in position announcements? Either yes, no, or only once; hold time will not be announced if <1 minute. |
Periodic Announcements | |
IVR Break Out Menu | You can optionally present an existing IVR as a ‘break out’ menu. This IVR must only contain single-digit ‘dialed options’. The recording set for the IVR will be played at intervals specified in ‘Repeat Frequency’, below. |
Repeat Frequency | How often to announce a voice menu to the caller (0 disable Announcements) |
Events, Stats and Advanced | |
Event When Called | When this option is set to YES, the following manager events will be generated: AgentCalled, AgentDump, AgentConnect and AgentComplete. |
Member Status Event | When set to YES, the following manager event will be generated: QueueMemberStatus. |
Service Level | Used for service level statistics (calls answered within service level time frame) |
Agent Regex Filter | Provides an optional regex expression that will be applied against the agent callback number. If the callback number does not pass the regex filter then it will be treated as invalid. This can be used to restrict agents to extensions within a range, not allow callbacks to include keys like *, or any other use that may be appropriate. An example input might be: ^([2-4][0-9]{3})$ This would restrict agents to extensions 2000-4999. Or ^([0-9]+)$ would allow any number of any length, but restrict the * key. WARNING: make sure you understand what you are doing or otherwise leave this blank! |
Reset Queue Stats | |
Run | Select how often to reset queue stats. The following schedule will be followed for all but custom: Hourly Run once an hour, beginning of hour Daily Run once a day, at midnight Weekly Run once a week, midnight on Sun Monthly Run once a month, midnight, first of month Annually Run once a year, midnight, Jan.1 Reboot Run at startup of the server OP of the cron deamon (i.e. after every service cron restart ) If Randomize is selected, a similar frequency will be followed, only the exact times will randomized (avoiding peak business hours, when possible). Please note: randomized schedules will be rescheduled (randomly) every time ANY backup is saved. |
Ring Groups
A ring group is a group of extensions that will ring when there is an external incoming call. You can even put your Mobile Phone number in the ring group if you want to. The 0400123456# is the Medical Centre’s Manager phone (see illustration below). For the mobile phone to work, you must have the appropriate route and trunk set up.
You may not want a ring group – it’s entirely up to you. If you don’t require a ring group, you may ignore this section.
When there is an incoming call to the ring group, the phones nominated in the selected group will ring. You may select different ring group for each of the incoming trunk or you may nominate the same group for all the trunks, in which case you will only need to define only one ring group.
The ring group screen is illustrated below:
Figure 2-4-23 Ring groups interface
Table 2-4-19 Definition of add Ring groups interface
Item | Definition |
Add Ring Group | |
Ring-Group Number | The number users will dial to ring extensions in this ring group |
Group Description | Provide a descriptive title for this Ring Group. |
Ring Strategy | Ringall : Ring all available channels until one answers (default) Hunt: Take turns ringing each available extension Memoryhunt: Ring first extension in the list, then ring the 1 st and 2 nd extension, then ring 1 st and 2nd and 3 rd extension in the list…etc. *-prim: there mode act as described above. However, if the primary extension (first in list) is occupied, the other extensions will not be rung. If the primary is FreePBX CF unconditional, then all will be rung First available: ring only the first available channel Firstnotonphone: ring only the first channel which is not offhook-ignored CW. |
Ring Time (max 300 sec) | Time in seconds that the phones will ring. For all hunt style ring strategies, this is the time for each iteration of phone(s) that are rung. |
Extension List | List extensions to ring, one per line, or use the Extension Quick Pick below to insert them here. You can include an extension on a remote system, or an external number by suffixing a number with a ‘#’. Ex:2448089# would dial 2448089 on the appropriate trunk (see outbound routing) Extension without a ‘#’ will not ring a user’s Follow-Me. To dial Follow-Me, Queues and other numbers that are not extensions, put a ‘#’ at the end. |
Extension Quick Pick | Choose an extension to append to the end of the extension list above. |
Announcement | Message to be played to the caller before dialing this group. To add additional recordings please use the “System Recordings” MENU to the left. |
Play Music On Hold | If you select a music on hold class to play, instead of ‘Ring’, they will hear that instead of Ringing while they waiting for someone to pick up. |
CID Name Prefix | You can optionally prefix the callerid name when ringing extensions in this group, ie: If you prefix with “Sales:”, a call from John Doe would display as “Sales: John Doe” on the extensions that ring. |
Alert Info | ALERT_INFO can be used for distinctive ring with SIP devices. |
Ignore CF Settings | When checked, agents who attempt to Call Forward will be ignored, this applies to CF, CFU and CFB. Extensions entered with ‘#’ at the end, for example to access the extension’s Follow-Me, might not honor this setting. |
Skip Busy Agent | When checked, agents who are on an occupied phone will skipped as if the line were returning busy. This means that call waiting or multi-line phones will not be presented with the call and in the various hunt style ring strategies, the next agent will be attempted. |
Enable Call Pickup | Checking this will allow calls to the ring group to be picked up with the directed call pickup feature using the group number. When not checked, individual extensions that are part of the group can still be picked up by doing a directed call picked to the ringing extension, which works whether or not this is checked. |
Confirm Calls | Enable this if you’re calling external numbers that need confirmation-eg, a mobile phone may go to voicemail which will pick up the call. Enabling this requires the remote side push 1 on their phone before the call is put through. This feature only works with the ringall ring strategy. |
Remote Announce | Message to be played to the person RECEIVING the call, if ‘Confirm Calls’ is enabled. To add additional recordings use the “System Recordings” MENU to the left |
Too-Late Announce | Message to be played to the person RECEIVING the call, if the call has already been accepted before they push 1. To add additional recordings use the “System Recordings” MENU to the left |
Change External CID Configuration | |
Mode | Default: Transmits the Callers CID if allowed by the trunk. Fixed CID Value: Always transmit the Fixed CID Value below. Outside Calls Fixed CID Value: Transmit the Fixed CID Value below on calls will continue to operate in default mode. Use Dialed Number: Transmit the number that was dialed as the CID for calls coming from outside. Internal extension to extension calls will continue to operate in default mode. There must be a DID on the inbound route for this. This will be BLOCKED on trunks that block foreign Caller ID Force Dialed Number: Transmit the number that was dialed as the CID for calls coming from outside. Internal extension to extension calls will be continue to operate in default mode. There must be a DID on the inbound route for this. This WILL be transmitted on trunks that block foreign CallerID |
Fixed CID Value | Fixed value to replace the CID with used with some of the modes above. Should be in a format of digits only with an option of E164 format using a leading “+”. |
Call Recording | |
Record Calls | You can always record calls that come into ring group, never record them, or allow the extension that answers to do on-demand recording. If recording is denied then one-touch on demand recording will be blocked. |
Time Conditions
You can create various time conditions and use these time conditions in conjunction with your Inbound Route to individualise each of the incoming trunk’s behaviour.
Figure 2-4-24 Time Conditions interface
Table 2-4-20 Definition of add Time Conditions
Item | Definition |
Time Condition name | Give this Time Condition a brief name to help you identify it. |
Time Group | Select a time group created under Time Groups. Matching times will be sent to matching destination. If no group is selected, call will always go to no-match destination. |
Time Groups
Figure 2-4-25 Time Groups interface
Internal Options & Configuration
Conferences
Figure 2-4-26 Conferences interface
Table 2-4-21 Definition of add Conference
Item | Definition |
Add Conference | |
Conference Number | Use this number to dial into the conference. |
Conference Name | Give this conference a brief name to help you identify it. |
User PIN | You can require callers to enter a password before they can enter this conference. This setting is optional. If either PIN is entered, the user will be prompted to enter a PIN. |
Admin PIN | Enter a PIN number for the admin user. This setting is optional unless the ‘leader wait’ option is in use, then this PIN will identify the leader. |
Conference Options | |
Join Message | Message to be played to the caller before joining the conference. To add additional recordings use the “System Recordings” MENU to the left |
Leader Wait | Wait until the conference leader (admin user) arrives before starting the conference |
Talker Optimization | Turn on talker optimization. With talker optimization, Asterisk treats talkers who are not speaking as being muted, meaning that no encoding is done on transmission and that received audio that is not registered as talking is omitted, causing no buildup in background noise. |
Talker Detection | Sets talker detection. Asterisk will sends events on the Manager Interface identifying the channel that is talking. The talker will also be identified on the output of the meetme list CLT command. |
Quiet Mode | Quiet mode (do not play enter/leave sounds) |
User Count | Announce user(s) count on joining conference |
User join/leave | Announce user join/leave |
Music on Hold | Enable Music on Hold when the conference has single caller |
Music on Hold Class | Music (or Commercial) played to the caller while they wait line for the conference to start. Choose “inherit” if you want the MoH class to be what is currently selected, such as by the inbound route. This music is defined in the “Music on Hold” to the left. |
Allow Menu | Present Menu (user or admin) when ‘*’ is received (‘send’ to menu). |
Record Conference | Record the conference call |
Maximum Participants | Maximum Number of users allowed to join this conference. |
Mute on Join | Mute everyone when they initially join the conference. Please note that if you do not have ‘Leader Wait’ set to yes you must have ‘Allow Menu’ set to Yes to unmute yourself. |
Languages
Figure 2-4-27 Languages interface
Table 2-4-22 Definition of add Language
Item | Definition |
Description | The descriptive name of this language instance. For example “French Main IVR” |
Language Code | The Asterisk language code you want to change to. For example “fr” for French, “de” for German. |
Misc Applications
Figure 2-4-28 Misc Applications interface
Table 2-4-23 Definition of add Misc Application
Item | Definition |
Description | The name of this application |
Feature Code | The feature code/extension users can dial to access this application. This can also be modified on the Feature Codes page. |
Feature Status | If this code is enabled or not. |
Misc Destinations
Figure 2-4-29 Misc Destinations interface
Table 2-4-24 Definition of add Misc Destination
Item | Definition |
Description | Give this Misc Destination a brief name to help you identify it. |
Dial | Enter the number this destination will simulate dialing, exactly as you would dial it from an internal phone. When you route a call to this destination, it will be as if the caller dialed this number from an internal phone. |
Music on Hold
The volume adjustment is a linear value. Since loudness is logarithmic, the linear lever will be less of an adjustment. You should test out the installed music to assure it is at the correct volume. This feature will convert MP3 files to WAV files. If you do not have mpg123 installed, you can set the parameter: Convert Music Files to WAV to false in Advanced Settings.
Figure 2-4-30 Music on Hold interfac
PIN Sets
Figure 2-4-31 PIN Sets interface
Table 2-4-25 Definition of add PIN Set
Item | Definition |
Record In CDR | Select this box if you would like to record the PIN in the call detail records when used. |
PIN List | Enter a list of one more PINs. One PIN per line. |
Paging and Intercom
Figure 2-4-32 Paging and Intercom interface
Parking Lot
Figure 2-4-33 Parking Lot interface
System Recordings
Figure 2-4-34 System Recordings interface
Voicemail Blasting
Figure 2-4-35 Voicemail Blasting interface
Table 2-4-26 Definition of add VMBlast Group
Item | Definition |
VMBlast Number | The number users will dial to voicemail boxes in this VMBlast group |
Group Description | Provide a descriptive title for this VMBlast Group. |
Audio Label | Paly this message to the caller so they can confirm they have dialed the proper voice mail group number, or have the system simply read the group number. |
Optional Password | You can optionally include a password to authenticate before providing access to this group voicemail list. |
Voicemail Box List | Select voice mail boxes to add to this group. Use Ctrl key to select multiple. |
Default VMBlast Group | Each PBX system cam have a single Default VOICEMAIL Blast Group. If specified, extensions can be automatically added (or removed) from this default group in the Extensions (or Users) tab. Making this group the default will uncheck the option from the current default group if specified. |
Remote Access
Callback
Callback is where you make a call to your IP-PBX and when reached you will be disconnected, but it does not end there. Your PBX will in turn call your mobile and reconnect you relieving you of the cost of the lengthy Mobile phone call that you will otherwise be up for.
Let’s take this step by step.
- 1. Setup DISA
Figure 2-4-36 click DISA
a. DISA name: MyMobile
b. Response Timeout:10
c. Digit Timeout:5
d. Caller ID:0400123456 (My Mobile Number)
e. Context: from-internal
Figure 2-4-37 Set on DISA
Click Submit Changes button.
- 2. Setup Callback
a. Callback Description:MyMobile
b. Callback Number: 0400123456 (My mobile Number)
c. Delay Before Callback:10
d. Destination after Callback: IVR – Residence (or Office IVR)
Figure 2-4-38 Callback interface
Click Submit Changes button
3. Inbound Routes
a. Description: Callback-MyMobile
b. DID Number:61247324100 (My DID number)
c. Caller ID Number: 0400123456 (My mobile Number)
d. Set Destination to: Callback - MyMobile
Click Submit Changes button then Click on the bar at the top & follow on screen prompts
Now enable send caller ID on your mobile and call your DID number. When connected you will get one beep and then followed by silence. Hang up your mobile and wait for approximately10 seconds and your mobile will ring.
When you answer your mobile, you will hear your IVR playing with the various options. One of the silent options in my IVR is DISA. If I need to make an external call using my PBX. If I know the option and select it, I will be then get DISA where I can make an external call at no cost to my Mobile.
Table 2-4-27 Definition of add Callback
Item | Definition |
Callback Description | Enter a description for this callback |
Callback Number | Optional: Enter the number to dial for the callback. Leave this blank to just dial the incoming CallerID Number. |
Delay Before Callback | Optional: Enter the number of seconds the system should wait before calling back. |
DISA
DISA (Direct Inward System Access) allows you to dial in from outside to the Asterisk switch (PBX) to obtain an "internal" system dial tone. You can place calls from it as if they were placed from within.
Figure 2-4-39 DISA interface
When you choose the DISA option to call a number, you will be greeted with “Please enter your password followed by the pound key” and after entering your password, you will then get a dial tone. You may start dialing the telephone number.
Table 2-4-28 Definition of add DISA
Item | Definition |
DISA name | Give this DISA a brief name to help you identify it. |
PIN | The user will be prompted for this number. If you wish to have multiple PIN’s, separate them with commas. |
Response Timeout | The maximum amount of time it will before hanging up if the user has dialed an incomplete or invalid number. Default of 10 seconds. |
Digit Timeout | The maximum amount of time permitted between digits when the user is typing in an extension. Default of 5. |
Require Confirmation | Require Confirmation before prompting for password. Used when your PSTN connection appears to answer the call immediately. |
Caller ID | (Optional ) When using this DISA, the users CallerID will be set to this. Format is “User Name” <5551234> |
Context | (Experts Only)Set the context that calls will originate from. Leaving this as from-internal unless you know what you’re doing. |
Allow Hangup | Allow the current call to be disconnected and dial tone presented for a new call by pressing the Handup feature code: ** while in a call. |
Caller ID Override | Determine if we keep the Caller ID being presented or if we override it. Default is Enable. |
2.4.2 Operator Panel
The option "Operator Panel" of the menu "PBX" in UC300 allows managing the telephony operations. You can control inbound calls, outbound calls, the order in which the calls are taken, the area that is designated to attend a call, etc.
This module is useful for receptionists who have a general view of the queues, conferences, parking lots, internal extensions, trunks. Here the receptionist can start a call or transfer a call by dragging one extension to another, or include several extension to a conference room, or a queue. The receptionist can also see the busy extensions, the elapsed time and the caller ID.
Figure 2-4-40 Operator Panel interface
2.4.3 Voicemails
The option "Voicemail" of the Menu “PBX” in UC300 lets us view a list with details of the voicemails for the extension of the logged user.
Figure 2-4-41 Voicemails interface
The report will change depending on the values of the filter:
Parameter | Description |
Start Date | Start date for the selection of voicemails. |
End Date | End date for the selection of voicemails. |
To delete a voicemail, just select the voicemail from the list and click on "Delete" button.
2.4.4 Calls Recordings
The option "Calls Recordings" of the Menu "PBX" in UC300 lets us view a list with details of all recorded calls for the extension associated to the connected user. The administrator account can see all the recordings.
Figure 2-4-42 Calls Recordings interface
2.4.5 Batch Configurations
2.4.5.1 Endpoint Configurator
The "Endpoint Configurator" module enables automatic remote configuration of supported endpoints. With this module, the UC300 administrator can point supported endpoints to the UC300 as their telephony server.
Figure 2-4-43 Endpoint Configurator interface
Interface description
Main listing
This is the listing of all endpoints that have been detected or entered. Unlike the old implementation, any endpoints detected or uploaded in past sessions will be kept and displayed until they are explicitly erased. The main listing contains the following columns:
Table2-4-29 Description of Interface description
Item | Description |
Status | This displays the status of the endpoint as one or more icons. The available flags are as follows: Scroll icon: the endpoint has not been scanned, but rather defined in an upload. Disk icon: the endpoint configuration has been updated in the database but not yet applied to its configuration files. Person icon: the endpoint has at least one endpoint assigned. |
MAC Address | This is the main identifier for the endpoint. Configurations in the database and uploaded files are considered to refer to the same endpoint if they reference the same MAC address. |
Current IP | If the endpoint was detected through a scan, this field will show the IP at which the endpoint was found. This field is a link to the HTTP configuration interface (if supported) of the phone. |
Manufacturer | This displays the detected manufacturer of the endpoint. |
Model | This displays the detected model of the endpoint. Since automatic model detection is not (yet) implemented for some manufacturers, this field allows the user to correct the model via a drop-down list. Accurate model detection is required for many other features (such as account assignment) to work. |
Options | This link displays a modal dialog on which common options for the endpoint can be manually configured. |
Endpoint scan toolbar button
This widget contains a textbox with a network/netmask definition, and a magnifying glass icon. By default, the network definition will be filled with the network definition of the first ethernet interface of the Elastix server. The user may correct this definition to restrict the scan, and then click on the icon to start the scan. When scanning, the toolbar will change to a spinning icon and a Cancel button. As endpoints are detected, they will be added to the main listing, along with their detected manufacturer and model. The toolbar will revert to its default state when the scan is done, or if the scan is aborted with the Cancel button.
Endpoint configuration toolbar button
Clicking on this icon will start applying the configuration for all selected endpoints (all endpoints for which the checkbox is set). When applying the configuration, the toolbar will change to a progress bar. As endpoints are configured, the progress bar will update, and the toolbar will revert to the default state when the configuration is done. During configuration, a log is generated, and can be viewed by clicking on the Configuration Log toolbar button.
Configuration Log toolbar button
Clicking on this icon will open a modal dialog in which a log of the last configuration run will be shown. This is useful for diagnosing issues with the module failing to configure an endpoint.
Remove configuration toolbar button
Clicking on this icon will (after a confirmation dialog) remove the database records for the selected endpoints, as well as any generated configuration files for these endpoints. It will NOT, however, contact the endpoints themselves in any way.
Download toolbar button
Clicking on this icon will display a list of links to download the list of endpoints stored on the database, in three different formats. The supported formats are:
- CSV (Legacy). This is the format used by the old Endpoint Configurator.
- XML. This format allows the definition of endpoints with multiple accounts and properties, as an XML document.
- CSV (Nested). This format can be generated by careful editing in a spreadsheet, and uses indentation to group multiple accounts and properties per endpoint.
Upload toolbar button
Clicking on this icon will display a small dialog in which the user may specify an endpoint list file to upload to the server. The file format is automatically detected.
2.4.5.2 Batch of Extensions
The option "Batch of Extensions" from the menu "PBX" in UC300 allows creating extensions from a CSV file. Also you can download a CSV file with all the extensions that are currently configured in UC300. This makes it easy the migration of data.
Figure 2-4-44 Batch of Extensions interface
To download a CSV file with all the extensions created in UC300, click on the "Download" link and save the file into your local hard drive.
To upload a CSV with the extensions you want to create, click on "Examine" button, select the CSV file and click on "Upload CSV File" button.
Make sure the following indications are taken into account:
- Duplicated extensions are not allowed.
- The first line of the CSV file must contain the headers of the columns.
- The file must have at minimum four columns.
- This type of file can be created and opened with any text editor or spreadsheets such as Open Office Calc, Excel, etc.
- The separator of the columns is the comma.
2.4.6 Conference
The option "Conference" in UC300 allows creating and managing conferences at any time. Here you can see all the current conferences. Use the filter to find past and future conferences.
Figure 2-4-45 Conference interface
Creating a new Conference
To create a new conference click on button and fill out the required fields. If you want to take control of a static conference created from the module "PBX Configuration", replace the "Conference Number" by the number of the static conference.
Figure 2-4-46 Create new Conference interface
Below a description of each parameter:
Table 2-4-30 Description of conference
Item | Mandatory | Description |
Conference Name | Yes | This is the name of the conference. It helps to identify it. |
Moderator PIN | No | A key that the moderator has to enter to join to the conference. |
User PIN | No | A key that the user has to enter to join to the conference. |
Start Time | Yes | Select the date and time in which the conference will start. |
Conference Number | Yes | When you create a conference a random number is generated automatically in this field. This number identifies the conference and you can change it if you want but make sure it is not being used by another conference. |
Conference Owner | No | The user who is in charge of the conference. |
Moderator Options | No | Different options for the moderator. |
User Options | No | Different options for the user. |
Duration (HH:MM) | No | The duration of the conference |
Max Participants | Yes | The number of users that can participate in the conference simultaneously. |
Invite a participant
There are two ways to join a user to the conference:
- Select the extension number from the dropdown list and click on "Invite Caller". Immediately the user's phone will start to ring. When the user answers the phone he will be part of the conference.
- Call to 5555 and when you are asked, enter the conference number followed by the pound key (#).
If you want to silence a user, just select the checkbox from the mute column and click on "Mute". If you want to terminate a call, select the checkbox from Kick column and click on "Kick".
If you want to terminate all the calls, just click on "Kick All" button.
To update the list of the current participants of the conference click on "Update" button. If you want to go back to the list of conferences, click on "Cancel" button (This will not cancel the current conference).
2.4.7 Tools
2.4.7.1 Asterisk-Cli
The option “Asterisk-Cli” of the Menu “PBX” in UC300 lets us execute Asterisk commands.
Figure 2-4-47 Asterisk-Cli interface
To execute a command, input the same in the Command field and click on the button.
2.4.7.2 Asterisk File Editor
The option "Asterisk File Editor" of the Menu "PBX" in UC300 lets us edit easily the configuration files of UC300 . The path of the files you can modify is /etc/asterisk/.
Figure 2-4-48 Asterisk File Editor interface
Editing a file
You can find a file by entering the name in the filter field. To edit the file, click on the name to go to the edit mode. Click on "Save" button to save changes and "Reload Asterisk" if necessary.
Figure 2-4-49 Editing a file interface
Creating a file
Also you can create a new file by clicking on "New File" button. This file will be created with the extension ".conf" in /etc/asterisk/.
Figure 2-4-50 Create a file interface
2.4.7.3 Text to Wav
The option "Text to Wav" of the Menu "PBX" in UC300 allows transforming text to Audio. The output format of the file can be ".wav" or ".gsm". Write the message you want to transform, select the output format and click on "Generate Audio File" button. Automatically you will be asked to save the file in a location of your hard drive.
Figure 2-4-51 Text to Wav interface
2.4.7.4 Festival
The option "Festival" of the menu "PBX" allows enabling and disabling the Festival service to work with Asterisk. Festival is a text-to-speech engine that can convert the text to audio.
Figure 2-4-52 Festival interface
If the file /usr/share/festival/festival. scm is not configured properly, when you turn on the service it will do it automatically.
2.4.7.5 Recordings
The option "Recordings" of the menu "PBX" in UC300 allows creating audio files from the recording of our voice. Also you can upload audio files from your hard disk. This option is only available if the connected user has an extension assigned to his account.
Figure 2-4-53 Recordings interface
To record an audio file, you have to enter the name of the recording and click on "Record" button. When your extension is ringing, answer the phone and start your voice recording after the tone. When done press '#' and hang up the phone. Click on "Save" button to save the recording.
2.4.8 Flash Operator Panel
The Operator Panel displays the Extensions, Queues and Trunks sections to monitor the usage of phone lines, extensions and queues. Each one of these elements is shown in different colors, each with its own meaning:
- Yellow: Extension associated with a queue
- Green: Extension or phone line unavailable (not busy).
- Red: Extension or phone line unavailable (busy).
In addition, each busy extension shows the external phone number or internal extension with which it is holding a conversation at the moment –Extension 215 talking with Extension 217.
Figure 2-4-54 Flash Operator Panel interface
When placing the mouse over a phone line in the Operator Panel, the line is highlighted as well as the extension that is currently using it.
The Panel also allows users to execute actions by previously authenticating via password. This password is the same one that was configured initially for UC300 series.
It is possible to transfer calls by clicking on the telephone icon displayed on the phone line through which a call was received, and dragging it towards the telephone icon of the extension to which we want to transfer the call.
2.5 Reports
2.5.1 CDR Report
The option "CDR Reports" of the Menu “Reports” in UC300 lets us view a list with the details of the calls. You can download this list in different format files such as CSV, XLS and PDF.
Figure 2-5-1 CDR Report interface
2.5.2 Channels Usage
The option "Channels Usage" of the menu "Reports" in UC300 lets us view graphically the number of simultaneous calls for each channel.
Figure 2-5-2 Channel usage interface
2.5.3 Billing
2.5.3.1 Rates
The option "Rates" of the menu "Reports" allows creating new rates and editing existing ones for billing.
Figure 2-5-3 Rate interface
To edit or delete a rate, click on the "View" link from the list
Figure 2-5-4 View Rate interface
Create a new Rate
You can create a new rate by clicking on button.
Figure 2-5-5 Create a new Rate interface
Click button to import a file into the system.
Figure 2-5-6 Import file interface
Below a description of each parameter:
Table2-5-1 Definition of Create a new Rate
Item | Description |
Prefix | All the numbers that begin with this prefix will apply to this rate. |
Name | This is the name to identify the rate. |
Rate (by min) | This is the rate that will be apply to every single minute of consumption. |
Rate offset | This is the rate assigned for the connection. |
Hidden Digits | This indicates the amount of digits you want to hide in the destination number. |
Trunk | Select the trunk that will apply for the rate. Make sure the trunk you want to use is enabled. To check this, go to "Billing Setup" module. |
2.5.3.2 Billing Report
The option "Billing Report" in UC300 shows a complete report of calls according to a rate established in "Billing Rates". You can filter the results by date, rate applied, duration and so on. Also you can download this report in different formats such as CSV, XLS and PDF.
Figure 2-5-7 Billing report interface
The fields in this report are:
Name | Description |
Date | Initial date of call |
Rate Applied | Name of Rate applied |
Rate Value | Rate value by minutes |
Source | Number or source |
Destination | Destination Number |
Dst. Channel | Channel Destination (Example: DAHDI/1) |
Account Code | Code of account extension |
Duration | Duration in seconds of calls |
Cost | Cost of call |
Summary Cost | Sum of all calls by cost field |
2.5.3.3 Destination Distribution
The “Destination Distribution” option of the “Billing” Menu in UC300 lets us view graphically the distribution of the outgoing calls grouped by rate. The graph will change depending on the values of the filter:
Name | Description |
Start Date | The start date for calls to be selected. |
End Date | The end date for calls to be selected. |
Criteria | Criteria for distribution: Distribution by Time, Distribution by Number of Calls, Distribution by Cost. |
Figure 2-5-8 Destination Distribution interface
2.5.3.4 Billing Setup
The option “Billing Setup” of the Menu “Billing” in UC300 lets us determine the cost per minute of the connection for the route by omission, and also determine which of the trunks will be used for the billing process.
Figure 2-5-9 Billing setup interface
The list shows all of the registered trunks; you should select the ones that will be used for billing and click on the “Billing Capable” button.
2.5.4 Asterisk Logs
The option "Asterisk Logs" of the "Reports" module allows visualizing the content of Asterisk logs for monitoring the events. You can filter the results by date or strings that are in the content of the logs
Figure 2-5-10 Asterisk logs interface
Below a description of each column.
Column | Description |
Date | The date of the event. |
Type | The type of the event. |
Source | Where the event comes from. |
Message | The description of the event. |
2.5.5 Graphic Report
The option "Graphic Report" of the "Reports" module allows visualizing graphically information about the number of calls, queues and trunks of the system both in quantity and percentage.
Figure 2-5-11 Graphic report interface
To see the information of a specific extension, select "Extension (Number)" and then click on the link "Here". In the pop-up window, choose the phone number and then click on "Show button".
Figure 2-5-12 Specific extension info
It is possible to generate a graphic of Number of Calls vs. Queues. To do this just select "Queue" from the dropdown menu.
Figure 2-5-13 Queue record
2.5.6 Summary
The option "Summary" of the menu "Reports" in UC300 shows a report of each Extension registered in the server. You can see the number of incoming and outgoing calls, the duration of the calls, the caller id and the dialing number. Use the filter to find an extension or user.
Figure 2-5-14 Summary interface
Click on "View" to see more information of an extension.
Figure 2-5-15 View extension info
2.5.7 Missed Calls
The option "Missed Calls" of the menu "Reports" in UC300 shows a report of the missed calls of all extensions so you can know when an extension has been receiving calls. You can download this report by clicking on "Download" button. The available formats for this file are csv, xml and pdf
You can filter the results by:
- Start Date: Find missed calls from this date.
- End Date: Find missed calls until this date.
- Search : You can filter the results by these parameters:
- Source: Number that made the call.
- Destination: Number that received the call.
Figure 2-5-16 Missed calls interface
2.5.8 System Logs
Figure 2-5-17 System Logs interface
2.6 Security
2.6.1 Firewall
UC300 system has been preconfigured with a built-in firewall which prevents your IP phone system from unauthorized access, phone calls and other attacks. To manage the firewall, navigate to web menu Security->Firewall.
2.6.1.1 Firewall Rules
The option "Firewall" of the menu "Security" in UC300 allows building iptables rules to control the packets that send and receive the UC300 series.
Figure 2-6-1 Deactivate firewall rules
To use this module the firewall must be enabled with the rules that appear by default. It can be done by clicking on "Activate Firewall" button. Once the firewall is enabled, you can create, delete, edit, disable and reorder the iptables rules.
Figure 2-6-2 Firewall rules interface
Every time you create or edit the rules, you have to save the changes. You can do this by clicking on "Save" button that will appear automatically when you modify something. If you don't save the changes the rules won't take effect in the system.
Adding a New Rule
To add a new rule click on the button and a form will appear with some data to fill out. The form can vary depending on the parameters you select for Traffic and Protocol.
Figure 2-6-3 Add a new rules interface
The ports used when you select the protocol TCP, UDP, ICMP and IP, are obtained from the module "Define Ports" in the same menu. Therefore, make sure the port you want to use is previously defined if you want to create a new rule.
In the source and destination address fields you have to enter the IP with the format x.x.x.x/y, where y is the network mask and should be a number between 0 and 32. If you let the default IP address (0.0.0.0) the netmask will be 0. If you let the netmask in blank it will not be taken into account. To enter a specific IP address, just let in blank the netmask value.
Once you created the rule, click on "Save" button and the new rule will appear in the list. Make sure you save the changes so they take effect in the system after creating a new rule.
Editing a Rule
To edit an existing rule, click on the blue notebook icon corresponding to the rule. Here you can modify parameters of the rule.
Figure 2-6-4 Edit a rules interface
Deleting a Rule
To delete a rule just select the checkbox corresponding to the rule at the left side and click on "Delete" button. Make sure you save the changes so they take effect in the system after deleting a rule.
Reordering the Rules
You can modify the order of the rules by clicking on the blue arrows in the column Order. If you click on the up arrow of a rule, this rule will go up one position and the one which was in that position will go down. If you click on the down arrow of a rule, this rule will go down one position and the one which was in that position will go up. Make sure you save the changes so they take effect in the system after modifying the position of the rules.
Activate /Deactivate a rule
You can activate or deactivate a rule by clicking on the light bulb corresponding to the rule. When it is ON the rule is activated, when it is OFF the rule is deactivated. Make sure you save the changes so they take effect in the system after doing this action.
2.6.1.2 Define Ports
The module "Define Ports" of the menu "Security" in UC300 allows creating, editing, and deleting ports that are used for the module "Firewall Rules". These ports can be from the protocols TCP, UDP, ICMP and IP. This module shows a list of all the existing ports and the results can be filtered by name and protocol.
Figure 2-6-5 Define Ports interface
Define Port
To define a new port, click on the button and a form will appear with some parameters to fill out. The form can vary depending on the parameters you select for the field Protocol. Once the information is filled, click on "Save" button.
Figure 2-6-6 Define Port interface
View Port
To view an existing port, click on the "View" link located in the row corresponding to the port. Here you can see the information of the port and edit it if needed.
Figure 2-6-7 View Port interface
Edit Port
To edit a port, click on the "View" link corresponding to the port you want to modify and then click on "Edit" button. A form will appear with the parameters of the port ready to be modified.
Figure 2-6-8 Edit Port interface
Delete a port
To delete a port just select the checkbox located at the left side corresponding to the port and click on "Delete" button.
2.6.1.3 Port Knocking Interfaces
Navigate to Security>Firewall > Port Knocking Interfaces:
Figure 2-6-9 Port knocking interface
2.6.1.4 Port Knocking Users
Navigate to Security>Firewall > Port Knocking Users:
Figure 2-6-10 Port knocking users
2.6.2 Audit
The module "Audit" of the menu "Security" in UC300 shows a list of all the users that have logged in the system with the date, the username, the source IP address and other details. The results can be filtered by date and string. The coincidences with the string will be highlighted in the results.
Figure 2-6-11 Audit interface
The results of the search can be downloaded in different formats such as PDF, XML and CSV by clicking on the "Download" button.
2.6.3 Weak Keys
The module "Weak Keys" of the menu "Security" lets us identify the keys that are not enough strong for the extensions created in UC300 (SIP and IAX2). This module shows all the extensions but you can filter the results by entering a specific extension number or part of it.
Figure 2-6-12 Weak keys interface
You can download the results in different formats such as PDF, XML and CSV by clicking on the "Download" button.
Change Key
If the key of an extension is not enough strong, you will be notified through the Status column and a link called "Change Secret" will be available to change the key. Once you click on this link, you will see a form where you can set the new secret. The secret must be at minimum six characters in length of which must contain at least two numbers and two letters. When the new secret is set, click on the "Save" button to apply the changes.
2.6.4 TLS Setting
The module "TLS Settings" of the menu "Security" implement greatly enhances the security. It's also rather confusing to get it working, and create or add a certificate on the asterisk server. There are three Client Methods for us to choose, it configures the clients to use TLS.
Figure 2-6-14 TLS setting interface
To use TLS, you need to understand the principle of it. Check the TLS configuration parameters below, you would be rewarded about it.
Table2-5-1 TLS Configuration Parameters
Option | Description |
TLS Enable | Check the checkbox to enable TLS. |
Port | TLS Port used for SIP registrations. The default is 5061. |
TLS Verify Server | If set to no, don't verify the servers certificate when acting as a client. If you don't have the server's CA certificate, you can set this and it will connect without requiring TLS CA file. The default is no. |
Allow Guest | Sip allows anonymous access. If set to yes, Sip client cannot send registration messages to server, and asterisk does not have to verify user identity. The default is no. |
TLS Client Method | Specify protocol for outbound client connections. The default is tlsv1. |
Figure 2-6-15 TLS setting
We can create the certificate when inputted the Key Name, Organization, IP address and the Password. After client and server mutual authentication, with a license, it can be allowed to access
There are several basic steps we need to do:
1. Your asterisk server needs a certificate.
We must create or add a certificate on the asterisk server. Creating a server key - We need to create a digital key for our server, and the key.pem is your server key. The key.pem file is your server key and the request.pem is your certificate request.
2. Add some configuration settings into the sip.conf file.
3. Configure the clients to use TLS