Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

IMG 1010 - Configuring a Channel to Play Treatment

The IMG can be configured to play a list of pre-recorded treatments (announcements) to a channel group. Some of the scenarios include:

  • Error Detection - Play a treatment when a call is made into a channel group that is not in service usually because maintenance is being performed on that specific channel group.

  • Play Treatment to specific cause code - If for some reason the span within the channel group is Not In Service or the number dialed is wrong, a treatment could be configured to be played when the IMG receives a specific cause code.

  • Pre-Call Announcements - Making Pre-Call Announcements like "Thank-you for calling Company ABC please hold while your call is connected"

  • Custom Announcements - The fourth way is by playing a custom announcement the user has created to one of the three scenarios above.

The procedure is one example on how to configure the IMG 1010 to play an announcement because a span or channel has been taken Out Of Service for maintenance. (Error Detection).

 

Background Information:

The announcements that are being played are not stored on the IMG. The announcements etc are stored on the GCEMS server. The IMG gets the announcements from the GCEMS server through NFS. The IMG downloads the vif.csv file from the GCEMS server. Once the vif file has been downloaded, the IMG can grab any treatment from the GCEMS server at any time. The vif.csv file is stored in the following location:

/opt/dialogic/common/treatment/datafiles  (Software Version 10.5.1 and above)

/opt/cantata/common/treatment/datafiles  (Software Version 10.3.x > 10.5.0)

 

Below is a table of the vif file:

File:

Description

000000.vox

Zero

000001.vox

One

000002.vox

Two

000003.vox

Three

000004.vox

Four

000005.vox

Five

000006.vox

Six

000007.vox

Seven

000008.vox

Eight

000009.vox

Nine

000100.vox

We're sorry your call could not be completed as dialed

000101.vox

We're sorry the number you have dialed

000102.vox

is no longer in service

000103.vox

We're sorry all circuits are busy now

000104.vox

We're sorry you must dial a 1 before calling numbers outside your calling area

000105.vox

We're sorry it's not necessary to dial a 1 or 0 when calling this number

000106.vox

We're sorry it's not necessary to dial a 1 or 0 when calling numbers within your calling area

000107.vox

We're sorry your call did not go through

000108.vox

Please check the number and dial again

000109.vox

If you need assistance please hang up and dial the operator

000110.vox

If you need assistance

000111.vox

Please hang up and dial the operator

000112.vox

Please hang up and try your call again

000113.vox

Please hang up and try again later

 

Also located in this folder is the img_vocab.dat file. The Vocabulary Index File contains a list of all the vox files needed along with the physical location of each of the vox files and their ID's. This file needs to be imported into the IMG so the IMG can find the correct file and link it to the File ID. When adding a custom announcement the file will need to be either added to the img_vocab.dat file or a new .dat file will need to be created.

 

Follow procedures below to play a treatment for four different scenarios:

 

Playing and Adding Announcements/Treatments on the IMG

The Error Detection example below uses the following diagram. Basically the call flow is an all IP scenario where an application named SJPhone is loaded on a PC running Windows® XP. SJPhone is making an IP call through the IMG to an IP phone connected to the local network. Follow the steps below to configure the IMG to play a treatment, click on each of the links and follow the procedures within.

 

Example1: Error Detection: (Call Failure Announcements)

"All circuits are busy, please hang up and try again later" would be played if switch is overloaded with calls.

Example 2: Pre-Call Announcements (Branding)

"Thank you for using ABC Communications, please hold for next available operator." would be played once ABC Communications answers the phone.

  • Create the .VOX or .WAV file and Edit GCEMS server to accept and play new announcement

  • Creating/Modify the prompts in the Vocabulary Index File

  • Configure a Treatment Table

  • Call Branding (Pre-Announcement)

Example 3: Route to a Cause Code

"We're sorry you must dial a 1 on international calls" would be played when IMG was sent the cause code for not prefixing an international number with a 1.

Route on a Translation Table

  • In Channel Group set Type of Operation to Error Detection

  • In Channel Group set error code to one of the selections from drop down menu

Route on a Route Table

  • In Channel Group set Route Action Type to Treatment Table

  • Set Outgoing Treatment Table to one of the selections from the drop down menu

Example 4: Adding a New Treatment

In this example you will create a new announcement and load it into the GCEMS server to be used for playing treatments

  • Create the .VOX or .WAV file and Edit GCEMS server to accept and play new announcement

  • Creating/Modify the prompts in the Vocabulary Index File

  • Use method to route call and play treatment

 

Creating a Cause Code Mapping Table

Create a cause code mapping table:

 

  • Right Click on the IMG EMS object in ClientView and select New Routing Configuration

  • Right-click Routing Configuration and select New Cause Code Tables.

  • Right-click Cause Code Tables and select New Cause Code Table. The IMG 1010 - Route Table/Cause Code Table/Service Route Table pane appears.

  • Enter a Name for the table by selecting the Name field and entering a Name.

  • The ID is automatically populated with the next available table number.

  • In the Routing Criteria Order field, order the criteria as required and click OK.

Adding Entries to a Cause Code Mapping Table

Create a table entry that maps a Cause Code to a Treatment.

  • Right-click the Cause Code Table you just created and select Add Route Entry. The Route Table Entry pane appears.


     

    • Entry ID - This field is automatically populated. It can be changed by selecting a different ID from drop down menu.

    • Enable - Select from drop down menu either True or False to Enable or Disable this Cause Code Entry

    • Route Criteria Type - This field is automatically populated with Cause Code.

    • Match IMG as well - This field is a drop down menu with all IMG's configured in ClientView. Select which IMG will play the treatment from this list

    • Criteria Values - Select from drop down menu the correct cause code.

    • Route Action Type - Select from drop down menu Treatment Table

    • Outgoing Treatment Table - Select from drop down a treatment.
       

Assigning a Cause Code Table to Channel Group

  • Go to the pane for the channel group you are configuring.

  • In the Incoming Treatment field, select Play Treatment

  • In the Cause Code Mapping Table field, select the Cause Code Table you created.

  • In the Outgoing Treatment field, select Play Treatment.

  • No labels