Page History

...

Stored Information Elements (IEs)

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 within Action Sets

...

• 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.

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

...

Looking at the configuration below, we can see that the first three Action Set entries are Always executed. You can also see that the Actions for the third entry's Success and Failure are configured to Continue. 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.

...

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.

1. Create a Transformation Table to be used by the Action Set
2. Create a Transformation Table to be used by the Call Route.
3. Create a Call Route Table and add any Call Route entries required to complete the calls.
4 and 5. Add any desired Actions in the Action Configuration table.
6. Add an Action Set table and populate it with whatever entries are required to complete the desired IE processing.

...

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

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 associated Transformation Table.
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 associated translation table.
8. Finally, the call is sent to the egress Signaling Group and
9. To the destination SIP Server.

...