Attention! Telephony operates with active license only. Also, SIP connector licenses and telephony payment are associated with the license number. Upon license upgrading or downgrading, old connections will become unavailable.
Prior to changing your product's edition license, disable rented or associated numbers or PBXs.
Telephony in Bitrix24 is implemented via the WebRTC technology that allows make/receive calls directly from web browser. This technology is supported by the browsers in versions not lower than: Google Chrome v29, Mozilla Firefox v27, Opera v18. (Unfortunately, Internet Explorer doesn't support WebRTC.)
Due to various browsers that depend on developer updates, IP-telephony stable operation is guaranteed only in Google Chrome and Mozilla Firefox. Opera browser operation is unstable depending on browser versions.
Bitrix24 On-premise call restriction on websites without SSL certificate
Google Chrome from version 47 disables WebRTC on all sites that do not use HTTPS protocol. It means that all Bitrix24 On-premise versions without installed HTTPS certificate, telephony will stop to operate as well as internal calls. For users it will look like "Cannot access web camera or microphone" error.
To solve this issue, you will need to purchase and configure HTTPS certificate for a site. Or use other browsers.
This warning is does not apply to Bitrix24 Cloud.
Local network setup
Telephony use requires a correct local network setup from which calls originate. Each type of calls has custom settings requirements, indicated on pages with description of a specific method. However, some general requirements exist as well. For correct operation, specific ports and addresses must be opened both-ways in your network.
Attention! Portion of addresses required to be opened are assigned Voximplant operator. These addresses are subject to change. When experiencing connection issues, It's recommended for account administrators to check status of your opened ports in your network.
URL: http://< your_domain >/bitrix/tools/voximplant/receiver.php (prior to version 17.0.7 the file was called - http://< your_domain >/services/telephony/info_receiver.php). Because telephony provider IP addresses are subject to change, this page should not have
any access limitations
However, when security policy require limits, minimal access to this page must be granted from the following IP:
126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168
For correct telephony operation, agents must be configured for cron, and not for hits.
Specific issue with launching agents at cron for telephony is the following: launch frequency is not less than 1 (once) per 2 (two) minutes; it's recommended to launch each minute.
Telephony is associated with a key. That's why if an operational instance works jointly with Development only instance with installed Telephony module, it can lead to errors during
- License check error on incoming call,
- Call can be forwarded to the Development only instance,
- During a call made to operational instance it may be refused with error in the log "Config isn't found for number: reg12345",
. It's recommended to delete Telephony module on the Development only instances.
Telephony operation (mobile, browser, and desktop client telephony) requires up-to-date time set at the operation system. Administrator checks if time sync is enabled in OS user settings or synchronizes local time server.
When administrator encounters cases when an account doesn't maintains call history, he/she must check NGINX server settings at the site or balancer. Usually, these are cases when connection proxy_ignore_client_abort on; is missing. This setting must be enabled for specific location.