Overview
Cisco Unified Border Element (CUBE) allows VoIP-to-VoIP connection by routing calls from one VoIP dial peer to another. VoIP interworking is achieved by connecting an inbound dial peer with an outbound dial peer.
Note |
All CUBE Enterprise deployments must have signaling and media bind statements that are specified at the dial-peer or Voice Class Tenants level. For voice call tenants, you must apply tenants to dial-peers used for CUBE call flows if these dial-peers do not have bind statements that are specified. |
Note |
H.323 protocol is no longer supported from Cisco IOS XE Bengaluru 17.6.1a onwards. Consider using SIP for multimedia applications. |
A dial peer is a static routing table, mapping phone numbers to interfaces or IP addresses.
A call leg is a logical connection between two routers or between a router and a VoIP endpoint. A dial peer is associated or matched to each call leg according to attributes that define a packet-switched network, such as the destination address.
Voice-network dial peers are matched to call legs based on configured parameters, after which an outbound dial peer is provisioned to an external component using the component's IP address. For more information, refer to the Dial Peer Configuration Guide.
Dial-peer matching is done based on the VRF ID associated with a particular interface. For more information, see Inbound Dial-Peer Matching Based on Multi-VRF.
In CUBE, dial peers are classified as LAN dial peers and WAN dial peers based on the connecting entity from which CUBE sends or receives calls.
A dial peer is used to send or receive calls between CUBE and the PBX (PBX)—a system of phone extensions within enterprise. Following are examples of inbound and outbound dial peers:
An another set of dial peer is used to send or receive calls between CUBE and the SIP trunk provider. Given below are examples of inbound and outbound dial peers.