The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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.
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.
If the INVITE transaction with preloaded outbound-proxy & route header fails because of no response, socket errors, or 4xx/5xx/6xx response, the call will fail. Subsequent calls may also fail if the same error condition occurs until a re-registration request updates the cached outbound-proxy and service-route with alternate P-CSCF/S-CSCF information. Failed calls do not cause a forced re-registration to update the outbound-proxy and service-route information; the registration retry timer needs to expire for re-registration to be initiated
Only a single registrar command configuration is recommended for this feature. If multiple registrar commands are configured, the outbound call selects the first registrar to which the associated registered-number is registered with.
The 200 OK response to initial INVITE should contain Record-Route header with outbound proxy IP address and Port used for sending INVITE as host-port in the topmost Record-Route header. The 200 OK response to initial INVITE overrides outbound proxy configuration for the future requests in the dialog. If the 200 OK response to initial INVITE does not contain Record-Route, subsequent requests are sent directly to the remote target.
Mode |
Outbound Proxy Support |
---|---|
Primary/secondary registrar mode |
IPv4 and IPv6 |
Multiple registrar mode |
IPv4 |
DHCP mode |
IPv4 |
The Cisco IOS gateway registers all its POTS dial peers to the registrar when the registrar is configured on the Gateway. The introduction of trunk registration support, the registration of a single number would represent the SIP trunk. The SIP trunk registration can then be associated with multiple dial-peers for routing outbound calls. This registration represents all of the gateway end points for routing calls from or to the endpoints.
The Cisco IOS SIP gateway sends the REGISTER request to the configured registrar after resolving the outbound-proxy DNS name. Upon successful registration the Cisco IOS SIP gateway re-uses the Outbound Proxy IP address, port number, service-route response received for sending subsequent REGISTER/INVITE.
The existing enabling the outbound proxy CLI would be extended to turn on/off using the resolved IP address and port for a successful registration to all the subsequent outbound INVITE/REGISTER.
1.
enable
2.
configure
terminal
3.
voice service voip
4.
sip
5.
outbound-proxy dns:host:domain reuse
voice service voip fax protocol cisco sip rel1xx disable outbound-proxy dns:rdc01pcscfgm.ims.voip.hrndva.rr.com no update-callerid authenticate redirecting-number sip-profiles 100
Use the following global or dia-peer configurations to associate a number with a dial-peer. When configured, the registration corresponding to this number is used for sending the OOD INVITE.
1.
enable
2.
configure
terminal
3.
voice
service
voip
4.
sip
5.
associateregistered-numbernumber
6.
exit
1.
enable
2.
configure
terminal
3.
dial-peer
voice
tag
voip
4.
voice-class sip
associate registered-number
tag
system
5.
exit
Use the following configuration to enable or disable authorization header support in REGISTER requests and associate the realm with the register. The configured private-id of the user is used for populating authorization header.
1.
enable
2.
configure
terminal
3.
sip-ua
4.
registrar registrar-server-address: ip-address
auth-realm
5.
exit
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 |
---|---|---|
SIP Trunk Registration |
15.1(2)T |
The SIP trunk registration support registration of a single number represents the SIP trunk and allows the SIP trunk registration to be associated with multiple dial-peers for routing outbound calls. This registration represents all the gateway end points for routing calls from or to the endpoints. The following commands were introduced or modified: associate registered-number,outbound-proxy, voice-class sip associate registered-number, registrar. |
SIP Trunk Registration |
Cisco IOS XE Release 3.7S |
The SIP trunk registration support registration of a single number represents the SIP trunk and allows the SIP trunk registration to be associated with multiple dial-peers for routing outbound calls. This registration represents all the gateway end points for routing calls from or to the endpoints. The following commands were introduced or modified: associate registered-number,outbound-proxy, voice-class sip associate registered-number, registrar. |