om multiple devices can share the same resources. Interworking: Ensures that non-homogenous Unified Communications (UC) applica- tions utilize the same SP SIP trunk and connect to one another. Demarcation: An SBC can act as the edge of an enterprise network to assist in prob- lem resolution. Security: An SBC has the requirement to protect an enterprise network from attacks that come from outside of the network. These functions are not all unique to an enterprise; however, there are a few distinct fea- tures that an enterprise SBC requires that an SP SBC does not. One of these requirements for an enterprise SBC that is unique from an SP SBC is tight integration with the current enterprise UC architecture. This is an important component because most enterprises have a goal of providing a consistent user experience to their end users or customers. This is often accomplished by sharing a common UC infrastruc- ture. The integration can be in the form of common tools and management configuration methods that extend from the UC call agents to the enterprise SBC to the capability for the UC to share resources such as transcoding resources with the SBC. In the case of Cisco products, the Cisco Unified Communications Manager (CUCM) can for example, share transcoding resources, with the Cisco Unified Border Element (CUBE). And the CUBE shares a common CLI for configuration with other Cisco voice infrastructure components such as TDM gateways and conferencing bridges. In small and medium business (SMB) networks, the functionality of the enterprise SBC is often included in the call agent. For example, the Cisco Unified Communications Manager Express product, which includes call control capability for up to 350 phones, includes the software functionality of the CUBE within the same devices. This combina- tion of multiple functions is common in SMB-based solutions and is different from large scale enterprise solutions that normally have distinct SBC devices. In summary, the enterprise SBC has most of the features and requiremen