Transcription

Configuration of SIP Trunking for PSTNAccess (SIP-to-SIP) Configuration Guide,Cisco IOS Release 12.4TAmericas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000800 553-NETS (6387)Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPEDWITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITEDWARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain versionof the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALLFAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADEPRACTICE.IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO ORITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.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 relationshipbetween 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 contentis unintentional and coincidental. 2011 Cisco Systems, Inc. All rights reserved.

CONTENTSConfiguration of SIP Trunking for PSTN Access SIP-to-SIP 1Finding Feature Information 1Configuration of SIP Trunking for PSTN Access SIP-to-SIP Features 1Configuring SIP Registration Proxy on Cisco UBE 3Finding Feature Information 3Registration Pass-Through Modes 4End-to-End Mode 4Peer-to-Peer Mode 5Registration in Different Registrar Modes 7Registration Overload Protection 8Registration Overload Protection--Call Flow 9Registration Rate-limiting 9Registration Rate-limiting Success--Call Flow 10Prerequisites for SIP Registration Proxy on Cisco UBE 11Restrictions 11Configuring Support for SIP Registration Proxy on Cisco UBE 11Enabling Local SIP Registrar 11Configuring SIP Registration at the Global Level 13Configuring SIP Registration at the Dial Peer Level 14Configuring Registration Overload Protection Functionality 15Configuring Cisco UBE to Route a Call to the Registrar Endpoint 16Configuring Cisco UBE to Challenge Incoming Requests 17Verifying the SIP Registration on Cisco UBE 19Example Configuring Support for SIP Registration Proxy on Cisco UBE 20Feature Information for Support for SIP Registration Proxy on Cisco UBE 20Configuring Cisco UBE Out-of-dialog OPTIONS Ping for Specified SIP Servers or Endpoints 23Finding Feature Information 25Troubleshooting Tips 25Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4Tiii

ContentsFeature Information for Cisco UBE Out-of-dialog OPTIONS Ping for Specified SIP Servers orEndpoints 26Additional References 29Related Documents 29Standards 30MIBs 30RFCs 31Technical Assistance 32Glossary 33Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4Tiv

Configuration of SIP Trunking for PSTN AccessSIP-to-SIPThis Cisco Unified Border Element is a special Cisco IOS software image that provides a network-tonetwork interface point for billing, security, call admission control, quality of service, and signalinginterworking. This chapter describes basic gateway functionality, software images, topology, andsummarizes supported features.NoteCisco Product Authorization Key (PAK)--A Product Authorization Key (PAK) is required to configuresome of the features described in this guide. Before you start the configuration process, please registeryour products and activate your PAK at the following URL http://www.cisco.com/go/license . Finding Feature Information, page 1Configuration of SIP Trunking for PSTN Access SIP-to-SIP Features, page 1Finding Feature InformationYour software release may not support all the features documented in this module. For the latest featureinformation and caveats, see the release notes for your platform and software release. To find informationabout the features documented in this module, and to see a list of the releases in which each feature issupported, see the Feature Information Table at the end of this document.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.Configuration of SIP Trunking for PSTN Access SIP-to-SIPFeaturesThis chapter contains the following configuration topics:Cisco UBE Prerequisites and Restrictions Prerequisites for Cisco Unified Border ElementRestrictions for Cisco Unified Border ElementConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T1

Configuration of SIP Trunking for PSTN Access SIP-to-SIPSIP trunk Monitoring Configuring Cisco UBE Out-of-dialog OPTIONS Ping for Specified SIP Servers or EndpointsCisco 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 partnerdoes 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 beactual 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 IPaddresses or phone numbers in illustrative content is unintentional and coincidental.Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T2

