IBM®
Skip to main content
    Country/region select      Terms of use
 
 
   
     Home      Products      Services & solutions      Support & downloads      My account     

developerWorks  >  Lotus  >  Forums & community  >  Inside Mobile Design and User Experience

Inside Mobile Design and User Experience

Thoughts on mobile and social business applications, design, and user experience, by Chris Reckling.

Sametime Meetings is an excellent client! You should try it. It works on Greenhouse, SmartCloud (4-4 digit meeting ids), and your own on premises install of Sametime. One problem we seek to solve for end users is that pesky server setup and configuration step - you know, the first step you have to do in most cases (although you can join SmartCloud meetings anonymously if allowed).

Like our other mobile apps, there's an easy solution for admins and help desks. The setup task can be done by the user simply tapping a link provided by the administrator. And, in the meetings app, we'll even make the url for you!

Here's how it works. Set up a server ("Company Meeting Server") in the app in Settings. Then open it as if to edit it and you should see an action button to either copy or email the configuration setting, as in the screenshot below.
Image:Sametime Meetings Mobile Configuration URLs

I emailed myself the configuration URL and got this message:

Please install IBM Sametime Meetings app and open the relevant link below to create a configuration for "meetings.ibm.com".

On Apple devices, use:
stmeetings://meetings.greenwell.com:443/stmeetings/configure?action=AddMeetingServer&serverName=Meetings&ssl=true&authProxy=imcproxy.greenwell.com%3A15008&authProxyReuseCredentials=true

On Android devices, use:
http://meetings.greenwell.com:443/stmeetings/configure?action=AddMeetingServer&serverName=Meetings&ssl=true&authProxy=imcproxy.greenwell.com%3A15008&authProxyReuseCredentials=true


The only difference in the URL is the protocol, mainly to ensure that the Android mail clients will turn the text into a clickable link automatically. Because of this limitation, we recommend you create a mobile friendly web page and include one link to configure the app, using the stmeetings:// protocol in your href tag.

Once you tap on the URL, the IBM Meetings client will launch to the server settings page and ask if you want to add a new meeting server. If you OK this, then you can enter your user name and password and be done. If you want to be extra nice and the domain name of your people is always the same, you can add that to the first server parameter, like this in red:

stmeetings://you%40greenwell.com@meetings.greenwell.com:443/stmeetings/configure?action=AddMeetingServer...etc

Here is the full table of parameters, but I'd send the email to yourself instead. Don't forget to encode those strings!
Name
Value
Notes
action
AddMeetingServer
This is the only action supported right now.
serverName
URL-encoded string
Optional. A user-friendly nickname for the newly created meeting server. If a name is not specified, a default name will be used based on the meeting server host name.
ssl
true or false
Determines whether SSL is enabled for this connection. Optional parameter, default value is true.
guestUser
true or false
Determines whether the username provided is a guest or an authenticated user. If the value is true the username is used as the displayname for the guest. Optional parameter, default value is false.
savePassword
true or false
Determines whether passwords are remembered for this connection. Applies to both Sametime meeting server and authenticating proxy passwords. Optional parameter, default value is true.
authProxyEnabled
true or false
Determines whether connection requires authentication with a reverse proxy server. Optional, default value is false. If this parameter is not present, but authProxy parm is supplied, it is inferred to be true.
authProxy
URL-encoded user id, password, proxy address and proxy port
Optional, If present, authProxyEnabled is assumed to be true. Data is formated using :@:
If User and password are omitted, authProxyReuseCredentials is assumed to be true. If port is missing, 80 or 443 will be assumes dependng on ssl setting.
authProxyReuseCredentials
true or false
Optional. If true, reverse proxy authentication will use the Sametime user ID and password. If present, proxy authentication is assumed to be enabled.








Thanks to engineering for the good spec to use as the basis for this post.

Chris

Chris Reckling | 30 May 2013 10:30:00 AM ET |

Search this blog 

Blog powered by 

Feeds 

Recent Entries 

    Archives 

      Links 

      Disclaimer 

          About IBM Privacy Contact