About the Application#

This application is triggered by an incoming phone call. When triggered, the application answers the call and plays a prompt back using various mechanisms (Text-to-Speech and pre-recorded WAV files). Once the prompt has completed the application will then hang up the call.

Creating the Application Project#

1. Open a Command Prompt window.

2. Navigate to the directory you want to use as your workspace. To use the CUAE command-line tool to create a new application, type the cuae create command and the name of the application project.

c:> cd \workspace

c:\workspace> cuae create AnswerAndPlay }}}

The tool then prompts you for additional information.

Note: Once you are more familiar with the options, you can type the full command rather than answering the prompts. For example://

cuae create -l language -m module -t string [options] projectname

cuae create -l csharp -m MakeCall -t app AnswerAndPlay

3. First the tool prompts you to choose between building an application or a plugin. In this example, the correct choice is application:

Project Type? [application or plugin] application

4. Next the tool prompts you to specify the programming language. In this example, the correct choice is csharp:

Programming language? [java or csharp] csharp

5. The tool asks you for the namespace for the application. A Java program might want to use a fully qualified namespace like com.company.answerandplay or something simple like answerandplay. The tool offers you a simple namespace based on the project name. Let's accept the tool's suggestion for now and use answerandplay:

Project namespace? [default: answerandplay] <Return>

6. Finally, the tool asks if you would like to specify a triggering event. All applications need to register against at least one triggering event. You can specify the triggering event now or wait and specify the triggering event later. You can also change the triggering event during development. Again, since we know that this application needs to be triggered on an incoming call, let's go ahead and specify the triggering event now. Select option 4:

 Available application triggering event:

0: Skip this step 1: cisco.uc.cuae.legacy.JTapi.JTapiIncomingCall 2: cisco.uc.cuae.legacy.JTapi.JTapiCallInitiated 3: cisco.uc.cuae.legacy.JTapi.JTapiCallEstablished 4: cisco.uc.cuae.legacy.CallControl.IncomingCall 5: cisco.uc.cuae.legacy.Http.GotRequest 6: cisco.uc.cuae.legacy.Presence.SubscriptionTerminated 7: cisco.uc.cuae.legacy.Presence.Notify 8: cisco.uc.cuae.legacy.TimerFacility.TimerFire Triggering event? [0-8] 4}}}

The tool now has enough information to generate the project template.

Generating:

• application named "AnswerAndPlay"
• with namespace "answerandplay"
• with laguage "csharp"
• with trigger event "cisco.uc.cuae.legacy.CallControl.IncomingCall"
• in location C:\workspace\

Created project "AnswerAndPlay" in directory "C:\workspace\AnswerAndPlay\"}}}

Here is the whole sequence again with all of the steps together:

wxp> cuae create AnswerAndPlay

Project type? [application or plugin] application Programming language? [java or csharp] csharp Project namespace? [default: answerandplay] Available application triggering event: 0: Skip this step 1: cisco.uc.cuae.legacy.JTapi.JTapiIncomingCall 2: cisco.uc.cuae.legacy.JTapi.JTapiCallInitiated 3: cisco.uc.cuae.legacy.JTapi.JTapiCallEstablished 4: cisco.uc.cuae.legacy.CallControl.IncomingCall 5: cisco.uc.cuae.legacy.Http.GotRequest 6: cisco.uc.cuae.legacy.Presence.SubscriptionTerminated 7: cisco.uc.cuae.legacy.Presence.Notify 8: cisco.uc.cuae.legacy.TimerFacility.TimerFire Triggering event? [0-8] 4 Generating:

• application named "AnswerAndPlay"
• with namespace "answerandplay"
• with laguage "csharp"
• with trigger event "cisco.uc.cuae.legacy.CallControl.IncomingCall"
• in location C:\workspace\

Created project "AnswerAndPlay" in directory "C:\workspace\AnswerAndPlay\"}}}

Inspecting the Generated Project#

Let's inspect the files that were generated by the CUAE command-line tool. It created an AnswerAndPlay directory in the directory from which you ran the cuae create command. The AnswerAndPlay directory contains the following files and directories:

• AnswerAndPlay.etch
• AnswerAndPlay.properties
• AnswerAndPlay.csproj
• cuae-resources/
• README.txt
• src/

The most important of which, for your purposes, are:

• AnswerAndPlay.etch -- CUAE application Etch service definition. Edit this file to use additional CUAE services in your project.
• AnswerAndPlay.csproj -- C# project file.
• cuae-resources/ -- CUAE application resource directory.
• src/ -- Generated application source files.

Declaring Services#

The first step in building an Etch-based application is identifying which Cisco Unified Application Environment hosted services the application requires and then editing the .etch file to declare the names of those services into the application.