Configuring SIP Registration Proxy on CiscoUBEThe Support for SIP Registration Proxy on Cisco UBE feature provides support for sending outboundregistrations from Cisco Unified Border Element (UBE) based on incoming registrations. This featureenables direct registration of Session Initiation Protocol (SIP) endpoints with the SIP registrar in hostedunified communication (UC) deployments. This feature also provides various benefits for handling CiscoUBE deployments with no IP private branch exchange (PBX) support.In certain Cisco UBE deployments, managed services are offered without an IPPBX installed locally atthe branch office. A PBX located at the service provider (SP) offers managed services to IP phones. ACisco UBE device located at the branch office provides address translation services. However, theregistration back-to-back functionality is required to get the phone registered, so that calls can be routed tothe branch or the phones.In such deployment scenarios, enabling the Support for SIP Registration Proxy on Cisco UBE featureprovides the following benefits: Support for back-to-back user agent (B2BUA) functionality.Options to configure rate-limiting values such as expiry time, fail-count value, and a list of registrarsto be used for the registration.Registration overload protection facility.Option to route calls to the registering endpoint (user or phone).Option to send the 401 or 407 message to request for user credentials (this process is known aschallenge) from an incoming registration.Finding Feature Information, page 3Registration Pass-Through Modes, page 4Registration Overload Protection, page 8Registration Rate-limiting, page 9Prerequisites for SIP Registration Proxy on Cisco UBE, page 11Restrictions, page 11Configuring Support for SIP Registration Proxy on Cisco UBE, page 11Example Configuring Support for SIP Registration Proxy on Cisco UBE, page 20Feature Information for Support for SIP Registration Proxy on Cisco UBE, page 20Finding Feature InformationYour software release may not support all the features documented in this module. For the latest featureinformation and caveats, see the release notes for your platform and software release. To find informationConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T3

End-to-End ModeRegistration Pass-Through Modesabout the features documented in this module, and to see a list of the releases in which each feature issupported, see the Feature Information Table at the end of this document.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.Registration Pass-Through ModesCisco UBE uses the following two modes for registration pass-through: End-to-End Mode, page 4Peer-to-Peer Mode, page 5Registration in Different Registrar Modes, page 7End-to-End ModeIn the end-to-end mode, Cisco UBE collects the registrar details from the Uniform Resource Identifier(URI) and passes the registration messages to the registrar. The registration information contains the expirytime for rate-limiting, the challenge information from the registrar, and the challenge response from theuser.Cisco UBE also passes the challenge to the user if the register request is challenged by the registrar. Theregistrar sends the 401 or 407 message to the user requesting for user credentials. This process is known aschallenge.Cisco UBE ignores the local registrar and authentication configuration in the end-to-end mode. It passes theauthorization headers to the registrar without the header configuration.End-to-End Mode--Call FlowsThis section explains the following end-to-end pass-through mode call flows:Register Success ScenarioThe figure below shows an end-to-end registration pass-through scenario where the registration request issuccessful.Figure 1End-to-End Registration Pass-through Mode--Register Success ScenarioConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T4

Peer-to-Peer ModeRegistration Pass-Through ModesThe register success scenario for the end-to end registration pass-through mode is as follows:1 The user sends the register request to Cisco UBE.2 Cisco UBE matches the request with a dial peer and forwards the request to the registrar.3 Cisco UBE receives a success response message (200 OK message) from the registrar and forwards themessage to the endpoint (user).4 The registrar details and expiry value are passed to the user.Registrar Challenging the Register Request ScenarioThe figure below shows an end-to end registration pass-through scenario where the registrar challenges theregister request.Figure 2End-to-End Registration Pass-through Mode--Registrar Challenging the Register Request ScenarioThe following scenario explains how the registrar challenges the register request:The user sends the register request to Cisco UBE.Cisco UBE matches the register request with a dial peer and forwards it to the registrar.The registrar challenges the register request.Cisco UBE passes the registrar response and the challenge request, only if the registrar challenges therequest to the user.5 The user sends the register request and the challenge response to the Cisco UBE.6 Cisco UBE forwards the response to the registrar.7 Cisco UBE receives success message (200 OK message) from the registrar and forwards it to the user.1234Peer-to-Peer ModeIn the peer-to-peer registration pass-through mode, the outgoing register request uses the registrar detailsfrom the local Cisco UBE configuration. Cisco UBE answers the challenges received from the registrarConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T5

Configuring SIP Registration Proxy on Cisco UBERegistration Pass-Through Modesusing the configurable authentication information. Cisco UBE can also challenge the incoming registerrequests and authenticate the requests before forwarding them to the network.In this mode, Cisco UBE sends a register request to the registrar and also handles register requestchallenges. That is, if the registration request is challenged by the registrar (registrar sends 401 or 407message), Cisco UBE forwards the challenge to the user and then passes the challenge response sent by theuser to the registrar. In the peer-to-peer mode, Cisco UBE can use the authentication command tocalculate the authorization header and then challenge the user depending on the configuration.NoteThe registrar command must be configured in peer-to-peer mode. Otherwise, the register request isrejected with the 503 response message.Peer-to-Peer Mode--Call FlowsThis section explains the following peer-to-peer pass-through mode call flows:Register Success ScenarioThe figure below shows a peer-to-peer registration pass-through scenario where the registration request issuccessful.Figure 3Peer-to-Peer Registration Pass-through Mode--Register Success ScenarioThe register success scenario for a peer-to-peer registration pass-through mode is as follows:1 The user sends the register request to Cisco UBE.2 Cisco UBE matches the register request with a dial peer and forwards the register request to theregistrar.3 Cisco UBE receives a success message (200 OK message) from the registrar and forwards it to theendpoint (user). The following functions are performed:Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T6

