Adobe Connect Support Blog

Updated April 20, 2021

Adobe Connect Server PGi Telephony Adapter Update

PGI is providing an upgraded audio integration adapter with the release of Adobe Connect 11.2.1. This new audio adapter uses PGI’s latest integration APIs to provide superior performance and enhanced controls vs. the original audio adapter released in 2006.  PGI’s new global audio platform requires only one adapter for the entire world – PGI-NA. 

This new adapter also has enhanced security and because of this requires additional credentials, referred to as SubID / SubPW.

Customers requesting these new credentials need to contact PGI and provide:

  • Adobe site URL (even if it’s internal only)
  • Support email address (distro or alias address that won’t change is preferred)
  • Existing WEB ID
  • Existing Web Password (not the hashed version from the XML files)
  • Company Name
  • Company ID
  • Company Bill To Name
  • Company Bill to ID

Please submit the above information via email to support@mymeetingroom.com.  Please allow up to 2 business days for turn around.

If you are not a current PGI customer and would like to elevate your integrated audio experience, please contact PGI https://www.pgi.com/contact-pgi-pgicom/

Once you have your new credentials you can proceed with the upgrade.

IMPORTANT NOTE:
When performing the upgrade to Adobe Connect 11.2.1, update the PGi Telephony Adaptor in place. To do so, the existing adapter needs to be renamed.  The act of renaming the adapter allows existing profiles to persist without end-user interaction. This upgrade will require a restart of the telephony services.

Old adapter:

<telephony-adaptor class-name=”com.macromedia.breeze_ext.premiere.gateway.PTekGateway” default-provider=”true” disable-profiles-on-disable=”false” disable-profiles-on-edit=”false” enabled=”false” id=”premiere-adaptor_OLD” name=”{premiere-adaptor_OLD}”>

New Adapter:

<telephony-adaptor class-name=”com.macromedia.breeze_ext.PGi_PIA_AdobeConnect_Adapter.PGi_PIA_Adapter” default-provider=”true” disable-profiles-on-disable=”false” disable-profiles-on-edit=”false” enabled=”true” id=”premiere-adaptor” name=”{premiere-adaptor}”>

Overview

This guide is meant to be used when the PGi Telephony Adapter is updated to a version that uses the PIA Cloud infrastructure for connecting to PGi’s conferencing services via Adobe Connect Meetings and the PGi Telephony Adapter. The steps described within should be performed by the systems administrator in charge of the Adobe Connect Server installation or the administrator responsible for setting up the audio provider(s) for the Adobe Connect Server server(s).

The steps provided will require write access to the following on each Adobe Connect Server in the cluster (or if single server installed then that specific server):

  1.  “..\Connect\[Version Number]\TelephonyService\conf\log4j.xml”
    1. this file may be called log4j2.xml depending on your Connect Server version
  2. “..\Connect\[Version Number]\TelephonyService\conf\telephony-capabilities.xml”
  3. “..\Connect\[Version Number]\TelephonyService\conf\telephony-settings.xml”

The steps provided will also require the ability to stop and start the “Adobe Connect Telephony Service” service.

Prerequisites

An existing installation of Adobe Connect Server, either single or cluster, and the PGi Telephony Adapter component installed. If either of these conditions are not fulfilled, please discontinue following this guide and complete those steps before continuing.

  1. There are several JAR files provided that are necessary for the new adapter to function. These should be provided in a folder called “externalJARS”. These JAR files all need to be placed in the same folder as the new adapter JAR.

Changing the Telephony-Settings.xml File

