1. Manuals
  2. Brands
  3. Far south networks Manuals
  4. Gateway
  5. Com.X
  6. Administrator's manual

Far south networks Com.X Administrator's Manual

Ip pbx / gateway
Hide thumbs
Table of Contents

Advertisement

Quick Links

Com.X
IP PBX / Gateway

Administrator Guide

(Com.X revision 1.4 software release)
Version 4.0.1, 19 September 2016
©2010 – 2014 Far South Networks

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Com.X and is the answer not in the manual?

Questions and answers

Related Manuals for Far south networks Com.X

Summary of Contents for Far south networks Com.X

  • Page 1: Administrator Guide

    Com.X IP PBX / Gateway Administrator Guide (Com.X revision 1.4 software release) Version 4.0.1, 19 September 2016 ©2010 – 2014 Far South Networks...

  • Page 2: Document History

    Document History Version Date Description of Changes 4.0.1 05/10/2016 Documented ported from 1.3 release ©2010 – 2016 Far South Networks...

  • Page 3: Table Of Contents

    Com.X Administrator Guide Page 3 Table of Contents 1 INTRODUCTION ..........................18 1.1 O ............................18 VERVIEW 2 MANAGING THE UNIT ........................19 2.1 A .......................... 19 CCESSING THE UNIT 2.1.1 Factory network configuration ..................... 19 2.1.2 Authentication ........................19 2.1.3 Remote web login ........................
  • Page 4 Com.X Administrator Guide Page 4 2.2.6 Upgrading a 1.3 system to 1.4 ....................32 3 COMMISSIONING THE UNIT ......................33 3.1 G ..........................33 LOBAL SETTINGS 3.2 N ........................36 ETWORK CONFIGURATION 3.2.1 Connections ........................... 36 3.2.2 Ethernet Interface Configuration ..................38 3.2.2.1 Listing ethernet interfaces ......................
  • Page 5 Com.X Administrator Guide Page 5 3.3.6.2 Editing classification and priority ....................68 3.4 H ..................... 68 ARDWARE EVICE CONFIGURATION 3.4.1 Configured devices ........................ 69 3.4.2 Detecting and scanning for devices ..................69 3.4.3 Adding Detected Devices ...................... 69 3.4.4 Manually adding devices ...................... 70 3.4.5 Configuring devices ......................
  • Page 6 Com.X Administrator Guide Page 6 3.6.6 Echo cancellation ........................91 3.6.7 Earthing the Com.X ....................... 93 3.6.8 Configuring devices for Fax / modem support ..............93 3.6.8.1 Echo cancellation ......................... 93 3.6.8.2 Telco issues ..........................94 3.6.8.3 Timing ............................94 3.6.8.4 Additional configuration for faxing over PRI ................
  • Page 7 Com.X Administrator Guide Page 7 3.8.3.2 Adding a SIP trunk ........................108 3.8.3.3 Sip trunk configuration ......................108 3.8.3.4 Editing a SIP trunk ........................113 3.8.3.5 Removing a SIP trunk ........................ 113 3.8.4 Inter-Asterisk Exchange (IAX) trunks ................. 113 3.8.4.1 Adding an IAX trunk ........................113 3.8.4.2 Editing an IAX trunk ........................
  • Page 8 Com.X Administrator Guide Page 8 3.12.2.2 Match ............................124 3.12.2.3 Start ............................125 3.12.3 FlexPath Destinations ....................... 125 3.12.4 Viewing existing FlexPaths ....................125 3.12.5 Adding FlexPaths ......................125 3.12.6 Deleting FlexPaths ......................126 3.12.7 Adding routes to a FlexPath ....................126 3.12.8 Changing route priority in a FlexPath ................
  • Page 9 Com.X Administrator Guide Page 9 3.16.1 Unattended transfer ......................140 3.16.2 Attended transfer ....................... 140 3.16.3 Call parking ........................140 3.16.4 Ring-back .......................... 140 3.16.4.1 Disabling Ringback Functionality .................... 143 4 ADVANCED CONFIGURATION ....................144 4.1 A ..........................144 NNOUNCEMENTS 4.2 C...
  • Page 10 Com.X Administrator Guide Page 10 5.3.1 Reviewing Call Detail Records ................... 176 5.3.2 Enabling logging to CSV ..................... 177 5.3.3 Accessing the CDR database ....................177 5.4 M ................177 ONITORING OF REMAINING CAPACITY ON THE UNIT 5.4.1 Deleting of call recordings ....................178 5.4.2 Changing the memory consumption threshold ..............
  • Page 11 Com.X Administrator Guide Page 11 6.13 T (TMS) ..................189 ELEPHONE ANAGEMENT YSTEMS 6.13.1 MAN 3000 ......................... 189 6.13.1.1 Installing MAN 3000 support ....................189 6.13.1.2 CDR format ..........................193 6.13.1.3 Defining outbound line numbers ....................195 6.13.1.4 Logging records from a specific date ..................195 6.13.2 Asterisk TMS systems ......................
  • Page 12 Com.X Administrator Guide Page 12 Table 3: Com.X Firewall default policies..............51 Table 4: Comma device configuration...............62 Table 5: Generic device configuration...............63 Table 6: Managed SIP device configuration..............63 Table 7: FXO port configuration................74 Table 8: FXS port configuration.................75 Table 9: BRI port configuration..................76 Table 10: PRI port configuration................77...
  • Page 13 Figure 7: System maintenance - backup..............22 Figure 8: The new backup is listed under the appropriate section......23 Figure 9: Backups can be scheduled to back up the Com.X settings automatically. 23 Figure 10: The schedule (if configured) is displayed on the title bar......23 Figure 11: Managing individual backup archives.
  • Page 14 Com.X Administrator Guide Page 14 Figure 20: Licenses submitted for authentication............28 Figure 21: Only system maintenance options available from the GUI of a system with no active licenses......................28 Figure 22: Select the Packages tab................29 Figure 23: Managed packages listed with version and status........29 Figure 24: Options available for managing packages..........29...
  • Page 15 Figure 58: The Com.X forwards and proxies the necessary traffic to the handsets so that they can sit safely behind a firewall and still be configured remotely....57 Figure 59: The GUI of the device is accessible through the Com.X GUI by selecting Connect........................58 Figure 60: Enabling lines on a handset..............59...
  • Page 16 Figure 85: 'sudo asterisk -rx "stop when convenient" ' stops the asterisk service, so that no calls are cut off, then 'sudo reboot' reboots the Com.X system....153 Figure 86: If an email address is listed in this field, voicemail recordings and notifications will be sent to the address.
  • Page 17 Figure 112: The Listen and whisper feature allows the operator to listen in on other calls, and talk to the local user on the call..............177 Figure 113: The landing page of the Com.X Gui.............178 Figure 114: Options available for configuring Nagios monitoring on a port or a service........................

  • Page 18: Introduction

    Com.X range of products, release 1.4, including the Wanderbox, Com.X5, Com.X10 and Com.X20 products. It forms part of a suite of manuals and guides for the Com.X product range, which also includes the Com.X End User manual, the Com.X Installation guide and the Com.X Trouble-shooting guide.

  • Page 19: Managing The Unit

    2.1 Accessing the unit 2.1.1 Factory network configuration The Com.X units ship with 2 - 4 external ethernet ports labeled lan1, lan2 etc. (enumerated from eth0 in the Operating System). Com.X1 and Com.X10 models have an internal ethernet port (eth3), and certain Com.X5 models have an internal port for DSL applications (wan).

  • Page 20: Wanderweb Activation

    South Networks. Configuration management 2.1.5 GUI layout The Com.X GUI facilitates status monitoring and control of the unit and peripheral devices via a set of menus accessible from the menu bar. After any changes have been made to the configuration, these need to be reviewed and applied before they take effect.

  • Page 21: Configuration Status

    Com.X Administrator Guide Page 21 Figure 3: GUI layout and configuration status 2.1.6 Configuration status The current configuration status, indicating pending tasks and status alerts, can be viewed from the configuration menu: When the status on the Status tab is SYNCHRONIZED, the configuration is up to date and synchronized with the underlying system configuration resources.

  • Page 22: Changing The Default Administrator's Password

    Com.X Administrator Guide Page 22 Figure 4: Review / apply task list Figure 5: Start menu options. 2.1.8 Changing the default administrator's password The password for the default administrative user (admin) can be changed by selecting the “Change Password” option from the Start menu. Enter the existing password, the new password and its confirmation and Accept to apply the change.

  • Page 23: Rebooting And Shutting Down

    2.2 System Maintenance 2.2.1 Backup and Restore The Com.X configuration can be backed up to the unit's internal hard drive, or downloaded to another machine. Backups can be scheduled daily, weekly and monthly, and individual sections of the configuration can be configured for backup, each with its own schedule.

  • Page 24: Backup Contents

    The following selection of backup sets are provided for backup: 2.2.1.1.1 Factory default configurations Com.X systems ship with a default factory configuration, which includes the default configuration of telephony ports in the system. This configuration is reflected on hardware the Hardware panel. Factory default configurations cannot be deleted from the GUI, but can be stored offline and may also be uploaded to the system.

  • Page 25: Managing Existing Backup Archives

    Com.X Administrator Guide Page 25 Figure 9: Backups can be scheduled to back up the Com.X settings automatically. The schedule setting is reflected in the backup set's title bar. Figure 10: The schedule (if configured) is displayed on the title bar.

  • Page 26: Restoring An Archive Onto The Same System

    To restore from a data file saved at an external location, first upload the archive to the Com.X and then follow the procedure above. Select “Upload” from the options menu on the appropriate backup set in order to upload an archive.
  • Page 27 Com.X Administrator Guide Page 27 Figure 15: Submit the desired archive for upload. Then follow the procedure in 2.2.1.5 to restore the backup onto the system. Note: After a configuration has been restored, you will be required to apply the changes.

  • Page 28: Licensing

    Figure 16: Updating the MAC address of a replacement unit Note: Updating of the MAC address is necessary only on iTA devices. Units that contain only MPX telephony devices (such as a Com.X 5 with no external iTA's ) will not require MAC addresses to be updated.
  • Page 29 Com.X Administrator Guide Page 29 Figure 17: Manage Licenses via the This will allow you to upload a license from your computer. Select they type of License you would like to add and then Browse your computer for the correct license file.

  • Page 30: Unlicensed Functionality

    Com.X Administrator Guide Page 30 After uploading a license to the Com.X, allow a few seconds for the GUI to update and refresh. If the license is accepted the appropriate GUI functionality will be available. Note: It may be necessary to manually restart the GUI from the command line after adding a license: sudo /etc/init.d/comma­gui restart...

  • Page 31: Managing Packages From The Gui

    Figure 23: Managed packages listed with version and status. The State column provides information comparing the version of the installed package to the version of the latest package available on the Far South Networks repository. Figure 24: Options available for managing packages.

  • Page 32: Download Updates

    This will pull the latest packages from the Far South Networks repository and store them on the Com.X, however it will not install the updates until requested to do so. This allows updates to be retrieved immediately, but installed at a convenient time, when service can be interrupted.

  • Page 33: Commissioning The Unit

    Com.X Administrator Guide Page 33 3 Commissioning the unit 3.1 Global settings A range of global settings are available for configuration, Double-click a field to edit the field and enter required information. ©2010 – Far South Networks 2016...
  • Page 34 Com.X Administrator Guide Page 34 Figure 26: Global Settings ©2010 – Far South Networks 2016...
  • Page 35 The subnet (IP and subnet mask in the form A.B.C.D/E.F.G.H) subnet for any additional local subnet. Traffic on this subnet will be treated as local by the Com.X for SIP purposes. Jitter Buffer When enabled, a SIP jitter buffer will be instantiated for each Enabled SIP call.

  • Page 36: Network Configuration

    Page 36 Field Content network slips Gateway If enabled, all calls on all trunks via the Com.X will be recorded. recording Please see section 3.13.5 for a detailed discussion on gateway recording. Gateway If enabled, all calls on all trunks recorded will be encrypted recording using the Com.X system's unique hardware key.
  • Page 37 Server Note: the Com.X uses an open-source, synchronous DNS lookup library. As a result, the Com.X makes use of a DNS proxy to facilitate DNS lookups. If the primary DNS is configured to an IP address outside the LAN (i.e. outside of the...

  • Page 38: Ethernet Interface Configuration

    Page 38 3.2.2 Ethernet Interface Configuration The Com.X GUI provides functionality to configure all ethernet interfaces, as well as provision of DHCP IP allocation for IP phones and booting of Comma iTA devices. The Com.X unit can serve both DHCP and Comma addresses simultaneously, provided the IP ranges do not overlap.

  • Page 39: Providing Dhcp Server Ip Allocation To Clients

    DHCP Router Address The address of the IP router / gateway to be used by the device requesting IP configuration, normally the same as the Com.X address on this interface. DHCP DNS Server The primary DNS address to be configured on the device requesting IP configuration, may be left blank.
  • Page 40 Com.X Administrator Guide Page 40 Figure 30: DHCP and Comma server configuration options. Apply the configuration. Note: When applying network configuration changes, the unit automatically restarts the affected network interface(s). NB. If the interface used for GUI access is reconfigured, GUI access may be affected.

  • Page 41: Providing Comma Ita Boot Services

    Comma units. Apply the configuration. Note: On Com.X 1 and Com.X10 units, the eth3 interface is the internal ethernet bus serving the Com.X Media processor card and should not changed from its factory configuration. ©2010 –...

  • Page 42: Configuration Of Pppoe Interfaces

    Com.X Administrator Guide Page 42 3.2.3 Configuration of PPPoE Interfaces Figure 31: PPPoE interface configuration options. Field Content Name A suitable name for the virtual interface. Description A description of the interface, marking it as PPPoE. Automatic IP If enabled, the interface will attempt to dynamically receive an IP address via IPCP.

  • Page 43: Interface Configuration

    (X21-1) in the Interfaces list. The Com.X X.21 interface is always DTE on the physical layer (although it may act as protocol DCE in Frame Relay mode). Therefore, the clock and thus the data rate of the interface is provided by the DCE equipment connected to the X.21 interface,...
  • Page 44 Com.X Administrator Guide Page 44 Figure 33: X21 interface configuration The fields are described in the table below. Note that only PPP mode supports Automatic IP configuration. Field Contents Name (not editable) serial0 Description (not X21-1 editable) Serial Protocol IP/HDLC – Raw IP in HDLC encapsulation Cisco HDLC –...

  • Page 45: Frame Relay Pvc Configuration

    Com.X Administrator Guide Page 45 Management Interface protocol selection. Valid values are: None ANSI DTE ANSI DCE CCITT DTE CCITT DCE Automatic IP (only valid for PPP mode) – obtain IP address automatically from the PPP peer Enabled Interface enabled/disabled at startup IP Address (except when Frame Relay or Automatic IP enabled) –...
  • Page 46 Com.X Administrator Guide Page 46 Figure 34: PVC interface shown in interface list PVCs are added by selecting Options → New PVC... The screenshot below shows the configuration of a new PVC. Figure 35: X21 PVC device configuration The fields are described in the table below.

  • Page 47: Creating Virtual Ports For Vlan And Pvc

    Com.X Administrator Guide Page 47 PVC encapsulation IP/Frame Relay – Raw IP is encapsulated in the PVC frame Ethernet/Frame Relay – IP over Ethernet is encapsulated in the PVC frame DLCI Data Link Connection Identifier – number from 1 to 1023...
  • Page 48 Com.X Administrator Guide Page 48 Figure 37: VLAN Configuration Options Field Contents VLAN Physical The actual physical LAN interface through which this virtual port Interface connects to the rest of the virtual network. This could be any of the LAN ports, or the internal dsl router on certain Com.X5 models.
  • Page 49 Com.X Administrator Guide Page 49 Enabled By default the port is enabled. Disabling the port prevents all functionality and will delete any associated IP routes. Re- enabling the port will recreate associated IP routes. IP Address If the interface is not configured as a DHCP client, a static IP address can be configured in this field.

  • Page 50: Vpn Interface

    Com.X Administrator Guide Page 50 3.2.5.2 VPN Interface Figure 38: VPN interface configuration page. Field Contents Name vpns1 – VPN server interface vpncX – VPN client interfaces (X=1,2,3...) Description Describes the type of VPN interface, automatically configured to either VPN Server or VPN Client with a number index.

  • Page 51: Vpn Server

    3.2.5.2.1 VPN Server By default a disabled VPN server port is configured on the Com.X. To configure, right-click the interface in the interfaces list and select edit. The VPN interface configuration as in Figure 38 will load. Configure interface IP settings appropriately, then select the VPN tab.

  • Page 52: Routes

    Com.X Administrator Guide Page 52 Defaults to 1194. Use LZO The VPN may be configured to use compression on all Compression packets. This will save network bandwidth but incur some performance penalty. Client and server configuration must match. Transport Select between TCP and UDP for VPN transport.

  • Page 53: Revoking Client Certificates

    Com.X Administrator Guide Page 53 Figure 41: Certificates are available as standard .p12 or in tar or zip format, for particular handset devices. Select your desired certificate packaging and save the file to a location on your desktop/laptop computer. Note: Changes must be applied after the creation of a client before requesting configuration.
  • Page 54 Com.X Administrator Guide Page 54 Figure 42: Client VPN configuration. Field Contents Port Number Port number on associated VPN server. Defaults to 1194. Transport Protocol to be used for traffic on the VPN. Select between UDP and TCP. Remote Server...

  • Page 55: Adding Ip Routes To Interfaces

    Com.X Administrator Guide Page 55 the button below, and may be supplied separately (e.g. ca.crt, client.crt, client.key) or in a PKCS12 package (e.g. client.p12) CA/Certificate/key/PK Click on the “...” button to upload certificates from your local CS12 file system to your client device.

  • Page 56: Firewall Configuration

    3.3.1 Zones The Com.X allows separation of its interfaces into different zones, each of which is authorized to access only portion s of the available network. The access provided to devices in each zone is configured through firewall policies (See section 3.3.2) Figure 45: Ports can be allocated a particular zone into which they fall.

  • Page 57: Policies

    Com.X The Com.X zone contains interfaces (physical and virtual) on the Com.X system itself. This includes the ports listed on the interfaces section of the Network page of the Com.X GUI. Interfaces placed in the LAN zone have access only to the internal network.

  • Page 58: Applying Default Policies

    Com.X Administrator Guide Page 58 Accept Allow traffic between the two zones. Drop Ignore any packets travelling from the source zone to the destination zone. Reject Reject any packets sent from the source zone to the destination zone with a rejection message.

  • Page 59: Managing Policies

    All Zones All Zones Reject Table 3: Com.X Firewall default policies. 3.3.2.2 Managing Policies Policies are evoked in preferential order based on their position in the list on the GUI. By right-clicking on a policy, it can be moved up and down, deleted and edited.

  • Page 60: Creating A New Policy

    Com.X Administrator Guide Page 60 Figure 50: Editing an existing Firewall policy. Figure 51: Logging Options for firewall policies. 3.3.2.4 Creating a New Policy To create a new firewall policy, select Options, then new policy. Figure 52: Options for new rules and policies.

  • Page 61: Rules

    Com.X Administrator Guide Page 61 Figure 53: Configuring a new firewall policy. 3.3.3 Rules Rules are very specific exceptions to the configured policies. Rules allow the forwarding of ports. Rules allow for traffic to move from particular ports or addresses in a manner that would normally be prevented by the policies.
  • Page 62 Com.X Administrator Guide Page 62 Illustration 1: Port Forward rule wizard options. Field Description Source Zone Since this is the port forward rule wizard, the source zone is automatically configured to “Internet” and can not be edited. Source IP address...

  • Page 63: Inbound Redirect

    The allocated zone of your destination device. As this is an inbound redirect rule, the zone is pre-configured to Com.X and can not be editted from the rule wizard. Destination start port The port to be accessed on the destination device.

  • Page 64: Inbound Access

    Description An optional description for the firewall rule. 3.3.3.3 Inbound Access An inbound access route can be configured to allow access to the Com.X device from particular devices on the external internet. Figure 56: Inbound access rule wizard. Field...

  • Page 65: Ping

    An optional description for the firewall rule. 3.3.3.4 Ping A ping rule allows the Com.X device to receive and respond to pings sent from particular devices in the internet zone (i.e. not on the local network, but rather on the external internet).

  • Page 66: Blacklist

    Com.X Administrator Guide Page 66 3.3.3.5 Blacklist If required, particular ip addresses or ranges of ip addresses can be black listed by the administrator. This results in any traffic from the source being rejected. Figure 58: Blacklist rule configuration wizard.

  • Page 67: Network Quality Of Service

    The special traffic classes support the setting of Layer 3 class of service (DSCP) and Layer 2 class of service (CoS Priority) for traffic generated by the Com.X. DSCP is generally visible right through the network path, whilst CoS Priority is only used for the local network queuing priority and on VLAN if configured.

  • Page 68: Editing Classification And Priority

    P0 is normal priority (unclassified traffic), P7 is highest. 3.4 Hardware Device configuration To list, detect and configure hardware devices (including the Com.X, external iTAs, IP phones and other network devices), select the Start button, then Configuration and open the Hardware panel.

  • Page 69: Configured Devices

    Where available, the device IP address and current status are also listed. 3.4.2 Detecting and scanning for devices The Com.X unit can detect network devices present on all networks attached to it. By default, devices requesting either DHCP IP information, internal telephony devices and external Comma iTA devices are automatically added to the list of detected devices.

  • Page 70: Manually Adding Devices

    Auto IP On first boot, request an IP address from the Com.X Manager. Once an IP has been allocated, the Auto IP field becomes disabled and the IP is statically reserved for the device by the Comma Manager, always issuing the same IP to the device ©2010 –...
  • Page 71 Comma services. Timing Mode The timing source for the device. Options are: Local: Recover timing from the local Com.X clock (i.e. this device is a clock master) System: Recover timing from another clock master (i.e. this device is a clock slave) This is equivalent to the iTA “Network”...

  • Page 72: Configuring Generic Devices

    Indicates whether the Com.X DHCP server should allocate an IP to the device on DHCP request. Once the DHCP lease on the IP expires, the Com.X DHCP server might issue a different IP to the device. To ensure a device is always allocated the same IP (static), disable Auto IP and enter the IP manually.

  • Page 73: Managed Sip Phone Provisioning

    Each handset will have to be re-added to the hardware panel to allow configuration of any of the settings mentioned. Note: If the phone connects to a network with a DHCP server other than the Com.X present, the DHCP server should configure option 66 to refer to the Com.X when responding to phone DHCP requests.

  • Page 74: Adding Hardware (Managed Sip Device)

    Note: If a phone is featured on the hardware list, either as a managed SIP phone, or a generic device, the GUI of the phone can be accessed through the GUI of the Com.X. This is done by forwarding ports, ensuring that all hardware is available remotely, even if it is behind a firewall.

  • Page 75: Adding An Auto-Detected Managed Sip Phone

    Com.X Administrator Guide Page 75 Note: If a Managed SIP Phone is receiving DHCP from a remote server(i.e. Not from the Com.X), that dhcp server should be configured to set option 66 to contain the location /etc/commagui/autoprovision on the Com.X server. Field...
  • Page 76 Select Options, and then Detected to see a list of detected phones. Select a Managed SIP Device. When configuring an auto-detected device the Com.X automatically detects and populates all fields with appropriate settings. The name of the device is defaulted to the Mac address of the unit, and this is the only field that should require (optional) editing.
  • Page 77 IP Address An auto-detected device will have received its IP address from a DHCP server on the Com.X, so this field will automatically be populated by the GUI. Network Mask The network mask of an auto-detected device will be automatically configured.

  • Page 78: Provisioning Via Spreadsheet Based Configuration

    For larger installations, featuring several sip endpoints,spread sheet provisioning is a very powerfull tool. Various fields are configurable on the spreadsheet and will be automatically added to the configuration of the phones, once the Com.X detects them. 3.5.1.3.1 Adding hardware via spreadsheet To add hardware via spreadsheet, first prepare a spreadsheet containing your handsets, extension numbers and settings (voicemail, DNS, NAT etc).

  • Page 79: Exporting Spreadsheet Of Current Hardware And Extensions

    Note: If a handset in the spreadsheet already exists on the Com.X (identified by MAC address) the handset will be updated with the settings from the spreadsheet.
  • Page 80 Com.X Administrator Guide Page 80 accept the handset configuration, then right-click and edit the hardware entry before the other interfaces become available for selection Figure 78: Select the VLAN interface as the attached network field The phone should then detect the changes to it's network settings and reboot itself, if this does not happen automatically, reset the handset to factory default settings from the GUI.

  • Page 81: Removing A Hardware Device

    Factory defaulting phones as you install them deletes any extensions configured in a previous installation and ensures that the Com.X is able to configure all lines seamlessly.

  • Page 82: Creating New Extensions

    A free extension configured on the system can be assigned to an available line on a SIP handset. Left-click the appropriate line in the port tree of the Extensions page of the Com.X GUI and (while holding left click) drag the line over the entry of the desired free extension and then release.

  • Page 83: Configuring A Port On The Phone To Register As An Extension On A Remote System

    If there is an unused port(line) on the handset, you can configure it to register as an extension on a remote PBX, from the Com.X GUI. Navigate to the hardware page and select the port from the port tree. Right-click and select Edit.

  • Page 84: Codecs

    Com.X Administrator Guide Page 84 system. SIP Server If Local Extension Port is disabled, this field can be edited to contain the IP address of the remote SIP server on which the extension is registering. SIP Server Port If Local Extension Port is disabled, this field can be edited to contain the port on which the extension should register on the remote system.

  • Page 85: Removing An Association To An Extension

    Com.X Administrator Guide Page 85 Figure 86: Extensions can be configured to support multiple Codecs. 3.5.7 Removing an association to an extension Two possibilities exist for removing extensions from device lines. 3.5.7.1 Unassigning Extensions To unassign an extension, right-click on the extension in the extensions list and select Unassign.

  • Page 86: Configuring Soft Keys

    Page 86 3.5.8.1 Configuring Soft Keys The Com.X GUI offers a mechanism to provision the soft keys keys of compatible handsets. These keys can be set to transfer to, and monitor the status (through BLF) of : other extensions, conference extensions, queues, ring groups, parking lots and particular parking bays within parking lots.

  • Page 87: Adding An Extension Module

    The EXT keys are configured as per section 3.5.8.1. Note: Applying any changes to Managed SIP Devices from the Com.X GUI will cause the handset to reboot. The device will reboot,and then update configuration upon startup.
  • Page 88 If this is the case, use the 'Any regular pattern' setting to detect such tones. For more information on the options available to detect end-of- call under such conditions, please see the Com.X Trouble- shooting guide. ©2010 –...

  • Page 89: Configuring Analogue Extension (Fxs) Ports

    If enabled, the phone using this port is allowed to transfer calls. Immediate mode When enabled, ring tone is not provided when the phone goes off hook and the Com.X is required to take immediate action, such as dialing an emergency number. Please see section 3.12.11.7 for more detail on using FlexPath with his feature.

  • Page 90: Configuring Pri

    If multiple devices are attached to the BRI cable (point-to- multipoint) and another device is providing termination, the Com.X can be configured not to terminate. A BRI link should always be terminated by a device on at least one side of the BRI connection, or electrical reflection on the link could interfere with BRI signaling and result in loss of layer 1 link establishment, or CRC errors.

  • Page 91: Removing Devices

    In analog phones, both the 2-wire to 4-wire converter (hybrid) and the handset can introduce echo. The Com.X impedance parameters are aligned with South African telecommunications standards. Non-compliant handsets with a large impedance mismatch are likely to introduce noticeable echo. The delay introduced by VoIP based systems can result in the returned echo becoming noticeable to the person who is speaking.
  • Page 92 Wiring problems, such as power cables crossing telephone cables, or insufficient earthing of the Com.X or iTAs may add noise to the audio path that may reduce performance of the algorithm. In diagnosing echo cancellation problems, establish good earth (~0.5 ohm or less, if...

  • Page 93: Earthing The Com.x

    It is important that Com.X and iTA devices are earthed in a “star” pattern to a single earthing point. Do not wire an iTA to a Com.X's earth stud or vice versa.

  • Page 94: Telco Issues

    Echo cancellation is performed at the source device, where 'source' here indicates a network endpoint that introduces a signal into the PBX system. In the Com.X systems echo cancellation takes place on FXO, BRI and PRI ports/channels terminating traffic from the PSTN for routing in the system, as well as FXS ports originating calls via the PBX.

  • Page 95: Additional Configuration For Faxing Over Pri

    GUI, Monitor – Telephony – dahdi statistics should show slips and skips increasing on the span to the iTA. The Com.X can be instructed to buffer in the receive direction from the iTA in order to alleviate such network delays. This is done by enabling the “Network slip tolerant”...

  • Page 96: Extension Configuration

    Com.X Administrator Guide Page 96 3.7 Extension configuration 3.7.1 Extensions and Extension Ports The Com.X treats extensions and extension ports differently. Extensions represent dialable numbers (users) in the system, e.g. extension • 1000. Extension Ports represent hardware devices available for making and •...

  • Page 97: Adding Extensions From Ports

    Com.X Administrator Guide Page 97 Figure 90: Assigning extensions 3.7.3.1 Adding extensions from ports Single extensions or a group of extensions can be assigned to available extension ports by selecting the ports in the ports list and selecting Assign from the context menu.

  • Page 98: Configuring Extensions

    Com.X Administrator Guide Page 98 •Same as Extension: The password for each newly created extension is the same as the extension number. Note: setting the extension password to the extension number is strongly discouraged and may lead to weak system security! •Random: A strong unique, random password of length 12 is generated , for each...

  • Page 99: Advanced Configuration

    Com.X Administrator Guide Page 99 3.7.4.2 Advanced configuration ©2010 – Far South Networks 2016...
  • Page 100 Com.X Administrator Guide Page 100 Field Content Voicemail Enable this to enable voicemail for the extension. Note: Disabling voicemail will reset any call recording settings that may have been configured on the extension! The user pin used to access voicemail and features...

  • Page 101: Campon Callback

    Com.X Administrator Guide Page 101 Field Content Use NAT When enabled, the system ignores the SIP and SDP headers' address and port and replies to the sender's address and port. Outboud CID Optional field to configure outbound caller identification Table 11: Advanced extension configuration 3.7.4.3 Campon Callback...
  • Page 102 Com.X Administrator Guide Page 102 Field Content Disable When checked, the follow-me configuration is ignored and the extension rings as usual. Note: when follow-me is disabled here, directed pick-up of the extension is no longer available. Initial Ring Time The number of seconds to ring the extension before processing the follow-me list.

  • Page 103: Logging Into Phones With An Extension (Hot-Desking)

    Com.X Administrator Guide Page 103 Field Content external number 0115551234 Announcement An announcement to be played to the calling party before processing the follow-me list. Please see section 4.17 for more detail on system recordings. Play Music on If set to Ring, will play ring-tone to the calling party while Hold? processing the follow-me list.

  • Page 104: Configuring Sip Extensions

    -> Configuration -> Setup and then setting the External address. Configure this field to the dynamic DNS name or the FQDN that resolves to the external (public) address of the Com.X (i.e. the external address should be set to the same as will be programmed into the remote phone).

  • Page 105: Configuring Multiple Extensions

    Com.X Administrator Guide Page 105 3.7.10 Configuring multiple extensions Multiple extensions can be configured simultaneously. When the list of extensions for configuration include both analogue and SIP extensions, only those fields that are not unique to any individual extension can be configured: When only SIP extensions are included in the list, only those fields not unique to any of the SIP extensions can be configured.

  • Page 106: Editing Trunk Groups

    Com.X Administrator Guide Page 106 Field Content Name Unique identifier for this group. Analogue groups (FXO) may only be numbers from 1 – 62, and BRI groups may be any unique combination of alpha-numeric characters. Type The group type. Only trunks of this type may be included in the group.

  • Page 107: Adding Trunks To A Group

    Com.X Administrator Guide Page 107 Field Content Enable trunk When disabled, though part of an outbound route, the trunk group will not be attempted for outbound or inbound calls. Instead, outbound calls will fail-over to the next trunk or group in the outbound route.

  • Page 108: Viewing Group Members

    Com.X Administrator Guide Page 108 3.8.2.6 Viewing group members Membership of trunks to their respective groups may be observed either by expanding individual devices listed under the Trunk Ports node, where group membership is denoted in parenthesis after trunks, or by selecting the desired group in the group list under the Trunk Groups node, where the devices and trunks included in the group are listed.
  • Page 109 An UNKNOWN peer will be created and the IP address of the peer will be associated with this trunk on registration. Note: When configuring a Com.X to Com.X SIP trunk, if the registering trunk is configured and applied on the registering Com.X before the SIP provider configuration is applied on the...
  • Page 110 Com.X Administrator Guide Page 110 Figure 92: SIP trunk basic configuration options. ©2010 – Far South Networks 2016...
  • Page 111 When enabled, the system ignores the SIP and SDP headers' address and port and replies to the sender's address and port. This should be enabled when the Com.X is located behind a NAT router. Secure If this is setting is enabled, after registration with the SIP provider, all invites will require successful authentication as well as port number matching.
  • Page 112 'g729:40' Note: Com.X systems support dynamic RTP payloads in the range 96-127. These are set up per-call by the peer using the SDP a:rtpmap parameter. ©2010 –...

  • Page 113: Editing A Sip Trunk

    IP overhead without creating additional latency. If the Com.X is located behind a NAT/firewall on the network, configure the NAT/firewall to forward UDP port 4569 to the Com.X internal IP address.
  • Page 114 An UNKNOWN peer will be created and the IP address of the peer associated with this trunk on registration. Note: When configuring a Com.X to Com.X IAX trunk, if the registering trunk is configured and applied on the registering Com.X before the IAX provider configuration is applied on the...

  • Page 115: Editing An Iax Trunk

    Com.X Administrator Guide Page 115 When negotiating an IAX call, the codec with the highest priority (at the top of the list) will be attempted first, then the second and so on. Codecs may specify the integration time in milliseconds after the codec name in the form codec:integration time, e.g.
  • Page 116 Com.X Administrator Guide Page 116 Field Content Budget Mode Select whether the trunk has an associated budget will be skipped in outbound calling routes when the budget is reduced to zero. Budget trunking is enabled when this is set to Skip When Depleted.

  • Page 117: Budget Trunk Behaviour

    3.10 Outbound route configuration A variety of trunk types can be combined and prioritized to form outbound routes, routing calls based on dial-patterns. The Com.X supports routing to trunk groups, as well as individual FXO trunks and BRI channels. 3.10.1 Viewing configures outbound routes The list of existing configured outbound routes can be accessed by selecting Start, followed by Configuration and the Outbound panel.

  • Page 118: Configuring Outbound Routes

    Com.X Administrator Guide Page 118 3.10.3 Configuring outbound routes Field Content Name A unique name for the route. If set, after a user has dialed a number that matches the dial pattern of this route, the user will be prompted to enter the pin code in order for the call to proceed.

  • Page 119: Adding Trunks To An Outbound Route

    3.11 Inbound route configuration Inbound routes allows incoming calls to be routed to a particular destination based on the incoming call's DID and CID number pair. The Com.X supports a rich set of destination types, greatly simplifying incoming call routing.

  • Page 120: Viewing Existing Inbound Routes

    Com.X Administrator Guide Page 120 3.11.1 Viewing existing inbound routes This list of configured inbound routes can be viewed by selecting Start, followed by Configuration and the Inbound panel. For each configured inbound route, the DID and CID pair used to match the route, the route description, destination type and destination are displayed.

  • Page 121: Configuring Inbound Routes

    Com.X Administrator Guide Page 121 3.11.3 Configuring inbound routes Field Content Direct Inward Dialing allows a number of incoming numbers to be serviced across a limited number of physical connections from the telco to the PBX. This field may contain a pattern to be matched against an incoming number.

  • Page 122: Configuring Call Destinations

    Com.X Administrator Guide Page 122 Table 20: Inbound route configuration 3.11.4 Configuring call destinations 3.11.4.1 Conferences To configure conferences, select Advanced from the main menu bar and Conferences. Once configured, the destinations will become available selections in the Inbound Routes destination menus.

  • Page 123: Phonebook

    To delete an inbound route, select Delete from the route's context menu. 3.12 FlexPath configuration The innovative Com.X FlexPath feature is extremely powerful and allows flexible routing, trunk to trunk routing, gateway and class of service capabilities. FlexPaths allow grouping of call sources into contexts (paths) which can be associated with outbound routes, inbound routing tables, transformations, destinations, etc.

  • Page 124: Flexpath Route Types

    Com.X Administrator Guide Page 124 A number of configuration parameters • One or more FlexPath Routes • Types of FlexPath Routes available are as follows: Include – the selected routing set is simply included (routing sets include • Inbound, Internal, other FlexPaths and Outbound routes) Match –...

  • Page 125: Start

    Com.X Administrator Guide Page 125 3.12.2.3 Start Start routes are special cases of Match routes and match when no DID are available. These routes are used to assign DIDs to originating calls when no DID information is present. Start routes will only match if no DID are available. If it is possible that a DID will be present, include a Match rule as well.

  • Page 126: Deleting Flexpaths

    Com.X Administrator Guide Page 126 Field Content Name Unique name for the FlexPath. Spaces are not allowed in the name. Description Custom description for the FlexPath. Account Code If configured, adds an account code to calls within a FlexPath which can be used to group calls for billing purposes.

  • Page 127: Changing Route Priority In A Flexpath

    Com.X Administrator Guide Page 127 Field Content Routing mode One of Include, Match or Start. Please see 3.12.2 for more detail on FlexPath route types Pattern The DID pattern that this route will match The CID pattern that this route will match...

  • Page 128: Partitioning / Multi-Tenant

    Com.X Administrator Guide Page 128 applied with no break in service. Scenario Extension 301 is required to have access to internal and national dialing only. • Extension 302 is required to have access to internal, national and • international dialing.
  • Page 129 Com.X Administrator Guide Page 129 Two Inbound routes: Fixed incoming DID 8000 is routed to Company A's reception. This DID will be • assigned to BRI calls originating from Company A's BRI channels in a FlexPath Fixed incoming DID 9000 is routed to Company B's reception. This DID will •...

  • Page 130: Simple Partitioned Did Routing

    SIP trunks and PSTN trunks provided for call routing at the head office location. Configuration: Both the head office and the branch office are provided with Com.X units. Extensions: Head office extensions configured as 101 – 105 •...

  • Page 131: Legacy Pbx Remote Extension Gateway

    Com.X Administrator Guide Page 131 3.12.11.5 Legacy PBX Remote extension gateway Scenario: A company has a head-office with 4 FXO trunks to the telco and 10 analogue extensions on a legacy PBX. The legacy PBX has a number of unused extension and trunk ports available.

  • Page 132: Immediate Dialing

    Com.X extension also rings. This enables calls to be recorded on the legacy analogue extensions. Though dialed numbers cannot be recorded in CDR records for the legacy extensions (since the number is not collected by the Com.X solution but rather passed straight through to the legacy PBX), the duration of calls originating from legacy extensions can be recorded.

  • Page 133: Assigning Dids To Bri Ports

    3.12.11.9 Assigning DIDs to BRI ports When DIDs are not provided over BRI channels, DIDs can be associated directly with BRI ports in the Com.X to facilitate call routing. Scenario: DIDs 9001 – 9004 need to be associated with 4 BRI ports.

  • Page 134: Fxo Trunk Pick-Up To Test For Trunk Service

    3.12.11.11 FXO Trunk pick-up to test for trunk service When installing a Com.X, at times it might be useful to determine whether a specific trunk port has been service provisioned by a device connected to the port. For example, the installer might want to check whether a legacy PBX is providing dial- tone in the trunk, or a premi-cell is available.

  • Page 135: Configuring Individual Extensions

    (E.g. a Com.X with a 250GB hard drive can record ~400,000 minutes of voice in A-law WAV format and a Com.X with a 60GB SSD drive ~500,000 minutes of voice in GSM format or 100,000 minutes in A-law WAV).

  • Page 136: On-Demand Recording

    3.13.4 Call recording conditions Due to privacy issues in countries that enforce these, the Com.X recording feature only records calls as follows: Outbound calls are recorded if the caller has recording enabled in the outbound direction or uses on-demand-recording on the call.

  • Page 137: Gateway Recording Encryption

    Com.X Administrator Guide Page 137 Gateway call recordings are stored in /var/spool/asterisk/monitor/ and are named with the prefix “gw-rec”. Note: Outbound calls from extensions will feature two recordings if gateway recording is enabled. One will be prefixed OUT<extension number> whilst the gateway recording will be prefixed ge-rec 3.13.5.1 Gateway Recording Encryption...

  • Page 138: Powering The Com .Xvia An Uninterrupted Power Supply

    • 3.15 Securing the system It is of utmost importance to ensure that the Com.X system is secure. If a Com.X unit is public facing, large costs can be incurred if the VoIP configuration security is weak, or downtime and degraded performance may result from the Operating System being compromised.

  • Page 139: General

    Com.X Administrator Guide Page 139 3.15.1 General Ensure that access to the unit is restricted. Install the Com.X in a secure • server room or locked cabinet. This prevents unauthorized access to the unit using the serial port or USB keyboard, as well as physical damage to the unit or its power supply.

  • Page 140: Call Behavior On No Answer / Busy

    MAC addresses, IP addresses or networks. 3.16 Call behavior on No answer / Busy This section describes the Com.X behavior and call routing for incoming calls that go unanswered or encounter a busy extension. 3.16.1 Unattended transfer On unattended transfer, the person transferring the call is taken out of the loop, i.e.
  • Page 141 Com.X Administrator Guide Page 141 with a modification to the CID. The new CID presented to the transferring party will be prefixed by “Ret:” to indicate that the call is returning, as well as a the extension number of the destination extension to which the original call was transferred. The Ringback caller id will have the form : “Ret: [original intended destination extension]CID”...
  • Page 142 Com.X Administrator Guide Page 142 √ √ Destination extension voicemail Destination √ √ √ √ extension Follow me failover. √ √ Destination √ √ √ √ extension Follow me failover. √ √ √ √ Destination extension voicemail √ √ √...

  • Page 143: Disabling Ringback Functionality

    Com.X Administrator Guide Page 143 Note: Users need to be informed as to what to expect. With ring-back enabled their phones should 'ring by itself' once available. If the hand-set it picked up, they should hear ringing while the initial calling party is being contacted.

  • Page 144: Advanced Configuration

    Com.X Administrator Guide Page 144 4 Advanced configuration Access to a variety of advanced features is provided via the Advanced menu. Selecting a function from this menu opens a new window, which can be maximized with detailed configuration options for the feature. Once configured, select Submit at the bottom of the configuration page.
  • Page 145 Com.X Administrator Guide Page 145 Field Content Callback description A custom description for this callback. Callback number The number to call back. If this is left blank, the caller ID will be used to callback. Note: the device to be called back must support incoming calls directly(e.g.

  • Page 146: Conferences

    Com.X Administrator Guide Page 146 4.3 Conferences This feature allows multiple users to join a conference with two-way audio on all devices. Conference features include join and leave announcements, passwords, conference administration, in-conference menus, etc. Field Content Conference number The number to dial to access the conference...

  • Page 147: Day / Night Control

    Page 147 4.4 Day / Night control A number of day / night modes can be programmed on the Com.X. Each has a feature index and can route calls according to its own set of rules. These allow configuration of day / night to support multiple receptionists, tea or lunch breaks, after hours, etc.

  • Page 148: Feature Codes

    Com.X Administrator Guide Page 148 Field Content Feature code index The index of this day/night mode. The index is the day-night feature code (please see section 4.5 for more detail on feature codes), with the last digit of the feature code (e.g. 280) replaced by this day/night's index (e.g.283, 284, 288, etc.) Up...
  • Page 149 Com.X Administrator Guide Page 149 enable or disable the function, or revert to the default feature code associated with the function. Field Content Name The name of the function category or the individual function. Code The feature code currently associated with the function...

  • Page 150: General Settings

    Com.X Administrator Guide Page 150 4.6 General Settings General settings apply system-wide on the Com.X platform. Users can typically override general settings with their own preferences, but some general settings override all user preferences. 4.6.1 Dial command options t: Allow the called user to transfer the call with the “in-call blind transfer” feature code (default ##).
  • Page 151 Call recording format Recordings will be saved on the Com.X hard drive in the format selected here. Options are: wav, law, alaw, GSM, SLN, G.729.
  • Page 152 Timeout/#-press default The internal destination to route a user after timeout. This should remain the default unless requested otherwise for test purposes by Far South Networks. Loop Exceed default The destination that a user is transferred to when ©2010 –...
  • Page 153 The email address from which faxes appear to have appear to come from been sent, when “Extension of fax machine for receiving faxes” is set to “system” Country Indications Configures the Com.X PBX country ©2010 – Far South Networks 2016...
  • Page 154 Allow the system to automatically check the internet for FreePBX and Asterisk version updates. Updates of the FreePBX and Asterisk modules are managed by Far South Networks for the Comma and Com.X product ranges. This field should be left blank. Update email An email address to send notifications of available updates to.

  • Page 155: Ivr

    Com.X Administrator Guide Page 155 4.7 IVR The Interactive Voice Response feature allows the creation and chaining together of interactive voice announcements and corresponding menu selections to facilitate user call transfer in the Com.X system. ©2010 – Far South Networks 2016...
  • Page 156 Com.X Administrator Guide Page 156 Field Content Change Name Changes the name used to identify this IVR from the default (Unnamed). This entry will be displayed in selection lists that support IVR. Announcement The audio message to be played to the user when this IVR is accessed.
  • Page 157 Com.X Administrator Guide Page 157 Field Content Invalid message If specified, this audio message is played when the user selection is invalid. Repeat loops The number of times the IVR should be played if the user does not provide an option before timeout, or if the option is invalid.

  • Page 158: Music On Hold

    Warning: If you incorrectly configure the application entry above, applying might result in the apply freezing up. To fix this, restart the Com.X, correct the application entry, or remove the streaming music on hold category and apply.

  • Page 159: Adding A Music Category

    If this is disabled, files are played in the order listed here. Table 33: Playback configuration 4.8.3 Adding a music category Music categories categorize the audio files available on the Com.X PBX server storage. Field Content Category name...

  • Page 160: Outbound Routes

    Com.X Administrator Guide Page 160 Field Content Category name A unique name for this streaming category. Application This is the "application=" line used to provide the streaming details to Asterisk. Please see information on the musiconhold.conf configuration for different audio and internet streaming source options.

  • Page 161: Paging

    Com.X Administrator Guide Page 161 Field Content Route name A unique name for this route. Route password An optional password. If present, users will be prompted to enter this password before call routing using this route is allowed. Note: this is a single password for the route.

  • Page 162: Intercom

    Com.X Administrator Guide Page 162 Field Content Paging extension The extension to dial to activate the page Group description A custom description for this group Device list The list of devices and extensions to include in this paging group Force if busy...

  • Page 163: Parking Lot

    Com.X Administrator Guide Page 163 4.12 Parking Lot Callers can be placed in a parking with a time out associated, after which the caller is transferred to the specified destination. This allows receptionist, for example, to place a caller on hold while waiting for their desired extension to become available. The caller in the parking lot would then, after the parked timeout, automatically ring reception again, by which time the desired extension might have freed up.

  • Page 164: Pin Sets

    “Name”;number;speeddial If large phonebook databases (> 2000 entries) are to be uploaded, additional configuration is required. Please see the Com.X Troubleshooting guide for more detail large phonebook imports. Note: If the delimiter is something other than ';' the import will fail. Please see your operating system / application help for configuring ';' as the CSV export...

  • Page 165: Queues

    Page 165 4.15 Queues Queues are a powerful feature of the Com.X system, allowing callers to be placed on hold and transferred according to a number of strategies and based on priority. Callers waiting in the queue are provided with their position in the queue, projected waiting time and the option to use self-service menus to exit the queue and transfer to other destinations.
  • Page 166 Com.X Administrator Guide Page 166 Field Content Queue number The extension number of the queue. Any calls or transfers to this extension will be routed to the queue. Queue name A unique name for the queue. Queue password An optional password. If set, agents will need to log in with this password before they can service the queue.
  • Page 167 Com.X Administrator Guide Page 167 Leastrecent: Rings the agent who was least recently called by this queue. Fewestcalls: Rings the agent who has serviced the fewest calls from this queue. Random: Rings an agent at random. Rrmemory: Round robbin with memory. Rings each agent...

  • Page 168: Ring Groups

    Com.X Administrator Guide Page 168 Frequency The frequency with which their position and estimated hold time is announced to the caller. Announce position If set to Yes, the annoucements will tell the caller their position in the queue. Announce hold...
  • Page 169 Com.X Administrator Guide Page 169 Field Content Ring group The number a caller will dial to ring extensions in this ring number group. Group description A descriptive title for this ring group. Ring strategy The strategy with which to ring extensions in this ring group.

  • Page 170: System Recordings

    Com.X Administrator Guide Page 170 and other features. Ignore CF settings When checked, agents who attempt to use call forward will be ignored. Skip busy agent If checked, agents on an occupied line will be skipped as if the line were returning an unavialble signal. This prevents calls form being presented to call waiting features.

  • Page 171: Time Conditions

    Page 171 4.18 Time Conditions Time conditions check the current Com.X system time and compares it with the specified Time Group to determine whether there is a match. The call is then routed either to a day-night entry if this over-ride has been enabled, or to the match destination if the current time falls within the time block specified in the Time Group, or to the no match destination otherwise.

  • Page 172: Time Groups

    Com.X Administrator Guide Page 172 4.19 Time Groups Time groups allows the specification of blocks of time for use in call routing rules, such as time conditions. Please see 4.18 for more detail on Time Conditions. Field Content Name A name to identify this time group with. This will appear in selection lists that allow time groups.

  • Page 173: Voicemail Blasting

    A DISA destination allows for an outbound dial tone to be configured as a destination on the unit. This could be used to allow particular external callers to make outbound calls through the outbound routes on the Com.X. Field Content DISA Name An appropriate name for the DISA destination.

  • Page 174: Listening In On Calls / Spy Feature

    4.22 Listening in on calls / Spy feature The Com.X PBX allows a spy feature to be enabled that allows the listener to listen in on calls in progress. Input from the listener will not be audible to the callers on the call being listened in to.

  • Page 175: Monitoring The System

    Configuration details, Host system monitoring, Telephony status and events and GUI web server status. 5.1 GUI Status Page The status page of the Com.X GUI offers vast monitoring features, as well as displaying the configuration status of the Com.X. 5.1.1 Status Display The GUI offers a display to indicate the overall status of the system configuration and synchronization.

  • Page 176: Call Detail Records (Cdr)

    Table 47: Logging levels Logging takes place on the CLI as well as to /var/log/asterisk/messages. From the Com.X GUI, two levels of detail can be selected, namely “brief” or “verbose”. These may be accessed using Monitor -> Asterisk -> Set log level <Brief/Verbose>...

  • Page 177: Enabling Logging To Csv

    A results summary is displayed at the bottom of the list, where navigation of the list is also facilitated. CDR records are stored in a database on the Com.X and can be backed up. Please see 2.2.1.1.4 for more detail on backing up the CDR database.

  • Page 178: Deleting Of Call Recordings

    Com.X Administrator Guide Page 178 The Com.X provides monitoring of the available space on the hard drive, SSD or SD card.Space on the device is consumed as new calls are recorded and the recordings are saved. The Com.X monitors the storage and sends a notification email (see section 3.1) once the space consumed in exceeds a particular threshold (default...
  • Page 179 Com.X Administrator Guide Page 179 Category Function Description Set log level brief Enable logging of notices, warnings and errors only Set log level verbose Enable logging of DTMF, verbose messages, notices, warnings and errors Configuration DHCP Configuration Dahdi system Dahdi span configuration (/etc/dahdi/system.conf)
  • Page 180 Com.X Administrator Guide Page 180 Category Function Description Reload mISDN Reloads the mISDN module. Service to BRI channels will be lost while reloading. Reload Dahdi Reloads the dahdi module. Service to analogue and PRI channels will be lost while reloading.
  • Page 181 Com.X Administrator Guide Page 181 Category Function Description might indicate network performance issues that could result in a decrease in call quality. Device discovery Displays the list of Comma devices visible to the Comma Manager on all networks, including their ethernet and IP configuration status.

  • Page 182: Advanced Administration

    Page 182 6 Advanced Administration 6.1 Console access Note: Any customisation or third party integration not explicitly endorsed and supported by Far South Networks will result in the software warranty becoming void. 6.1.1 Authentication Default username: comma Default password: farsouth It is advisable to change the authentication information from the default if the unit is accessible over the network via secure shell.

  • Page 183: Editing System Files

    Figure 101: 'sudo asterisk -rx "stop when convenient" ' stops the asterisk service, so that no calls are cut off, then 'sudo reboot' reboots the Com.X system. 6.3 Configuring email services 6.3.1 Configuring voicemail to email...

  • Page 184: Configuring Sendmail For Mail Relay

    6.3.2 Configuring sendmail for mail relay Note: Mail relay configuration is not backed up by the Com.X backup utility. The Com.X product range makes use of sendmail for outbound SMTP mail delivery. The sendmail server will attempt to directly resolve destination mail server addresses and contact these servers directly for mail delivery.

  • Page 185: Sending A Test Email

    Com.X Administrator Guide Page 185 Figure 103: Sendmail configuration 6.3.3 Sending a test email You can send a test email by using the 'mail' command. The first parameter of the mail command is the destination email address. After entering a subject, enter the message body.

  • Page 186: Stopping And Restarting The Asterisk Pbx Software

      sudo asterisk ­rx "core show channels" | grep ­x "0 active calls"    sleep 1  done 6.5 FreePBX access Though we strongly recommend using the Com.X GUI for all configuration tasks, occasional advanced configuration might be required that necessitate the use of FreePBX. To access the FreePBX configuration GUI, point your browser at: http://<ip­of­pbx>/freepbx...

  • Page 187: Manually Backing Up And Restoring The Configuration

    6.7 Setting the system's date, time and timezone The Com.X unit tries to obtain date and time from an NTP server on the internet. Failing this, or in the case where the date / time discrepancy on a unit is large, the date and time can be configured as follows: 1.

  • Page 188: Video Call Support (H.263 And H.263+)

    Com.X Administrator Guide Page 188 6.8 Video call support (H.263 and H.263+) The Com.X platform may be configured to support video calls. Care should be taken to evaluate potential performance impacts of video codec translation on the platform in question.

  • Page 189: Booting The Com .Xin Recovery Mode

    6.13.1 MAN 3000 6.13.1.1 Installing MAN 3000 support The Com.X supports logging of call records to a MAN 3000 buffer across ethernet. To enable support for MAN 3000 on a Com.X unit, from the shell, install the MAN3000 support package: sudo aptitude install commaman3000 For Man3000 releases prior to 11.02:...
  • Page 190 Activate the Man3000 TCP/IP configuration by enabling Soft Online Authentication, or your Man3000 USB software dongle: Figure 104: Man3000 settings menu Figure 105: Man3000 port settings Configure the TCP/IP settings with the IP address of the Com.X PBX: ©2010 – Far South Networks 2016...
  • Page 191 Page 191 Figure 106: Man 3000 TCP/IP configuration Installing the PBX templates: Download the Far South Networks MAN3000 PBX format template from the Far South Networks website at http://farsouthnet.com/support/technical-notes/(right-click Save Target As, or Save Link As) Alternatively, download the formats directly (using a downloader such as wget) from: http://archive.farsouthnet.com/support/fsnInbound.PBX...
  • Page 192 Com.X Administrator Guide Page 192 Figure 107: Man3000 format settings Figure 108: Importing a Man3000 format template ©2010 – Far South Networks 2016...

  • Page 193: Cdr Format

    Com.X Administrator Guide Page 193 6.13.1.2 CDR format Records are streamed to MAN 3000 in the following format: Column: 1 2 Type / Line Type / Line Date Time Channel Source Destination Bill Account Code Table 49: Man3000 CDR format column headers ©2010 –...
  • Page 194 Com.X Administrator Guide Page 194 Field Content Type / Line In the first column, a value of 'I' indicates that the record is for an incoming call. Any other value indicates the line number as defined in /etc/commagui/man3000.patterns for an outgoing call, or 9 in case the channel for the outgoing call was not pattern matched.

  • Page 195: Defining Outbound Line Numbers

    To configure the Com.X to start logging records again at some date in the past, modify the /var/lib/commaman3000/lastdate file located in the Com.X file system. This file can be created on a separate system or laptop and copied onto the Com.X as follows: scp lastdate comma@<ip­of­com.x>:/var/lib/commaman3000/...

  • Page 196: Asterisk Tms Systems

    We strongly recommend installing third party TMS software on a separate machine, accessing the Com.X CDR files and database with read-only access. Third party TMS systems have access to Com.X CDR records via one of the following tools: After installation of the commaman3000 package, CDRs are served on the •...

  • Page 197: Setting Up A Streaming Music Server

    /usr/bin/mpg123 ­q ­s ­­mono ­r 8000 ­f 8192 ­b 100 ­@ http://<ip>:<port>/recurse.m3u  Warning: If the above application entry is incorrectly configured, applying might result in the apply freezing up. To fix this, restart the Com.X, correct the application entry, or remove the streaming music on hold category and apply. ©2010 –...

  • Page 198: Microsoft Outlook Integration

    6.15.1 Outcall Outcall supports only SIP extensions, but in addition to making outbound calls also pops up contact details for incoming calls. Outcall has been tested with the Com.X using Outlook 2000 and Outlook 2007. Download the Outcall installer from http://code.google.com/p/outcall/downloads/list...
  • Page 199 Add the extension to be used for the PC running outlook. This must be a SIP extension: Figure 111: Outcall extension configuration Log in via the ssh shell onto the Com.X and create an AMI user account as follows in /etc/asterisk/manager.d/outcall.conf [testuser] secret = fsntestuser...

  • Page 200: Asttapi

    Com.X Administrator Guide Page 200 In Outlook, select the contact to call and select the “Outcall” button. When a call is received by the Com.X, the calling contact, or a new contact window should appear in Outlook. Figure 112: Outlook contacts integration 6.15.2 asttapi...
  • Page 201 User Channel The extension channel (e.g. SIP/8263 or Zap/8) Line name The name of the line as displayed in Outlook (e.g. Far South Networks Com.X) Context from-internal (or the flexpath context for class of service configurations) Called ID The caller ID for the extension Table 52: asttapi configuration Apply the configuration.

  • Page 202: Fail2Ban Integration

    Com.X systems are shipped with fail2ban installed and enabled. fail2ban provides a comprehensive and flexible mechanism for preventing unauthorized access to Com.X systems. The fail2ban application acts as a security monitor and firewall manager, detecting multiple failed attempts to access a service (such as ssh or SIP) from the same IP address and then blocks the address for a configured period of time.

  • Page 203: Flash Operator Panel

    From the operator panel, calls can be answered, transferred, originated, recorded and ended, using simple clicks of a mouse. The demo version of the Flash operator panel included as stock on Com.X products allows for up to 15 extensions, trunks, queues or parking lots. By default, the panel will show buttons for the first 15 such mechanisms configured, but not for any configured thereafter.

  • Page 204: Accessing Flash Operator Panel

    Com.X Administrator Guide Page 204 Figure 117: FOP access can be limited to the operator only, if required. 6.18.5 Accessing Flash operator panel The flash operator panel is accessed by selecting the “Operator Panel” icon on the launch page of the GUI.

  • Page 205: Using Fop2

    Com.X Administrator Guide Page 205 6.18.6 Using FOP2 Once logged in to the Flash operator panel, the extension of the logged in user will be displayed on the top left button, with the extension number in bold. Operator extensions will be presented with more functionality options than regular users, controlled by black button icons listed above the extensions.

  • Page 206: Answering Calls

    Com.X Administrator Guide Page 206 panel users. Figure 123: Dialling extension 2000 from extension 1000. Notice the blue outline around extension 2000. This first causes extension 1000 to ring, and upon a user answering, dials extension 2000 from extension 1000.

  • Page 207: Listening To Calls

    6.19 Nagios The Nagios application provides an expandable and highly customisable platform for monitoring of system services and network health. Com.X units are shipped with a Nagios Core suite preconfigured to monitor the state of selected services and interfaces on the system.

  • Page 208: Hosts

    6.19.1 Hosts Nagios can be configured to monitor network and service status on mulitple hosts. The Nagios application on the Com.X system has the localhost defined as the only host, however more hosts can be defined and monitored, if required.

  • Page 209: Disabling Active Nagios Checks On A Service Or Port

    Com.X Administrator Guide Page 209 Service What is monitored? BRI mISDN Port Provides the status of each BRI mISDN port on the system. Status Including the link type (Point-to-point or point-to-mulitpoint), the network or terminal status of the port, as well as the status of the L1 and L2 links.

  • Page 210: Customised Monitoring And Reporting

    Com.X Administrator Guide Page 210 Figure 130: Options available for configuring Nagios monitoring on a port or a service. Select “Disable active checks of this service” . This will prevent the Nagios application from monitoring the service or port. Thereafter, select “Submit passive check result for this service” and set the check result to “OK”.

  • Page 211: Troubleshooting

    Com.X Administrator Guide Page 211 7 Troubleshooting Please refer to the Com.X Troubleshooting Guide for trouble-shooting information. This guide can be accessed from http://farsouthnet.com/support/ ©2010 – Far South Networks 2016...

Table of Contents