Archive for August, 2012

Adobe connect users getting re-connected to meeting room

Posted on August 30, 2012 by Mohit . | Comments (0)

PROBLEM -: Meeting users are getting re-connected to the meeting room randomly within a second.

My connect server is hosted on Amazon EC2 cloud on windows 2008 R2 OS.

SOLUTION -:

1. Capture the connect add-in logs generated on the user’s computer joining on the meeting room, To generate addin logs follow the KB Doc http://helpx.adobe.com/adobe-connect/kb/enable-logging-acrobat-connect-professional.html

The connect addin logs would be generated on client/user side , not on the server side.

2. Open the connectaddin log file generated under your documents folder when you expreience reconnects.

3. If you find the lines -:

Player   TRACE: StreamHandler::public/all/screenshare_0::NetStream onStatus for stream: public/all/screenshare_0, code: NetStream.Play.InsufficientBW

4.  And your server is hosted in the Amazon EC2 cloud and has Win 2008 64 bit OS.

5. The fix for this is to switch onto Win 2003 OS

6. This is a known issue reported by a lot of users having Win 2008 server hosted on Amazon EC2 cloud, on this video streaming issue. You can check the blog at http://forums.adobe.com/thread/572258

Configuring Cisco Call Manager with Adobe Connect

Posted on August 30, 2012 by Mohit . | Comments (1)

PROBLEM -: I want to enable Universal Voice feature on my on-premise Adobe connect server using our internal Cisco call manager server.

SOLUTION -:

There are some basic network configurations needed for this integration as -:

1. SIP port 5060 should be opened between Adobe connect and cisco call manager for SIP communications

2. Port range 5000 – 6000 should be opened between Adobe connect and cisco call manager  for transversing voice packets via RTP.

3. DTMF mode RFC 2833 must be supported by cisco call manager as well as its carrier.

Integration steps -:

1. I need to create username/password based SIP account on cisco call manager

2. Login into cisco call manager and Navigate to Device -> Phone -> Add new ->

Refer to the screenshot below

 Select Third party Basic device

Select Sip profile as standard sip profile

Select Digest user as LDAP ID of a user x

Check mark Media Termination Point Protocol.

 

3. Navigate to User Management > End User .

Search for LDAP ID of user x

The user-id of the LDAP user x would be the username of SIP account

The pin would be the password of the SIP account.

 

4. Configure your adobe connect SIP account settings with username of SIP account , password of the SIP account as per step 3.

Adobe Connect connection test page fails in step 2 on Google Chrome

Posted on August 30, 2012 by Mohit . | Comments (0)

PROBLEM : – Adobe connect meeting connection test page fails in connection to FMS on Google chrome even though i have removed MS Patch (MS12-006 )which is conflicting with the TLS/SSL handshake

The same test page successfully completes step 2 on firefox web browser

Sample connection test page URL -: https://your-connect-url/common/help/en/support/meeting_test.htm

SOLUTION -: This is applicable when connect server is secured via SSL and chrome browser has Flash Pepper (PPAPI) plug-in

 Disable the default Flash Pepper (PPAPI) plug-in in Chrome 21 as per the screenshots

  

  1. Type chrome://plugins in a browser tab (Figure 1).
  2. Expand Details in the upper-right area of the screen (Figure 1).
  3. Click Disable for the PPAPI Flash plug-in. Ensure that the NPAPI Flash plug-in listed below the PPAPI Flash plug-in is not disabled.
  4. Refresh the browser tab.

 

Adobe Connect disable the “Change My Password” link on the My Profile page

Posted on August 30, 2012 by Mohit . | Comments (0)

PROBLEM -: Need to disable “Change My Password” hyperlink on “My Profile” page

SOLUTION -:  

To Remove the link on login page:
1.  Backup the file: C:\breeze\appserv\apps\lang\en.xml

2.  Open the file: C:\breeze\appserv\apps\lang\en.xml

3.  Find the xml tag : <m id=”forgot-password”>Forgot your password?</m>

4.  Change it to : <m id=”forgot-password”></m>

How to disable the Change My Password link on the My Profile page:

1. Stop the connect service and backup the feature.xml file on location  C:\Breeze\appserv\apps\home\feature.xml

2. Open the file as above in a xml editor like editplus/notepad++.

3 Search the following block of code on feature.xml file 

        <feature id=”password” name=”password” title=”change-my-password” nav=”level-2″ propagate=”true”>        
            <template name=”home/password.xsl”/>
            <param name=”account-id” path=”/results/common/account/@account-id” propagate=”true”/>
            <action name=”password-rules”>
               <param name=”acl-id” from=”account-id”/>
            </action>
            <param name=”user-id” path=”/results/common/user/@user-id”/>
                   
            <feature name=”save” title=”save” nav=”button-bottom” type=”submit”>
             <param name=”user-id” path=”/results/common/user/@user-id”/>
             <action name=”user-update-pwd”/>
             <goto status=”ok” feature=”info”/>
           </feature>           
            <link title=”cancel” feature=”info” nav=”button-bottom”/>
          </feature>

