Table Of Contents
Implementing SBC Adjacencies
Contents
Prerequisites for Implementing Adjacencies
Information About Implementing Adjacencies
Properties Common to Both SIP and H.323 Adjacencies
About SIP Adjacencies in the Deployment
About H.323 Adjacencies in the Deployment
How Adjacencies Affect Media Routing
How to Implement Adjacencies
Configuring an H.323 Adjacency
Assigning H.323 Adjacencies to Adjacency Groups
Configuring a SIP Adjacency
Assigning SIP Adjacencies to Adjacency Groups
Configuration Examples for Implementing Adjacencies
Configuring an H.323 Adjacency: Examples
H.323 Adjacency Example 1 (Two Gateways/Endpoints)
H.323 Adjacency Example 2 (Gatekeeper in Network)
Configuring a SIP Adjacency: Example
Where to Go Next
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Related Command Summary
Implementing SBC Adjacencies
Accounts and adjacencies are the key objects used to control signaling. An account represents a service relationship with a remote organization on the signaling border element (SBE), with which the SBC will interact. Within each account, the user defines one or more signaling adjacencies, which connect the SBC to devices within that organization. The account is used to:
•
Define customer-specific admission control
•Define routing policy configurations
•Organize billing records
An adjacency represents a signaling relationship with a remote call agent. There is one adjacency defined per external call agent. The adjacency is used to define protocol-specific parameters as well as admission control and routing policy. Each adjacency belongs within an account.
Each incoming call is matched to an adjacency, and each outgoing call is routed out over a second adjacency. Adjacencies can also be associated with a media gateway location, so that the most appropriate virtual data border element (VDBE) can be selected for a given call leg. Typically, an SBC has at least one account representing the internal network.
You can assign each adjacency to an adjacency group, so you can enable and disable features per interface. For example, you can turn off high bandwidth features on all adjacencies to customers on a known low-bandwidth link.
Note For a complete description of commands used in this chapter, refer to the Cisco IOS XR Session Border Controller Command Reference. To locate documentation for other commands that appear in this chapter, use the command reference master index, or search online.
Feature History for Implementing SBC Adjacencies
Release
|
Modification
|
Release 3.3.0
|
This feature was introduced on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.4.1
|
On the Cisco XR 12000 Series Router the following features were added:
•Adjacency Groups
•Media Bypass occurring between different adjacencies
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Contents
•Prerequisites for Implementing Adjacencies
•Information About Implementing Adjacencies
•How to Implement Adjacencies
•Configuration Examples for Implementing Adjacencies
•Where to Go Next
•Additional References
•Related Command Summary
Prerequisites for Implementing Adjacencies
The following prerequisites are required to implement adjacencies:
•You must be in a user group associated with a task group that includes the proper task IDs for SBC commands being used. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
•You must install and activate the package installation envelope (PIE) for the SBC software.
For detailed information about PIE installation, refer to the Upgrading and Managing Cisco IOS XR Software module in the Cisco IOS XR Getting Started Guide.
•Before creating an adjacency, the SBC must already be created. See the procedures described in the "SBC Configuration Prerequisites" module.
Information About Implementing Adjacencies
Adjacencies are used to enable call signaling between the SBE and other VoIP devices. The SBC supports adjacencies in both Session Initiation Protocol (SIP) and H.323 network deployments.
•In a SIP network, the devices might be user agents, proxies, softswitches, or back-to-back user agents (B2BUAs). When you configure a SIP adjacency, the SBE functions as a B2BUA within the SIP network.
•In an H.323 network, the devices might be terminals, gateways, or gatekeepers. When you configure an H.323 adjacency, the SBC functions as a gateway within the H.323 network.
Adjacencies can represent both trunking and subscriber signaling relationships. The network topology and configuration of an adjacency determine its role.
For further information about implementing adjacencies, see the following sections:
•Properties Common to Both SIP and H.323 Adjacencies
•About SIP Adjacencies in the Deployment
•About H.323 Adjacencies in the Deployment
•How Adjacencies Affect Media Routing
Properties Common to Both SIP and H.323 Adjacencies
The following properties are common to both SIP and H.323 adjacencies:
•Adjacencies are known by name. The name makes it easy for an SBC policy to reference the adjacency.
•An adjacency has a local address and port for incoming call setup. The IP address must be an address that falls within the address range of the Service Virtual Interface (SVI) for the service card on which the SBC resides.
•An adjacency has a peer address and port. This is the point of contact for outgoing calls. In the SIP case, this is only true if the "force-signaling-peer" option is set for that adjacency.
•An adjacency forms the output of a routing policy decision. In other words, the routing phase for a call results in selection of an outgoing adjacency for that call. Normally, adjacency selection is done based on a destination telephone number prefix. However, two adjacencies can also be bridged together by using a source adjacency as a routing input.
About SIP Adjacencies in the Deployment
Figure 2 shows a simple SIP network where:
•SIP subscribers register with the SIP proxy, which acts as a single point of contact for all of them.
•The softswitch is a gateway between the SIP network and the PSTN network.
•The softswitch routing policy assigns a particular phone prefix to each SIP proxy, allowing calls from the PSTN network to be routed through the proxy to a given subscriber. (In other deployments, subscribers may register directly with a softswitch without going through a proxy first.)
Figure 2 SIP Network
Figure 3 shows placement of an SBC in two possible positions within the SIP network, with the adjacencies noted. Each adjacency enables call setup to one or more neighboring devices, as follows:
•ADJ_SIP1A allows call setup between SBC1 and the softswitch.
•ADJ_SIP1B allows call setup between SBC1 and the proxy.
•ADJ_SIP2A allows call setup between SBC2 and the proxy.
•ADJ_SIP_SUBSCRIBERS allows call setup between SBC2 and the subscribers.
In the case of SBC2, SIP registrations are being routed through the SBC. Registrations received on ADJ_SIP_SUBSCRIBERS are being routed to the proxy over ADJ_SIP2A.
The key difference between subscriber and non-subscriber adjacencies is that:
•Nonsubscriber adjacencies have a configured single point of contact, the peer address for the adjacency.
•Subscriber adjacencies do not have a single point of contact and are instead configured to accept registrations.
SIP registrations require a routing policy to determine which is the correct outgoing adjacency for a given registration. This works in a very similar way to a call routing policy. See the procedures described in the "Implementing SBC Policies" module.
Figure 3 Adjacencies in a SIP Network Deployment
About H.323 Adjacencies in the Deployment
Figure 4 shows a simple H.323 network where:
•H.323 terminals and gateway both register with the gatekeeper.
•Prior to placing a call, an endpoint resolves the destination address with the gatekeeper.
•Call signaling flows directly between endpoints (whether terminals or gateway).
Figure 4 H.323 Network
Figure 5 shows a possible deployment of an SBC in the network, with two adjacencies noted. Each adjacency allows call setup to one or more neighboring devices.
•ADJ_H3231A allows call setup between the SBC and the gateway.
•ADJ_H3231B allows call setup between the SBC and the terminals.
An H.323 adjacency may or may not be registered with a gatekeeper. In Figure 5, ADJ_H3231B is registered with a gatekeeper and ADJ_H3231A is not.
•Gatekeeper adjacencies can set up calls to multiple endpoints. Their peer address is set to the address of the gatekeeper.
•Non-gatekeeper adjacencies can set up calls to a single remote endpoint. Their peer address is set to that of the endpoint (for example, a gateway).
Figure 5 Adjacencies in an H.323 Network Deployment
How Adjacencies Affect Media Routing
For a distributed SBC deployment, each adjacency is configured with a media location. The media location is an ID used to select the DBEs suitable for relaying media traffic for calls set up over the adjacency.
If a call is routed out over the same or different adjacency, the media may bypass a DBE. The media bypass feature allows the media packets to bypass the SBC to enable the endpoints to communicate directly to each other. Media packets flow directly without going through the DBE component of the SBC after the call signaling is done. Signaling packets still flow through the SBC as usual.
The configuration is set per adjacency, and allows media bypass across different adjacencies. Media-bypass configuration is enabled under adjacency configuration. Media bypass is useful when two endpoints are on the same subnet, but the DBE is located elsewhere on the network.
Figure 6 and Figure 7 illustrate how adjacency configuration controls media routing. In this example:
•Adjacency A connects to Peer1
•Adjacency B connects to Peer2a and 2b
•Adjacency C connects to Peer3
Adjacencies A and B are configured with media location 1. In other words, calls routed over them will use the same DBE (or set of DBEs) for media. Adjacency C is configured with media location 2.
Figure 6 How Adjacency Configuration Controls Media Routing
Now consider three calls: Peer1-Peer3, Peer1-Peer2a, and Peer2a-Peer2b. The media for these calls is routed as shown in Figure 7.
•The first call traverses two adjacencies with different media locations. Its media is relayed through two DBEs.
•The second call traverses two adjacencies with the same media location. Its media is relayed through a single DBE.
•The third call traverses a single adjacency with media by pass enabled. Its media is sent directly between the two peers without involving a DBE.
Figure 7 Media Routing for Three Calls: Peer1-Peer3, Peer1-Peer2a, and Peer2a-Peer2b
How to Implement Adjacencies
Adjacencies are the key objects used to control signaling. The user defines one or more signaling adjacencies, which connect the SBC to devices within that organization. Each incoming call is matched to an adjacency, and each outgoing call is routed out over an adjacency. The adjacencies are then attached to the appropriate account. Adjacencies can be associated with a media gateway DBE location, so that the most appropriate DBE can be selected to route media for a given call leg.
Note If two or more adjacencies have identical vrf, signaling-address and signaling-port, they must have the same security configuration. Otherwise, the security trusted encrypted configuration fails to commit.
The following sections describe implementing an H.323 adjacency and a SIP adjacency, depending on your implementation requirements:
•Configuring an H.323 Adjacency
•Configuring a SIP Adjacency
Configuring an H.323 Adjacency
This task configures an H.323 adjacency.
SUMMARY STEPS
1. configure
2. sbc service-name
3. sbe
4. adjacency h323 adjacency-name
5. signaling-address ipv4 ipv4_IP_address
6. signaling-port port_num
7. signaling-peer [gk] peer_address
8. signaling-peer-port port_num
9. remote-address ipv4 ipv4_IP_address/prefix
10. account account_name
11. commit
12. attach
13. commit
14. exit
15. adjacency h323 adjacency-name
16. signaling-address ipv4 ipv4_IP_address
17. signaling-port port_num
18. signaling-peer [gk] peer_address
19. signaling-peer-port port_num
20. remote-address ipv4 ipv4_IP_address/prefix
21. account account_name
22. show
23. commit
24. attach
25. commit
26. exit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/0/CPU0:router# configure
|
Enables global configuration mode.
|
Step 2
|
sbc service-name
Example:
RP/0/0/CPU0:router(config)# sbc umsbc-node10
|
Enters the mode of an SBC service.
Use the service-name argument to define the name of the service.
|
Step 3
|
sbe
Example:
RP/0/0/CPU0:router(config-sbc)# sbe
|
Enters the mode of an SBE entity within an SBC service.
|
Step 4
|
adjacency h323 adjacency-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# adjacency
h323 2651XM-5
|
Enters the mode of an SBE H.323 adjacency.
Use the adjacency-name argument to define the name of the H.323 adjacency.
|
Step 5
|
signaling-address ipv4 ipv4_IP_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-address ipv4 88.88.137.10
|
Specifies the local IPv4 signaling address of the H.323 adjacency.
|
Step 6
|
signaling-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-port 5000
|
Specifies the local signaling port of the H.323 adjacency.
|
Step 7
|
signaling-peer [gk] peer_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-peer 200.200.200.41
|
Specifies the remote signaling peer for the H.323 adjacency to use.
|
Step 8
|
signaling-peer-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-peer-port 5000
|
Specifies the remote signaling-peer port for the H.323 adjacency to use.
|
Step 9
|
remote-address ipv4 ipv4_IP_address/prefix
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
remote-address ipv4 200.200.200.0/24
|
Restricts the set of remote signaling peers contacted over the adjacency to those with the given IP address prefix.
|
Step 10
|
account account_name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
account core-sided
|
Defines the H.323 adjacency as belonging to an account on an SBE.
|
Step 11
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 12
|
attach
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
attach
|
Attaches the adjacency.
|
Step 13
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 14
|
exit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
exit
|
Exits the adj-h323 mode to the sbe mode.
|
Step 15
|
adjacency h323 adjacency-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# adjacency
h323 2651XM-6
|
Enters the mode of an SBE H.323 adjacency.
Use the adjacency-name argument to define the name of the H.323 adjacency.
|
Step 16
|
signaling-address ipv4 ipv4_IP_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-address ipv4 88.88.137.10
|
Specifies the local IPv4 signaling address of the H.323 adjacency.
|
Step 17
|
signaling-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-port 5050
|
Specifies the local signaling port of the H.323 adjacency.
|
Step 18
|
signaling-peer [gk] peer_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-peer 10.10.119.12
|
Specifies the remote signaling peer for the H.323 adjacency to use.
|
Step 19
|
signaling-peer-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
signaling-peer-port 5050
|
Specifies the remote signaling-peer port for the H.323 adjacency to use.
|
Step 20
|
remote-address ipv4 ipv4_IP_address/prefix
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
remote-address ipv4 10.10.l19.0/24
|
Restricts the set of remote signaling peers contacted over the adjacency to those with the given IP address prefix.
|
Step 21
|
account account_name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
account node-side
|
Defines the H.323 adjacency as belonging to an account on an SBE.
|
Step 22
|
show
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
show
|
Shows contents of configuration.
|
Step 23
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 24
|
attach
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
attach
|
Attaches the adjacency.
|
Step 25
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 26
|
exit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-acc-ser)#
exit
|
Exits the adj-h323 mode to the sbe mode.
|
Assigning H.323 Adjacencies to Adjacency Groups
Use the procedure in this section to assign an H.323 adjacency to an adjacency group.
SUMMARY STEPS
1. configure
2. sbc service-name
3. sbe
4. adjacency h323 adjacency-name
5. group adjacency-group-name
6. commit
7. exit
8. show
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/0/CPU0:router# configure
|
Enables global configuration mode.
|
Step 2
|
sbc service-name
Example:
RP/0/0/CPU0:router(config)# sbc umsbc-node10
|
Enters the mode of an SBC service.
Use the service-name argument to define the name of the service.
|
Step 3
|
sbe
Example:
RP/0/0/CPU0:router(config-sbc)# sbe
|
Enters the mode of an SBE entity within an SBC service.
|
Step 4
|
adjacency h323 adjacency-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# adjacency
h323 2651XM-5
|
Enters the mode of an SBE H.323 adjacency.
Use the adjacency-name argument to define the name of the H.323 adjacency.
|
Step 5
|
group adjacency-group-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
group isp1
|
Assigns the H.323 adjacency to an adjacency group.
Use the adjacency-group-name argument to define the group name.
|
Step 6
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 7
|
exit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
exit
|
Exits the adj-h323 mode to the sbe mode.
|
Step 8
|
show
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-h323)#
show
|
Shows contents of configuration.
|
Configuring a SIP Adjacency
This task configures two session initiation protocol (SIP) adjacencies. The first adjacency is configured for a gateway/endpoint. The second adjacency is configured with proxy/softswitch.
SUMMARY STEPS
1. configure
2. sbc service-name
3. sbe
4. adjacency sip adjacency-name
5. signaling-address ipv4 ipv4_IP_address
6. signaling-port port_num
7. remote-address ipv4 ipv4_IP_address/prefix
8. signaling-peer [gk] peer_address
9. signaling-peer-port port_num
10. account account-name
11. registration rewrite-register
12. attach
13. exit
14. adjacency sip adjacency-name
15. signaling-address ipv4 ipv4_IP_address
16. signaling-port port_num
17. remote-address ipv4 ipv4_IP_address/prefix
18. fast-register disable
19. signaling-peer [gk] peer_name
20. signaling-peer-port port_num
21. account account-name
22. registration target address host
23. registration target port
24. attach
25. commit
26. exit
27. show
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/0/CPU0:router# configure
|
Enables global configuration mode.
|
Step 2
|
sbc service-name
Example:
RP/0/0/CPU0:router(config)# sbc mysbc
|
Enters the mode of an SBC service.
Use the service-name argument to define the name of the service.
|
Step 3
|
sbe
Example:
RP/0/0/CPU0:router(config-sbc)# sbe
|
Enters the mode of an SBE entity within an SBC service.
|
Step 4
|
adjacency sip adjacency-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# adjacency
sip sipGW
|
Enters the mode of an SBE SIP adjacency.
Use the adjacency-name argument to define the name of the service.
|
Step 5
|
signaling-address ipv4 ipv4_IP_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-address ipv4 88.88.141.3
|
Specifies the local IPv4 signaling address of the SIP adjacency.
|
Step 6
|
signaling-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-port 5060
|
Specifies the local signaling port of the SIP adjacency.
|
Step 7
|
remote-address ipv4 ipv4_IP_address/prefix
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
remote-address ipv4 10.10.121.0/24
|
Restricts the set of remote signaling peers contacted over the adjacency to those with the given IP address prefix.
|
Step 8
|
signaling-peer [gk] peer_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-peer 10.10.121.10
|
Specifies the remote signaling peer for the SIP adjacency to use.
|
Step 9
|
signaling-peer-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-peer-port 5060
|
Specifies the remote signaling-peer port for the SIP adjacency to use.
|
Step 10
|
account account_name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
account iosgw
|
Defines the SIP adjacency as belonging to an account on an SBE.
|
Step 11
|
registration rewrite-register
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
registration rewrite-register
|
Configures SIP REGISTER request rewriting.
|
Step 12
|
attach
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
attach
|
Attaches the adjacency.
|
Step 13
|
exit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
exit
|
Exits adj-sip mode to sbe mode.
|
Step 14
|
adjacency sip adjacency-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
adjacency sip sipPROXY
|
Enters the mode of an SBE SIP adjacency.
Use the adjacency-name argument to define the name of the service.
|
Step 15
|
signaling-address ipv4 ipv4_IP_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-address ipv4 88.88.141.11
|
Specifies the local IPv4 signaling address of the SIP adjacency.
|
Step 16
|
signaling-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-port 5060
|
Specifies the local signaling port of the SIP adjacency.
|
Step 17
|
remote-address ipv4 ipv4_IP_address/prefix
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
remote-address ipv4 200.200.200.0/24
|
Restricts the set of remote signaling peers contacted over the adjacency to those with the given IP address prefix.
|
Step 18
|
fast-register disable
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
fast-register disable
|
Disables fast register support on the SIP adjacency.
|
Step 19
|
signaling-peer [gk] peer_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-peer 200.200.200.98
|
Specifies the remote signaling peer for the SIP adjacency to use.
|
Step 20
|
signaling-peer-port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
signaling-peer-port 5060
|
Specifies the remote signaling-peer port for the SIP adjacency to use.
|
Step 21
|
account account_name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
account COREvlan
|
Defines the SIP adjacency as belonging to an account on an SBE.
|
Step 22
|
registration target address host_address
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
registration target address 200.200.200.98
|
Sets the address to use if rewriting an outbound SIP REGISTER request.
|
Step 23
|
registration target port port_num
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
registration target port 5060
|
Sets the port to use if rewriting an outbound SIP REGISTER request.
|
Step 24
|
attach
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
attach
|
Attaches the adjacency.
|
Step 25
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 26
|
exit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
exit
|
Exits adj-sip mode to sbe mode.
|
Step 27
|
show
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# show
|
Shows contents of configuration.
|
Assigning SIP Adjacencies to Adjacency Groups
Use the procedure in this section to assign an SIP adjacency to an adjacency group.
SUMMARY STEPS
1. configure
2. sbc service-name
3. sbe
4. adjacency sip adjacency-name
5. group adjacency-group-name
6. commit
7. exit
8. show
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/0/CPU0:router# configure
|
Enables global configuration mode.
|
Step 2
|
sbc service-name
Example:
RP/0/0/CPU0:router(config)# sbc mysbc
|
Enters the mode of an SBC service.
Use the service-name argument to define the name of the service.
|
Step 3
|
sbe
Example:
RP/0/0/CPU0:router(config-sbc)# sbe
|
Enters the mode of an SBE entity within an SBC service.
|
Step 4
|
adjacency sip adjacency-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# adjacency
sip sipGW
|
Enters the mode of an SBE SIP adjacency.
Use the adjacency-name argument to define the name of the service.
|
Step 5
|
group adjacency-group-name
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
group InternetEth0
|
Assigns the SIP adjacency to an adjacency group.
Use the adjacency-group-name argument to define the group name.
|
Step 6
|
commit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
commit
|
Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 7
|
exit
Example:
RP/0/0/CPU0:router(config-sbc-sbe-adj-sip)#
exit
|
Exits adj-sip mode to sbe mode.
|
Step 8
|
show
Example:
RP/0/0/CPU0:router(config-sbc-sbe)# show
|
Shows contents of configuration.
|
Configuration Examples for Implementing Adjacencies
This section provides the following configuration examples:
•Configuring an H.323 Adjacency: Examples
•Configuring a SIP Adjacency: Example
Configuring an H.323 Adjacency: Examples
This section contains two example H.323 adjacency configurations:
•H.323 Adjacency Example 1 (Two Gateways/Endpoints)
•H.323 Adjacency Example 2 (Gatekeeper in Network)
H.323 Adjacency Example 1 (Two Gateways/Endpoints)
In this example, the configuration is performed to support SBC peering with two H.323 gateways/endpoints in two different networks (as shown in shown in Figure 8).
Figure 8 SBC with Two H.323 Gateways/Endpoints in Two Different Networks
1. Go SBE submode
2. Configure an H.323 adjacency name and type (as a result, you will be in the H.323 adjacency submode):
3. Configure the local signaling address and port. All H.323 signaling traffic should be sent to this address and port by the gateway (default port is 1720).
signaling-address ipv4 88.88.137.10
4. Configure the signaling address and port for the peer gateway. SBC will send all H.323 signaling traffic to this address and port.
signaling-peer 200.200.200.41
5. Restrict the set of remote signaling peers contacted over the adjacency. To be successful, the address of the endpoint originating or terminating the call should be within this subnet.
remote-address ipv4 200.200.200.0/24
6. Configure the account that the adjacency will belong to:
7. Commit the configuration and attach the H.323 adjacency. On attaching, the adjacency is activated.
(When attached, no additional configuration changes can be made to the adjacency. To make changes, do no attach; commit and then make changes and attach afterwards.)
8. Similarly, configure a second adjacency pointing to the gateway in another account, where the calls will terminate (or vice versa):
signaling-address ipv4 88.88.137.10
signaling-peer 10.10.119.12
remote-address ipv4 10.10.119.0/24
9. Use the show command to verify that the adjacency is attached.
H.323 Adjacency Example 2 (Gatekeeper in Network)
In this example, there is a gatekeeper (as shown in Figure 9) in the network. Therefore, everything is pointing to the gatekeeper on the remote side instead of the gateway; configuring a signaling port is not required.
The keyword "gk" is added to the signaling-peer command and an alias is configured. The rest of the configuration is the same as shown in "H.323 Adjacency Example 1 (Two Gateways/Endpoints)".
Figure 9 SBC with Two H.323 Gatekeepers in Two Different Networks
1. Go to SBE submode
2. Configure an H.323 adjacency name signaling-peer gatekeeper, and alias:
signaling-peer gk 200.200.200.40
3. Configure the local signaling address and port. All H.323 signaling traffic will be sent to this address.
signaling-address ipv4 88.88.137.10
4. Restrict the set of remote signaling peers contacted over the adjacency. To be successful, the address of the endpoint originating or terminating the call should be within this subnet.
remote-address ipv4 200.200.200.0/24
5. Configure the account that the adjacency will belong to:
6. Commit the configuration and attach the H.323 adjacency. On attaching, the adjacency is activated.
(When attached, no additional configuration changes can be made to the adjacency. To make changes, do no attach; commit and then make changes. Then attach afterwards.)
7. Similarly, configure a second adjacency pointing to the gateway in another account (as shown in Figure 9), where the calls will terminate (or vice versa):
signaling-address ipv4 88.88.137.10
signaling-peer gk 10.10.119.8
remote-address ipv4 10.10.119.0/24
8. Use the show command to verify that the adjacency is attached.
Configuring a SIP Adjacency: Example
The following example configures two SIP adjacencies. The first adjacency is configured for a gateway/endpoint. The second adjacency is configured with proxy/softswitch.
1. Start the SBC service, as follows:
service-location preferred-active 0/2/CPU0
2. Create interface SBC, as follows:
ipv4 address 88.88.141.10 255.255.255.0
service-location preferred-active 0/2/CPU0
3. Activate SBE, as follows:
4. Activate DBE, as follows:
media-address ipv4 88.88.141.2
5. Create the SIP adjacencies, as follows:
6. Create the SIP adjacency for gateway/endpoint:
signaling-address ipv4 88.88.141.3
remote-address ipv4 10.10.121.0/24
signaling-peer 10.10.121.10
registration rewrite-register
7. Create the SIP adjacency for proxy/softswitch:
signaling-address ipv4 88.88.141.11
remote-address ipv4 200.200.200.0/24
signaling-peer 200.200.200.98
registration target address 200.200.200.98
registration target port 5060
Where to Go Next
After you have configured adjacencies, you should configure routing policies as discussed in the "Implementing SBC Policies" module.
Additional References
The following sections provide references related to implementing SBC adjacencies.
Related Documents
Related Topic
|
Document Title
|
Cisco IOS XR master command reference
|
Cisco IOS XR Master Commands List
|
Cisco IOS XR SBC interface configuration commands
|
Cisco IOS XR Session Border Controller Command Reference
|
Initial system bootup and configuration information for a router using the Cisco IOS XR Software
|
Cisco IOS XR Getting Started Guide
|
Cisco IOS XR command modes
|
Cisco IOS XR Command Mode Reference
|
Standards
Standards
|
Title
|
No new or modified standards are supported by this feature, and support from existing standards has not been modified by this feature.
|
—
|
MIBs
RFCs
RFCs
|
Title
|
RFC 2833
|
RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
|
RFC 3261
|
SIP: Session Initiation Protocol
|
Technical Assistance
Description
|
Link
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/techsupport
|
Related Command Summary
This section provides an alphabetical list of the commands related to SBC adjacencies on the Cisco XR 12000 Series Router. For more information about the commands, see the Cisco IOS XR Session Border Controller Command Reference.
Command
|
Purpose
|
account account_name
|
Specifies the account with which the SIP or H.323 adjacency is associated.
|
alias alias_name
|
Specifies the endpoint alias of an H.323 adjacency.
|
attach
|
Attaches a SIP or H.323 adjacency.
|
authenticate
|
Enables authentication on a SIP adjacency.
|
authentication auth_type
|
Configures H.323 adjacency authentication so that the SBC will authenticate itself with a gatekeeper.
|
authentication-key key
|
Specifies the H.323 adjacency authentication key.
|
call-policy-set policy-set-id
|
Enters the mode of routing policy set configuration within an SBE entitiy, creating a new policy set, if necessary.
|
dbe-location-id dbe_location_id
|
Specifies a media gateway DBE location for a SIP or H.323 adjacency to use when routing media.
|
fast-register disable
|
Disables fast-path register support on a SIP adjacency.
|
fast-register-interval interval
|
Configures the fast-path register interval (in seconds) of a SIP adjacency.
|
local-id host name
|
Specifies the local identity name for a SIP adjacency.
|
media-bypass
|
Configures a SIP or H.323 adjacency to allow media traffic to bypass the DBE.
|
nat-enable
|
Enables NAT support on a SIP adjacency. By default, NAT traversal procedures are not used unless enabled using nat-enable.
|
registration rewrite-register
|
Configures a SIP adjacency to allow rewriting of inbound SIP REGISTER requests on this adjacency.
|
registration target address target-address
|
Configures a SIP adjacency registration target host address.
|
registration target port port-num
|
Configures a SIP adjacency registration target port number.
|
reg-min-expiry period
|
Configures the minimum registration interval period (in seconds) of a SIP adjacency.
|
remote-address ipv4 ipv4_IP_address/prefix
|
Specifies the IP address and prefix used to match an incoming call (SIP and H.323).
|
rtg-src-adjacency-table table-name
|
Enters the configuration mode of a routing table (creating one if necessary) within the context of an SBE policy set whose entries match the source adjacency.
|
rtp payload-type nte number
|
Configures the dynamic RTP payload type for RFC 2833 Named Telephone Event (rtp-nte) packets when doing DTMF interworking on an H.323 adjacency.
|
signaling-address ipv4 ipv4_IP_address
|
Specifies the local IPv4 signaling address of a SIP or H.323 adjacency.
|
signaling-peer [gk] peer_address
|
Specifies the remote signaling peer for a SIP or H.323 adjacency to use.
|
signaling-peer-port port_num
|
Specifies the remote signaling port for a SIP or H.323 adjacency to use.
|
signaling-port port_num
|
Specifies the local signaling port for a SIP or H.323 adjacency to use.
|
vrf vrf_name
|
Ties an adjacency to a specific virtual private network (VPN).
|
Feedback
