Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

...

  • Hide in CDR-View: allows hiding last X digits in CDR-View from phone numbers consisting of more than 7 digits. Must be used together with ACL “Can/cannot see full number in CDR-View” (see ACL rules and Call classes management Guide)
  • Delete calls / chats / voicemail / recording after: these options allow auto-deleting old calls, chats, voicemails and recordings after a specified number of months 

    Note

    Notes:

    • Starting from WMS 6.07.20240906.1, the option Delete recording after is not displayed if Company Data Storage is activated.
    • By default, the system clears data older than 12 months, if other values are not specified. Clearing of old data is run at 4 am every day.
    • Deleting chat history in WMS Network.
      In case WMS Network is enabled, chat history from CDR-backend will be deleted using the minimum value. For example, "Delete chats after 2 month" is set on Server PBX and "Delete chats after 1 month" is specified on Client PBX -> chats will be deleted after 1 month (the value of Client PBX is applied).


...


Zoho Integration

Enable integration with Zoho CRM. Refer to Zoho CRM integration with Wildix PBX for detailed information.

...

  • Cloud Analytics (available from WMS 6.03.20230630.3): enables events sending/ data gathering for Cloud Analytics (CDR-View 2.0) in Collaboration and x-bees. Starting from WMS v. 6.06.20240530.1, it is activated by default on all types of PBXs. Also, enabled Cloud Analytics is required for Webhook integration (for more information, check the document How to set up Webhook integration).

    Note

    Note:

    • If sending of the events was enabled and then disabled, the old data is still stored in the data base. For the old data be removed, a ticket to customer care has to be opened.
    • On versions prior to WMS v. 6.06.20240530.1, Cloud Analytics is enabled by default if a PBX or whole WMS Network are running in the Cloud. In case of a standalone Virtual/ Hardware PBX, or if there is a mix of Cloud and Virtual/ Hardware PBXs in a WMS Network, Cloud Analytics should be enabled manually by admin. 


...

  • Collaboration call control (available from WMS 6.03.20230630.3): enables Call control mode for Collaboration. By default, only 1 active Collaboration session is permitted. However, there is an option to allow the second Collaboration tab – in Call Control mode. This can be used, for example, for media devices when connecting via remote desktop. The option is particularly practical for teams4Wildix integration. Once the feature is activated, an additional option appears on the Collaboration login window – Call Control only.

    Note

    Use case: User can set "Call control only" mode to be automatically enabled by adding a parameter in the URI (useful when it is needed to share the link among all employees or bookmark the page)

    How-to: add ?sip=no to PBX domain name ->  https://pbxname.wildixin.com/collaboration/?sip=no


  • (available from WMS 6.04.20231020.2): enables location-based MFA on the PBX, which uses users' location (determined by the IP address) to confirm their identity. If the IP address appears to be from an unfamiliar location, users need to confirm the IP address via email. Read more in the documentation: Security Policy at Wildix

...

Refer to Active Directory Single Sign-On for detailed description.


Active Directory Single SignOn via SAML 2.0

Note

Note: The support starts from WMS 6.07.20240906.1. 

It is possible to configure support of Active Directory Single Sign-On via SAML 2.0 protocol.

Check out the document How to configure support of Active Directory SSO via SAML 2.0 protocol for instructions.

System

Network (Hardware, Virtual PBX)

...

  • Click + to add a new Fax/ SMS server profile
  • Enter the following parameters:
    • Name: enter the name (identifier)
    • Protocol: select the protocol of communication with your email server (POP3 or IMAP)
    • Auth type: select the preferred authorization type, Basic or OAuth2 (the support of OAuth2 for Fax/SMS Server starts from WMS 6.01.20221019.4). Depending on the chosen type, fill out the following fields:

      a) In case of Basic Auth type:
      • Server: settings of your email server to access incoming messages
      • User: email address of user to access to the server

        Note

        Note: don't use here an email of a user who must send faxes via Fax2Mail service.


      • Password: password to access to email address of user specified in the field above
      • Use SSL: enables secure connection to the server (required by some email servers)
      • SSL Certificate check: allows to disable SSL certificate check, e.g. in cases when the mail server uses a self-signed certificate. The parameter is enabled by default.

        Note

        Note: The support starts from WMS 6.03.20230630.3. 


      b) In case of OAuth2 authorization type: 
      • Auth provider: choose auth provider (Google or Office 365) -> click Login and perform the login 
    • Dialplan procedure: select the Dialplan procedure to manage faxes sent by users
    • Protection password: security password for MAIL2FAX service
    • Default LOCALSTATION: sender’s fax machine ID, appears at the top of each page of outgoing fax, if not specified the default value “Fax Server” is used
    • Default LOCALHEADER: fax header to identify the sender, appears at the top of each page of outgoing fax, if not specified the default value “Wildix PBX” is used
    • Keep e-mails and faxes on server: enables storing of messages on the server

...

Note

Note: Alternatively, logo can be uploaded by a request to Customer Success Specialist. 


Click Download logo to make the logo appear in the upper right part of WMS / Collaboration interface / Remove logo to remove the logo from WMS / Collaboration interface. 

...