Transcription

Data SheetCisco Unified SIP Proxy Version 9.0Product OverviewCisco Unified SIP Proxy (USP) is a high-performance, highly scalable Session Initiation Protocol (SIP) proxyserver that helps enterprises aggregate their SIP elements into a centralized architecture in order to simplify andimprove the flexibility of their network.The Cisco USP simplifies call routing within multielement SIP networks using call-routing rules to improve controland flexibility of the overall network. For example, an enterprise network may include Cisco UnifiedCommunications Manager for call control, Cisco Unified Border Element for session border control, and CiscoUnified Customer Voice Portal (Cisco Unified CVP) for interactive-voice-response (IVR) as well as other Cisco andthird-party SIP-based elements. Cisco USP interconnects these different SIP-based elements so that SIP networkdesign and troubleshooting, when needed, are greatly simplified. Because Cisco USP acts as a “stateless” routingintermediary between these elements, it greatly reduces the call-routing combinations to help identify problemsfaster and speed troubleshooting. As such, each SIP-based element needs only to route its call activities to CiscoUSP to help ensure proper call routing to any other SIP-based element in its network. By forwarding call-routingrequests between call-control elements, the Cisco USP provides the means for routing sessions within enterpriseand service provider networks.Cisco Unified SIP Proxy Version 9.0 provides important new features not available in previous versions. Cisco USPVersion 9.0 runs in a virtualized OS environment, such as VMware, on the Cisco Unified Computing System (Cisco UCS ) Series of servers (refer to Figure 1), and includes the Cisco UCS E-Series Server modules that areinstallable in Cisco 2900, 3900, 3900E, and the 4000 Series Integrated Services Routers. On the other hand, CiscoUSP Versions 8.5.7 and earlier run on the Cisco Integrated Services Routers Generation 2 (ISR G2) ServicesReady Engine (SRE) blade, but are not supported on the Cisco UCS servers, they do not operate in virtualized OSenvironments, and they do not support all the features that Cisco USP Version 9.0 and later provide.Figure 1.Cisco UCS Servers (UCS B, C, and E) on Which Cisco USP Version 9.0 Operates 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 1 of 15

ApplicationsBy simplifying SIP-based call routing, Cisco Unified SIP Proxy Version 9.0 enables a broad range of unifiedcommunications applications and services, as described in the following paragraphs.Cisco Unified Border Element Scalability and Load BalancingCisco Unified Border Element (CUBE) is Cisco’s enterprise session border controller providing demarcation,security, interworking, session control, and demarcation in SIP trunking deployments. Cisco Unified SIP Proxyprovides a central route point for management of multiple CUBEs, helping simplify and scale large SIP trunkingdeployments. You can establish logical separations and use a single Cisco Unified SIP Proxy for either or bothingress and egress traffic. You can apply load balancing and rule-based routing, and provide interfacing to the SIPtrunk signal normalization where needed (Figure 2).If a CUBE is unavailable, Cisco Unified SIP Proxy can intelligently reroute to an alternate CUBE. When that CUBEreturns to service, Cisco Unified SIP Proxy resumes sending traffic back to that original CUBE. This design enablesneed-based growth of the service provider interconnect and also avoids risk associated with a single point of failurefor the border element.Figure 2.Cisco Unified Border Element Scalability and Load Balancing in a SIP Trunking DeploymentSIP Trunk for Contact CenterWhether for inbound or outbound traffic, Cisco Unified SIP Proxy enables routing and management across contactcenter time-division multiplexing (TDM) and SIP trunks. Routing is provided across gateways connecting outsidethe network as well as across multiple Cisco Unified CVPs. If a Cisco Unified CVP or gateway is unavailable, CiscoUnified SIP Proxy can intelligently reroute to an alternate Cisco Unified CVP or gateway until that one is availableagain. You can apply load balancing and rule-based routing, and provide interfacing to the SIP trunk signalnormalization where needed (Figure 3). 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 2 of 15

