3CX Phone System v12.5 Beta Leverages WebRTC

3CX takes a huge leap forward with the release of 3CX Phone System v12.5 Beta, bringing with it the 3CX WebRTC Gateway. The WebRTC Gateway revolutionizes the way you collaborate & communicate with customers and colleagues, as WebRTC phone calls can take place from any open standard browser and no longer need to go via the telecoms network. This provides great cost savings, but also adds video and screen sharing ability to each call.

3CX WebRTC Boosts your Customer Service with Click-to-Call Capability!

With WebRTC, you can now allow your customers to call you from their browser – saving them from having to dial a number, and you from having to pay for the 800 number costs. Calls go directly to your 3CX Phone System and based on where your customer is on your website, you can route the call to enable them to speak to the right person straight away. The call can be easily elevated to a video call, allowing you to communicate face-to-face or to share your screen with your customers, thereby providing a personalised customer service experience.

In addition to the click-to-call functionality, you can share a WebRTC call link via chat or email and allow anyone to place a call from any open standards browser (Chrome, Firefox) directly to your extension within seconds.

Attended Transfer from your Desk Phone via CTI

Now you can make attended transfers from your Desk Phone via CTI Mode using 3CXPhone for Windows. Save valuable time as this new feature eliminates the need to learn archaic procedures for your desk phone.

New Callback Features: Unsuccessful Blind Transfer and Busy Callee

Following an idea submitted to 3cx.com/ideas, we have now implemented an automatic callback feature in Blind Transfer. If you perform a blind transfer and the recipient of the call is busy, then the call will automatically return back to you. This way you can inform the caller that the person they are trying to contact is busy and proceed to transfer to another destination.

Deployment Improvements & New VoIP Providers

We’ve made 3CX even easier to deploy by simplifying and reducing the number of ports required. For a detailed explanation of the changes read this doc. In addition, we have added numerous new VoIP providers with more being added soon.

Other Features in v12.5 Beta

  • Dropped support for 3CX Phone System on x86 systems.
  • Video calls from 3CXPhone for Windows.
  • Significant chat improvements on 3CXPhone for Windows.
  • Elevate a chat in 3CXPhone for Windows to a WebRTC call or WebMeeting.
  • Schedule 3CX WebMeetings from 3CXPhone for Mac.
  • New echo cancellation module for 3CXPhone Windows and Mac for clearer calls.
  • For the complete list of changes view the complete change logs for 3CX Phone System, 3CXPhone for Windows, 3CXPhone for Mac.

Download v12.5 & Documentation

  • Download 3CX Phone System Version v12.5.
  • Read our detailed step-by-step instructions on how to install or upgrade to the 3CX Phone System v12.5.
  • The 3CXPhone for Windows client is included in the 3CX Phone System v12.5 installation package and will be updated automatically, or download the client here.
  • 3CXPhone for Mac OS is also included in the 3CX Phone System 12 installation package and will be updated automatically, or download the client from here.
  • Download 3CXPhone for Android from Google Play.
  • Download 3CXPhone for iPhone from the Apple App Store
  • Demo Key: SAOY-3LMW-U3OT-GLJV

Liked this article?

