Unified Communications Policies

Last Updated : Jan 11, 2019 |

With Unified Communication Policies, enterprise UC administrators can govern Unified Communications through the enforcement of business rules. Rules can be based on user identity, domain affiliation, network identity, time of day, and time of week.

UC Policies have two high-level concepts, flows and Domain Policies. When Avaya SBC receives a packet , the content of the packet, such as IP addresses and URIs, determines the flow that the packet matches. After the flow is determined, the flow points to a policy that contains several rules concerning processing, privileges, authentication, and routing. After Avaya SBC applies routing and determines the destination endpoint , it applies the policies for this destination endpoint . The context is applied to future packets in the same flow.

Flows

The packet field values that are configured in flows are matched to categorize a packet so that the appropriate policy can be applied. The flows match starting with the highest order, lowest numeric value. The most particular flows are used at the top, while those lower in the order can be more general.

Endpoint Flows

Endpoint Flows are used to determine signaling endpoints to apply the appropriate endpoint policy.

The types of endpoint flows are:

  • Subscriber Flows: Identify SIP phones and users.

  • Server Flows: Identify SIP servers

Domain Policies

  • End Point Policy Groups: An ordered list of policy sets. The policy set with the highest order, lowest numeric value, is applied if Time of Day (ToD) matches what?. Smaller time windows are used at the top with larger time windows further down the order.

  • Policy Set: A set of application, border, media, security, signaling, vcharging, and ToD rules.

  • Rules: The processing method, privileges, and authentication method of packets.

  • Session Policies: The set of policies for the media sessions. For example, which codec is to be applied to the media session between the source and destination.

The following is an example of matching flows and policies for securing a SIP Trunk and SIP Phones with Avaya SBC:



UC policy process