Figure 3.SIP Trunk for Contact CenterCisco Unified Communications Manager and Cisco Unified Communications Manager ExpressSIP AggregationCisco USP can also simplify the network for an enterprise deploying a distributed call-control network using CiscoUnified Communications Manager at large sites and Cisco Unified Communications Manager Express at thebranch offices. Management of SIP dial peers across midsize and large Cisco Unified Communications Managerand Cisco Unified Communications Manager Express networks presents a challenge. As opposed to a full mesh,dial peers can be pointed to Cisco Unified SIP Proxy, which provides a central route point. This process alsosimplifies the addition and removal of new call-processing agents. If a call-processing agent is unavailable,alternate routing and recovery can be provided. You can apply dial normalization and load balancing as needed(Figure 4).Figure 4.Cisco Unified Communications Manager and Cisco Unified Communications Manager Express SIP Aggregation 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 3 of 15

Cisco Unity PBX IP Media Gateway IntegrationCisco Unity PBX IP Media Gateways (PIMGs) are used to connect time-division multiplexing (TDM)-based privatebranch exchanges (PBXs) into Cisco Unity voice messaging systems. Placement of Cisco Unified SIP Proxy infront of the Cisco Unity application enables PIMGs to share Cisco Unity ports, in turn enabling scalability of hybridTDM PBX and IP messaging deployments (Figure 5).Figure 5.Cisco Unity PBX IP Media Gateway IntegrationService Provider SIP Interconnect ServicesFor interconnection among service providers, Cisco Unified SIP Proxy enables normalization of dial strings and SIPsignaling variants. Cisco Unified SIP Proxy also provides routing and load balancing among SIP elements,including Cisco Unified Border Elements (Figure 6).Figure 6.Service Provider SIP InterconnectProduct ArchitectureCisco Unified SIP Proxy Call ProcessingThe Cisco Unified SIP Proxy is a call and dialog stateless SIP proxy, meaning that after Cisco USP determines thecorrect SIP-based routing, it withdraws from the signaling interaction and allows the SIP-based elements toperform midcall signaling directly between one another. In a network with multiple SIP-based elements, thisstateless proxy function greatly simplifies the various SIP protocol interactions between these elements.Furthermore, Cisco USP does not perform any media-handling functions. Instead, session media flows bypass theCisco USP and go directly to the SIP-based endpoints, which Cisco USP has interacted with in the sessionsignaling process. The Cisco USP can also modify SIP headers (normalization). Routing and normalization aredetermined based on administrator-configured policies. Policies are selected based on triggers, administratorconfigured conditions that are matched based on information in the SIP message. 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 4 of 15

As SIP messages come into the proxy, a determination is made as to whether any prenormalization policies needto be applied. Following prenormalization, new triggers are used to determine application of routing policies. Afurther series of triggers provides for further header modifications; for example, postnormalization policies after therouting decision has been made. In cases where policy is not asserted, the proxy provides for pass-through of theSIP message (Figure 7).Figure 7.Cisco Unified SIP Proxy Call-Processing ModelYou can apply distinct rules to groups of requests to create independent “virtualized proxies” within a single CiscoUnified SIP Proxy. The rules are highly flexible and scalable to form routing or normalization policies.Features Proxy for SIP unified communications signaling Signaling support: voice, video, fax, physical terminal line (TTY), modem, caller ID, caller name, updates,transfer, forward, hold, conference, status, message-waiting indicator (MWI), dual-tone multifrequency(DTMF) relay, and SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE) (presence) Address resolution (Domain Name System [DNS]: Type A and SRV and Type NAPTR) Domain name resolution based on RFC 3263, Locating SIP Servers TCP, User Datagram Protocol (UDP), and Transport Layer Security (TLS) Standard (RECORD ROUTE ON) mode: This mode keeps a record of the SIP sessions it connects. Thisrecord can be very valuable in the SIP-based network to determine if the call-routing policies (dial plan)defined within Cisco USP are working as intended Lite (RECORD ROUTE OFF) mode: This mode allows Cisco Unified SIP Proxy to run at a higher SIPrequest rate than the RECORD ROUTE ON call rate by disabling record-route functions. This mode istypically used after the SIP-based network call routing using Cisco USP has been thoroughly tested. Formore details about RECORD ROUTE OFF mode, refer to the “Performance” section 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 5 of 15