Get notified of new articles
or share
You might also be interested in:
  1. Craig

    excited to see a “new” release… It is still v12.

    October 21, 2014 at 5:45 pm
  2. matteo

    Any news about Patton Snbx that support only 32bit OS. Ia there a possibility for 64 OS on this platform ?

    October 21, 2014 at 9:45 pm
    • @Matteo – You need to contact the manufacturer for information like this.

      October 22, 2014 at 10:09 am
    • No, we really dont recommend use of such appliances. Why when you can get competitive modern server hardware or even virtualize.

      October 22, 2014 at 4:43 pm
    • Renato P

      Hi Nick,

      as 3CX Partner I´m so excited with that news but I would like to tell you that the LEADS for Brazil are coming too late since too many calls to users reveals that they are already using another solutions.

      Can you check that in a way to decrease this time to contact the user and present your solutions?

      October 29, 2014 at 5:47 pm
  3. Good job guys ,

    There are a manual how to configure webrtc click to call is very interesting

    October 21, 2014 at 11:53 pm
    • @Bruno – information is coming on the way. But in a nutshell, make sure you configure public ip and external FQDN correctly in the wizard and then after log in to the management console, click on WebRTC Gateway on the left tree of the management console, click on WebRTC Links and enable the links you want for the extension. Play around in that page with the DID string and generate buttons – it is very easy…

      October 22, 2014 at 10:14 am
    • Great Great Great , Nick i have found my error and it work very fine .
      Also i have connect another pbx via trunk to 3cx and call route to this pbx and voice quality is good
      Thanx for this improvement

      October 22, 2014 at 5:24 pm
  4. Hi 3CX, and THANKS:-)
    Once Again, great job…

    Update went like a charme.
    I like the Hotkeys, they just seems to Work.
    One little isue, you dont seem to use the local domainname in the provisioning, it seems that this is still the local IP.
    We will keep testing
    Thanks again, looking forward to the real V12.5


    October 22, 2014 at 3:56 am
    • @Jesper – yes this is by design. We think that local communication can use IP Addresses because this catches all those clients that do not have an internal DNS… So local use IP, External use FQDN by default..

      October 22, 2014 at 10:16 am
    • bruno

      Hi nick , i have try and call setup work perfectly !!
      But i have issue with audio Always no rtp packet

      22-ott-2014 15:07:19.912 [MS105000] C:6.1: No RTP packets were received:remoteAddr=,extAddr=,localAddr=
      22-ott-2014 15:07:18.322 Leg L:6.1[Line:90000<<WebRTC] is terminated: Cause: BYE from PBX
      22-ott-2014 15:07:18.322 [CM503008]: Call(C:6): Call is terminated
      22-ott-2014 15:07:18.320 Leg L:6.2[Extn:14001] is terminated: Cause: BYE from
      22-ott-2014 15:07:16.279 [CM503007]: Call(C:6): Extn:14001 has joined, contact
      22-ott-2014 15:07:16.278 [CM503007]: Call(C:6): Line:90000<<WebRTC has joined, contact
      22-ott-2014 15:07:16.276 L:6.2[Extn:14001] has joined to L:6.1[Line:90000<<WebRTC]
      22-ott-2014 15:07:13.585 [CM503025]: Call(C:6): Calling T:Extn:14001@[Dev:sip:14001@;ob] for L:6.1[Line:90000<<WebRTC]
      22-ott-2014 15:07:13.537 [CM503027]: Call(C:6): From: Line:90000<<WebRTC ("WebRTC (" ) to T:Extn:14001@[Dev:sip:14001@;ob]
      22-ott-2014 15:07:13.537 [CM503004]: Call(C:6): Route 1: from L:6.1[Line:90000<<WebRTC] to T:Extn:14001@[Dev:sip:14001@;ob]
      22-ott-2014 15:07:13.537 [CM505002]: Gateway:[webrtc] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX WebRTC proxy] PBX contact: [sip:90000@]
      22-ott-2014 15:07:13.536 [CM503001]: Call(C:6): Incoming call from Line:90000<<WebRTC to
      22-ott-2014 15:07:13.536 Line limit check: Current # of calls for line Lc:90000(@webrtc[]) is 1; limit is 25
      22-ott-2014 15:07:13.533 [CM503012]: Inbound any hours rule (unnamed) for 90000 forwards to DN:14001

      October 22, 2014 at 4:09 pm
    • @Bruno – WebRTC Gateway is not designed to be used from Internal Network
      To test and make it work in the internal network, then go to Settings > Network > STUN Server Disable Stun and in the Static Public IP instead of putting the public ip put your private IP.
      This will break voip providers but in any case – if you are testing then it is OKAY…

      October 22, 2014 at 4:44 pm
  5. Erik Gantar

    How to configure WebRTC and is SSL must (port 443 forward to 3cx server) ?

    October 22, 2014 at 10:39 am
  6. Dropped support for 3CX Phone System on x86 systems.
    What about 3CX v12 systems who are already running on x86 ? All the Beronet appliances we have are x86 because they use a motherboard which only has x86 drivers for several things.

    October 22, 2014 at 1:37 pm
    • @Thomas – You simply remain on Version 12…
      Appliances are going to need to start to move forward with 64 bit support like what is happening in the mobile/telephony front if they want to remain competitive… If a mobile can do it in such limited space, then an appliance should be able to do it also…

      October 22, 2014 at 1:44 pm
  7. bp

    Great job! Will you guys ever support running 3cx server on Microsoft Azure Virtual Machine? We’d like to move our on premise server to the cloud in Azure. It would be great if you would publish a whitepaper on how to configure Azure ports to make this work. Thanks!

    October 22, 2014 at 4:04 pm
  8. Andrew McJannett-Smith

    Is there any chance that we can get in the next release of 3CX a mobile Admin System Management Console? I have suggested this in the Ideas section: http://www.3cx.com/ideas/index.php?page=idea_detail.php&i=1541

    Most Admins are away from their Desk and having the ability to use a native App on your cellphone to be able to see the System Console would be a great improvement and allow admins to be more mobile.

    October 22, 2014 at 9:07 pm
  9. Hi,

    I couldn’t see video call in 3CX phone for iPhone as i downloaded it from above link in version 12.1.6

    October 24, 2014 at 5:49 am
    • @Sophal – 3CXPhone for iPhone does not have video support.

      October 24, 2014 at 10:04 am
  10. Scott Buchanan

    This is going to sux with 3Cx running on Server 2012 R2 Essentials. We forward port 443 to the server box which uses IIS bound to the Remote Anywhere web site to service the remote requests.

    October 29, 2014 at 4:17 pm
    • @Scott – this is just for the bETA period. In the final release, you wil be allowed at setup time to choose the port you want for both http and https. Don’t worry much about this.

      October 29, 2014 at 5:44 pm
  11. robert

    Will it work with click or dial to call telephony features in crm, ie. Goldmine

    October 29, 2014 at 4:36 pm
    • @Robert For features like click to dial to work in the WEB Interface of Goldmine, then a plugin needs to be created (like we did for Sage, Dynamics, Outlook Etc).
      Therefore you need to make a plugin that can be loaded by 3CXPhone for Windows which can receive click to dial requests from your CRM.
      More information can be found from this link http://www.3cx.com/blog/docs/3cxphone-for-windows-api/

      October 29, 2014 at 6:07 pm
  12. smile

    Could you tell detail on how to configure WebRtc and how can customer call from the link to our extensions?

    November 3, 2014 at 12:51 pm
    • @Smile http: //www.3cx.com/blog/voip-howto/how-to-configure-webrtc-links/

      November 3, 2014 at 12:59 pm
  13. uptime

    Hi Nick,

    We’re loving 3CX WebRTC!

    In the 3CXPhone Windows client, will you please consider showing the personal WebRTC call link url when the blue icon in the upper right corner is highlighted.

    Separately, we’re seeing vast video quality difference when with a WebRTC call (very good quality) versus a WebRTC Web Conferencing call, even though they seem (?) to be using the same underlying technology?

    Finally, will you please strongly consider offering a video option whereby only the called party (the 3CX user) video is displayed instead of the present situation where both sides are visible? This will avoid embarrassing and legal issues like sexual harassment when the calling party is doing something inappropriate like wearing no clothes! Seriously. Since there is no control of who’s able to call, there has to be a control that limits the called party from seeing the calling party until the calling party approves a disclosure saying they will wear clothes! ;-)

    December 4, 2014 at 11:21 pm
    • @uptime
      Thanks for your comments.
      The next update will resolve most issues. Coming soon..

      December 5, 2014 at 8:26 am
  14. Bailey


    any reason why it would be stuck on choosing web ports screen?

    I’m trying to upgrade from v12

    Using ports 5000/5001 http/https

    Running window server 2008 x64

    December 24, 2014 at 12:57 am