Tips: Once you identify the services you need, you can familiarize yourself with them by visiting the API reference for the version of the Unified Application Environment you are using.

The following snippet is the default content of the .etch file that the CUAE command-line tool generates. We use the mixin command to declare the appropriate services.

// CUAE Application Etch Service Definition

This service defines your application and the CUAE services that you use in your application.

The service module namespace, this will be translated to the namespace of the generated source code. module AnswerAndPlay

The name of your service.service AnswerAndPlay{ By default, you must always use the EtchBridge service. Do not remove this mixin, otherwise your application won't work.mixin cisco.uc.cuae.EtchBridge

You may add any additional service mixins that you require. For example, if you'd like to make and receive phone calls, add the following line: mixin cisco.uc.cuae.legacy.CallControl mixin cisco.uc.cuae.legacy.CallControl } }}}

Because this application will answer an incoming phone call and play a media stream back to the caller, we need to utilize the CallControl and MediaControl services. The default etch file already has a mixin for Call Control because of the triggering event you selected when creating the application project.

  mixin cisco.uc.cuae.legacy.CallControl

We need to add a declaration for the MediaControl service, using the full namespace. Add the following line right after the mixin for CallControl but before the final "}":

  mixin cisco.uc.cuae.legacy.MediaControl

The new AnswerAndPlay.etch file should look like this:

// CUAE Application Etch Service Definition

This service defines your application and the CUAE services that you use in your application.

The service module namespace, this will be translated to the namespace of the generated source code. module AnswerAndPlay

The name of your service.service AnswerAndPlay{ By default, you must always use the EtchBridge service. Do not remove this mixin, otherwise your application won't work.mixin cisco.uc.cuae.EtchBridge

You may add any additional service mixins that you require. For example, if you'd like to make and receive phone calls, add the following line: mixin cisco.uc.cuae.legacy.CallControl mixin cisco.uc.cuae.legacy.CallControl mixin cisco.uc.cuae.legacy.MediaControl } }}}

Building the Application#

After declaring the services you need, you must build the application to generate source files.

1. Open a Command Prompt and navigate to the application directory.

2. Run the msbuild command to generate source files.

c:\workspace> cd AnswerAndPlay

c:\workspace\AnswerAndPlay> msbuild}}}

The following source file templates are then created in the directory src\answerandplay:

• MainHttpMakeCallClient.cs
• ImplHttpMakeCallClient.cs

Creating Configuration Items#

YAML is the file format for Unified Application Environment application configuration (config.yaml) and metadata definitions project_name.yaml).

All application configuration items are written in the config.yaml file, which is located in the cuae-resources directory.

Configuration items follow a specific syntax, as follows.

-name:

[display name:] format: [description:] [minvalue:] [maxvalue:] [defaultvalue:] [readonly:] [required]}}}

• Items in square brackets [] are optional

The default config.yaml file contains the following information:

# CUAE Application Configuration Definition

2. You only need to edit this file if you want to expose configuration to
3. the administrator through cuaeadmin.
5. This file was auto-generated from a template but will never be
6. overwritten. You should edit this file directly if required.

configuration:

1. Indicates the name of your configuration item. It will be how you
2. reference this configuration item from code.
3. - name: myConfValue

1. Controls how the visible label of the configuration value. For
2. example, if 'name' was defined as: myConfValue, you may choose to
3. define 'displayName' as: My Config Value. Think of it as a friendly
4. name. This field is optional.
5. displayName: My Config Value

1. Defines the format of the configuration item's value. This will
2. control how cuaeadmin renders and validates the value. Possible
3. values for the 'format' field are: String, Bool, Number, IP_Address,
4. Array, HashTable, Password.
5. format: String

1. A description of the configuration item that will be displayed to
2. the administrator in cuadmin. This field is optional.
3. description: Some description here.

1. For configuration items that are formatted as numbers, the
2. 'minValue' and 'maxValue' configuration items define the acceptable
3. range of input for the item. These fields are optional.
4. minValue:
5. maxValue:

1. Defines the default value of the configuration. This field is
2. optional.
3. defaultValue:

1. Inidicates whether the configuration item is editable. If
2. 'readOnly' is set to true, the administrator will not be able to
3. edit it in cuaeadmin, but will be able to view it. The default is
4. false, and this field is optional.
5. readOnly:

1. Indicates whether the configuration item is required. If required,
2. the administrator will have to set a value before the application
3. will run. The default is false, and this field is optional.
4. required: false }}}

In this example, the application has one configuration item, the content of the rendering text. Add the following block to the config.yaml file in the configuration section:

Code Sample#

- name: TTSMessage

format: String displayName: TTSMessage defaultValue: Hello, welcome to answer and play demo application}}}

Writing the Application Code#

This section provides instructions and code samples for writing the application logic.