Deployment options: Cisco USP Versions 8.5.7 and earlier runs natively on an SRE server module installedin the Cisco 2900, 3900 and 3900E, or 4000 Series Integrated Services Routers. Cisco USP Versions 9.0and later are virtualized and run on Cisco UCS Series Servers, including the Cisco UCS E-Series Servermodules, which are also modules on Cisco 2900, 3900 and 3900E, or 4000 Series Integrated ServicesRouters The server modules impose minimal performance impact on the router, thereby allowing for concurrentrouter applicationsRouting Routing based on policy Configurable multistep routing policies with route-table lookup Configurable match rules (for example, longest prefix, exact match, and fixed-length match) Configurable keys selected from the SIP request: Remote address, local address, request for UniformResource Identifier (URI), P-Asserted-Identity (caller ID), diversion, remote-party ID, To, and From; withinthese headers Cisco Unified SIP Proxy can select the user, host, port, domain, phone number, URI,carrier codes, and location routing numbers Configurable key modifiers (for example, case insensitivity, ignore plus, ignore display characters, etc.) Numerous routing decisions: Forward to a single route, forward to a route group, reject, and chain toanother route policy Table-based routing for mapping of requests to destinations Support for a large number of routes in a table (10,000 ) Routes populated through command-line interface (CLI) or upload of a route file Example routing scenarios: URI-based routing (number and name) Call block between specified sources and destinations, including policy-based transit routing (policy mayrequire certain calls to either avoid or take certain routes) Class of restriction Translation of on-net to off-net dial plans (including public switched telephone network [PSTN] and IP-IP);simplifies network management, eliminating the need to configure translations in each call agent Percentage and weight-based routing Load balancing among downstream elements based on preset weight Priority values assignable for routing of selected calls; also enables configuration for least-cost routing Time policy routing Time(s) in a day, day(s) in a week, day(s) in a month, and month(s) in a year Ability to form downstream elements into a single logical group for load balancing and failover SIP element health management and monitoring Rerouting around unavailable SIP elements Ping for service availability and restoration of routing when unavailable SIP element is restored Rerouting based on redirect responses (Routing policy and postnormalization applies to the new destinationspecified in the contact header of the redirect response, and provides for sequential forking) 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 6 of 15

Transport protocol conversion: TCP, UDP, TLS (For example, an incoming call received over UDP can beforwarded to a destination over TLS) Configurable record routing (on/off) Global unique caller ID pass-throughNormalization Normalization of SIP headers based on configurable policy Ability to add, remove, or update headers and header parameters Ability to update URI components such as user, domain, and host and ability to add, remove, and updateURI parameters Digit manipulation Address manipulation TEL URI SIP URI conversion Domain conversions Regular-expression processing Construction of multistep normalization policies Pre- and postnormalization Prenormalization prior to proxy application of routing rules (for example, applied to message coming intothe proxy) Postnormalization after proxy application of routing rules (for example, applied to message going outfrom the proxy)Rules-Based Selection of Routing and Normalization Policies Rich set of configurable rules SIP message type (for example, request and response) SIP method: INVITE, UPDATE, REFER, PRACK, BYE, SUBSCRIBE, NOTIFY, unsolicited NOTIFY,MESSAGE, PUBLISH, REGISTER, INFO, OPTIONS, and any custom or future SIP extensions Request-URI: User, host, phone number, etc. Local and remote IP, port, and protocol of the received SIP message Network name of the incoming and outgoing request (A network is a set of SIP listening points.) Transport protocol Regular expression match on any SIP header Time policy check SIP response code Mid-dialog message check Call Admission Control Call-counting based 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 7 of 15