Registration in Different Registrar ModesRegistration Pass-Through Modes Cisco UBE picks up the details about the registrar from the configuration.Cisco UBE passes the registrar details and expiry value to the user.Registrar Challenging the Register Request ScenarioThe figure below shows a peer-to-peer registration pass-through scenario where the registration request ischallenged by the registrar.Figure 4Peer-to-Peer Registration Pass-through Mode--Registrar Challenging the Register Request ScenarioThe following scenario explains how the registrar challenges the register request:1 The user sends the register request to Cisco UBE.2 Cisco UBE matches the register request with a dial peer and forwards the register request to theregistrar.3 The user responds to the challenge request.4 Cisco UBE validates the challenge response and forwards the register request to the registrar.5 Cisco UBE receives a success message from the registrar and forwards it to the endpoint (user).NoteYou can configure Cisco UBE to challenge the register request and validate the challenge response.Registration in Different Registrar ModesThis section explains SIP registration pass-through in the following registrar modes:Primary-Secondary ModeIn the primary-secondary mode the register message is sent to both the primary and the secondary registrarservers simultaneously.The register message is processed as follows:Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T7

Configuring SIP Registration Proxy on Cisco UBERegistration Overload Protection The first successful response is passed to the phone as a SUCCESS message.All challenges to the request are handled by Cisco UBE.If the final response received from the primary and the secondary servers is an error response, the errorresponse that arrives later from the primary or the secondary server is passed to the phone.If only one registrar is configured, a direct mapping is performed between the primary and thesecondary server.If no registrar is configured, or if there is a Domain Name System (DNS) failure, the "503 service notavailable" message is sent to the phone.DHCP ModeIn the DHCP mode the register message is sent to the registrar server using DHCP.Multiple Register ModeIn the multiple register mode, you can configure a dial peer to select and enable the indexed registrars.Register messages must be sent only to the specified index registrars.The response from the registrar is mapped the same way as in the primary-secondary mode. See theRegistration in Different Registrar Modes, page 7.Registration Overload ProtectionThe registration overload protection functionality enables Cisco UBE to reject the registration requests thatexceed the configured threshold value.To support the registration overload protection functionality, Cisco UBE maintains a global counter tocount all the pending outgoing registrations and prevents the overload of the registration requests asfollows: The registration count is decremented if the registration transaction is terminated.The outgoing registrations are rejected if the count goes beyond a configured threshold.The incoming register request is rejected with the 503 response if the outgoing registration is activatedby the incoming register request.A retry timer set for a random value is used for attempting the registration again if the registrations areoriginated from Cisco UBE or a gateway.The registration overload protection functionality protects the network from the following: Avalanche Restart--All the devices in the network restart at the same time.Component Failures--Sudden burst of load is routed through the device due to a device failure. Registration Overload Protection--Call Flow, page 9Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T8

Registration Overload Protection--Call FlowRegistration Rate-limitingRegistration Overload Protection--Call FlowThe figure below shows the call flow when the register overload protection functionality is configured onCisco UBE:Figure 5Register Overload ProtectionThe following steps explain the register overload protection scenario:1 The user sends a register request to Cisco UBE.2 Cisco UBE matches the request with a dial peer and forwards the register request to the registrar.3 The registration is rejected with a random retry value when the registration threshold value is reached.NoteThe call flow for the DNS query on the Out Leg is the same for the end-to-end and peer-to-peer mode.Registration Rate-limitingThe registration rate-limiting functionality enables you to configure different SIP registration pass-throughrate-limiting options. The rate-limiting options include setting the expiry time and the fail count value for aCisco UBE. You can configure the expiry time to reduce the load on the registrar and the network. CiscoUBE limits the reregistration rate by maintaining two different timers--in-registration timer and outregistration timer.The initial registration is triggered based on the incoming register request. The expiry value for theoutgoing register is selected based on the Cisco UBE configuration. On receiving the 200 OK message(response to the BYE message) from the registrar, a timer is started using the expiry value available in the200 OK message. The timer value in the 200 OK message is called the out-registration timer. The successresponse is forwarded to the user. The expiry value is taken from the register request and the timer isstarted accordingly. This timer is called the in-registration timer. There must be a significant differencebetween the in-registration timer and the out-registration timer values for effective rate-limiting.Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T9

