Configuring “Play On Phone” for Outlook with 3CX Phone System

Edit 16th September 2015: Please note that 3CX Phone System only works with MS Exchange Server 2013 and 2013 SP1

If you have enabled Exchange integration inside 3CX Phone System, with Outlook 2007/2010/2013 as an Email client you can take advantage of the “Play On Phone” feature. For details about enabling 3CX Phone System and Exchange Server Integration, please refer to the following article: Exchange Server 2007 / 2010 / 2013 

For the “Play On Phone” function to work with Outlook, you must ensure sure that the Auto Discovery function on your Outlook installation is correctly implemented to integrate with Exchange/DNS. If this is not implemented correctly, you will typically receive an error message reading “The Microsoft Exchange Unified Messaging service cannot be contacted”. If you encounter this error, you will need to investigate your configuration to correctly implement the Auto Discovery function.

Configuring a Connection for the Exchange “Play On Phone” feature

  1. Create a new “Generic SIP Trunk” and name it “Exchange”
    screenshot_40
  2. Click “Next” at the bottom of the page, and then accordingly:
    • For Exchange 2010/2013 on latest service pack and roll up proceed as follows:
      • Set the “SIP server hostname or IP” field to the FQDN of the Exchange Server. Please note that it MUST NOT be the IP Address.
      • Set the “SIP Server port” to “5060”.
      • Click “Next” at the bottom of the page.
        screenshot_41
    • For Exchange 2007 on latest service pack and roll up please follow the next steps
      • Set the “SIP server hostname or IP” field to the FQDN of the Exchange Server. Please note that it MUST NOT be the IP Address.
      • Set the “SIP Server port” to “5065”.
      • Click the “Next” button at the bottom of the page.
        screenshot_01
  3. In the “Account Details” section:
    • Set the “External Number” field to “0”.
    • In the “Simultaneous Calls” section, set the “Maximum simultaneous calls” field to “100”.
    • Click “Next” at the bottom of the page.
      screenshot_02
  4. In the inbound routing page:
    • Set the destination for calls to “End Call”.
    • Enable the check-box labelled “Same as Out of Office hours”.
    • Click the “Next” button at the bottom of the page.
    • At the Outbound Rule page, click the “Skip” button at the bottom of the page.
  5. In the 3CX Management Console, expand the “VoIP Providers” node, and click on “Exchange 2010”. In the “Advanced” tab:
    • Set the “Which IP to use in ‘Contact’ field for registration” option to “Internal”.
    • Click the “Apply” button at the bottom of the page.
      screenshot_03
    • In the “Source ID” tab, add a source identification rule. In the “Call Source Identification” section:
      • For Exchange 2007:
        • Set the “SIP Field” dropdown to “Contact: Host Part”.
        • Set the “Variable” dropdown to “GWHostPort gateway/provider host/port”.
        • Click the “Add/Update” button.
        • Click “Apply” at the bottom of the page.
          screenshot_05
      • For Exchange 2010/2013:
        • Set the “SIP Field” dropdown to “FROM: Host Part”.
        • Set the “Variable” dropdown to “GWHostPort gateway/provider host/port”.
        • Click the “Add/Update” button.
        • Click the “Apply” button at the bottom of the page.
          screenshot_04
      • In the “DID” tab, create a DID number for each extension which will be using the “Play On Phone” feature. Each DID number should match the relevant extension number.
  6. For each DID, route the call to the relevant extension number.
  7. This image shows “Play On Phone” successfully implemented for extension 100.

Liked this article?


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

    Any ideas why I would be receiving the following error, when trying to use ‘Play on Phone’ feature, after setting up based on your instructions?

    Additional information: Peer to peer endpoint does not support authentication.

    Thanks!

    December 6, 2010 at 5:47 am
    • Kevin

      @James
      Could it be that you used the “Generic VoIP Provider” template instead of the “Generic SIP Trunk” template? We’ve run tests against the document and it all works fine for us…

      December 6, 2010 at 3:38 pm
  2. Paul Lukandwa

    This is really great, a perfect selling point for the IP-PBX productivity Featureset

    December 15, 2010 at 1:38 am