Security and Privacy TLS (bidirectional) Through-header stripping (for topology hiding) User privacy (RFC 3325 P-Asserted ID: Removes P-Asserted ID when receiving a message from anelement not configured as trusted, and removes P-Asserted ID and Privacy header when forwarding amessage to an element not configured as trusted)Network Design Multiple IP addresses (up to eight) to provide for flexible configuration and network topology design; you cangroup IP addresses to form networks and apply rules on these networks Multiple SIP listening points; each listen point can have a configurable port “Virtualized proxies” with multiple independent routing and normalization processing in a single server Redundancy through clustered network design for high availability Clusters addressed as Fully Qualified Domain Names (FQDNs); DNS resolution through Service (SRV)record Virtual IP addressing using Hot Standby Router Protocol (HSRP) Very high scalability with clustering of multiple Cisco Unified SIP Proxies Hierarchical and peer requests among clustered Cisco Unified SIP Proxies, either as server-based orvirtualized platformsManagement Flexible management through GUI and CLI Monitoring of system status using Simple Network Management Protocol (SNMP) MIBs Load of preexisting configurations onto the Cisco Unified SIP Proxy module Copy of configurations off the Cisco Unified SIP Proxy module Graceful shutdown and restore, allowing for completion of transactions in process RADIUS accounting for SIP events SIP message logging for call monitoring Trace logging for troubleshooting FTP access to Cisco Unified SIP Proxy for easy download of trace logs, SIP message logs, configurationfiles, and route files, and upload of configuration files and route files SIP message metrics logging (peg counting); for example, count of incoming and outgoing messages over aperiod of time and logging to a file Detailed call statistics with call attempt, success, and failure rates per element Database store for debugs and logs Selectively log messages using regular expressions Search through stored log messages Log up to 1 million log messages 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 8 of 15

Supported Standards as a SIP Proxy IETF RFC 2246: TLS Protocol Version 1.0 IETF RFC 2327 SDP: Session Description Protocol IETF RFC 2617 HTTP Authentication: Basic and Digest Access Authentication IETF RFC 2782: A DNS record route (RR) for specifying the location of services (DNS SRV) IETF RFC 2806: URLs for Telephone Calls IETF RFC 2976: The SIP INFO Method IETF RFC 3204: MIME media types for ISUP and QSIG Objects IETF RFC 3261 SIP: Session Initiation Protocol IETF RFC 3262: Reliability of Provisional Responses in the Session Initiation Protocol (SIP) IETF RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers IETF RFC 3264: An Offer/Answer Model with the Session Description Protocol (SDP) IETF RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification IETF RFC 3311: The Session Initiation Protocol (SIP) UPDATE Method IETF RFC 3325: Private Extensions to the SIP for Asserted Identity within Trusted Networks IETF RFC 3326: The Reason Header Field for the Session Initiation Protocol (SIP) IETF RFC 3515: The Session Initiation Protocol (SIP) Refer Method IETF RFC 3665: Session Initiation Protocol (SIP) Basic Call Flow Examples IETF RFC 3666: Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows IETF RFC 3725: Best Current Practices for Third-Party Call Control (3PCC) in the SIP IETF RFC 3842: A Message Summary and Message-Waiting Indication Event Package for the SessionInitiation Protocol (SIP) IETF RFC 3856: A Presence Event Package for the Session Initiation Protocol (SIP) IETF RFC 3891: The Session Initiation Protocol (SIP) "Replaces" Header IETF RFC 3892: The Session Initiation Protocol (SIP) Referred-By Mechanism IETF RFC 4480 RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE)OrderingThe Cisco Unified SIP Proxy (USP) Version 9.0 introduces a major enhancement in the ordering and licensingprocesses compared to prior versions. This major enhancement is the introduction of Cisco Smart Licensing as themechanism for ordering, enabling, and tracking the software licensing associated with Cisco USP.Cisco Smart Licensing is a licensing innovation that is being applied to a wide range of Cisco software products, both those based on Cisco IOS Software and those that aren’t, in order to achieve a greater level of licensingconsistency and improve the overall user experience for Cisco customers. For more information about Cisco SmartLicensing, please visit: http://www.cisco.com/c/en/us/products/abt sw.html. 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 9 of 15