Registration Rate-limiting Success--Call FlowRegistration Rate-limiting Registration Rate-limiting Success--Call Flow, page 10Registration Rate-limiting Success--Call FlowThe figure below shows the call flow when the rate-limiting functionality is successful:Figure 6Rate-limiting Success ScenarioThe following steps explain a scenario where the rate-limiting functionality is successful:1 The user sends the register request to Cisco UBE.2 Cisco UBE matches the registration request with a dial peer and forwards it to the registrar. Theoutgoing register request contains the maximum expiry value if the rate-limiting functionality isconfigured.3 The registrar accepts the registration.4 Cisco UBE forwards the success response with the proposed expiry timer value.Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T10

Enabling Local SIP RegistrarPrerequisites for SIP Registration Proxy on Cisco UBE5 The user sends the reregistration requests based on the negotiated value. Cisco UBE resends the registerrequests until the out-leg expiry timer value is sent.6 Cisco UBE forwards the subsequent register request to the registrar, if the reregister request is receivedafter the out-leg timer is reached.Prerequisites for SIP Registration Proxy on Cisco UBE You must enable the local SIP registrar. See Enabling Local SIP Registrar, page 11.You must configure dial peers manually for call routing and pattern matchingCisco Unified Border Element Cisco IOS Release 15.1(3)T or a later release must be installed and running on your Cisco UnifiedBorder Element.Cisco Unified Border Element (Enterprise) Cisco IOS XE Release TBD or a later release must be installed and running on your Cisco ASR1000 Series Router.Restrictions IPv6 support is not provided.Configuring Support for SIP Registration Proxy on Cisco UBE Enabling Local SIP Registrar, page 11Configuring SIP Registration at the Global Level, page 13Configuring SIP Registration at the Dial Peer Level, page 14Configuring Registration Overload Protection Functionality, page 15Configuring Cisco UBE to Route a Call to the Registrar Endpoint, page 16Configuring Cisco UBE to Challenge Incoming Requests, page 17Verifying the SIP Registration on Cisco UBE, page 19Enabling Local SIP RegistrarPerform this task to enable the local SIP registrar.Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T11

Configuring SIP Registration Proxy on Cisco UBEConfiguring Support for SIP Registration Proxy on Cisco UBESUMMARY STEPS1. enable2. configure terminal3. voice service voip4. sip5. registrar server [expires [max value] [min value]]6. endDETAILED STEPSCommand or ActionStep 1 enablePurposeEnables privileged EXEC mode. Enter your password if prompted.Example:Router enableStep 2 configure terminalEnters global configuration mode.Example:Router# configure terminalStep 3 voice service voipEnters voice-service configuration mode.Example:Router(config)# voice service voipStep 4 sipEnters service SIP configuration mode.Example:Router(conf-voi-serv)# sipStep 5 registrar server [expires [max value] [minvalue]]Example:Router(conf-serv-sip)# registrar serverEnables the local SIP registrar. Optionally you can configure the expiry time of the registrarusing the following keywords: expires--Configures the registration expiry time.max--Configures the maximum registration expiry time.min--Configures the minimum registration expiry time.Note The registrar command must be configured in peer-to-peermode. Otherwise, the register request is rejected with the 503response message.Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T12

Configuring SIP Registration at the Global LevelConfiguring Support for SIP Registration Proxy on Cisco UBECommand or ActionPurposeStep 6 endExits service SIP configuration mode and returns to privileged EXECmode.Example:Router(conf-serv-sip)# endConfiguring SIP Registration at the Global LevelPerform this task to configure the support for the SIP registration proxy on the Cisco UBE at the globallevel.SUMMARY STEPS1. enable2. configure terminal3. voice service voip4. sip5. registration passthrough [static] [rate-limit [expires value] [fail-count value]] [registrar-index[index]]6. endDETAILED STEPSPurposeCommand or ActionStep 1 enableEnables privileged EXEC mode. Enter your password if prompted.Example:Router enableStep 2 configure terminalEnters global configuration mode.Example:Router# configure terminalStep 3 voice service voipEnters voice-service configuration mode.Example:Router(config)# voice service voipConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T13