Importing the Project into Your IDE#

1. Open Visual Studio (or another IDE of your preference).

2. Create a new CSharp project from the existing project file by choosing File -> Open -> Project/Solution.

3. Browse to the AnswerAndPlay directory and choose AnswerAndPlay.csproj.

Reading Application Configurations#

The CUAE application receives the current application configurations from CUAE server using method server.getConfig("partition name") in incomingcall event handler in the ImplAnswerAndPlayClient.cs file. The developer can iterate through the configurations array and parse the configuration item based on its type.

Handling the incomingCall Triggering Event#

You should write a method to handle the event of the incoming call trigger to answer the call and begin playing the message.

You will need to add the following declaration to ImplAnswerAndPlayClient.cs in order to use CuaeResult:

using cisco.uc.cuae.legacy.types.CuaeCommon;

Code Sample#

// Handle incoming call

String sTTSMessage = "";

public override void incomingCall(String sessionId, IncomingCallOptions options) { PlayResult pResult = null; AnswerCallResult acr = server.answerCall(sessionId, options.callId, null, null); ConfigEntry[] config = null;

try { config = server.getConfig("Default");

Display configs to consoleif(config.Length > 0){for(int i = 0; i < config.Length; i++){if(config[i].name.Equals("TTSMessage")){sTTSMessage = Convert.ToString(config[i].configValue);Console.WriteLine("TTSMessage: " + sTTSMessage);}}}}catch(BridgeException e){Console.WriteLine(e);server.removeCuaeSession(sessionId);return;}

try { pResult = server.beginPlay(sessionId, sTTSMessage, acr.connectionId, null, null, acr.callId); } catch(Exception e) { Console.WriteLine(e); server.removeCuaeSession(sessionId); return; } if(pResult.returnValue != CuaeResult.SUCCESS) { Console.WriteLine("beginPlay failed"); server.hangup(sessionId, acr.callId, null); server.removeCuaeSession(sessionId); } } }}}

Completing the onPlayComplete Function#

When using the "Play" action (above), you should follow-up with the "onPlayComplete" function:

Code Sample#

// Handle play complete
        public override void onPlayComplete(String sessionId, PlayResult results, Object state)
        {
            Console.WriteLine("Play completed..");
            String callId = (String) state;

            Console.WriteLine("\nLocal Hangup..");
            if(server.hangup(sessionId, callId, null).returnValue != CuaeResult.SUCCESS)
                Console.WriteLine("Hangup failed");

            Console.WriteLine("\nEndScript");
            server.removeCuaeSession(sessionId);
        }

Handle startTx event#

Event occurs to indicate the transmit audio channel has been established.

public override void startTx(String sessionId, StartTxOptions options)

{ } }}}

Handle startRx event#

The application server has established the receive audio channel and communicated the Rx info to the remote endpoint on the underlying call control protocol

public override void startRx(String sessionId, StartRxOptions options)

{ } }}}

Handle stopTx Event#

Indicates that the transmit audio channel has been closed.

public override void stopTx(String sessionId, StopTxOptions options)

{ } }}}

Handle remoteHangup Event#

Indicates that call has been terminated by the remote endpoint.

public override void remoteHangup(String sessionId,RemoteHangupOptions options)

{ } }}}

Registering the Application#

The previous steps completed the core logic of the example applications, but before any Etch-based API calls can actually be made, we must register the application with the Cisco Unified Application Server. To register your application, follow these steps: 1. Open the MainAnswerAndPlayClient file in the /src directory. It contains the following content by default:

// Generated by:

0.95.0 (ETCH-TRUNK-840) / java 0.95.0 (ETCH-TRUNK-840) Sun Jun 08 22:47:33 CDT 2008

package answerandplay;

/ Main program for AnswerAndPlayClient. This program makes a connection to the listener created by MainAnswerAndPlayListener./public class MainAnswerAndPlayClient implements AnswerAndPlayHelper.AnswerAndPlayClientFactory

{ / Main program for AnswerAndPlayClient.

• @param args command line arguments.
• @throws Exception
• /

public static void main( String[] args ) throws Exception { TODO Change to correct URIstring uri = "tcp://localhost:4001";RemoteAnswerAndPlayServer server = AnswerAndPlayHelper.newServer( uri, null,new MainAnswerAndPlayClient() );

Connect to the serviceserver._startAndWaitUp( 4000 );

TODO Insert Your Code Here

Disconnect from the serviceserver._stopAndWaitDown( 4000 );}

public AnswerAndPlayClient newAnswerAndPlayClient( RemoteAnswerAndPlayServer server ) throws Exception { return new ImplAnswerAndPlayClient( server ); } } }}}

2. To make a connection to the listener, add a server.registerApplication() request.

// TODO Insert Your Code Here