With the introduction of Cisco Smart Licensing as part of Cisco USP Version 9.0, the ordering for Cisco USP isgreatly simplified. You need only three Cisco USP Smart Licensing product IDs (PIDs), as shown in Table 1.Table 1.Cisco Unified SIP Proxy Version 9.0 Software Licensing Product IDsPart NumberDescriptionMinimum Version of Cisco UnifiedSIP Proxy Software RequiredL-CUSP-SL-100 Cisco Unified SIP Proxy version 9.0 licensed for 100 SIPRequests per second (CPS) processing9.0.0L-CUSP-SL-30 Cisco Unified SIP Proxy version 9.0 licensed for 30 SIPRequests per second (CPS) processing9.0.0L-CUSP-SL-10 Cisco Unified SIP Proxy version 9.0 licensed for 10 SIPRequests per second (CPS) processing9.0.0Some of the beneficial aspects of these Cisco USP Smart Licensing PIDs include: They are transferable: These licenses can be moved between Cisco USP Version 9.0 virtual platforms asneeded to support your SIP network deployment model. Furthermore, if these licenses are initially installedon a Cisco UCS E-Series virtualized server platform, they can be transferred to a Cisco UCS B-Seriesvirtualized server platform at any time without any license upgrade or transfer fee. They are additive: You don’t need to purchase confusing licensing upgrade PIDs, as required in priorversions. If you initially order the 100 SIP Requests per second (RPS) Cisco USP Smart Licensing PID, buteventually need a higher level of CPS licensing, such as 200 CPS, then you can order an additional 100CPS Smart Licensing PIDs, for a total of 200 CPS Cisco USP Licenses. They are incremental: You can increase CPS scale by increments of 10 CPS on any Cisco USP Version 9.0virtual platform up to the full operating capacity of the platform.In summary, the Cisco USP Smart Licensing PIDs provide dramatic improvements in the flexibility of Cisco USPlicensing that have not been possible previously.If you are purchasing Cisco USP for the first time, Cisco recommends that you acquire and deploy the newvirtualized Cisco USP Version 9.0, because this version (and future Cisco USP versions) is where new Cisco USPfeatures will be added. Previous Cisco USP versions running natively on the Cisco Services-Ready Engine (SRE)(described in the next section) will be supported with respect to fixing product defects (bug fixes) only, and no newfeature enhancements will be made.Ordering for Existing Customers with Versions Earlier than 9.0Cisco will continue to support Cisco USP versions prior to 9.0 running natively on the Cisco SRE, but only for fixingproduct defects, not for any new feature enhancements. Therefore, you will need to transition to Cisco USPVersion 9.0 to gain the newest features and functions. If you are an existing Cisco USP user and transition yourinstallations by September 2016, Cisco will provide the replacement Cisco USP licenses (based on SmartLicensing, as described previously) at no charge. If you are unable to transition by September 2016, Ciscoreserves the right to charge for the new Cisco USP Version 9.0 Smart Licensing as per the terms of existing CiscoUSP licensing.User self-server migration of existing Cisco USP 8.0 SWIFT licenses to Cisco USP 9.0 Smart Licenses will besupported in the Cisco Smart Licensing Portal after June 2015. Existing users who have an urgency to migrate thelicenses prior to June 2015 can contact the Cisco USP Product Management team @ [email protected] with relevant information. 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 10 of 15