4. Comment out the block of code as follows

<!–
         <feature id=”password” name=”password” title=”change-my-password” nav=”level-2″ propagate=”true”>        
            <template name=”home/password.xsl”/>
            <param name=”account-id” path=”/results/common/account/@account-id” propagate=”true”/>
            <action name=”password-rules”>
               <param name=”acl-id” from=”account-id”/>
           </action>
            <param name=”user-id” path=”/results/common/user/@user-id”/>
                   
            <feature name=”save” title=”save” nav=”button-bottom” type=”submit”>
             <param name=”user-id” path=”/results/common/user/@user-id”/>
             <action name=”user-update-pwd”/>
             <goto status=”ok” feature=”info”/>
            </feature>           
            <link title=”cancel” feature=”info” nav=”button-bottom”/>
          </feature> –>

5. Start the connect services.

Adobe Connect Custom link on “Forgot Your Password” hyperlink.

Posted on August 30, 2012 by Mohit . | Comments (4)

ISSUE -: Need to customize the “Forgot your password” link on connect login page to redirect it to custom link.

SOLUTION -: We have tested out the customization on connect 8.2.0.1

1. you need to update the following files on -:

C:\Breeze\8.2.0.1\appserv\apps\system\login.xsl
C:\Breeze\8.2.0.1\appserv\apps\lang\en.xml

Sample updated files -: custom_url_on_forgot_your_password_link

2. Find the line on en.xml -:

 <m id=”forgot-password”>Forgot your password?</m>

 Replace it with

 <m id=”forgot-password”></m>

3. I have already updated en.xnl file with respect to step 2.

4. Replace login.xsl with the attached file.I have routed the help link to http://google.com on the attached login.xsl file

Search for the line http://google.com on login.xsl file attached on this mail and replace with your custom URL.

5. Restart the connect services to apply the changes.

 

 

Participant Code does not come in Outlook Addin Meeting invite in C8.2.2

Posted on August 30, 2012 by Jasmeet Bhatia | Comments (0)

Problem:

Participant Code does not display in Outlook Add-in Meeting invite’s Audio Conference details in Connect 8.2.2

Reason:

By default,only conference number comes in default Outlook Add-in meeting invite like below:

Please join me in a Adobe Connect Meeting.

Meeting Name: attmeetingtest
Summary:
Invited By: Jasmeet Bhatia (jbhatia@xxxx.com)
Conference Number(s): Conference number:8666xxxx
To join the meeting:

http://my.adobeconnect.com/uv45/

Solution:

In order for us to add Participant Code to Meeting Invite, we need to make following changes

  • Go to outlook.
  • Click on Add-ins.
  • Click on Preferences.
  • Select a Meeting room.
  • Then click on customize invitations.
  • Click on Edit Audio Conference.

  •  Put in Conference Number and Participant Code.

  • Click on Ok.
  • Then click on Apply to save it.

 

This will put conference details in the room’s meeting Invitation.

Telephony conference fails to start when we have an edge server in front of Connect Origin server.

Posted on August 29, 2012 by Ashwani Gupta | Comments (0)

Issue:

Telephony conference fails to start when we have an edge server in front of Connect Origin server.

Reason:

Licensed customers who use telephony that makes call-back to Connect (Intercall, for example) must open port 9080 on their firewall so that the call-back can be made. If the Intercall bridge cannot make the call-back to this URL on port 9080 the conference will not launch. It uses the call-back URL for anything you do in the conference call – mute a user, hang-up etc. The call-back URL must provide Intercall with a direct route to the origin running the meeting room.

When we have an edge server between the telephony provider and Origin server, we need to ensure that edge listens on port 9080 (in addition to 80,443,1935) and forwards 9080 traffic to Origin server. Additionally, if the origin server is clustered, we need to ensure that the response of call-back requests is sent back to the origin server who initiated the request. We cannot let edge server send these request to load balancer and have latter load balance this traffic between the origin nodes. If we do so, half of the call-back (round robin) requests will fail.


Solution:

To ensure call back is successful:

1) Make the Edge listen on ports 9080 and 9081 (in addition to current 80, 443, 1935).

2) Add redirects for each of these ports in adaptor.xml file such that

Port 9080 is redirected to origin1:9080

Port 9081 is redirected to origin2:9080

3) Change call-back URLs on both origin servers such that

Call-back URL on origin1 is connect.example.com:9080

Call-back URL on origin2 is connect.example.com:9081

4) Open TCP ports 9080 and 9081 to the Edge servers on the firewall.

 

The Connect configuration:

1) In \edgeserver\win32\conf\_defaultRoot_\adaptor.xml, add entries to map edge:ports to origins:ports as follows

origin1 IP Address:9080

origin2 IP Address:9080

2) In \edgeserver\conf\config.ini add entries to for ports on which the&nbsp; Edge listens as follows:

FCS.HOST_PORT=:1935,80,443,9080,9081

3) On origin 1:

