Simple and abstracted library for integrating with web meetings providers such as WebEx and Citrix.

v0.2.9 2013-04-10 20:31 UTC


Brief Description

Class library and abstraction layer for integrating with web meetings providers such as WebEx and Citrix.

Table Of Contents


The purpose of the SmxSimple_Meetings library is to provide a simple and consistent interface for interacting with any web meetings service provider. Using a Factory/Adapter design pattern the library can be extended to support any number of service providers, yet consumers of the library will only need to write their code once and with a simple configuration change be able to switch between any supported service providers.

Service Providers

Below is the initial list of service providers we intend to support with this library. It is our hope that by developing this library as open source that additional service providers or developers will extend the functionality.

  1. WebEx Meeting Center [COMPLETE]
  2. Citrix GoToMeeting [90% Complete - Missing create/edit user features. Need an admin account to dev/test with.]
  3. BigBlueButton [COMPLETE]
  4. Join.Me [COMPLETE] - Note that this is a very basic service with limited functionality and an even more limited API.

Improvement Ideas / TODO

  1. Create Smx\SimpleMeetings\Exception to create consistent error reporting and exception interface. Primarily to ensure errors from service providers are translated and returned to developer consistently.
  2. Create Smx\SimpleMeetings\Base\Time class to create consistent/standard way to handle dates internally and require each service provider to convert them to proper format. Added \Smx\SimpleMeetings\Shared\Time utility class for getting current local timestamp in UTC and it is now expected that times be unixtimestamps in objects and then converted to proper string formatting in each adapter as necessary for each API.
  3. Need another developer to perform a code review and help identify areas of inconsistency.


You have at least three options for how to instal Smx\SimpleMeetings. The first and preferred method is to use Composer. The second option is to just clone the Git repository. The third, old school method, is to just download an archive of the source.

Installation - Using Composer

If you have never used composer, check it out at It provides a simple way for you to define your requirements, run a command, and have it automatically download and install any dependencies. Since the installation of Composer is so simple, I'll provide the full instructions of installing Composer and using it to install Smx\SimpleMeetings. Installing Composer, from the root directory of your project, run:

curl -s | php

