Deploying the Inbound Outbound BOT sample

Introduction

The GotUC.net developer sandbox is a fully functioning Office Communications Server environment where you can host BOT applications. In order to deploy the application in this document you most have a GotUC.net Sandbox account. Please read this blog post for more information:  GotUC.net Developer Sandbox Technical Overview

To deploy the IMEcho BOT application you will need the following items installed on your developer PC.
?    Visual Studio 2008 SP1
?    .NET Framework 3.5 SP1 
?    UCMA 2.0 SDK
?    Office Communicator Client (Optional)
?    Inbound Outbound BOT sample application

 

Inbound Outbound Sample Application Configuration

If you don't have the UCMA 2.0 SDK Installed on your PC, it can be found here:

(32 BIT)
http://www.microsoft.com/downloads/details.aspx?familyid=768efa33-6606-4b2b-809a-6c69274621d3&displaylang=en

(64 BIT)
http://www.microsoft.com/downloads/details.aspx?FamilyID=b20967b1-6cf5-4a4b-b7ae-622653ac929f&displaylang=en

The Inbound Outbound BOT sample application  can be downloaded here: http://gotuc.net/media/p/100.aspx

 

To get started open the Inbound Outbound BOT project in Visual Studio and open the App.config file.

VSScreen
 

You will need to modify the sections highlighted above there is no need to change the ocsServerFqdn or the Domain these settings are already configured for you in the sample.

You should use the user, password and sip address of account number two provided in your Account Activation email.

  • UserName
  • Password
  • SipUri

 

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <configSections>
    <section name="userEndpointSettings" type="System.Configuration.NameValueSectionHandler"/>
  </configSections>

  <userEndpointSettings>
    <add key="ocsServerFqdn" value="ae.gotuc.net"/>
    <add key="userName" value="testuserbot"/>
    <add key="password" value="password"/>
    <add key="domain" value="gotuc"/>
    <add key="sipUri" value="sip:testuserbot@gotuc.net"/>
  </userEndpointSettings>
</configuration>



Once you have changed the App.config settings save your changes.
Now open the workflow1.xoml file in Visual Studio, This is the Windows Workflow for our sample application.

WorkflowFile

 

You should now see the Workflow loaded in Visual Studio.
Select the getPresenceActivity and view its properties by pressing F4 on your keyboard.

Workflow

 

In the property window change the Targets property value to the sip address of account number one provided in your account activation email !

Step1

Now we need to change the CalledParty property value for the imOutbound and voiceOutbound activities. Set these values to the sip address of account number one provided in your account activation email

calledparty

 

Just to be clear on the sip address configuration i have a screen shot of my GotUC account activation email.
If you are confused about which account to use and where this should help clarify things.

email

 

Now press F5 to debug the sample application and you should see the following screen.
All three steps should show complete once this is completed logon to Office Communicator or Communicator Web Access.

 vstoolbar

Once the application starts you will see a command window appear, All three steps should show completed if you configured your app.config file correctly and you are on the Internet.

cmdwindow  

In communicator type the name of your BOT user you received in your account activation email, you should see the contact appear. Start a conversation with this contact to test the BOT.

communicatorstep1

Make sure you Presence is set to Available for the first demo.

Communicator1

Start an IM conversation with your BOT account send over a text message, you should see an inbound IM message arrive from the BOT after pressing enter.

Communicator2

You can see the invite in the screen shot below.

IMMessage

The IM conversation should respond with your original message and append the following text (This is a message from inbound outbound sample.)

Communicator3

Now lets change our presence to Busy and start a new conversation with our BOT.This time the workflow will place an outbound AudioCall because the IfElseActivty has logic to place an outbound call instead of an IM message based on the status of my presence.This was done using the getPresenceActivity in our workflow.

 Communicator4

Start a new conversation and after pressing enter you should receive an Inbound call from the BOT. The BOT will speak a text to speech message and hang up.

Communicator2

Click on the incoming call request and you should hear the message. (You will need audio configured to hear it)

Inbound Call

 

This sample demonstrated an out bound IM and Voice call based on the status of a users presence. The trigger was my inbound IM message to the BOT but this could easily be triggered by a service application that monitors a database or even an email arriving in Exchange.

 

Please send any comments or questions to keith@gotuc.net

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: keith
Posted on: 5/20/2009 at 7:45 AM
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (297) | Post RSSRSS comment feed

Deploying the IMEcho Bot Sample Application

Introduction

The GotUC.net developer sandbox is a fully functioning Office Communications Server environment where you can host BOT applications. In order to deploy the application in this document you most have a GotUC.net Sandbox account. Please read this blog post for more information:  GotUC.net Developer Sandbox Technical Overview

To deploy the IMEcho BOT application you will need the following items installed on your developer PC.
?    Visual Studio 2008 SP1
?    .NET Framework 3.5 SP1 
?    UCMA 2.0 SDK
?    Office Communicator Client (Optional)
?    IMEcho BOT sample application

 

IMEcho Sample Application Configuration

If you don't have the UCMA 2.0 SDK Installed on your PC, it can be found here:

(32 BIT)
http://www.microsoft.com/downloads/details.aspx?familyid=768efa33-6606-4b2b-809a-6c69274621d3&displaylang=en

(64 BIT)
http://www.microsoft.com/downloads/details.aspx?FamilyID=b20967b1-6cf5-4a4b-b7ae-622653ac929f&displaylang=en

The IMEcho application sample can be downloaded here: http://gotuc.net/media/p/99.aspx

 

To get started open the IMEcho project in Visual Studio and open the App.config file.


Appconfig