The following steps must be done on any Adobe Connect Server installation in either a single installation or a cluster installation.

  1. Navigate to and open the “..\Connect\[Version Number]\TelephonyService\conf\telephony-settings.xml” file in your favorite text editor.
  2. Locate the “<telephony-adapter” tag entry for the PGi Telephony Adapter (typically it has an id of “premiere-adaptor”).
    1. Copy the entire “<telephony-adapter” tag entry all the way to its closing tag.
    2. Paste the copied text after the closing tag for the existing adapter.
  3. Locate the ‘class-name=”com.macromedia.breeze_ext.premiere.gateway.PTekGateway”’ and replace it with ‘class-name=”com.macromedia.breeze_ext.PGi_PIA_AdobeConnect_Adapter.PGi_PIA_Adapter”’. This value must match exactly for the adapter to load when the service is started.
  4. Locate the ‘id=”premiere-adapter”’ entry inside the opening tag and change that to ‘id=”pgi_pia_adapter”’. This id will be used throughout this guide and when modifying the telephony capabilities and logging files.
  5. Locate the “name=” entry in the opening tag and change the value after the equal sign to “PGi_PIA_Adapter”. This name will be used when setting up the audio provider using the new adapter.
  6.  After the right chevron of the opening tag (“>” symbol) add the following (change values to be appropriate to whatever Environment the adapter is running in, e.g. in a Stage or QAB environment the websocket value will be wss://piacloud-qab.pgilab.com/1.0_WS/PiaWebSocket.svc):
    1. <setting id=”PREMIERE_WEBSOCKET”>wss://piacloud.pgiconnect.com/1.0_WS/PiaWebSocket.svc

</setting>

  • <setting id=”PREMIERE_SUBID”>[Client ID]</setting>
    • The [Client ID] should be the client id provided by PGi. This will correlate to intlclientid if that is a value you’ve received previously.
    • <setting id=”PREMIERE_SUBPW”>[Client PW]</setting>
      • The Client PW should be the client pw provided by PGi. This should be the password that is associated with the above Client ID.
    • <setting id=”PREMIERE_DIALOUTTYPE”>1</setting>
  • Replace the following entry (change values to be appropriate to whatever Environment the adapter is running in, e.g. in a Stage or QAB environment the host value will be https://piacloud-qab.pgilab.com/2.0/PiaRestWebServices.svc):
    •     <setting id=”PREMIERE_HOST”>
              adobe-axis.globalmeet.com
          </setting>
      WITH
          <setting id=”PREMIERE_HOST”>
              https://piacloud.pgiconnect.com/2.0/PiaRestWebServices.svc
           </setting>
  • Ensure the values for ‘<setting id=”PREMIERE_WEB_ID”>’ and ‘<setting id=”PREMIERE_PASSWORD”>’ are equal to the entries for ‘<setting id=”PREMIERE_DOWNLOAD_LOGIN”>’ and ‘<setting id=”PREMIERE_DOWNLOAD_PASSWORD”>’
    • These values should be provided by PGi for both the ID and PW. These values should be the same from the old adapter. Do not confuse these with the client id and password. These values can be the same if they were provided that way.
  • If desired you may increase the value of MAX_SUB_CONFS from 9 to 20.
    • This will increase the number of breakout rooms supported with telephony from 9 to 20.
  • Save and close the telephony-settings.xml file.

Changing the Telephony-Capabilities.xml File

The following steps must be done on any Adobe Connect Server installation in either a single installation or a cluster installation.

  1. Navigate to and open the “..\Connect\[Version Number]\TelephonyService\conf\telephony-capabilities.xml” file in your favorite text editor.
  2. Locate the “<telephony-adapter” tag entry for the PGi Telephony Adapter (typically it has an id of “premiere-adaptor”).
    1. Copy the entire “<telephony-adapter” tag entry all the way to its closing tag.
    2. Paste the copied text after the closing tag for the existing adapter.
  3. Locate the ‘class-name=”com.macromedia.breeze_ext.premiere.gateway.PTekGateway”’ and replace it with ‘class-name=”com.macromedia.breeze_ext.PGi_PIA_AdobeConnect_Adapter.PGi_PIA_Adapter”’. This value must match exactly for the adapter to load when the service is started.
  4. Locate the ‘id=”premiere-adapter”’ entry inside the opening tag and change that to ‘id=”pgi_pia_adapter”’. This id will be used throughout this guide and when modifying the telephony capabilities and logging files. This id must match the id given to the entry for the new adapter in the “telephony-settings.xml” file from the previous section.
  5. Save and close the “telephony-capabilities.xml” file.

Changing the Log4J2.xml (or Log4J.xml) File

The following steps must be done on any Adobe Connect Server installation in either a single installation or a cluster installation.

  1. Navigate to and open the “..\Connect\[Version Number]\TelephonyService\conf\log4j2.xml” file (or log4j.xml) in your favorite text editor.
  2. Locate the ‘<RollingFile’ tag entry for the PGi Telephony Adapter (typically it has a name of “PREMIERELOG”).
    1. Paste the copied text after the closing tag for the existing adapter.
  3. Type the value “PGi_PIA_Adapter” after the equals sign in the ‘name=’ option, ensuring you remember this name to use further on in this file.
  4. Type a value into the ‘fileName=”${TELEPHONY_LOGS_DIR}/Premiere_Adaptor.log”’ option, replacing (or not) the ‘Premiere_Adapter.log’ value with “PGi_PIA_Adapter_Log.log”.
  5. Follow the same instructions as Step 4 for the ‘filePattern=’ option, appending a file name format you would like for rolled over files.
    1. For Example: filePattern=”${TELEPHONY_LOGS_DIR}/PIA_Premiere_Adaptor.log.%d{yyyy-MM-dd-a}”
  6. Type the same name specified in Step 3 inside the double quotes of the ‘<IfFileName glob=”Premiere_Adaptor.log.*”>’ option, making sure to leave the “.*” at the end of the filename.
  7. Locate the <Logger name=’ tag entry for the PGi Telephony Adapter (typically it has a name of “com.macromedia.breeze_ext.premiere.gateway.PTekGateway”).
    1. Paste the copied text after the closing tag for the existing adapter.
  8. Locate the ‘’ and type the name you defined in Step 3 and replace the name inside the double quotes of the ‘ref=’ option with that name.
  9. Locate the ‘<Logger name=”com.macromedia.breeze_ext.premiere.gateway.PTekGateway”’ and replace it with ‘<Logger name=”com.macromedia.breeze_ext.PGi_PIA_AdobeConnect_Adapter.PGi_PIA_Adapter”’. This value must match exactly for the adapter to write logs when the service is started.

Start the Service

Go to the Windows search bar or click Start and then Run, and type “Services” and press Enter. Locate the “Adobe Connect Telephony Service” entry and start the service. Check the log in the logging directory for the Telephony Service for the log with the filename specified in the previous section. Once you see several lines of logging points the adapter is ready to go. If, after 5 minutes, you do not see any lines in the log file, the log file doesn’t appear, or you see errors in the log file then something happened and the adapter may or may not be working. Work with the Adobe Customer Care team for next steps.

General, Install, Meeting, Telephony, Uncategorized

Join the discussion

  • By Mike - 10:15 PM on April 19, 2021   Reply

    Hi Frank,
    The description is a bit confusing…Especially when you need to modify files.
    There are several “Paste the copied text after the closing tag for the existing adapter.” in the text. Could you please explain what “copied text” means (where should I copy it from?)

    “Changing the Log4J2.xml (or Log4J.xml) File” is the most confusing part…
    I assume I have to use “RollingRandomAccessFile” instead of “<RollingFile" tag in Log4J2.xml.
    Aren't #4 and #5 the same actions?
    #8 There is no "class-name" thing in "<Logger name=".
    Could you please correct typos/mistakes in the article?
    Thank yo in advance.

    • By Frank DeRienzo - 3:50 PM on April 20, 2021   Reply

      Hi Mike, Thanks for the excellent review. The corrections and improvements you recommended are made:
      – I assume I have to use “RollingRandomAccessFile” instead of “<RollingFile" tag in Log4J2.xml. <RollingFile is the correct tag in this case. Please do not change this to RollingRandomAccessFile.
      – Aren't #4 and #5 the same actions? They are not but I have edited the blog to clear up confusion.
      – #8 There is no "class-name" thing in "<Logger name=". I have edited the blog to reflect the proper tag and value.

Join the discussion