connect.example.com:9080/services/CCAPICallbackSOAP

4) On origin 2:

connect.example.com:9081/services/CCAPICallbackSOAP

Now if a meeting is launched on Origin server 2 and an Intercall conference is started, that Origin server will make a connection to the Intercall conference bridge. The call-back URL that Intercall receives will contain the port number 9081. Intercall will hit the Edge server on port:9081 and the Edge server will redirect the request to Origin server 2 because of the redirect we placed in its Adaptor.xml.

Encrypting traffic between Edge and Origin Server on 8506.

Posted on August 29, 2012 by Ashwani Gupta | Comments (0)

Issue:

Encrypting traffic between Edge and Origin Server on 8506.

Solution:

By default, the traffic between external edge and origin server is in clear. To encrypt that, follow the steps below:

Step 1:

On the remote Edge servers, edit: /breeze/edgeserver/win32/conf/_defaultRoot_/_defaultVhost_/vHost.xml:

replace:
<RouteTable protocol=""> with
<RouteTable protocol="rtmps">
replace:
<RouteEntry></RouteEntry> with
<RouteEntry protocol="rtmps">*:*;*:*</RouteEntry>

Step 2:

Secure the 8506 traffic at the Origin server on 8506 exactly as though it were client traffic inbound to port 1935 except using port 8506 instead.

On the origin servers (or on the origin’s SSL accelerator), encrypt the inbound Edge to origin traffic on port 8506. The example below shows an stunnel.conf file on origin server, add for the IP receiving rtmp traffic on the meeting server VIP:

#[rtmps-vip for Origin]

accept = 10.40.2.54:8506

connect =InternalIP02:8506

 

Note:

One caveat with this technique of doing SSL, is that when you view the RTMP sequence from within a test meeting (Help>Shift>About Adobe Connect) the second leg of the RTMP sequence will read RTMP even though it is actually RTMPS. We are testing for a means to adjust that output, but it is very trivial as the first leg does read RTMPS and adjudicates both legs.

Adobe Connect Upgrade Error | Port 80 in use | Win 2003 / 2008

Posted on August 27, 2012 by Sushma | Comments (0)

Problem :

My Adobe Connect service doesn’t start and I cannot get the login page to come up;

Reason :

The Adobe Connect service will not start or will not open the login page, if the server’s port 80 is in use, by any other application/process.

Solution :

Port 80 can be in use by other web servers[like IIS,Apache Tomcat], if installed on the same machine, as the Connect server machine. It is highly recommended, that you should ensure that no other application (or IIS), is listening on port 80.

Additionally, if you’re running on a Win 2003/2008 server, and if you have your SQL server installed on the same box as Connect, it is very likely that you might run into this issue.

SQL Server Reporting service on Windows 2003/2008, are bound to listen on port 80 by default. This would prohibit Adobe Connect, to start or launch the login page, since the port would be occupied, by the SQL’s reporting service. To fix this problem, ensure that this service is not running or listening on port 80.

In order to ensure that, port 80 is not in use by this service, we can run the following command to find out :

  • Open a command prompt window on the Connect server
  • Run the command netstat -a -b
  • This command determines, the list of ports, which are in use by the system, along with their process names, & via this process name, we can identify, which service/process, is using port 80.
  • If you find port 80 in use by a system.exe process, which has a Process Id(Pid) 4, ensure your SQL Server’s Reporting service is not running.
  • Once this service is stopped or alternately configured to listen on any other port, you should be able to start the Adobe Connect service successfully and get to the login page as well.

 

Adobe Connect 8 | Login page not coming up after upgrade | SSL

Posted on August 27, 2012 by Sushma | Comments (0)

Problem :

I upgraded my Adobe Connect 7 server to version 8 and I can’t get the login page to come up. I tried connecting to the admin console through localhost:8510/console and it doesn’t get through that either.

Reason :

Adobe Connect 8 requires an additional modification, in the configuration files, for SSL to be enabled. Starting Connect 8, we need to enable, the 8443 connector separately for SSL to work; the connector is turned off by default.

Solution :

If you have SSL configured and you are performing an upgrade to version 8, you are required to follow these steps, to enable SSL completely :

√ Navigate to {root}\Breeze\appserv\conf   folder on your Adobe Connect server

√  Save a backup copy of server.xml file

√  Now open the file in an editor

√  Search for the below tags and ensure that these lines are uncommented :

<Executor name=”httpsThreadPool”
namePrefix=”https-8443-”
maxThreads=”350″
minSpareThreads=”25″/>

<Connector port=”8443″ protocol=”HTTP/1.1″
executor=”httpsThreadPool”
enableLookups=”false”
acceptCount=”250″
connectionTimeout=”20000″
SSLEnabled=”false”
scheme=”https”
secure=”true”
proxyPort=”443″
URIEncoding=”utf-8″/>

√  Please note that these are two separate tags which can be located separately within the file.

√  Save the file and restart the Adobe Connect services.

 

Note  :  These settings are also applicable for your Adobe Connect 9 server with SSL configured.