You will need to modify the sections highlighted above there is no need to change the ocsServerFqdn or the Domain these settings are already configured for you in the sample.

  • UserName
  • Password
  • SipUri

 

Appconfigzoom 

 

Once you have changed the App.config settings save them and press F5 to run the project.

vstoolbar

Once you press F5 you will see the following screen. All three steps should show complete once this is completed logon to Office Communicator or Communicator Web Access.

cmdwindow 

In communicator type the name of your BOT user you received in your welcome email. You should see the contact appear. Start a conversation with this contact to test the BOT.

communicatorstep1

You should see your IM message returned from the BOT. This is an extremely basic sample just to make sure you are able to work with OCS in the cloud. You should now able start developing your own applications on GotUC.net.

communicatorstep2

 

Please send any comments or questions to keith@gotuc.net

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: keith
Posted on: 5/18/2009 at 12:56 PM
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (227) | Post RSSRSS comment feed

GotUC.net Developer Sandbox Technical Overview

Introduction

The GotUC developer sandbox is a fully functioning Office Communications Server environment with Microsoft Exchange 2010. If you are a registered user you will be able to use Office Communicator client to sign-in and have IM, Video and Voice conversations with other members in additions to your Automated BOT applications.

The environment is merely for testing and can be used to quickly develop and deploy unified communications applications into the GotUC cloud. You can test a proof of concept or perform a customer demo without having to have your own OCS infrastructure in place.

Getting Started

To develop applications using the UCMA 2.0 SDK you will need the following items installed on your developer PC.

? Visual Studio 2008 SP1

? .NET Framework 3.5 SP1

? UCMA 2.0 SDK (32bit or 64 bit)

Download UCMA 2.0 (32 Bit)

Download UCMA 2.0 (64 Bit)

? Office Communicator Client

 

In order to use the developer sandbox you must register for an account at http://www.gotuc.net once registered you can click on the Developer Sandbox tab and register for developer access.

 

Step 1 ? Sign-on to http://www.gotuc.net and click the Developer Sandbox tab.

GotucTabs

Step 2 ? Click Register for developer access.

sandboxhomepage

Step 3 ? Complete the form and you will receive your account in 1-2 business days.


RegForm 

 

You will receive two Accounts one to logon to Office Communicator and the other can be used by your application. Once your application is running you simply have an IM or voice conversation with the application sip address provided.

 

Office  Communicator Options

If you don?t already have Office Communicator installed please install a licensed version or one of the trial versions available for download.

Microsoft Office Communicator 2007 R2 Trial Download

Microsoft Office Communicator 2007 Trial Download

It is recommended that you use the newer R2 version, If you already have communicator installed you can use it by simply changing your sign-in address. If you need to run the non R2 version of Office Communicator 2007 this will work as well.

If you are unable to install Office communicator or you are unable to alter your sign-in address no worries you can use the communicator web access client by pointing your browser to:    
https://cwa.gotuc.net

 

Configuring  Office  Communicator

To configure Communicator select the menu in the top left and navigate to:
Connect > Change Sign-In Address?

CommunicatorConfigStep1

Enter the sip address provided to you in your welcome email in the field labeled Sign-in address.

CommunicatorConfigStep2

Now click the advanced button and make sure your server settings are set to automatic. If you currently use Office Communicator for another network you can revert back to your original settings once finished. You can also federate your sip domain with gotuc.net so you could test your bots from your existing sip domain. This is explained in a blog post on gotuc.net.

CommunicatorConfigStep3

 

Using Communicator Web Access
Office Communicator Web Access can be run using your web browser. Navigate to https://cwa.gotuc.net
Sign in using your credentials provided in your registration email. Make sure you supply the domain name before your userid for example: ?gotuc\keith? enter your password and click sign in.

Note
Make sure you enable pop-up windows for this site once authenticated a new browser windows will be displayed with the Communicator Web Client.

cwaStep1 cwaStep2

Once logged on you can add contacts and start conversations.

cwaStep3

Accessing Exchange 2010
Your GotUC.net account gives you access to our Exchange 2010 server. You can access email using Outlook web access and also use Exchange web services in your applications for testing and development. You can send and receive email from your gotuc.net email address.

?    Outlook Web Access
?    Exchange Web Services
?    Unified Messaging (Available  in June 2009)

 

Logging into Outlook Web Access
To access your GotUC email account navigate to:
https://exchange.gotuc.net/owa

owastep1

Logon to Exchange using the info you received in your welcome email. Once logged in you can send and receive email for testing applications. Email on this server is not backed up and should primarily be used for testing applications.

To access Exchange Web Services from Visual Studio you will need to add a service reference to:
https://exchange.gotuc.net/ews/services.wsdl
For writing applications using Exchange Web Services please read the Article
?Exchange Web Service for UC Developers? on http://www.gotuc.net

 

 

Please direct comments and questions to keith@gotuc.net

Currently rated 4.0 by 1 people

  • Currently 4/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: keith
Posted on: 5/18/2009 at 12:55 PM
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (189) | Post RSSRSS comment feed

Unified Communications Certificate Partners for Exchange 2007 and OCS 2007

Microsoft works with public X.509 certification authorities (CAs) to make sure that Microsoft Exchange Server customers can obtain the certificates that they require in order to use Microsoft Exchange Server 2007 for the Domain Security feature to enable secure client access from the Internet.
Microsoft also works with CAs in order to make sure that Microsoft Office Communications Server 2007 customers can obtain certificates that they require for Communications Server 2007 servers.

Please view the complete article here

 

Sunset

Currently rated 1.0 by 2 people

  • Currently 1/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: admin
Posted on: 7/10/2008 at 12:18 PM
Categories: Office Communications Server | Security
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (312) | Post RSSRSS comment feed