Cisco Software Support ServiceFor all customers who either purchase Cisco USP Version 9.0 as a new user or transition to Cisco USP Version9.0 from a previous version, Cisco will require the purchase of Cisco Software Support Service (SWSS) contractsto receive both technical support and new version enhancements. Information regarding SWSS contracts for CiscoUSP v9.0 will be posted by March 31, 2015, at the SWSS partner and customer websites, as follows: SWSS Partner website SWSS Customer website SWSS Disti SWSS Support GuideOrdering Cisco Unified SIP Proxy with Cisco Services-Ready EngineAlthough Cisco Unified SIP Proxy will remain available on the SRE blade as a nonvirtualized software license, itwill not include support for Cisco Unified SIP Proxy Version 9.0 or later. If you want ongoing softwareenhancements for Cisco USP, you must transition to Cisco USP Version 9.0 running on the Cisco UCS serverplatforms.Cisco Unified SIP Proxy on the SRE is supported on specific Cisco ISR platforms, as explained in Tables 2 and 3.Table 2.Supported ISR Platforms for Cisco Unified SIP Proxy Version 8.5.0 and Earlier on SRE Blade for ISR G2 RoutersPart NumberDescriptionMinimum Version of Cisco Unified SIP Proxy SoftwareRequiredSM-SRE-700-K9Cisco Service Ready Engine 700 Service Module8.5.1SM-SRE-900-K9Cisco Service Ready Engine 900 Service Module8.5.1Table 3.Cisco Unified SIP Proxy Version 8.5.0 and Earlier ISR Platform Support for SRE ModulePart NumberCisco ISR PlatformCisco 2911 and 2921Cisco 2951 and3900Cisco 3900ECisco NoMinimum Cisco IOS Softwareversion on ISR15.0(1)M15.1(1)TNot applicableCisco Unified SIP Proxy on the SRE platform does not use Cisco Smart Licensing, but employs a counted featurelicense based on the maximum number of new incoming SIP requests per second. Requests that belong to anexisting dialog, including SIP responses, are not counted. Refer to Table 4 for Cisco Unified SIP Proxy SIPrequests per second supported on the SRE modules.Table 4.Cisco Unified SIP Proxy Licenses Supported on SRE ModulesSIP Requests per esYes100YesYes200NoYes 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 11 of 15

Refer to Tables 5, 6, and 7 for the Cisco Unified SIP Proxy feature licenses available for the SRE modules.Table 5.Cisco Unified SIP Proxy Feature Licenses - Used for Preinstall on SRE Shipments from the FactoryPart NumberDescriptionFL-CUSP-2Cisco USP Feature License for 2 SIP requests/secondFL-CUSP-10Cisco USP Feature License for 10 SIP requests/secondFL-CUSP-30Cisco USP Feature License for 30 SIP requests/secondFL-CUSP-100Cisco USP Feature License for 100 SIP requests/secondFL-CUSP-200Cisco USP Feature License for 200 SIP requests/secondNote:The licensed number of requests/second refers to new incoming SIP requests. Requests that belong to anexisting dialog, including SIP responses, are not counted.Note:Product with part number FL-CUSP-200 is supported on product with part number SM-SRE-900-K9 only.A Cisco Unified SIP Proxy license can be added to an SRE (those with part number SM-SRE-700-K9 or SM-SRE900-K9) after shipment from the factory. In this case, a spare feature license is used. You can receive these sparelicenses through standard delivery or in an email message. Refer to Table 6 for Cisco Unified SIP Proxy spare feature licenses that you want to receive by standarddelivery. Refer to Table 7 for Cisco Unified SIP Proxy feature licenses that you want to receive through an emailmessage (e-delivery).Table 6.Cisco Unified SIP Proxy Spare Licenses for SRE Modules - Standard DeliveryPart NumberDescriptionFL-CUSP-2Cisco USP Feature License for 2 SIP requests/second SpareFL-CUSP-10Cisco USP Feature License for 10 SIP requests/second SpareFL-CUSP-30Cisco USP Feature License for 30 SIP requests/second SpareFL-CUSP-100Cisco USP Feature License for 100 SIP requests/second SpareFL-CUSP-200Cisco USP Feature License for 200 SIP requests/second SpareNote:Product with part number FL-CUSP-200 is supported on product with part number SM-SRE-900-K9 only.Table 7.Cisco Unified SIP Proxy Spare E-delivery Licenses for SRE ModulesPart NumberDescriptionL-FL-CUSP-2Cisco USP Feature License for 2 SIP requests/second Spare (e-delivery)L-FL-CUSP-10Cisco USP Feature License for 10 SIP requests/second (e-delivery)L-FL-CUSP-30Cisco USP Feature License for 30 SIP requests/second (e-delivery)L-FL-CUSP-100Cisco USP Feature License for 100 SIP requests/second (e-delivery)L-FL-CUSP-200Cisco USP Feature License for 200 SIP requests/second (e-delivery)Note:Part number L-FL-CUSP-200 is supported on part number SM-SRE-900-K9 only. 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.Page 12 of 15

