Page History

...

When a call arrives at SBC, the information contained in the incoming message (called number, calling number, name, etc.) is stored into variables within SBC. These variables are called Information Elements, a nomenclature lifted from ISDN definitions. So, for example, when a SIP call arrives, the number in the FROM header is stored in SBC's Calling Number IE. All arriving SIP headers or ISDN messages are similarly stored.

...

An Action Set Table contains the list of entries that are executed when that particular Action Set is called (from the ingress SG). Unlike a Call Route Table, the entries in an Action Set are not necessarily processed in sequential order. Instead, by using Action On Success, Action on Failure, or Execute If (in any combination), you can control which Action Set entries are processed.

...

...

...

Actions

...

Image Removed

Actions within Action Sets

When an Action Set Entry is executed, the associated Transformation Table is evaluated to be either TRUE or FALSE (the result of whether the Transformation Table succeeded or failed in its matching). So far, exactly the same as an entry in a Call Route Table.

...

• If the Transformation Set succeeds, the Action configured in the Action on Success is performed.
• If the Transformation Set fails, the Action configured in the Action on Failure is performed.

Processing In the Action Set Entry above, processing will Continue with the next entry (if any) if of the transformation is TRUE; , but , it will disconnect the call if the transformation is FALSE.

So, unlike Unlike the Call Routes, we can control the SBC controls what happens when a Transformation Table succeeds or fails.

...

When an Action Set is executed, the execution of individual Action Set entries is controlled by the Execute If. Whereas   Call Route entries can only be Enabled or Disabled, but the execution of Action Set entries can be controlled based on success or failure of the previous entry.

Looking at the configuration below, we can see that the first three If all Action Set entries are Always executed. You can also see that the Actions for the third entry's execute, and entries for Success and Failure are configured to Continue. Regardless , regardless of the outcome of the third entry's Transformation Table, processing will continue. The question is with which entry?

Notice that the fourth entry's Execute If is configured to Prior Success. This means that the fourth entry will run only if the third entry is successful. Alternatively, if the third entry is not successful, the fourth entry will be skipped and the fifth entry will run.

Using Execute If  in the You can see that using Execute If the order of entry execution can be controlled.

...

Much like the configuration of Call Routes, there are a number of inter-dependecies in configuring Action Sets. The diagram (below) will help guide you through the process.

...

Basic steps are below, refer to Creating and Modifying Entries to Action Set Tables for details.

1. Create a Transformation Table to be used by the Action Set.

...

1. Create a Transformation Table to be used by the Call Route.

...

1. Create a Call Route Table and add any Call Route entries required to complete the calls.

...

1.  Add any desired Actions in the Action Configuration table.

...

1.  Add an Action Set table and populate it with whatever entries are required to complete the desired IE processing.

How Action Sets Process a Call

Let's put it all together and see what The processing of an Action Set call looks like.

includes the following steps:

1. Call arrives at ingress port.
2. Ingress Signaling Group sends the call to the configured Action Set. Note that the Call Routing Table configuration is ignored when an Action Set Table is defined.
3. The first entry in the Action Set Table executes and.
4. Processes the The associated Transformation Table is processed.
5. If the Transformation Table fails, the call is disconnected per the Action on Failure configuration. If the transformation succeeds, the call is sent to the Lync Routes Call Route Table.
6. The Lync Routes Call Route Table executes and.
7. Processes the The associated translation table is processed.
8. Finally, the The call is sent to the egress Signaling Group and.
9. The call is sent to To the destination SIP Server.

...