Introduction - Dashboard - Wildix Training

 This step-by-step guide leads you through the process of activation and configuration of the Wildix system.Created by Elena KornilovaUpdated: May 2016WMS version: 3.81.31891Online version: INDEX:IntroductionPART 1. First Time Login and PBX Activation1.1. Connection and first time login1.1.1. Connection1.1.2. HTTP/HTTPS Access to WMS1.1.3. Change admin passwordAppendix 1: PBX access via RS-232 serial port and SSH1.2. PBX Activation via WMP1.3. Introduction to WMSPART 2. Network configuration2.1. Choosing the Network scenario2.1.1 Shared data and voice network2.1.2 Separated data and voice networks2.1.3 Separated data and voice networks with traffic shaper2.2. PBX domain name *.PART 3. Basic WMS configuration3.1. Time and date settings3.2. Remote Support3.3. Activation3.4. Storage services3.5. System Backup and Upgrade3.5.1. Generate a System Backup3.5.2. Upgrade the System to the Latest Release3.6. DHCP Server3.7. SMTP Client3.8. CDR3.9. SIP-RTP3.10. General Dialplan SettingsPART 4. WMS Network configuration4.1. Basic features of WMS Network4.2. Master and Slave configurationPART 5. Users5.1. Add / Import usersAppendix 2: User preferencesPART 6. Provisioning of devices6.1. Provisioning modes supported by Wildix PBX6.1.1 Auto-configuration via auto.Appendix 3: Network configuration for auto. provisioningAppendix 4: Auto-configuration of W01GSM with auto.6.1.2 Auto-provisioning (Automatic mode)6.1.2 Remote provisioning (Semi-Automatic mode)PART 7: Assign phones and FXS ports to users7.1. Connection and login of WP600A / WP600ACG7.2. Assign Wildix phones (WP4X0)7.2.1 Assign WP4X0 to users via WMS7.2.2 Assign WP4X0 to users via Feature Code7.3 Assign analog ports of FXS to users7.3.1 Assign W01FXS7.3.2 Assign ports of W04/24FXSPART 8: W-AIR DECT solution8.1 Introduction8.2. Create a W-AIR network8.3. Configuration and login of W-AIR handsetsPART 9. Introduction to Unified Communication9.1. Introduction to Wildix Collaboration9.2. App for Android / iOS9.3. Call activity analysis and reporting with CDR-ViewPART 10. Trunk Configuration10.1. VoIP Trunk configuration10.1.1 Make a test of SIP trunking between 2 PBXs10.2. Connection of Wildix media gateways10.2.1 Configuration of BRI/PRI trunk10.2.3 Connection of a GSM gatewayAppendix 5: Trunk groupsAppendix 6: PricelistsPART 11. Dialplan: how it works11.1. Association to users and trunks11.2. Add and edit Dialplan procedures11.3. Matching called numbers11.4. Included procedures11.5. Dialplan applicationsPART 12. Dialplan practical examples12.1. External Dialplan: “main”12.1.1 Route incoming calls to call agents (call groups)12.1.2 Record and playback audio messages12.1.3 Create a switch12.1.4 Create a timetable12.1.5 Create an IVR tree12.1.6 Incoming faxes management12.1.7 DID and DISA12.1.8 Mobility extension lookup12.1.9 Example of “main” procedure configuration12.2. Internal Dialplan: “users”12.2.1 Example of “users” procedure configurationPART 13. Introduction to WebRTC Kite solution13.1. Personal Kite link for each PBX user13.2. WebRTC Video conferencePART 14. Debugging and troubleshooting14.1. SSH connection14.2. Dialplan debug14.3. Trace generation14.4. Syslog, Reset and recovery of media gateways and phones14.5. OtherAppendix 7: Ports to open for Wildix servicesIntroductionWelcome to the Wildix Ecosystem.Wildix is a multinational company operating in the telecommunications industry, specializing in VoIP products. Wildix offers a complete HW/SW solution allowing you to avoid 3rd party product-related issues:VoIP PBX (Physical / Virtual / Cloud) and USB key resistant to high temperaturesPoE Switches (including Gigabit models) and VDSL PoE ExtenderVoIP Phones (including Gigabit models) and accessoriesDECT system and VoIP DECT handsetsMedia gateways (PRI / BRI / FXO / FXS / GSM)Enterprise WiFi system Basic features of Wildix VoIP PBX:Support of WMS Network mode for multisite installationsIntegrated Failover Integrated Fax ServerIntegrated WMS software with PBX admin interface accessible via the browser Auto-provisioning of all Wildix devices (phones, media gateways, base stations)Support of upgradesSupport of Unified Communications (Wildix Collaboration and its components)Support of WebRTC (Wildix Kite)Support of SIP operatorsSupport of ISDN lines, analog lines (FXO), analog devices (FXS), GSM media gatewaySupport of Unified Communications Wildix WMS software consists of two components:WMS admin interfaceCompletely web based and accessible via the browser on Mac OS, Windows, Linux allowing a system administrator to manage PBX, users, devices, lines and Dialplan.Collaboration user interfaceCompletely web based and accessible via the browser on Mac OS, Windows, Linux Free of charge app for smartphones iOS / AndroidCan be activated on any Wildix PBX and provides access to Unified Communications services, such as presence of colleagues, chat, audio and video calls, conferencing, sending of Faxes and SMS messages, screen sharing etc, from PC, Android / iOS devices…Additional applications: CDR-View (call activity analysis and reporting), W-TAPI (Windows TAPI and WebAPI), WebRTC Kite (videoconference and possibility for external users to contact PBX users via a link or a contact button on the website).USEFUL LINKS:Official website: WMP (activation, licenses, orders, tickets): news: Wizards FB group: Blog: : 1. First Time Login and PBX Activation1.1. Connection and first time login1.1.1. Connection1.1.2. HTTP/HTTPS Access to WMS1.1.3. Change admin passwordAppendix 1: PBX access via RS-232 serial port and SSH1.2. PBX Activation via WMP1.3. Introduction to WMS1.1. Connection and first time login1.1.1. ConnectionAccess is possible via HTTP – HTTPS – SSH or via RS-232 serial port. Insert the USB Memory Key (WKEY2GB) into the USB port of the PBXPower on the PBX (connect the PBX to the power supply and move the switch situated on the front panel to the “1” position)Connect the PBX to the Switch (use WAN port) or to your PC (use LAN1 port) via RJ-45 network cableDOCUMENTATIONLook for the following documentation on : PBX Quick Start GuidePBX and USB key datasheetsWildix Switches datasheets and manualsVirtual PBX: Cloud PBX: 1.1.2. HTTP/HTTPS Access to WMSDefault settings of Ethernet ports:LAN1: DHCP – Server, IP – 10.135.0.1/24Use the IP address 10.135.0.1WAN: DHCP – Client, IP – DynamicUse the IP address released by the DHCP server;Access the WMS interface:Open the browser (we recommend Google Chrome last version)Type or into the URL, example: the credentials for the first time access:user : adminpassword : wildix1.1.3. Change admin passwordNote: to change the language of the WMS interface, double click on the “admin” user and select the language from the list.Before starting to configure the system, you must change the admin password:Note: this admin user is the “super admin” and is the only user with full access to all the levels of the system management. Select the admin user and click the button “Set passwords”:Current: enter the current password (wildix)New: click “Generate” to automatically generate a strong password (click “Show” to display the password generated by the system). Otherwise you can compose your own strong password, consisting of at least 8 symbols, at least 1 uppercase, 1 lowercase, 1 digit.Note: this password is used by the admin user to access the WMS interface.SIP/VoIP password is used to register and assign remote devices. Enter the email address of the admin user to be able to receive email notifications: double click on the admin user and fill in the field “Email” Appendix 1: PBX access via RS-232 serial port and SSHRS-232 serial portUse the RS-232 cable to connect your PC to the serial port of the PBXOpen the RS-232 terminal (such as PuTTY for Windows or ZetaTerm for Mac) and set up the baud rate to 19200Connect the PBX to the power The boot menu is displayed: Reset root password: enables PBX password recovery, returning it to default (user : admin , password : wildix).Recovery system: recovers the system and deletes all the current configuration (Attention: this operation must be authorized by Wildix technical support). At the end of the startup procedure, the PBX requests the access credentials, then displays the console menu: SSHIf your PBX is already accessible in the network at the default IP (LAN port) or at the IP released by your DHCP server (WAN port), you can access your PBX using some SSH client. 1.2. PBX Activation via WMPWMP stands for Wildix Management Portal available at portalWMP must be used for:PBXs activation and activation of Wildix applications (Collaboration, CDR-View…)Remote support (remote connection to PBX)Support ticketsAuto-configuration of Wildix devicesThis is why it is important to make sure your PBX can connect to the remote server wmp. (see Appendix 7)Make sure that Firewalls that limit the Internet access to the PBX, allow the traffic to wmp. and vpn2. on the 443 TCP and 1194 UDP ports.Access the Wildix Management Portal (WMP – portal) using your credentials (which you must have received by email)Go to the tab “PBXs”Enter the serial number of the PBX into the field “Serial” and click “Apply”Note: the serial number (MAC) can be found on the PBX shipping boxClick “Details”Click “Register”Select the license “PBX activation” from the list and click “Submit”Note: in the same way you can register other licensesThe PBX is now activated (as well as the trial licenses, which are available for one of your PBXs):1.3. Introduction to WMSWMS is accessible via the browser on any OS (Mac OS, Windows, Linux). Main menu: 1 - Users: add users, change preferences and passwords, move users from one PBX to another one in WMS network, set up permissions of ACL groups, import phonebooks2 - Trunks: add VoIP trunks, set up parameters of media gateways, create huntgroups (groups of trunks), import pricelists3 - Devices: provision devices, assign WP phones and ports of analog devices to users, create W-AIR networks4 - Dialplan: set up the strategy for call routing, create timetables, switches, create call groups, create IVRs, set up the general dialplan parameters5 - Settings: system and network configurationSecondary menu: 6 - Port blocks: notification (red=error; yellow=warning) in case ports needed for remote trunks / phones are not open (see Appendix 7)7 - SIP blocks: click to see the list of temporarily banned IP addresses (in case of unsuccessful login attempt). The icon is visible only in case there are banned devices.8 - Info: click to open monit application that provides the information on the system performance, the current processes, the resources engaged, etc9 - Generate call: click you to perform a test call or an echo test using a selected Dialplan procedure10 - Sounds: via this menu you can upload music on hold and ring tones, record the messages for operator (More information in Dialplan configuration chapter)11 - Terminal: access to the console (enabled only for the admin user)12 - Debug: click to view the simple log of each call generated on the PBX (More information the last chapter of this Guide)13 - Reboot / Halt 14 - LogoutPART 2. Network configuration 2.1. Choosing the Network scenario2.1.1 Shared data and voice network2.1.2 Separated data and voice networks2.1.3 Separated data and voice networks with traffic shaper2.2. PBX domain name *.2.1. Choosing the Network scenarioGo to Settings > System > NetworkSet up the network parameters based on the selected network scenario: Shared data and voice networkSeparated data and voice networks Separated data and voice networks with traffic shaper2.1.1 Shared data and voice networkIn this scenario the single connected interface is ETH0, the IP address is released by the DHCP server in the network.Select the WAN eth0 interface and enable the option “Get the address from the DHCP server” The other interfaces remain disabled.Click “Apply the network settings”.The IP address assigned to the PBX could have changed. Check the leases list of your DHCP server to know the correct IP address of the PBX.2.1.2 Separated data and voice networksIn this scenario the PBX is used as the DHCP server and releases the IP addresses for all the devices.Select the WAN eth0 interface and enable the option “Get the address from the DHCP server”:Select the LAN eth1 interface, the IP address by default is 10.135.1.1:Click “Apply the network settings”The IP address assigned to the PBX could change. Check the address of WAN eth0 interface to know the correct IP address of the PBX.2.1.3 Separated data and voice networks with traffic shaperIn this scenario the bridge is created between eth0 and eth2 interfaces, while the third interface eth1 is used for the separate network.It is possible to set up the bandwidth upload and download limits on the WAN eth0 interface. The PBX reserves the bandwidth needed for the communication with VoIP operators and remote phones. The priority is given to the traffic generated on the LAN eth1 port.2667000Connect the second Switch to the LAN2 port of the PBXClick “Enable traffic shaper eth0-eth2”Click “Apply the network settings”The bridge between WAN eth0 and LAN eth2 interfaces is created, leaving a separate network to the remaining LAN eth0 interface. The interfaces eth0 and eth2 are no longer present on the page, the interface wbr0 is used as WAN which maintains the same settings of the eth0 interface (either static IP or DHCP client.Select the WAN wbr0 interface and set up the bandwidth limits for Downlink and Uplink, to reserve this bandwidth for the communication with VoIP operators and remote phones:LAN eth1 interface settings:Click “Apply the network settings”The IP address assigned to the PBX could change. Check the address of WAN wbr0 interface to know the correct IP address of the PBX.2.2. PBX domain name *. The “Hosts” section contains DNS settings. Wildix provides the domain name *. which is available for all the PBXs. Insert the name of your PBX into the field “System name”, for example: elenatestEach PBX with Public IP can be accessed over HTTP/HTTPS in several ways:Public IP address PBX Serial number + , example: 0a1bc2345d67.Domain name set up in “System name” field, for example: elenatest.The last variant is obviously the easiest one to remember.In addition, domain name is be very useful if your PBX doesn’t have a static Public IP address. In this case you will be always able to access the PBX by its domain name, even in case the Public IP has changed. Note: Value set up in “System name” is synced with the one set up in WMP > PBX Details > “Name”.DOCUMENTATIONNetwork settings guide: Blog article about domain: 3. Basic WMS configuration3.1. Time and date settings3.2. Remote Support3.3. Activation3.4. Storage services3.5. System Backup and Upgrade3.5.1. Generate a System Backup3.5.2. Upgrade the System to the Latest Release3.6. DHCP Server3.7. SMTP Client3.8. CDR3.9. SIP-RTP3.10. General Dialplan SettingsAfter you have set up the network parameters in Settings > System > Network, the PBX can connect to the Internet. 3.1. Time and date settingsGo to Settings > System > NTP Server:Make sure that:The timezone is correctTime and date are synced with NTP servers3.2. Remote SupportGo to Settings > Tools and utilities > Remote support: “Server status” must be “started”.To enable the PBX to connect to the Wildix server (WMP), make sure that Firewalls that limit the Internet access to the PBX, allow the traffic to wmp. and vpn2. on the 443 TCP and 1194 UDP ports.3.3. Activation Go to WMS Settings > Tools and utilities > Activation and licenses: check that the PBX and the Additional services are activated (“Activation” section > “Activated”, “Additional licenses” section: “Yes” in front of each service). To refresh the licenses you enabled on WMP, click “Refresh via Internet”3.4. Storage servicesGo to Settings > System > StoragesThe USB key you have inserted into the PBX serves to store such data as Voicemail messages, call recordings, faxes, CDR, CTI data, etc.It is recommended to store the Backups on another USB drive or on a Windows / NFS Share, to be able to restore the system in case of the primary USB drive’s failure.The first section “Storage Device” displays the storage devices mounted at the system startup with the relative table of the partitions and the usage of the specified partition.Click “Initialize” (under “Action” column) to start the partition and formatting procedure of the storage device.Click “+” (under “Action” column) to add a partition.Click “+” (under “Windows Share” or “NFS Share”) to add a storage server.3.5. System Backup and Upgrade3.5.1. Generate a System BackupEach time before proceeding with the system upgrade, it is necessary to create a backup.Note that to be able to perform the upgrade, the PBX must be able to connect to the remote server wmp. (see Appendix 7).Firewalls that limit the Internet access to the PBX should allow the traffic to wmp. and vpn2. on the 443 TCP and 1194 UDP ports.Go to Settings > Tools and utilities > Backup systemThis menu allows you to create and download the system backup and set up a scheduled system backup.To create a backup:Click “Generate and download backup” to save the backup to your PCOtherwise click “Create a backup” to save a backup on the PBX (in our case, to the USB key).The tab “Scheduled backups” allows you to set up a scheduled system backup (daily, weekly, monthly) to share, FTP or mail.3.5.2. Upgrade the System to the Latest ReleaseGo to Settings > Tools and utilities > UpgradeEnter the name of the repository (rel380) into the field “Upgrade repository” and click “Save”.The system checks whether there is a new version available in the selected repository.In case there is a new version available, click “Perform upgrade”.Click “Yes” in the popup window:As a rule, the Upgrade procedure takes several minutes:As soon as the update procedure is over, the button “Reboot” appears:Click “Reboot” and wait till the system is being rebooted:As soon as the PBX has been rebooted, the login page appears.Log in to the WMS, the current WMS version is shown in the upper right part of the screen:NOTE: In case the upgrade procedure was not successful, it is possible to apply the backup that you had previously created (Settings > Tools and utilities > Backup system).NOTE: Wildix offers the repository rel380beta for its Partners to test the latest features and fixes, the changelog is available at 3.6. DHCP ServerGo to Settings → System → DHCP server.If the chosen network scenario uses the PBX as the DHCP server to assign IP addresses to devices, check that the options of the service are enabled with the correct settings:DHCP server is integrated for auto provisioning of supported devices. It’s possible to enable the server for the initial configuration of the devices and successively disable it, otherwise to enable the parameter “Deny unknown clients”.Parameters:Enable DHCP server at boot time: enables internal DHCP server and allows you to select the interface on which the server is enabled (normally eth1)must be more than / must be less than: range of IP addresses that can be assigned to hostsDefault lease time (mins): minimum time period for lease durationMaximum leases: maximum number of leases that can be assignedDomain name suffix: if the hosts are inserted in the network which is managed by the domain controllerDefault gateway: IP address of the router or of the PBX (in case of LAN interface)Primary / Secondary DNS server: addresses of DNS serversPrimary /Secondary NTP Server: addresses of NTP serversPrimary / Secondary WINS Server: addresses of WINS serversDeny unknown clients: if enabled, IP addresses are not automatically assigned to unknown hostsAll the IP addresses which DHCP server has assigned to devices, appear in the “Leases” table below.3.7. SMTP ClientGo to Settings > System > SMTP client.SMTP client enables the PBX to send notifications of the new voicemails, missed calls, chat requests, call recordings, faxes, etc.Add a new SMTP profile: Select “Default” and click “Edit”Fill out the fields:Email from: address to be used by PBX to send emailsSMTP mail server: server’s postal address used by the companyPort: listening port of the SMTP serverUser: user name to access the serverPassword: password to access the serverHELO domain: domain defined for sending emails. Default value is “localhost”, change it in case anti-spam filters of the SMTP server block sending the messageEnable TLS: TLS protocol enabled for the security of the connection to the serverEnable STARTTLS: STARTTLS option enabled if provided by SMTPClick “Save”To make sure that the entered parameters are correct, select the SMTP profile that you have just created and click “Test”.You receive the following email:3.8. CDR Go to Settings > PBX > CDRWildix PBX supports three CDR storage modes:External server Microsoft SQL: MySQL or MSSQL. The server must be previously installed and must be reachable by the PBX.Internal database: CDR Sqlite. CDR is saved on the PBX (on the backend specified for CDR storage, in our case, the USB key). This backend is available only for PBXs WGW40 and lessCSV file Important: For the PBX models WGW90 and bigger under high load, MySQL or MSSQL are recommended.Step 1. Enable connection to the databaseThe tabs “CDR MSSQL”, “CDR MySQL”, “CDR Sqlite” and “CDR CSV” allow you to enable connection to an internal or external database for saving CDR. All the four storage modes can be enabled at the same time.Configure at least one backend (MSSQL / MySQL /MySQL).Example of MSSQL/MySQL configuration:Enabled: Check the box to enable the backendHostname: The name or the IP address of the remote serverDatabase name: The existing database where the CDR must be savedCDR Table name: The name of the table that the PBX creates on the remote databaseUser: The user to access to the serverPassword: The password to access to the serverPort: specify the port usedStep 2. Select the backend for CDR storage.The first tab “CDR Settings” allows you to select the backend used for displaying CDR statistics. You can choose just one backend.For each backend there is a log shown in the right part of the screen, with the actual status and eventual problems and errors.After you have enabled the backend for saving CDR, the PBX can save the calls history.Calls history can be accessed from Collaboration, Wildix Phones (WP with a display, W-AIR), iOS and Android applications.3.9. SIP-RTP Go to Settings > PBX > SIP-RTPThe default parameters present on this page are set up in accordance with VoIP protocol. Check the following parameters:Auto discover external IP address: enable to automatically discover the public IP address using DynDNS website url entered into the field belowDynDNS website url: here you can indicate the URL of the service used to discover the IP address ( by default)Note that you can reach your PBX with the Public IP by its domain name (Settings > System > Networks, “Hosts” section, enter the PBX name into the field “System name”)External secure port (Default 443): this option allows you to enter a different port used for TLS connectionsLanguage: PBX language settings (note that language of the WMS interface is selected in Users: double click on the “admin” user and change the language) . Enable wideband codec usage in LAN: codecs are chosen automatically by the system, normally the priority is given to non-compressed codecs (G.711 aLaw) for fast connections (LAN) and compressed codecs (G.729) for remote connections. You can disable this option and successively enable it for single networks in “Networks where force usage of wideband codecs”, to optimize the bandwidth usage in VPN network, which is considered by the PBX as LAN.Auto add new devices in local networks: must be enabled to allow auto-configuration of Wildix devices via auto.DOCUMENTATIONWMS settings guide: . General Dialplan Settings Go to Dialplan > General Settings.This menu allows you to set up the default parameters for calls management.The default parameters present on this page should be changed in case the operator requires it.Parameters:Park call timeout: timeout in secondsPrefix for external line: prefix to get the outside line (0 by default)International Prefix: prefix to call abroad (00 by default)National Prefix: prefix to call within your country (0 by default)Note: The prefixes selected on this page are used for correct call class detection (see Documentation section for more information on call class detection). Country Code: IMPORTANT! select your country for the correct routing of incoming and outgoing callsInternal call default timeout: default timeout after which the call to another user is forwarded (if forwarding is enabled in user preferences) or is terminatedFirst digit timeout (secs): timeout after which the call is terminated in case there is no input, time countdown starts when the headset is raisedInterdigit timeout (secs): timeout in seconds after which the number is dialed automatically unless the user presses the Send call key on the phoneSend call key: it’s possible to select #, *, or None as a send keyPlayback tones while entering number: enable the option to hear DTMF tonesQuality of recorded voicemails / recordings: choose the optimal quality and sizeSet dialplan variables: this field allows you to set Custom Dialplan variables. E.g.: GDIAL_TIMEOUT=600 (global Dialplan timeout = 600 seconds)Set quick dial patterns: set custom dial patterns. This field should be modified if the internal numeration of users is different from the pattern 1XX / 2XXIMPORTANT: Change “Country Code” to your country’s code. Click “Save” to apply.DOCUMENTATIONCall class detection for processing external calls: 4. WMS Network configuration4.1. Basic features of WMS Network4.2. Master and Slave configuration4.1. Basic features of WMS NetworkWMS Network is a secure intra network, which enables the colleagues located in offices to collaborate in one transparent and automatic system. Basic featuresUsers:Presence status of colleagues and internal communication free of charge (pay only for Internet connection)No limit on the number of users in WMS NetworkUsers database resides on a distributed LDAP server; each user added to the system is immediately visible and can be contacted by other users of the systemRoaming profile: users can move between the sites while keeping the same number and user preferences; employees can be always reached at the same phone numberMaster vs SlavesAny PBX in the network can become a MasterAll the updates on some Slave PBX, become first known to the Master PBX and then, in real-time this information is passed to all the SlavesDirect peer-to-peer communication between the PBXsAuto-recovery and survivabilityWMS Survivability: continuity of internal and external calls in case one PBX in the network (including the Master) becomes unavailable WMS Auto-recovery: in case of Master failure, another PBX in the WMS Network dynamically takes up all the functions of the Master Local survivability: a Slave PBX disconnected from the network can continue to operate, but without the possibility to receive the users database updates In case an attempt to initiate the direct connection between two Slaves is failed, the PBXs can anyway communicate, using the Master PBX as proxyAll the services are available at each siteAuto sync of users, call groups and ACL configuration between the PBXs, allowing significant time savings on configuration and maintenanceEach PBX has its own local lines, own users, IVRs and Dialplan procedures, however you can set up the Dialplan to route calls via any PBX in the Network, which allows you to use local lines to call from another country 4.2. Master and Slave configurationImportant: If PBXs are remote and communicate via Internet, forward the ports 443 TCP and 1194 UDP on the router of the Master PBX to the IP address of the Master.Go to Settings > PBX > WMS Network.Master configurationPBX mode: MasterMTU: the size of the largest protocol data unit that the can be passed on VPN (MTU = maximum transmission unit)Login: set up the Login (must be the same on Master and Slaves)Password: set up the Password (must be the same on Master and Slaves)Slave configurationPBX mode: SlaveMaster PBX IP: specify the WAN IP of the Master PBX (or the *. domain name)MTU: same as on Master PBXLogin: same as on Master PBXPassword: same as on Master PBXNOTE: Go to Users > PBXs to view the PBXs in your WMS network; on this page you can find the URL addresses by which you can reach each PBX in your WMS Network. NOTE: Enabling WMS Network will delete users and groups from the Slave. In case you enable WMS Network on a Slave PBX that had been previously in use, users and groups will be deleted from the Slave. To restore the existing users, follow these steps:Export the CSV file of users of the Slave Enable WMS NetworkImport CSV file of Slave users to the MasterAccess the Slave and move the newly exported users from the Master to the SlavePART 5. Users5.1. Add / Import usersAppendix 2: User preferencesIt is possible to add users manually or import them from MySQL / MSSQL, LDAP / AD, Google, Office 365, Exchange Server, CSV file.5.1. Add / Import usersGo to Users > UsersClick “+” to add a new user and enter the parameters into the table:User: select the user type:Admin – system administrator with WMS accessUser – a normal user of the systemFax – T.38 support for FXS (analog phones, faxes)User Name: name and surnameLogin: used for AD integration (see Documentation on Import of users)DOCUMENTATION: Import of users and phonebooks from MySQL / MSSQL / LDAP / AD / Office 365 / Google / Exchange server: : the extension number (normally in format 1XX, 2XX)Fax and Office: DID number for faxes and callsNote: the number to call user directly from outside linesDOCUMENTATION:Fax server is by default enabled on all the Wildix PBXs and allows you to:Send faxes and SMS messages from Wildix CollaborationSend faxes from different Mac OS X and Windows applicationsSend messages via remote PBX in WMS Network Use Fax2Mail servicesUse Mail2Fax and Mail2SMS serviceFax Server Quick Guide: : personal email address for notifications (Voicemail, call recordings)Mobility: personal mobile number for mobility extension managementNote: Mobility feature allows users to receive calls to their mobile phone numbers, for more information see Appendix 7.Dialplan: dialplan procedure for outgoing calls (by default “users”)Note: in case outgoing calls should be processed in a different way for some users, create more procedures in Dialplan > Dialplan rules and assign them to usersFax dialplan: dialplan procedure for sending faxes from Wildix Collaboration (by default “users”)Language: the interface languageGroup: the ACL groupNote: by default newly created users belong to “default” group; go to Users > Groups and select the “default” group to see and edit the permissions for this group of users. DOCUMENTATION: ACL and Call classes management GUIDE this guide you can find the information on:managing permissions of users to call certain destinations and use certain Unified Communications servicesmanaging permissions of PBX administrators (PBX users with type “admin”) to manage PBXs and to access certain menus of WMSsupported Countries and call class management Department: this line is used for notes **IMPORTANT: In Wildix Collaboration interface, users are grouped either by parameter “Group” or by “Department” (if the last one is filled out)Once created, users appear in the table:NOTE:The first column displays the user type (admin / user / fax). The second column displays the user status. At the moment status is grey, because users have no devices registered to their accounts and they are not connected to Wildix Collaboration.1 - “+”: add user2 - “Edit”: edit the basic information that appears in the table (User Name, Phone, Fax, etc)3 - “-”: delete one or multiple users4 - Set passwords: change user passwordsNote: you can only set passwords, you can not view existing passwords for security reasons. To know the users passwords, use “Export CSV” option (available only for the admin user)WEB - password to access to WMS / CollaborationSIP/VoIP - password to assign remote phonesClick “Generate” to automatically generate a strong password (click “Show” to see the password generated by the system)You can compose your own password, consisting of at least 8 symbols, at least 1 uppercase, 1 lowercase, 1 digit.5 - Edit preferences: here you can manage all the user settings and phone features, see Appendix 2 for details6 - Send Welcome Message: send a message to newly created users with details of access to Wildix Collaboration (URL, login, password); the email template is customizable7 - Move users to another PBX: in case of WMS Network, you can select one or more users and move them to another PBX in the network. IMPORTANT: you must do it from the destination PBX, otherwise user image and settings will not be moved.Example: User 100 belongs to PBX A and must be moved to PBX B; access the PBX B, select user 100 and click “Move users to another PBX”8 - Export CSV (available only for the admin user): save a CSV file containing users information to your PCNote: In this way the admin user can know the passwords of users.9 - Import: import users from MySQL / MSSQL, LDAP / AD, Google, Office 365, Exchange Server, CSV file. DOCUMENTATION: Import of users and phonebooks from MySQL / MSSQL / LDAP / AD / Office 365 / Google / Exchange server: - Search field11 - Select PBX: in case of WMS Network, you can select to view users of a different PBX in the Network or to view all the users registered to all the PBXs in the WMS Network.NOTE: admin users cannot edit other admins and set their passwords (this option is available only for the super admin for security reasons) Appendix 2: User preferences Note: all the features except for “Shared voicemail” and “Hotline” can be modified directly by user via Collaboration interface (Settings); “Features” section can be also modified from Wildix phones (WP).Features: phone features for different call classesClasses: select the call class (internal / external / whitelist / blacklist) before modifying the phone features below; the phone features will be applied only to the selected call classDo not disturb: enable DND phone featureBusy call forward / Unavailable call forward / Force call forward: enable call forwarding in case user is busy / unavailable / unconditional call forwarding; enter the destination number or VOICEMAIL into the field Call waiting: enable the option to receive more than one call at a timeCall timeout: if enabled, the call is terminated in case there is no answer within the specified timeout (enter timeout in seconds into the field)Mobility extension management: if enabled, the call is routed also to the user mobile phone number (mobile phone number must be present for this user) after the specified timeout (enter timeout in seconds into the field)Read the Mobility Guide (“Mobility Enterprise” section): confirmation: if enabled, the user is notified on who the caller is once he receives the call to mobility extension numberNotify missed calls via email / via sms: enable missed calls notification to email / via SMSCustom Ring: enable the option and select the ringtone for this call classNote: ringtones can be uploaded via Sounds menu (more information in Dialplan management chapter)Settings: Shared voicemail: enable this option to subscribe this user to the Voicemail of another user; enter the extension number to subscribe toHotline: if enabled, the number you enter into the field is automatically dialled once the user lifts the handset (indicate the timeout in seconds in the corresponding field)NOTE: “Shared voicemail” and “Hotline” are especially useful for Directory / Secretary settings, allowing secretaries to check the Voicemail of Director and enabling Director to dial the Secretary by lifting the handset Phonebooks: select the Phonebooks which can be accessed by user from Collaboration and Wildix phones (move the phonebooks from “Available” to “Selected” section)Popup URL: allows you to specify the URL to open upon receiving / placing a call Format: {param}Where {param} can be: {CALLERNUM} - Caller number; {CALLERNAME} - Caller name; {USERNUM} - User number; {USERNAME} - User name; {CALLTYPE} - Call Type (incoming / outgoing); {TAGS} - Call tagsFunction keys: set up the behavior of Wildix phone (WP) BLF keysMore information in Wildix Collaboration Guide (Settings > Function keys) classes by phone: if disabled, Phone features (“Features” section) can be modified from Wildix phone (WP) only for internal call class; if enabled, it’s possible to modify phone features for other call classesCompany / Fax machine id / Fax header / Company logo: Fax cover settingsNote: Fax Server is by default enabled on your Wildix PBX Roster: select the users which appear in Wildix Collaboration > Colleagues menu (move users from “Available” to “Selected” section)PART 6. Provisioning of devices6.1. Provisioning modes supported by Wildix PBX6.1.1 Auto-configuration via auto.Appendix 3: Network configuration for auto. provisioningAppendix 4: Auto-configuration of W01GSM with auto.6.1.2 Auto-provisioning (Automatic mode)6.1.2 Remote provisioning (Semi-Automatic mode)6.1. Provisioning modes supported by Wildix PBXWildix PBX supports three provisioning modes:Auto-configuration via auto. of Wildix devices connected to the same network as the PBX (supported by Wildix devices starting from a certain FW version)Auto-provisioning of Wildix devices connected to the local LAN or remote network via VPNRemote provisioning of remote/unreachable devices behind NAT/firewallIn this chapter we will learn how to provision:Wildix gateways (PRI, BRI, W01GSM, FXO, FXS)WP4X0 Wildix phonesW-AIR base stationsAfter the devices have been provisioned, follow the procedure to assign WP4X0 and Analog ports to users - chapter 7.For provisioning of WP600A/WP600ACG - see the chapter 7 right away.After you have provisioned W-AIR base stations, follow the procedure to log in W-AIR handsets described in chapter 8.6.1.1 Auto-configuration via auto.Auto-configuration of Wildix devices in the same network as the PBXFor more information about network and WMS configuration, see Appendix 3. For auto-configuration of W01GSM, see Appendix 4.Go to Devices > DevicesConnect WP4X0 Wildix phones and media gateways to the Switch. Provisioned devices appear in the table:How to understand that devices have been provisioned:They have received the IP address (column “IP Address”)Device’s model is correctly indicated (column “Model”)Wildix phones (WP) display “loginX” on the screen, which means they are ready to be assigned to users (column “Phone”)1 - “+Add”: Add a new device via Auto-provisioning or Semi-provisioning mode 2 - “Edit”: Edit one or multiple devices (set up Default Tone for FXS media gateways, DNS server, NTP Server and Zone, set up Voice VLAN, CoS voice priority, Data VLAN, CoS data priority and other parameters)3 - “-”: Delete one or multiple devices4 - “Configure / Sync device”: send configuration to one or multiple devices 5 - “Assign to user”: assign WP4X0 and W01FXS to users6 - “i”: The icon “i” and the blue color indicates that there is a new firmware version available To update the firmware: select one or more devices and click “Configure/Sync device” button (during the FW upgrade procedure devices are rebooted).7 - “Connect”: Enable / disable access to deviceTo enable/disable connection to device:Click on the green triangle icon “Connect” to allow the connection to this deviceClick on the link “Open” to connect to the device’s web interfaceClick on the red square icon “Disconnect” to close the access to the device8 - “Phone”: “loginX” available for WP4X0 phones and W01FXS gateways means that devices are not assigned to users; otherwise extension number of user is displayed9 - “Firmware”: the current firmware version10 - “Password”: password to access device’s web interface after provisioningAppendix 3: Network configuration for auto. provisioningFeatures:Automatically add and provision Wildix devices during new installationsAutomatically add and provision Wildix devices that had been resetNetwork configuration:If internal DHCP server is used, it must return PBX address as Primary DNS Server addressIf external DNS server is used, you must add the correct DNS record (auto. must be resolved to the PBX IP)If external DHCP server is used, you must use PBX address as Primary DNS serverFor auto-configuration of W-AIR base stations (not SB), you must first manually create a W-AIR network via WMS interfaceWMS configuration: Two parameters present on the SIP-RTP page in WMS Settings > PBX serve to enable and customize the auto-configuration feature.Require provisioning password in local networks (default on): when enabled, the system does not provision those devices whose passwords are different from the passwords present on Devices page (default passwords are given to devices during reset procedure)Auto add new devices in local networks (default on): when enabled, devices are added and provisioned automatically in local networksAppendix 4: Auto-configuration of W01GSM with auto. For auto-configuration of W01GSM follow this procedure:Connect W01GSM to Wildix SwitchGo to device’s web interfaceEnter credentials for the first time access: admin : adminGo to the menu System > System ConfigurationEnter the following string into the field “Primary Profile URL”: on “Save”Press “Back” on the prompt pageClick on “Provision”Go to WMS > Devices: device has been provisioned6.1.2 Auto-provisioning (Automatic mode)Auto-provisioning of Wildix devices connected to the local LAN or remote network (VPN)Go to Devices > DevicesConnect WP4X0 phones / media gateways / W-AIR base stations to the Switch. Note: make sure that all the devices have received the IP address from the DHCP server of the network (PBX or external DHCP). Click “+Add” to add a new deviceSelect “Automatic mode” and click “Next”Click “Scan” (you can specify the IP range for the search)Select your device(s) on the list and click “Next”Wait till device(s) “Status” changes from “Provisioning” to “Provisioned”6.1.2 Remote provisioning (Semi-Automatic mode)Provisioning of remote / unreachable devices behind NAT/FirewallGo to Devices > DevicesConnect WP4X0 Wildix phones media gateways to the Switch. Note: make sure that all the devices have received the IP address from the DHCP server of the network (PBX or external DHCP).Click “+Add” to add a new deviceSelect “Semi-Automatic mode” and click “Next”Enter the device’s Mac Address The provisioning link has been generated:Copy the link address of the Provisioning URL NOTE: Use the option “Copy Link Address” in order to copy the complete string of the provisioning URL.Examples of a Provisioning links:http://[PBX_IP]/?action=setaps&config=xml (W01GSM)http://[PBX_IP]/?action=setaps (other devices)Access the web interface of the device and insert the provisioning link EXAMPLE: WP4X0 2015Credentials for the first time access: admin : adminGo to the menu Upgrade > AdvancedClick “Autoprovision”Device is now rebooting (the phone screen indicates that the device is rebooting; after the reboot, you can see the date and time, soft keys and “login0X” on the screen)DOCUMENTATION: Remore provisioning procedure for each Wildix device: to WMS > Devices: device is now provisioned:Credentials to access the device’s web interface after it has been provisioned:login : adminpassword : use the value in the column “Password” in WMSPART 7: Assign phones and FXS ports to users7.1. Connection and login of WP600A / WP600ACG7.2. Assign Wildix phones (WP4X0)7.2.1 Assign WP4X0 to users via WMS7.2.2 Assign WP4X0 to users via Feature Code7.3 Assign analog ports of FXS to users7.3.1 Assign W01FXS7.3.2 Assign ports of W04/24FXSAfter you have provisioned WP4X0 phones and FXS gateways, proceed with assigning phones and analog ports of the gateways to users.For configuration of Android based phones WP600A/WP600ACG, follow the easy procedure described in the chapter 8.To assign W-AIR handsets to users, follow the procedure described in the chapter 9.7.1. Connection and login of WP600A / WP600ACGConnect the phone to the Wildix Switch using RJ45 network cableAfter the phone has booted, Phone app (Login page) opens automatically, enter your credentials:Domain: PBX IP address or domain nameUser name: extension number (user name or email address are also accepted)Password: user WEB passwordNOTE: password of “admin” user is also accepted!NOTE: to know the user’s password, go to Users and click “Export CSV” (only “admin” user)DOCUMENTATION: User guide: datasheet and flyer: . Assign Wildix phones (WP4X0) Before proceeding with assigning WP4X0 phones make sure to:Connect the phones to Wildix Switch Provision the phonesThere are several modes of assigning WP4X0 to users:Via WMS: for system administratorDirectly from the phone by dialing Feature Code “Login” (99 by default): for user or for system administrator7.2.1 Assign WP4X0 to users via WMSGo to WMS > DevicesSelect a provisioned WP4X0 Click “Assign to user”NOTE: the option “Unknown” allows you to log out the phone that had been previously assigned to a user.Select the user from the listAfter a few seconds, “loginX” changes to the extension number of user both on the phone screen and in WMS (“Phone” column):This means, the phone is assigned and user can make and receive calls.To make a test, call 76 (Feature code for the echo sound test).DOCUMENTATION: Feature codes: can consult and edit all the Feature codes used by the system in WMS Dialplan > Feature codes:Enable / disable / adjust phone features (such as DND, Call forwarding, Mobility etc) from analog phonesPerform Call transfer and Call recording from analog phonesUse CONTINUITY feature allowing you to pass an active call from one device to another one Manage Voicemail; Record an audio fileUse such services as: intrusion, intercom, call pickup, paging, speed dial (a phonebook contact)Change Switches and Timetable statuses from analog phone, call a call group or transfer a call to a call groupCall a conference; Make an echo testNOTE: To change the language of the phone from the WMS interfaceGo to Users and select the user of the phoneDouble-click on the userEdit the “Language” column and click “Save”After several seconds the phone receives a new configuration. Otherwise go to Devices, select the phone and click “Configure / Sync device” button.7.2.2 Assign WP4X0 to users via Feature CodeTake a provisioned WP4X0 phone, “loginX” is indicated on the display.Dial 99 from the phone (“Login” feature code) and follow the audio instructions:Enter the extension number of userEnter the password of userNOTE: password of “admin” user is also accepted!NOTE: to know the user’s password, go to Users and click “Export CSV” (only “admin” user)HOW DO I ENTER THE PASSWORD FROM THE PHONE?Enter digits instead of lower and upper case letters and “*” instead of all the special characters:Instead of letters, press corresponding digits on the phone’s keypad (e.g. if you need to enter A or B, press “2”)No difference between uppercase and lowercase letters (press “2” to enter A or a)Press * instead of all the special characters (to enter such symbols as $, %, &)Press the button just once to enter any option corresponding to this button (e.g. to enter 2, A, B or C, press the button “2” just once, not twice, not three times)EXAMPLE: Password: 4Ag7$Z1528763666754 - press “4”A - press “2”g - press “4”7 - press “7”$ - press “*”Z - press “9” NOTE:In Users menu the status of the user to whom the phone has been assigned, has changed to green, the newly assigned device is displayed next to the status:DOCUMENTATION: Blog article about 99 Login procedure: Wildix Phones WP datasheet and User Guide: Headsets: Assign analog ports of FXS to users Before proceeding with assigning analog ports of FXS gateways make sure to:Connect the gateways to power supply (for non-PoE models) Connect the gateways to Wildix SwitchConnect analog phones to the gatewaysProvision the gatewaysDOCUMENTATION: FXS quick installaton guides: addition to FXS media gateways which allow you to connect analog devices, Wildix offers an FXO gateway (W04FXO), allowing you to connect analog lines, or to integrate a Wildix VoIP PBX into an existing analog system infrastructure:FXO whitepaper: (available also in It / Fr at )Difference between FXS and FXO - Blog post: 7.3.1 Assign W01FXSW01FXS gateways are assigned via WMS, procedure is the same as for WP4X0:Go to WMS > DevicesSelect the provisioned gatewayNote: “loginX” is displayed in “Phone” columnClick “Assign to user”Select the user from the list and click “Save”NOTE: In Devices menu the value in the “Phone” column changes from “loginX” to user extension numberIn Users menu, by focusing the mouse on the corresponding user status, it is possible to see that there an FXS gateway registered to this account.7.3.2 Assign ports of W04/24FXSGo to WMS > Devices Note: after you have provisioned the gateway, it’s possible to select the Default Tone for your country:Select your device(s)Click “Edit Device”“Default Tone”: select your country and press “Save”Go to WMS > Devices > Analog portsThe provisioned FXS gateway is displayed in the table:Double-click on the gatewayAssign analog ports to the users and click “Save”Assigned ports are displayed in the table:PART 8: W-AIR DECT solution8.1 Introduction8.2. Create a W-AIR network8.3. Configuration and login of W-AIR handsets8.1 IntroductionW-AIR is the DECT system developed on the CAT-iq protocol, which allows data and voice transfer on the radio channel and, thanks to it, offers a number of features, such as:Presence status of colleagues Access to shared PBX phonebooksWildix offers two solutions: W-AIR base station (supports multi-cell installations) and W-AIR base station Small Business (single cell). W-AIR base station multicell solution4238625123825PoE poweredUp to 1000 users per system (coming soon)Up to 30 users per base Up to 250 bases per system Up to 8 concurrent calls per baseUp to 8 concurrent handovers per baseSupport of repeatersUp to 50 bases = 3 repeaters50-125 bases = 1 repeater125-1000 bases = no repeaterUp to 5 concurrent calls per repeaterUp to 100 repeaters per base345757538100W-AIR Small Business (SB) solution:Up to 8 users per systemUp to 4 concurrent callsUp to 3 repeaters per baseNo multicellW-AIR handsets Presence status of usersOnline access to PBX phonebooksHD wideband audioCAT-iq Loudspeaker3.5 mm handset jackVibration (W-AIR100 and W-AIR150)Bluetooth (W-AIR150)IP65 (W-AIR150)Lone worker alarms (W-AIR150)DOCUMENTATIONW-AIR documentation: datasheetW-AIR system Administrator Guide (includes information on the site survey for multicell installations)W-AIR70, W-AIR100, W-AIR150 User GuidesCompatible Headsets: PoE Extender allows extending the network over long distances: . Create a W-AIR networkBefore proceeding with creation of W-AIR network and assigning W-AIR handsets to users: Connect W-AIR base stations to Wildix Switch.Note: Base stations (multicell) support PoE, they must be only connected to Switch, while Small Business (SB) base stations must be also connected to power supply.Provision the base station following procedures described in Part 6.For W-AIR Small Business (SB) base station: proceed now with assigning W-AIR handsets to users (chapter 8.3). For W-AIR Base Stations (multicell), follow the procedure below.Go to WMS > Devices > W-AIR Networks Click “+Add” Enter the name of the networkSelect the MAC addresses of the base station(s) from the left section and move selected items to the right section Click “Save”W-AIR Network is now created:NOTE: follow this procedure in case you have one Base Station (multicell) and also in case you have several W-AIR Base Stations (multicell) that you would like to connect into one DECT network. In case of multicell installation, DECT tree is automatically created.8.3. Configuration and login of W-AIR handsetsTurn on the phoneGo to the Menu Connectivity > RegisterEnter the code “0000” and select “Ok”Please note that in case you have several W-AIR networks (for example, in test environment), handset might register to a base station belonging to another network. In such situation it’s recommended to hold the handset closer to the base station.Wait till the phone shows “unknownX” account on the screen.Registered handsets are displayed in WMS Devices > W-AIR Networks, column “GW Users”:Handset is now ready for login procedure.Follow the same procedure as for WP4X0 to assign the phone via 99 Login Feature Code.Note that it is possible to use the password of the “admin” user to assign the phone.PART 9. Introduction to Unified Communication9.1. Introduction to Wildix Collaboration9.2. App for Android / iOS9.3. Call activity analysis and reporting with CDR-View9.1. Introduction to Wildix CollaborationWildix Collaboration is the user interface of Wildix PBX that offers access to Unified Communications features on PC (Mac OS X, Windows, Linux) via the browser (any HTML5 standard browser, however Chrome is recommended, since it fully supports WebRTC). Basic features:Presence status of colleagues and geolocationPersonal presence status and geolocationAudio and video callChat and File transferSending of Faxes and SMS, memo messages and personal remindersScreen sharing and remote controlNo client to install, accessible via the browserAccess to PBX shared phonebooksEvents historyConferenceIntegrated Softphone (Web Phone)Attendant Console for call management in high load environmentFirst time access to Wildix Collaboration: Open your browser (Google Chrome is recommended) and enter the URL address or the domain name of your Wildix PBX: (HTTPS mode is recommended)Example: the login and WEB password of user and click login Note: user extension number, User Name and email address are supported as LoginOnce you access the Collaboration interface, follow the popup notifications inviting you to add colleagues to your roster, enable desktop notifications, geolocation, etc. DOCUMENTATIONWildix Collaboration information: videoUser Guide (includes Attendant Console, Screen sharing, Softphone)Attendant Console for Blind and Visually Impaired Users - White paperWildix Collaboration first time access video: . App for Android / iOSWildix offers free of charge mobile application for iOS / Android.Search “wildix” in Google play store or in Apple itunes to download and install the application on your device.Basic features: Calls via VoIP or GSM to call phonebook contactsVideo calls to usersMobility callback serviceChat with usersVirtual reminders to usersOnline access to call historyOnline access to PBX shared phonebooksEncrypted HTTPS connection to the PBXCheck the ports to open in Appendix 7.First time access to Wildix Collaboration Mobile application:Launch the applicationEnter your credentials: Domain: PBX IP or domain nameUser name: Extension or User name or Email addressPassword: WEB password of user DOCUMENTATIONCollaboration Mobile User Guide: CardDAV sync of contacts with your Wildix PBX: PBX is ready for implementation of BYOD concept (Bring Your Own Device), in addition to applications for smartphones, Wildix offers an Enterprise WiFi system with single sign-on:Wildix Overlay Wi-Fi solution . Call activity analysis and reporting with CDR-View CDR-View allows detailed analysis of call activity of users and groups, costs, usage of trunks, duration and type of all the calls made and received, missed calls.First time access to CDR-View:Open Wildix Collaboration Go to History tab and click “CDR-View”The first time you launch CDR-View, click to install the Integration ServiceOnce installed, you can access CDR-View DOCUMENTATIONDatasheet and promo video: Guide: 10. Trunk Configuration10.1. VoIP Trunk configuration10.1.1 Make a test of SIP trunking between 2 PBXs10.2. Connection of Wildix media gateways10.2.1 Configuration of BRI/PRI trunk10.2.3 Connection of a GSM gatewayAppendix 5: Trunk groupsAppendix 6: PricelistsWildix PBX supports:SIP trunks: possibility to use the services of VoIP providers (a VoIP trunk is needed)PRI/BRI trunks: connection to ISDN lines (PRI/BRI media gateway)FXO trunks: connection to analog lines and analog PBXs (FXO gateway)GSM trunks: call via GSM network, send SMS (GSM gateway and a SIM card)Each trunk is displayed in the corresponding section of the page:Country code is indicated for each trunkReal-time registration status is displayed (green indicates that all the parameters entered for trunk configuration are correct and trunk is active)Note that SIP trunks can be outgoing or incomingFor GSM trunk, also the signal power status is displayedFor BRI/BRI and GSM trunks, status for each port is displayed10.1. VoIP Trunk configurationGo to WMS > Trunks Click on “+” under the “SIP” sectionEnter parameters:Title: description of trunkTrunk name: trunk name (optional)Auth login: provided by the VoIP carrier for authentication (mandatory field)From user: forced from number header and used for invite messages and for registration (if “From domain” is not empty), usually the same as “Auth login” (optional)From domain: forced from domain header and used in register and invite SIP messages (optional)Address or host name: address or host name of sip proxy for outgoing registration; otherwise enter “dynamic” for incoming registration (incoming invites are allowed); you can specify the port in the field after the colon “:” symbol (5060 is used by default) Password: password for authentication, provided by the VoIP CarrierDialplan: Dialplan procedure used for calls on this trunk (“main” by default)Country Code: used for number normalization, specify the code of the country where the trunk is usedEnable registration: enables outgoing registration (enable it for outgoing trunk)Advanced and Registration Proxy: other advanced trunk settings, check documentation section for more informationDOCUMENTATIONSupported VoIP operators: SIP trunk settings guide: 10.1.1 Make a test of SIP trunking between 2 PBXs If you don’t have a real SIP trunk, you can make a establish SIP interconnection between two PBXs, to test calls between them. In this case one PBX is used for outgoing registration, another one - for incoming registration.Incoming trunk (Master PBX):Address or host name: dynamicOutgoing trunk (Slave PBX):Address or host name: IP or domain name of the first PBXEnable registration: yesMake sure password and selected codecs (Advanced settings) are the same on both PBXsThe status became green, it means that parameters entered for trunk configuration are correct and you can make calls between the two PBXs:10.2. Connection of Wildix media gateways10.2.1 Configuration of BRI/PRI trunk Before proceeding with configuration of ISDN trunk make sure to:Connect the gateways to power supply (for non-PoE models) Connect the gateways to Wildix SwitchConnect the phone lines to the gatewaysProvision the gatewaysOnce you have provisioned the gateway, a new trunk automatically appears in the corresponding section in WMS > Trunks (BRI/PRI section).Double click on the trunk to edit the trunk parameters.Check the following parameters:Default toneCountry codeDialplan (“main” by default - Dialplan procedure used for calls on this trunk)DOCUMENTATION: Quick installaton guides and media gateways datasheet: trunks settings guide: 10.2.3 Connection of a GSM gatewayBefore proceeding with configuration of ISDN trunk make sure to:Screw the antenna into the ANT jack plug of the gateway Insert the SIM card (press the yellow button to make the SIM tray pop out)Note: Make sure the PIN code of the SIM card is disabledConnect the WAN interface of the gateway to Wildix SwitchProvision the gatewayOnce you have provisioned the gateway, a new trunk automatically appears in the corresponding section in WMS > Trunks (GSM/UMTS).Double click on the trunk to edit the trunk parameters.Check the following parameters: Default ToneCountry CodeDialplan (“main” by default - Dialplan procedure used for calls on this trunk)Number of SIM: the number corresponding to the line which is present in the associated Dialplan procedureEnable SMS receiving: enable incoming SMS messages to the SIM card (it’s necessary to specify the e-mail address in the field below)SMS2EMAIL service e-mail: e-mail address used for new messages notificationsFor more information on SMS sending - consult the Fax server guide DOCUMENTATION: Fax Server Guide (SMS sending): Quick installaton guide and media gateways datasheet: trunk settings guide: Appendix 5: Trunk groupsGo to WMS > Trunks > Trunk groups Trunk groups allows implementation of an intelligent least call routing strategy. Trunk groups make sense when you have many trunks and you would like to set up a certain priority in which trunks must be tried one after another. Example: you would like to route the calls to mobile numbers via GSM trunk, however you would like to have the opportunity to place a call even in a situation when GSM trunk is occupied: In this case call is routed via GSM trunk, if it’s busy, call is routed via the ISDN trunk.It is possible to remove or prepend digits to called number, set up the maximum concurrent calls on each trunk and define the timeout after which the system tries to place a call via the next trunk in the trunk group. Appendix 6: PricelistsPricelists are the tables that you can import on the PBX in csv format to enable the system to calculate call costs. Call costs can be then verified using CDR-View application introduced in the Part 9. Each trunk can be associated to a pricelist (the first line in trunk configuration window):To add pricelists, go to WMS > Trunks > Pricelists Example of csv file:Wheredialprefix: verification prefix (the longest prefix matching criteria applies)destination: country of the call destinationrate: price per call unitmin_duration: minimum duration of the call without billing in seconds billing block: call unitconnect_change: connection feestart_day: start day of the week (1 = Monday, 7 = Sunday)stop_day: end day of the week start_time: start time in seconds from midnight (example: 25200 = 7am; from 0 to 86400)stop_time: end time in seconds from midnightPART 11. Dialplan: how it works11.1. Association to users and trunks11.2. Add and edit Dialplan procedures11.3. Matching called numbers11.4. Included procedures11.5. Dialplan applicationsDialplan is responsible for routing all the incoming and outgoing calls to the right destination. Wildix offers an advanced Dialplan that allows you to program the system to match your specific needs. Wildix Dialplan is very easy to set up and to modify, in this guide we will only see the most popular Dialplan scenarios which are easy to implement, however Wildix Dialplan offers countless opportunities and in order to learn more, you can study our documentation, participate in FE advanced trainings, discuss your ideas with other technicians on FB Tech Wizards group and of course, make tests. 11.1. Association to users and trunksWe have seen already that each entity: a user, a VoIP trunk, or a media gateway - requires association to a Dialplan procedure. As a rule, users follow “users” (Internal Dialplan) procedure for outgoing calls, VoIP trunks and media gateways are associated to “main” (External Dialplan) procedure to route the incoming calls. You can create more Dialplan procedures if needed and then associate them to trunks, to users or to other Dialplan procedures (depending on your needs).UsersEach time a user generates a call, the system verifies the Dialplan procedure that this user is associated to. In case the “called number” dialled by user is found inside the Dialplan procedure associated to this user (“users” by default) the system starts to execute Dialplan applications that you have set up for this called number, in the order defined by you. “Called number” can be an exact match or a pattern (a prefix, for example if you would to route calls to mobile numbers through a different trunk than landline calls).Media gateways and SIP trunksEach time there is an incoming call on a SIP trunk or a media gateway, the Dialplan procedure associated to this trunk is verified (“main” by default). The system searches the called number (exact match or a pattern) inside the Dialplan procedure this trunk is associated to.If a match is found, the system starts to execute Dialplan applications that you have set up for this called number, in the order defined by you.In this way you can decide, for example, to route the incoming calls to your Tech Support number to the response group consisting of technicians; in case you are using the same phone number for faxes and calls, you can enable the system to detect a fax and if not detected, route the call to the secretary or a receptionist, or to IVR. This is just an example, the number of scenarios is unlimited.11.2. Add and edit Dialplan proceduresGo to Dialplan menu > Dialplan rules.By default you can find two procedures in this menu:main (associated to media gateways and VoIP trunks)users (associated to users)You can edit these procedures or add new ones and later on associate them to users (in WMS > Users, double click on user) or to trunks (in WMS > Trunks, double click on a trunk).To modify an existing procedure: double-click on a procedure.To add a new procedure: click “+”. You can add multiple called numbers to be verified within the same Dialplan procedure.To add a new called number, click “Add number”: To add a Dialplan application (an operation to be executed for this called number), click “Add application”: In this way you can add multiple called numbers within the same Dialplan procedure and multiple operations to be executed (Dialplan applications) for the same called number. Dialplan applications are executed in the priority defined by you, however you can change their order any time: use drag&drop.To display the dropout list of Dialplan applications relative to a called number, click “+” situated to the left from the called number. To delete a called number, click “-” situated to the right from the called number.To remove a Dialplan application, click “-” situated to the right from the Application.11.3. Matching called numbersEach Dialplan procedure can contain multiple called numbers. Trunks example:Your company uses 3 numbers, one for technical assistance, one for sales and one for faxes - you can add all of them inside the “main” Dialplan procedure and depending on the called number, the system will route the call to the destination you indicated.Users example:The calls placed by users can be routed via different trunks or trunk groups depending whether it is a local call, an international call, a call to another country where you have a branch office and a PBX installed, a call to a mobile number, etc. For instance, in Germany mobile numbers begin with 15, 16, 17 or 18. We can add “1[5-8].” as a called number inside “users” procedure and in case a user calls a number starting with 15 or 16, the system routes this call through a different trunk than a international call or a landline call. Another example: your company has a branch office, for instance, in France, you can route all outgoing calls to France (calls with French prefix) via your remote PBX installed in France and save significantly on international calls, because they will be charged as local ones.Called number can be:An exact match: a simple phone number (an extension number or an external number), example: 1220.Pattern: a sequence of numbers and special characters allowing you to match all the numbers that correspond to the specified criteria, example: 12XX - any number containing four digits which start from “12” (1200, 1211, 1245 etc) Syntax to match a pattern:X (uppercase X): any digit from 0 to 9. (point): one or more characters from 0 to 9 of any length[ ] (square brackets): any digit from those specified inside the bracketsZ (uppercase Z): any digit from 1 to 9N (uppercase N): any digit from 2 to 9! (exclamation point): zero or more charactersExamples:0. – the numbers starting with 0 followed by a one digit or a sequence of digits (typically used for direct calls to the public line)1XX – the numbers starting with 1 followed by two other digits, e.g. 125, 167[37]2X – the numbers starting with 3 or 7, followed by 2 and by any other digit, e.g. 326, 728X. – all the calls from any numbers[1237-9] – matches 1,2,3,7,8,9XXX! – all numbers containing three or more characters (while XXX. matches all numbers containing at least four characters) “default” destinationCalled number “default” is added when it’s necessary to include all the possible called numbers. Be careful using “default” destination! Normally “default” is added to give the notification to the caller that the number dialed is incorrect (no match to a called number was found inside the Dialplan procedure)11.4. Included proceduresThe section “Included procedures” allows you to add the called numbers that must be analysed after the content of the current procedure.In this way you can create the correct order of operations’ execution in case several patterns (called number prefixes, for instance) come into conflict within the same Dialplan procedure. Example of how to differentiate national and international calls where “0” is the prefix for external line engagement, “000” is the prefix for international calls: The called number “0.” for national calls and “000.” for international ones come into conflict, since “0.” is valid both for the numbers starting with 0 and for those starting with 000.To resolve this issue:Create a dialplan procedure “national” containing the called number “0.”Create a dialplan procedure “international” containing the called number “000.”Add “national” to “Included procedures” inside the “international” procedureAs a result, the system verifies if the called number matches the sequence “000.”, if not, it verifies if it matches the sequence “0.”NOTE: The procedure “pbxinternal (Users and call features/services dialplan)” is already present on the list of Included procedures for Internal Dialplan procedure (“users”), which by default enables the users to call each other and to use the Feature Codes of the system and which is analyzed only after the content of the Dialplan procedure:11.5. Dialplan applicationsDialplan applications are the operations (rules) executed one after another (in the priority defined by you) in case the match to the called number is found inside the Dialplan procedure.Many Dialplan applications allow the change of the called number on the go. Many Dialplan applications require association to another Dialplan procedure. Example: You have the headquarters in Germany and a branch office in France. You would like to route the calls to French phone numbers through your remote PBX installed in France.German PBX, “users” procedure:Add the French prefix as a called number and add the Dialplan Application “Call through remote PBX” (“slave” in our example is the name of the French PBX, “users” is the name of the procedure present on the French PBX): the call is routed through the French PBX, so inside the indicated “users” procedure on French PBX, the match for the indicated called number “00033.” must be present.French PBX, “users” procedure:Add the same called number “00033.” and click “set” to modify this called number:Here is the result that we get: the call is routed to the French PBX, before dialling the trunk “local - 22” the system removes the first 5 digits from the called number (the number is normalized), so the number dialled in the international format (for example, 000331234567890), becomes a local French number (1234567890)In the same way many other Dialplan applications allow modifying the called number or require association to another Dialplan procedure present on the same PBX (or on another PBX as in the previous example). Modify called number Example: the called number is 0323111 Select the Dialplan application that allows modifying the called number, for example “Dial the phone” → “Set”:“Remove” - “2”: two first digits are removed, the number is changed to 231111“prepend digits” - “00”: “00” is appended, the number is changed to 0023111“Custom”: you can completely change the called number, for example, enter 1234: the number is changed to 1234 Jump to another procedureIn the same way, many Dialplan applications allow under certain conditions jumping to a different Dialplan procedure.Example: you would like to treat incoming calls in a different way during the hours when your offices are closed. Create a timetable “Closed” in WMS > Dialplan > Timetables / Switches and set up the state “check time”. It means that each time this Timetable is verified by the Dialplan, the system checks if your offices are closed at the moment, according to this timetable. Edit the “main” procedure and add the application “Verify timetable” for your office phone number. In case your offices are closed, the Dialplan routes the call to another procedure called “Offices_closed”. You must separately create this Dialplan procedure in which, for example, you enable the system to play the audio message to the caller and send the call to Voicemail. DOCUMENTATION: Dialplan applications guide with practical examples: PART 12. Dialplan practical examples12.1. External Dialplan: “main”12.1.1 Route incoming calls to call agents (call groups)12.1.2 Record and playback audio messages12.1.3 Create a switch12.1.4 Create a timetable12.1.5 Create an IVR tree12.1.6 Incoming faxes management12.1.7 DID and DISA12.1.8 Mobility extension lookup12.1.9 Example of “main” procedure configuration12.2. Internal Dialplan: “users”12.2.1 Example of “users” procedure configurationIn this part we will learn how to use the most popular Dialplan applications for managing outgoing and incoming calls.12.1. External Dialplan: “main”12.1.1 Route incoming calls to call agents (call groups)To create call groups, go to WMS > Dialplan > Call groupsClick on “+” to add a new Call groupEnter the title of the call groupSelect the agents from the box on the left and move them to the box on the rightClick “Save”Note that you can add the same call agents to different groups. You can add users from all your PBXs in WMS Network to call groups.Select the group and click on “Edit strategy” to modify the strategy of call distribution. Now you can edit the “main” procedure to enable the Dialplan to route the incoming calls to your tech support phone number to the call group “Tech_support”:Example: You can: set the timeout, after which next Dialplan application is executedselect the message for the operator providing more information about the call (example of an audio message that the operator hears: “technical support call”)select the music on hold DOCUMENTATION: Call distribution in call groups: Automatic call distribution and call queues (ACD) - Blog article: 12.1.2 Record and playback audio messages You can record the message for the operator or an audio message to be played back to the caller directly from the Dialplan or from Sounds menu.Example: you have set up the Dialplan to check the timetable and to route the incoming calls to another Dialplan procedure in case the offices are closed. In this case you can enable the system to playback the audio file to the caller and then to route the calls to Voicemail:To record the sound to be played to the caller, click the “...” button or the Sounds menu:Enter the name for your message and your extension number into the field “Phone”Click the red “record” button: the call arrives to the device registered to your account (e.g. a Wildix phone)Answer the call and pronounce your message (e.g. “Our offices are closed. Your call will be forwarded to Voicemail”). Hang up to save your message:Via this menu it is possible to upload audio files: Click “Choose File” Select the file on your PC that you wish to uploadClick “Upload”WMS supports all the common audio formats: mp3, wav, alaw.DOCUMENTATION: Video tutorial: 12.1.3 Create a switch You can create switches to enable the system to change the strategy of incoming calls routing depending on the actual Switch status. Examples: Director / Secretary service - director can enable the switch in order not to be disturbed by calls. When the switch is enabled, all the calls are routed to the secretary; this configuration is normally applied to “users” procedure in order to forbid employees to call the director and to forward all the calls to the secretary or to the group of secretaries. Check the documentation section.Voicemail switch - enable the switch in case you would like to temporarily route all the incoming calls to Voicemail. Three state switch - this switch has three states (on / off / extra) and allows you to route the calls to different Dialplan procedures in each case.Go to WMS Dialplan > Timetables / SwitchesClick “+” under Switch table to add a new switch (click “+” under 3 states switch to add a new three states switch).Example: Step 1. Create a switch to forward calls to Voicemail:Click “+” in the “Switches” section:Enter the name for the switch and select the State “enabled” (you can change the state of the switch from the phone or by calling a feature code)Step 2. Create a Dialplan procedure to be executed if the switch is on:Step 3. Modify the “main” procedure to check the status of the switch before routing the call:Change the state of the switchVia a Feature code: Call the Feature code 93 from your WP phones and follow the audio instructions.From the phone: press the function key (BLF key) that you have previously configuredConfigure a function key from WMS > Users (the same operation can be done via Collaboration Settings > Function keys):Select the user and click “Edit preferences”Go to the section “Settings”, “Function keys” and click on “Switch” to add Switch to the list of function keysType the ID number of the Switch (Switch ID can be checked in WMS > Dialplan > Timetables / Switches)Click “Save”In the same way you can configure 3 state switch or Timetable function key.DOCUMENTATION: Director / Secretary service: Feature codes guide: 12.1.4 Create a timetable Create the working hours timetable for your office:Click “+” in the section “Timetable”Enter the “Timetable Name” and select State “check time”:Select the timetable and click “Edit” and specify the working hours:In the same way as we did for the Switch, you must create a separate procedure to be executed in case the office is closed according to this timetable. You can then enable the Dialplan to jump to another procedure in case the offices are closed: 12.1.5 Create an IVR treeIVR (Interactive Voice Responder) is a technology that allows humans interacts with telephone system by entering DTMF tones. An example of IVR is when a caller hears “Press 1 for English, press 2 for German” and call is routed to a different destination based on the choice made by the caller. Wildix graphical IVR tree can be multilevel and is easy to manage. You can define each node (each level) of an IVR tree as an action or as a submenu:Submenu is an intermediate node which brings the caller to the next level of IVR. You can set up the system to playback an audio file inviting the caller to make a new choice. Action ends the IVR execution and routes the call to the specified Dialplan procedure with the possibility to modify the caller number.Example: create an IVR of three levels.Level 1: Audio file inviting to press 1 for English, 2 for GermanLevel 2, caller pressed 1: audio file inviting to press 1 for tech support, 2 for salesLevel 3, caller pressed 1: call is routed to the English speaking operator of the tech supportLevel 3, caller pressed 2: call is routed to the English speaking sales assistant Level 2, caller pressed 2: audio file inviting to press 1 for tech support, 2 for sales, in GermanLevel 3, caller pressed 1: call is routed to German speaking Tech_support groupLevel 3, caller pressed 2: call is routed to German speaking Sales groupGo to WMS > Dialplan > IVR Click “+” to create a new IVR tree and give it a name. Click “Save”Double click the IVR to edit it:At this step we can create levels (nodes) of our IVR tree.Node of the first levelAudio file inviting to press 1 for English, 2 for GermanClick “Edit”:Item time: “Sub menu” (an intermediate node)Action:Sound file: select the audio file (or record it)Times: number of times the audio file is played back to the callerTimeout: after this timeout in seconds, the Timeout action is performedBackcode: code to come back to the previous menuTimeout action:Dialplan procedure: set up to route the call to a different Dialplan procedure in case caller pressed nothing within the specified timeoutCalled number: this option allows you to modify the caller number (match must be found in the specified Dialplan procedure)Nodes of the second levelAudio file inviting to press 1 for tech support, 2 for sales (in English in case caller entered 1, in German, in case caller entered 2)Press “+” in front of the first level node to add a new level.Number: the number that the caller must enter in order to arrive to this nodeNodes of the third levelRoutes the call to the final destination (user or group).Click “+” in front of the corresponding second level node, to add a new level, for example: All of these nodes terminate the execution of the IVR tree: Item type: Action Action:Called number: extension number Where 123 and 224 are English speaking operators (tech support and sales) Where 111 and 222 are the called numbers present in the procedure “IVR” that we must create separately. According to this procedure, incoming calls to 111 are routed to tech support call group, incoming calls to 222 are routed to sales call group: Called number 111: call is routed to Tech_Support call group (in case of no response within 20 seconds, call is routed to Voicemail)Called number 222: call is routed to Sales call groupHere is the ready IVR tree: Now we can use it inside our “main” procedure:DOCUMENTATION: IVR blog article: 12.1.6 Incoming faxes managementWildix systems integrate Fax server by default. All the services for managing incoming and outgoing faxes are enabled on all Wildix PBXs. Consult documentation section for more information about outgoing faxes management.Note: Make sure SMTP client is defined in WMS Settings > System > SMTP clientFax to e-mailAnswers an incoming call using FAX Server and forwards fax to one or multiple fax numbers / users:If you indicate an extension number (e.g. 101), a copy of fax is sent to the user email address, and a link to fax download appears in Wildix Collaboration > History menu and in CDR-View. You can enter several extension numbers / email addresses into the field, separated by spaces, in this case the copy of received faxes is sent to multiple destinations: All received and sent faxes are permanently saved on the storage device defined in Settings > System > Storages.Detect faxNote: especially helpful when the same number is used for incoming calls and faxesAnswers the call and within a timeout specified in “fax detect time” waits for the tones of a remote fax (in the meantime the system to continue the Dialplan execution).Fax detect time: enter the timeout for fax detection in seconds (usually 3 seconds are enough)Continue the execution: if enabled, the Dialplan execution continues without waiting for the number of seconds specified in “fax detect time” field before the fax is detected (to avoid silence while the fax is being detected)Procedure: select the procedure to route the call in case the fax is detectedSet Number: modify called number (the match must be present in the specified Dialplan procedure)In our example in case within 4 seconds fax is detected, the system stops the execution of the application “Call group” and the call is forwarded to the called number “fax” (present inside the same Dialplan procedure “main”), in which the fax is being sent to email.Incoming fax from trunk to FXS user (fax machine)Add Dialplan application “Detect fax” in case phone number is used both for faxes and calls, otherwise you can use “Jump to”.Select the procedure “pbxfeatures” or “pbxservices” and edit the called number:“custom” - 90*[fxs_extension_number], example:Where “pbxfeatures” / “pbxservices” are procedures that are present by default on Wildix PBX for recognition of PBX services and features (including feature codes) “90” is the feature code “Fax relay”; “101” is the fxs user extension numberDOCUMENTATION: Fax server guide: 12.1.7 DID and DISADID and DISA services enable the caller to reach PBX users directly by dialing their extension numbers.Example of DID (Direct Inward Dial) configuration:First 8 digits are removed from the called number. Depending on the last two digits of the called number (1XX) incoming call is routed to the extension, examples:Incoming call to 04611715111 is routed to extension 111Incoming call to 04611715112 is routed to extension 112Incoming call to 04611715122 is routed to extension 122...Example of DISA configuration:Called number “default”:The message is played inviting the caller to enter the extension numberThe system waits for digits for 5 secondsIn case of no input within the specified timeout, call is routed to call group Called number “XXX”:In case caller entered extension number, call is routed to user12.1.8 Mobility extension lookupIt is possible to enable the system to recognize PBX users when they call the office phone number from their mobile phone numbers. Note that user mobile phone number must be present in WMS.Thanks to this feature PBX, mobile calls of employees become an extension of Wildix PBX and calls can be treated in the same way, as the ones done from the office phone. If the caller number corresponds to the mobile number of one of PBX users, Dialplan jumps to the procedure predefined for the outgoing calls of this user. “Set” - “caller number”: allows you to modify the caller number to match the one present in the procedure for the outgoing calls for this user, e.g. “users” “Set” - “Options” - “d”: hangs up a call and makes a call back to the user (in this way call is free of charge for the user)12.1.9 Example of “main” procedure configurationIn our example, the enterprise has three phone numbers:+49 0461 1715110 – general company phone number+49 0461 1715111 – technical support+49 0461 1715112 – sales assistance In case of incoming call to “+4904611715110”, the following operations are executed:Mobility extension lookup. In case the phone number from which the call arrives is present in the field “Mobility” of one of the users of the system, the call is hanged up and the system makes an automatic callback to the callerCheck the timetable “Working_hours”, in case the call has arrived at the time when the office is closed, another Dialplan procedure “Working_hours” is executedCheck the switch “Voicemail”, in case the switch status is “enabled”, another Dialplan procedure “Voicemail” is executedThe call is routed to IVRIn case of incoming call to “+4904611715111”, the following operations are executed:Check the timetable “Working_hours”, in case the call has arrived at the time when the office is closed, another Dialplan procedure “Working_hours” is executedCheck the switch “Voicemail”, in case the switch status is “enabled”, another Dialplan procedure “Voicemail” is executedThe call is routed to the call group “Tech_support”In case no one responds within 20 seconds, another Dialplan procedure, “Voicemail” is executed In case of incoming call to “+4904611715112”, the following operations are executed:Check the timetable “Working_hours”, in case the call has arrived at the time when the office is closed, another Dialplan procedure “Working_hours” is executedCheck the switch “Voicemail”, in case the switch status is “enabled”, anotherDialplan procedure “Voicemail” is executedThe call is routed to the call group “Sales”In case no one responds within 20 seconds, another Dialplan procedure, “Voicemail” is executed12.2. Internal Dialplan: “users”12.2.1 Example of “users” procedure configurationAn example of Dialplan configuration for outgoing calls:+XXXX. : Check if the called number is an international phone number (e.g. +39.). In this case the “0” is added as the default prefix for the outgoing line selection01[567]. : Check if the called number a mobile number (any number starting with 15, 16 or 17). In this case the call is routed via the trunk group “gsm_calls”. The first digit (0 for the external line selection) is removed from the called number0X. : Check if the called number is the landline number (any number starting with any digit). In this case the call is routed via the trunk group “isdn”. The first digit (0 for the external line selection) is removed from the called number00039. : Check if the called number is an Italian phone number. In our example, the enterprise has an office in Italy and one of the PBXs in the WMS Network is installed in Italy. In this case, it is possible to take advantage of the trunks present on the remote PBX: the call is routed via the remote PBX installed in Italy, following the “users” procedure present in the Dialplan on that PBXDOCUMENTATION: Dialplan applications guide: PART 13. Introduction to WebRTC Kite solution13.1. Personal Kite link for each PBX user13.2. WebRTC Video conferenceWildix Kite is a professional solution for business communication based on the WebRTC technology that brings Unified Communications to the corporate website.Features supported:Chat / file transferAudio callVideo streamingDesktop sharingVideo conference13.1. Personal Kite link for each PBX userWildix Kite service allows each PBX user to have a personal Kite link by which he or she can be contacted on the Internet via the browser. Examples of Kite implementation:Contact button on the website (simple HTML template) Widget (embedded into the website or into a separate web page)HTML email signature with contact button (simple HTML template)An example of Kite implementation can be found here: contacts One of the advantages of Kite is that it’s fully integrated into the Wildix telephony system:Chat requests are managed by PBX users via Wildix Collaboration interfaceAudio calls can be answered from any Wildix devices (WP, W-AIR, mobile apps, Collaboration)Wildix Kite uses a separate Dialplan which makes it easy to customize the serviceChat requests and calls from Kite service can be routed to separate call agents or to call groupsDOCUMENTATION: Kite guide: Kite website page: 13.2. WebRTC Video conferenceWildix Videoconference is based on WebRTC technology and Kite solution and allows access for PBX users and external users via a link or a phone call.Features supported:Access for internal and external users via invitation by email, via link, audio callMulti user chat, audio and video conferenceScreen sharing Document sharing / application sharing / link sharingRecordingConference schedulingMute/unmute participantsDynamic video allocationDOCUMENTATION: Videoconference guide: Videoconference website page: PART 14. Debugging and troubleshooting14.1. SSH connection14.2. Dialplan debug14.3. Trace generation14.4. Syslog, Reset and recovery of media gateways and phones14.5. OtherAppendix 7: Ports to open for Wildix servicesWildix systems offer logging, debugging and troubleshooting possibilities on different levels. In this chapter we will only see the basics. 14.1. SSH connectionConnect to PBX via SSH to view the logs of the callweaver and to analyse the basic problems with PBX activation, trunk registration, Dialplan operations, impossibility to place calls, ACL permissions etc. To connect via SSH you can connect to the PBX via console (on Windows you can use “putty” or other SSH clients) or click on “terminal” icon in WMS upper menu (“admin” user)To analyze call logs: select the entry 1 (Connect to PBX engine)To analyze the syslog: select the entry 5 (Open Syslog)For other advanced operations: select the entry 11 (Shell)Example:14.2. Dialplan debugClick “Debug” icon in the upper menu, tick off “Debug dialplan” and click “Save”.Now the logs of the calls are saved and you can see the log of each call:14.3. Trace generationWMS Settings > Tools and utilities > Generate traceThis tool allows generation of a *pcap trace that helps you to debug and analyze eventual problems with VoIP traffic on the PBX or on separate interfaces.DOCUMENTATION: Pcap trace generation guide: 14.4. Syslog, Reset and recovery of media gateways and phonesWP4X0 reset and recovery: Press the central button of the Navigation keys and hold it for several seconds.Enable remote syslog on Wildix devices: WMS > Devices, double click on a provisioned device to edit it and select “Syslog Server” (enter the address of the remote server).ISDN gateways: Access the media gateway web interface System menu > Syslog and activate “Diagnostic Traces”Connect to the media gateway via SSH (on Windows you can use “putty” or other SSH clients) using the same credentials you used for access to web interfaceType “logs on” (at the end of the session, type “logs off”)Make a test callThe logs help you to understand eventual issues, here is what happens when a user places an outgoing call to a trunk:PBX receives a request from the user and forwards it to the BRI/PRI gatewayThe gateway forwards the call to the operatorThe operator responds to the gateway with the status “Call Proceeding” to confirm the reception of the requestThe operator responds with the status “Call Progress” to indicate that the call has been routed to the destinationThe operator responds with the status “Alerting” to indicate that the destination is availableThe operator responds with the status “Setup Confirm” to indicate that the call has been responded In case the call could not be connected or the call was hang up by the operator, the media gateway receives the following message: “Unicast RECV Disconnect”Check the field indicating the reason of the call disconnection, for example: “Cause: Normal call clearing (16)”. Check the codes of disconnection reasons: 14.5. OtherUpper menu > “info”: Monit service allows you to check the performance of the system services, CPU, memory usage.Upper menu > “ports block”: check if any ports needed for remote trunks and calls are not openAppendix 7: Ports to open for Wildix servicesRemote support, upgrades, auto-configuration via auto.Make sure that Firewalls that limit the Internet access to the PBX, allow the traffic to wmp. and vpn2. on the 443 TCP and 1194 UDP portsWMS networkEnable the port 443 TCP (or another custom secure port) and 1194 UDP on the side of the Master PBXRemote provisioning of devices Incoming ports: 443 TCP (default) or another external secure port (SIP-RTP page); 5060 UDP - 5061 TCP for SIP registrationRTP ports: from 10000 to 15000 (SIP-RTP page)SIP Trunks registrationOutgoing ports:5060 UDP or another custom port specified in trunk settings Collaboration and Web Phone443 TCP (default) or another external secure port (SIP-RTP page); RTP ports: from 10000 to 15000 (SIP-RTP page)iOS/AndroidSIP: 5061/TLS, if blocked 443/TLSXMPP: 443 TCP for Android; 5223 TCP for iOS, if blocked 443 TCPConfiguration: 443 TCPCustom secure port (SIP-RTP page): add manually on the app login page: Account > Domain, example: pbx.:443 (for iOS works only with public IP)RTP ports: from 10000 to 15000 (SIP-RTP page)WebRTC Kite serviceOutgoing ports:5061 TCPIncoming ports:RTP ports: from 10000 to 15000 (SIP-RTP page)WebRTC Kite Video conference Open the port 443 TCP (default) on a firewall towards:conference.ws2sip.videobridge.turn. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download