SIP-to-SIP Basic Functionality for Cisco Unified Border Element (Cisco UBE) and Cisco Unified Border Element (Enterprise) (Cisco UBE (Enterprise)) provides termination and reorigination of both signaling and media between VoIP and video networks using SIP signaling in conformance with RFC3261. The SIP-to-SIP protocol interworking capabilities support the following:
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 IP-to-IP Gateway SIP-to-SIP Basic Functionality
Cisco Unified Border Element
Cisco IOS Release 12.2(13)T3 or a later release must be installed and running on your Cisco Unified Border Element.
Cisco Unified Border Element (Enterprise)
Cisco IOS XE Release 2.5 or a later release must be installed and running on your Cisco ASR 1000 Series Router.
Restrictions for IP-to-IP Gateway SIP-to-SIP Basic Functionality
Connections are disabled by default in Cisco IOS images that support the Cisco UBE (Enterprise).
How to Configure SIP-to-SIP Connections in a Cisco Unified Border Element Enterprise
To configure SIP-to-SIP connection types, perform the steps in this section.
SUMMARY STEPS
1.enable
2.configureterminal
3.voiceservicevoip
4.allow-connectionsfrom-typetoto-type
5.exit
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Device> enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Device# configure terminal
Enters global configuration mode.
Step 3
voiceservicevoip
Example:
Device(config)# voice service voip
Enters VoIP voice-service configuration mode.
Step 4
allow-connectionsfrom-typetoto-type
Example:
Device(config-voi-serv)# allow-connections sip to sip
Allows connections between specific types of endpoints in an Cisco UBE. Arguments are as follows:
from-type--Type of connection. Valid values:
h323,
sip.
to-type--Type of connection. Valid values:
h323,
sip.
Note
H.323-to-H.323: By default, H.323-to-H.323 connections are disabled and POTS-to-any and any-to-POTS connections are enabled.
Step 5
exit
Example:
Device(config-voi-serv)# exit
Exits the current mode.
Feature Information for IP-to-IP Gateway SIP-to-SIP Basic Functionality
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.
Table 1 Feature Information for IP-to-IP Gateway: SIP-to-SIP Basic Functionality
Feature Name
Releases
Feature Information
SIP-to-SIP Basic Functionality
12.2(13)T3
12.3(7)T
This feature provides termination and reorigination of both signaling and media between VoIP and video networks using SIP signaling in conformance with RFC3261.
In Cisco IOS Release 12.2(13)T3, this feature was implemented on the Cisco Unified Border Element.
The following commands were introduced or modified:
allow-connections
SIP-to-SIP Basic Functionality
Cisco IOS XE Release 2.5
This feature provides termination and reorigination of both signaling and media between VoIP and video networks using SIP signaling in conformance with RFC3261.
In Cisco IOS Release 12.2(13)T3, this feature was implemented on the Cisco Unified Border Element (Enterprise).
The following commands were introduced or modified:
allow-connections