- Cisco Unified Border Element Enterprise Fundamentals and Basic Setup
- IP-to-IP Gateway SIP-to-SIP Basic Functionality
- SIP-to-SIP Extended Feature Functionality for Session Border Controllers
- SIP Gateway Support for the bind Command
- Configuring an Inbound Dial Peer to Match the URI on SIP Calls
- Multiple Destination Pattern Support on a Voice Dial Peer
- SIP Video Calls with Flow Around Media
- Additional References
- Glossary
Configuring an Inbound Dial Peer to Match on a URI
To configure an inbound dial peer to match an URI on a remote IP Address on SIP Trunks, perform the following task.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Configuring an Inbound Dial Peer to Match on a URI
Cisco Unified Border Element
Cisco IOS Release 15.1(2)T or a later release must be installed and running on your Cisco Unified Border Element.
Cisco Unified Border Element (Enterprise)
Cisco IOS XE Release 3.6S or a later release must be installed and running on your Cisco Unified Border Element (Enterprise).
Configuring an Inbound Dial-Peer to Match the URI on SIP Calls
This task describes how to configure an inbound dial-peer to match the URI in a SIP call.
DETAILED STEPS
Feature Information for Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Name | Releases | Feature Information |
---|---|---|
Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks |
15.1(2)T |
The Support Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks feature supports the expansion of inbound dial-peer matching logic to include matching based on the source IP address of inbound signaling on a SIP trunk. This feature enables enforcement of specific call-treatment, security, and routing policies on each SIP trunk. In Cisco IOS Release 15.1(2)T this feature was implemented on the Cisco Unified Border Element. The following commands were introduced or modified: dial-peer voice, voice-class uri. |
SIP and TEL URL support |
Cisco IOS XE Release 3.6S |
The Support Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks feature supports the expansion of inbound dial-peer matching logic to include matching based on the source IP address of inbound signaling on a SIP trunk. This feature enables enforcement of specific call-treatment, security, and routing policies on each SIP trunk. In Cisco IOS Release 15.1(2)T this feature was implemented on the Cisco Unified Border Element (Enterprise). The following commands were introduced or modified: dial-peer voice, voice-class uri. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.