Configuring SIP Registration at the Dial Peer LevelConfiguring Support for SIP Registration Proxy on Cisco UBECommand or ActionStep 4 sipPurposeEnters service SIP configuration mode.Example:Router(conf-voi-serv)# sipStep 5 registration passthrough [static] [rate-limitConfigures the SIP registration pass-through options.[expires value] [fail-count value]] [registrar-index You can specify different SIP registration pass-through options[index]]using the following keywords: Example:Router(conf-serv-sip)# registrationpassthroughStep 6 endrate-limit--Enables rate-limiting.expires--Configures expiry value for rate-limiting.fail-count--Configures fail count during rate-limiting.registrar-index--Configures a list of registrars to be usedfor registration.Exits service SIP configuration mode and returns to privilegedEXEC mode.Example:Router(conf-serv-sip)# endConfiguring SIP Registration at the Dial Peer LevelPerform this task to configure SIP registration at the dial peer level.SUMMARY STEPS1. enable2. configure terminal3. dial-peer voice tag {pots voatm vofr voip}4. voice-class sip registration passthrough static [rate-limit [expires value] [fail-count value][registrar-index [index]] registrar-index [index]]5. exitDETAILED STEPSCommand or ActionStep 1 enablePurposeEnables privileged EXEC mode. Enter your password if prompted.Example:Router enableConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T14

Configuring Registration Overload Protection FunctionalityConfiguring Support for SIP Registration Proxy on Cisco UBECommand or ActionPurposeStep 2 configure terminalEnters global configuration mode.Example:Router# configure terminalStep 3 dial-peer voice tag {pots voatm vofr voip}Enters dial peer voice configuration mode.Example:Router(config)# dial-peer voice 444 voipStep 4 voice-class sip registration passthrough static [rate- Configure SIP registration pass-through options on a dial peer ona dial peer.limit [expires value] [fail-count value] [registrarindex [index]] registrar-index [index]] You can specify different SIP registration pass-throughoptions using the following keywords:Example:Router(config-dial-peer)# voice-class sipregistration passthrough staticStep 5 exit rate-limit--Enables rate-limiting.expires--Configures expiry value for rate-limiting.fail-count--Configures fail count during rate-limiting.registrar-index--Configures a list of registrars to beused for registration.Exits dial peer voice configuration mode and returns to globalconfiguration mode.Example:Router(config-dial-peer)# exitConfiguring Registration Overload Protection FunctionalityPerform this task to configure registration overload protection functionality on Cisco UBE.SUMMARY STEPS1. enable2. configure terminal3. sip-ua4. registration spike max-number5. endConfiguration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T15

Configuring Cisco UBE to Route a Call to the Registrar EndpointConfiguring Support for SIP Registration Proxy on Cisco UBEDETAILED STEPSCommand or ActionStep 1 enablePurposeEnables privileged EXEC mode. Enter your password if prompted.Example:Router enableStep 2 configure terminalEnters global configuration mode.Example:Router# configure terminalStep 3 sip-uaEnters SIP user-agent configuration mode.Example:Router(config)# sip-uaStep 4 registration spike max-numberConfigures registration overload protection functionality on CiscoUBE.Example:Router(config-sip-ua)# registration spike 100Step 5 endExits SIP user-agent configuration mode and returns to privilegedEXEC mode.Example:Router(config-sip-ua)# endConfiguring Cisco UBE to Route a Call to the Registrar EndpointPerform this task to configure Cisco UBE to route a call to the registrar endpoint.NoteYou must perform this configuration on a dial peer that is pointing towards the endpoint.Configuration of SIP Trunking for PSTN Access (SIP-to-SIP) Configuration Guide, Cisco IOS Release 12.4T16

Configuring Cisco UBE to Challenge Incoming RequestsConfiguring Support for SIP Registration Proxy on Cisco UBESUMMARY STEPS1. enable2. configure terminal3. dial-peer voice tag {pots voatm vofr voip}4. session target registrar5. exitDETAILED STEPSCommand or ActionPurposeStep 1 enableEnables privileged EXEC mode. Enter your password if prompted.Example:Router enableStep 2 configure te

C O N T E N T S Configuration of SIP Trunking for PSTN Access SIP-to-SIP 1 Finding Feature Information 1 Configuration of SIP Trunking for PSTN Access SIP-to-SIP Features 1 Configuring SIP Registration Proxy on Cisco UBE 3 Finding Feature Information 3 Registration Pass-Through Modes 4 End-to-End Mode 4 Peer-t