This will create a composer.phar and vendor/ folder. Next, create a composer.json file with contents:

    "require": {
        "smx/simplemeetings": "dev-master"

Next, run the following command to tell composer to install the package:

php composer.phar install

Now you'll have the folder vender/smx/simplemeetings/ with the library source inside. One of the great things about composer is it automatically inspects the tags from the Git repository and checks out the latest tag (if you use dev-master in your require statement). To update the library you just run:

php composer.phar update

Installation - Using GitHub / Cloning the repository

If you dont want to use Composer, you can simply clone the repository. If you are not already using Git for source control management, you really should be, you can learn more about it and how to install it at When cloning the repository you want to also make sure to checkout the latest tag to ensure you have a stable copy:

$ git clone git://
Cloning into 'Smx_Simple_Meetings'...
Resolving deltas: 100% (84/84), done.
$ cd Smx_Simple_Meetings/
$ git tag -l
$ git checkout v0.1.2
Note: checking out 'v0.1.2'.
HEAD is now at 46f9d40... 

To update the library with this method:

$ git pull
$ git tag -l
$ git checkout v#.#.#

Installation - Downloading Files

From the GitHub project homepage, browse to the latest Tag under the Branches button. When you're viewing the latest tag, click on the Zip button to download an archive of the source. Then simple unzip it to wherever you want. To update the library using this method you'll need to download the latest tag again, unzip it, and then sync the files over top of the original ones you downloaded.

Usage Instructions

The purpose for Smx\SimpleMeetings is to make interacting with web meetings service providers very easy and consistent.

In order to include Smx\SimpleMeetings into your application, you have two options: Standard Composer autoloader, or a single include file. If you used composer to install, we recommend you just include the vendor/autoload.php file that contains autoloaders for other composer libraries you may be using. If you did not use composer or do not wish to use the included autoloader, simply include the SmxSimpleMeetings.php file. We plan to also provide configurations for common autoloaders so that you don't need to include anything but rather just update our autoloader configuration.

Simple example of how to schedule a WebEx meeting:

require_once 'path/to/vendor/autoload.php';

* Sitename is the webex subdomain your account is on, 
* like (you can get a free account there)
$webexAuthInfo = array(
    'sitename' => 'mycompany',
    'username' => 'myusername',
    'password' => 'mypassword'

$meeting = Factory::SmxSimpleMeeting('WebEx', 'Meeting', $authInfo);
* All meeting options are optional, except maybe 
* meetingPassword if your site requires a password.
    'meetingPassword' => 'Comp123', 
    'meetingName'     => 'This is my meeting',
    'startTime'       => '03/01/2013 10:00:00',
    'duration'        => '60',
    'isPublic'        => true

echo "Meeting is scheduled, meeting key: " . $meeting->meetingKey;

More comprehensive API documentation is under development, but for now just read through the interfaces defined in adapters/Smx/SimpleMeetings/Interfaces/ to understand what methods are available.

Variations in Authentication

Each service provider API requires a different authentication approach and therefore your application will need a little knowlege of the differences. As a consumer of smx/simplemenetings you only need to pass the authentication information as an array into the factory and each adapter will handle the rest, but you will need to know what format is required for each adpater. Here are some examples for each service provider:

* WebEx AuthInfo
* Sitename is the subdomain for your webex site, so for 
*, the sitename is mycompany
* Password is sent in clear text, although over https, so it 
*   is recommended to store this in an encrypted format for at 
*   least a little safety
$webexAuthInfo = array(
    'sitename' => 'mycompany',
    'username' => 'myusername',
    'password' => 'mypassword'

*  Citrix AuthInfo
*  Citrix uses oAuth for authentication of users. This means you 
*  need a unique API Key for your application as well as an access 
*  token for your user. smx/simplemeetings can help with this process,
*  all you need to provide is the API key, the library can give you an 
*  auth url for the user to visit and authenticate. When the user 
*  is redirected to your application you can call the library again 
*  with the provided response code and the library will handle getting
*  the access token used for further API calls. The access token is valid
*  until invalidated by the user, so you should store this somewhere safe.
*  Also after retreiving the auth token, the user's organizer key (think
*  of this as their unique user id) will be returned, so store this as well.
$citrixAuthInfo = array(
    'apiKey' => '123456789098765432101234567890ab',
    'accessToken' => 'ab123456789098765432101234567890',
    'organizerKey' => 'abcdef1234567890eefab'

* BigBlueButton AuthInfo
* BigBlueButton (BBB) is maybe the weirdest of them all in terms of how it 
* authenticates API calls. Rather than use individual user credentials,
* it uses an API Security Salt. With BBB all meetings are instant and 
* users either join using a moderator password or an attendee password and 
* the system assigns rights based on the password provided. BBB assumes you 
* already have an application full of users and that you'll manage the association
* between users and meetings. When creating a meeting it is possible to supply
* your own meta data including a user id that you can use to link data for reporting.
* Base URL is the API endpoint to be called, since BBB is open source you
* can host it wherever you like.
$bbbAuthInfo = array(
    'baseUrl' => '',
    'salt' => 'ab123456789098765432101234567890'

* Join.Me AuthInfo
* Join.Me is similar to WebEx in that it uses a user's username and password
* for authentication. It is slightly different however in that it uses the
* username and password to generate an auth token for use with further API
* calls. The thing that is odd about Join.Me though is that the auth token
* is created for a user, not a user+application level, so if another application
* generates an auth token for the same user, the previous token you generated
* will be invalidated. For this reason we recommend you always just use
* the user's username and password and let the library fetch a new auth
* code for you with each use. You could also store just the auth token and 
* require your user to re-authenticate if the token is ever invalidated, it is
* up to you.
$joinmeAuthInfo = array(
    'email' => '',
    'password' => 'mypassword',
    'authCode' => 'ab123456789098765432101234567890'

Citrix Notes

Citrix uses oAuth for authentication and uses an access token to authorize any API calls. If you've integrated with other oAuth providers then you're already familiar with the flow.

To call Citrix APIs you'll also need an API Key. You can get one of these by registering at Make sure your application URL is the same domain that you'll be hosting your application. For oAuth the user can only be redirected to URLs on the same domain.

Assuming you do not already know your user's access token:

  1. Get new object from factory.
  2. Get Auth URL
  3. Redirect user to Auth URL
  4. After user logs in and grants access to your application they will be redirected back to your site with a parameter ?code= which will be a responseKey
  5. Get a new object from factory again and call the authForAccessToken method with the response key
  6. Your object will now have the accessToken and organizerKey attributes set, you may want to store these to save the user from logging in again in the future, but be responsible of course.


$authInfo = array(
    'apiKey' => 'YOUR_API_KEY_HERE'
$account = Factory::SmxSimpleMeeting('Citrix', 'Account', $authInfo);
$authUrl = $meeting->getAuthUrl();
// Redirect User to Auth URL
// ...
// User has returned with ?code=123456789
$responseKey = $_GET['code'];
$authInfo = array(
    'apiKey' => 'YOUR_API_KEY_HERE'
$account = Factory::SmxSimpleMeeting('Citrix', 'Account', $authInfo);
echo 'Access token: '.$account->getAccessToken();
echo 'Organizer Key: '.$account->organizerKey;
// Future calls
$authInfo = array(
    'apiKey' => 'YOUR_API_KEY_HERE',
    'accessToken' => 'YOUR_ACCESS_TOKEN_HERE',
    'organizerKey' => 'YOUR_ORGANIZER_KEY_HERE'
$options = array(
    'meetingName' => 'My First Meeting'
$meeting = Factory::SmxSimpleMeeting('Citrix', 'Meeting', $authInfo, $options);

Join.Me Notes

Join.Me ( is a very simple and easy to use desktop sharing service. They also have an even more basic API to provide limited integration capabilities with their product. There are pretty much only two APIs:

  1. Authenticate a user and get an authCode returned
  2. Create a meeting/session and get a code and ticket to use to start it

You can checkout their APIs at

One thing to note is that their concept of an authCode is based at a user level, but not also at an app level. So if you generate an authCode for a user using this library, and then that user uses some other service that calls the same API, it will invalidate the previous authCode. So just something to be aware of.

Feedback / Support

Please use the GitHub ticket system to raise feature requests and bugs. We want this to be an extremely easy yet flexible library for you to use so please let us know how we can improve on it. We would also love for anyone to join the project to help provide adapters for additional service providers and extend the ones we already have.