String key = server.registerApplication("AnswerAndPlay", "Default", "<username>", "<password>"); Console.WriteLine("AnswerAndPlay application registered with key: " + key);

Console.WriteLine("Hit any key to exit."); Console.ReadLine(); }}}

3. Modify the String URI to match the IP address and port of the Cisco Unified Application Server.

URI settings vary slightly between 2.5(1) Beta 1 and more recent versions of 2.5(1), as follows:

2.5(1) and 2.5(1) Beta 2, Beta 3, Beta 4 and later releases#

// TODO Change to correct URI

String uri = "tls://appserver_ipaddress:9000?TlsConnection.authReqd=false&filter=KeepAlive &KeepAlive.Count=5&Packetizer.maxPktSize=102400&TcpTransport.reconnectDelay=4000"; }}}

In Beta 2, the Etch Bridge was updated to use Transport Layer Security for encryption by default. For your applications to work, you must specify TLS as the protocol in the URI and set the authReqd parameter to false. In the example above, the KeepAlive filter and Max Packet Size and Reconnect Delayparameters have also been set.

2.5(1) Beta 1#

// TODO Change to correct URI

String uri = "tcp://appserver_ipaddress:9000?&TcpConnection.reconnect_delay=4000"; }}}

Note: In addition to setting the correct IP address and port for the Cisco Unfied Application Server, the Reconnect Delay parameter should be set on all connection URIs.

Packaging the Test Application#

1. Execute a successful build request for your test application within your IDE.

2. To package the JAVA application, execute the "cuae package" command from a DOS command shell in the parent directory of the test application.

C:\workspace\AnswerAndPlay>cuae package

Created package file "C:\workspace\AnswerAndPlay\bin\AnswerAndPlay.mca"}}}

The following files will be added to the "\bin" sub-directory:

• AnswerAndPlay.mca (application bundle to be uploaded into the CUAE server)
• INSTALLER.xml - (contains the config items in config.yaml)
• MANIFEST.xml - (bundle details for the package comamnd)

Installing the Test Application#

To install the test application on a CUAE server, execute the cuae install command from a DOS command shell in test application parent directory of the test application. The cuae install command varies slightly between 2.5(1) Beta 1 and Beta 2.

2.5(1) Beta 2#

You are prompted to enter an IP address, username, and password (to view the help, run the cuae install -h command). When prompted, enter Y or N to save management settings. This will save the answers to the above three questions in the properties file and remember them the next time you go to install.

Note: You are also prompted for the communications protocol (TCP or TLS). Select the protocol that is set on the Management Service. TLS is the default supported protocol. If you want to use TCP, follow the instructions in Management Service Transport Layer Security (TLS) to change the default URI of the Management Service before running these commands.

C:\workspace\AnswerAndPlay>cuae package

Created package file "C:\workspace\AnswerAndPlay\bin\AnswerAndPlay.mca"

C:\workspace\AnswerAndPlay>cuae install Enter the hostname or IP address of the management service (for example: localhost, 1.1.1.1): localhost Protocol: tls Generated mgmt-service uri: tls://localhost:9001?TlsConnection.authReqd=false Enter management service login username: Entermanagement service login password: Save the amanagement settings with the project? [yes or no] no Application : C:\workspace\AnswerAndPlay\bin\AnswerAndPlay.mca Uploading : ===========================> 100% Application has been installed successfully}}}

2.5(1) Beta 1#

You are prompted to enter an IP address, username, and password (to view the help, run the cuae install -h command). When prompted, enter Y or N to save management settings. This will save the answers to the above three questions in the properties file and remember them the next time you go to install.

C:\workspace\AnswerAndPlay>cuae package

Created package file "C:\workspace\AnswerAndPlay\bin\AnswerAndPlay.mca"

C:\workspace\AnswerAndPlay>cuae install Enter management service uri or host/IP <for example: localhost, tcp://1.1.1.1.:4001>: Enter management service login username: Entermanagement service login password: Save the amanagement settings with the project? [YyNn] n Application : C:\workspace\AnswerAndPlay\bin\AnswerAndPlay.mca Uploading : ===========================> 100% Application ahas been installed successfully}}}

Configuring the Application in the Administration Interface

Adding a Trigger#

1. Log in to the Administration interface.

2. Click Applications -> Find/List Triggers to generate a list of applications and their associated triggers.

3. Select the application AnswerAndPlay in the list.

4. Enter "to" and the number that will be used to trigger the application.

5. Click Add Parameter.

Running the Application#

1. Run the class AnswerAndPlay.MainAnswerAndPlayClient to register the application.

At this point the application will remain registered and running until either you stop your application or the application loses connectivity to the Unified Application server.

2. Run the program by dialing the number you specified as the trigger.