cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Adding Night Mode Functionality in UC With Existing Auto Attendant

Adding Night Mode Functionality in UC With Existing Auto Attendant

The purpose of this document is to illustrate how to add night mode functionality to an existing auto attendant in UC server. This functionality allows a user to toggle night mode on or off manually. Depending on the current state of the system mode, the auto attendant can direct the caller to a different announcement or menu.

This document operates under the assumption that an auto attendant is already in place on the UC server. This auto attendant must be an identity with a service attached to it. The night mode illustrated in this document does not affect individual users. This document was created using UC 5.0 as an example. It will work with earlier versions, but some menus and options may differ.

Creating Night Mode Database

In order to store the current night mode state, a local data store must be created on the server. From the administration tab of the UC client, go to “Data Sources”, then right click and select “New”, “User Data”

01.jpg


Fill in a name, description, and instructions for the database. Be sure to name the database “Night Mode”. The description and instructions are purely descriptive and have no impact on the functionality of the database.

02.jpg

Click the “New” button in the “Database Fields” section. Set the name to “NightMode”, the data type to “Number”, the default value to “0”, and the display width to “1”. Click OK

03.jpg

Back at the “Data Sources” window, right click on the newly created database and select “Edit”

04.jpg

Click “Add”. A field should automatically populate with a value of “0”. Click “Close”

05.jpg

Creating Night Mode Selector Service

Navigate to “Services” and create a new service. Name this service “Night Mode Selector”

06.jpg

Open the service. In the service editor, add a “Fetch Data” element. Click the arrow pointing right and select “Night mode” as your data source.

07.jpg


Connect a “Compare Data” element to the “One Row Fetched” pin of the previously created element. For the “Compare To” value, select the “NightMode” value. You can optionally record a “Play Announcement” element to announce when an error has occurred. Connect this to the “Many Rows Fetched”, “No Rows Fetched”, and “Otherwise” pins of the element you created in the previous step.

08.jpg


Click the “Add” button to add a field. Set one of the fields to “0” and the other to “1”

09.jpg

Attach an “Update Data” element to the pins corresponding to “0” and “1”. Name the elements connected to 0 “Change to On” and the element connected to 1 “Change to Off”. Select “Night Mode” as the data source for each element.

10.jpg


For each “Update Data” element, click “Add”. Select “NightMode” as the field. In the “Change To On” element, set the new value to “1”. In the “Change To Off” element, set the new value as “0”.

11.jpg

Attach a “Play Announcement” element to each of the “Update Data” elements. Record announcements stating that night mode is off or on.

12.jpg


The service is now complete. The final service should look like this:

13.jpg

Creating Night Mode Selector Identity

From the Identities section, right click and select “New Identity”

14.jpg


Click “Next”. Select the ECS Communication System, select “Admin” as the user profile, and check the radio button for “Attendant service”. Click Next.

15.jpg


Name the identity “Night Mode Selector”. For the address, assign the extension you wish to call in order to toggle night mode on or off. It can be any unused extension. Select the previously created “Night Mode Selector” as the service. Click “Next”, then click “Finish”.

16.jpg

Testing Night Mode Service

Before modifying your primary auto attendant, test to confirm that the service works properly. From the “Data Sources” menu, right click on the Night Mode database and click “Edit”.

17.jpg

Dial the extension you assigned to the Night Mode Selector identity. When the service completes and hangs up, the entry in the database should change to “1”. Dialing the service again should change the entry back to “0”.

18.jpg


Adding Night Mode to Existing Auto Attendant

Open the existing auto attendant in the service editor. The example below shows a sample AA. When a customer dials, they will receive a menu that allows them to dial by name, listen to a message, or be transferred to the operator. Once these steps are completed, the example will use this existing service during the day and send a user straight to voicemail when Night Mode is enabled.

19.jpg


Drag a “Fetch Data” element into the existing service. Select “Night Mode” as the data source

20.jpg

Connect a “Compare Data” element to the “One Row Fetched” pin.  Select “NightMode” as the value to compare to.

21.jpg

Use the “Add” button to add an additional row. Fill in “0” for the first pin and “1” for the second.

  22.jpg

Drag the pin connected to “0” to the top left corner of the element that previously begun the auto attendant. This will connect the “Compare Data” element and move it ahead of the existing service elements.

23.jpg

Connect the alternate service to the “1” pin on the “Compare Data” element. The actions connected to this pin will be followed when Night Mode is enabled.

24.jpg


Save the service and exit. Night Mode has now been implemented. When the Night Mode Selector identity is called, it will change the behavior of the auto attendant.

A speed dial can be created on a phone in order to toggle Night Mode with one button.

Other options for implementing similar behavior are possible. Optional ADTRAN ProServices are available to help with more customized implementations.

Version history
Revision #:
1 of 1
Last update:
‎01-09-2014 12:55 PM
Updated by:
 
Contributors