Cisco Unified SIP Proxy supports upgrade from one license level to a higher one according to the capacity of themodule. Refer to Table 8 for Cisco Unified SIP Proxy upgrade licenses. In the case of a multilevel upgrade, forexample, to upgrade from 2 SIP requests per second to 100 SIP requests per second, you should order licenseswith part numbers FL-CUSP-2U10 and FL-CUSP-10U100 .Table 8.Cisco Unified SIP Proxy Upgrade LicensesPart NumberDescriptionFL-CUSP-2U10 Cisco USP Upgrade License for 2 to 10 SIP requests/secondFL-CUSP-10U30 Cisco USP Upgrade License for 10 to 30 SIP requests/secondFL-CUSP-10U100 Cisco USP Upgrade License for 10 to 100 SIP requests/secondFL-CUSP-30U100 Cisco USP Upgrade License for 30 to 100 SIP requests/secondFL-CUSP-100U200 Cisco USP Upgrade License for 100 to 200 SIP requests/secondNote:Product with part number FL-CUSP-100U200 is supported on product with part number SM-SRE-900-K9only.You can receive Cisco Unified SIP Proxy upgrade licenses in an email message. In order to receive upgradelicenses by e-delivery, you must choose an e-delivery type license. Refer to Table 9 for Cisco Unified SIP Proxye-delivery upgrade licenses.Table 9.Cisco Unified SIP Proxy Upgrade E-Delivery LicensesPart NumberDescriptionL-FL-CUSP-2U10 Cisco USP Upgrade License for 2 to 10 SIP requests/second (e-delivery)L-FL-CUSP-10U30 Cisco USP Upgrade License for 10 to 30 SIP requests/second (e-delivery)L-FL-CUSP-10U100 Cisco USP Upgrade License for 10 to 100 SIP requests/second (e-delivery)L-FL-CUSP-30U100 Cisco USP Upgrade License for 30 to 100 SIP requests/second (e-delivery)L-FL-Cisco USP-100U200 Cisco USP Upgrade License for 100 to 200 SIP requests/second (e-delivery)Note:Product with part number L-FL-CUSP-200 is supported on product with part number SM-SRE-900-K9only.PerformancePerformance is limited by both the number of incoming SIP requests specified in the feature license and moduleprocessing capability. With Cisco Unified SIP Proxy Versions 8.5 and later, you can operate Cisco Unified SIPProxy in standard (Record Route On) and lite (Record Route Off) modes.Standard mode (also referred to as RECORD ROUTE ON) supports the SIP requests-per-second performancedescribed by the feature license installed. For example, the Cisco USP Smart license (part number L-CUSP-SL100 ) authorizes 100 SIP requests per second. This standard mode is used in most deployments because i

SIP Trunk for Contact Center Cisco Unified Communications Manager and Cisco Unified Communications Manager Express SIP Aggregation Cisco USP can also simplify the network for an enterprise deploying a distributed call-control network using Cisco Unified Communications Manager at large sites and Cisco Unifi