vCUSP Webinar Slides - Cisco · •SIP trunk aggregation CUCM,CUCME,SP trunk, CVP •Flexible routing and normalization policies qCUSP offers the following benefits • Simplified

RASHMI RAJESH

vCUSP WEBINAR

08-MAY-2018

© 2018 CISCO and/or its affiliates. All right reserved . Cisco confidential

© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Confidential

q CUSP BASICS • Features and Benefits• What CUSP is not?• CUSP Deployments

q vCUSP • Features• Smart Licensing

q CUSP call Processing Model

q Monitoring

q Logging

q Troubleshooting

AGENDA


CUSP – BASIC

© 2018 CISCO and/or its affiliates. All right reserved . Cisco confidential


q CUSP simplifies call routing between SIP network elements

q CUSP provides the following features• Dial plan provisioning DNS, TLS • SIP trunk aggregation CUCM,CUCME,SP trunk, CVP• Flexible routing and normalization policies

q CUSP offers the following benefits • Simplified Management and Troubleshooting • Improved Reliability• Enhanced Scalability of SIP network • Improved Bandwidth Management

q Stateless call Routing and Signaling Interoperability

q Integrated solution in ISR or in VM form factor• Single box • Eliminates need for separate stand – done server

CUSP-Features and Benefits


• Not a B2BUA• Not a SIP Registrar• Routing policy is based on static configuration • Not dynamic SIP registration information • Not intended as an outbound proxy of endpoints

WHAT CUSP IS NOT?


CUSP DEPLOYMENTS



vCUSP


• CUSP 9.0 release adds virtualization support.

• VMware ESxi platform supported.

• Tested and validated on Cisco UCS-E and ucs platform only.

• Increases performance/ scalability of CUSP.

• vCUSP supports all features on SRE platform.

• Additional new features like smart licensing, enhanced lagging and TLS enhancements.

• Simplified installation and easy management.

• vCUSP supports provisioning using GUL and CLI.

vCUSP


q Virtual machine Requirements for UCS and UCS(E) Platform

CPU speed is greater than or equal to 2.99GHz

q Virtual Machine Requirements for Low Speed Cisco UCS and UCS(E) platform

CPU speed is less than 2.99GHz

vCUSP PERFORMANCE MATRIX

CPS 100 CPS 200 CPS 300 CPS 400 CPS

vCUSP

vCPU 2 4 4* 4*

RAM 4 GB 4 GB 4 GB 4 GBMB Resv 4096 4096 4096 4096

Disk 80 GB 80 GB 80 GB 80 GB

CPS 100 CPS 200 CPS 300 CPS 400 CPS

vCUSP

vCPU 2 4 6* 6*RAM 4 GB 4 GB 4 GB 4 GB

MB Resv 4096 4096 4096 4096

Disk 80 GB 80 GB 80 GB 80 GB


https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cusp/rel9_0/install/cuspinstall90.html

vCUSP INSTALLATION

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cusp/rel9_0/install/cuspinstall90.html


SMART LICENSING


• Cisco smart Software Licensing facilitates simplified and flexible deployment.

• It provides centralized and automated approach to manage licenses in your network.

• Removes need for PAKs (Product Activation Keys) and not hardware particular

• Must have a valid account in Cisco Smart Manager to configure Smart Licensing for CUSP.

• HTTP/HTTPS proxy mode deployment approach for current release.

SMART LICENSING


CONFIGURATIONqSmart Licensing on CUSP can be configured using• CLI• GUI

q CLI Based Configuration• Set the destination address• Set the HTTP(S) proxy address• Activate smart licensing with entitlement count• Register the device with smart licensing server

qGUI Based Configuration• Single step process for registration and entitlement.


CLI BASED CONFIGURATION CLI Based Configuration

§ Set the destination address

§ Set the Proxy address

§ Activate licensing agent

§ Register to smart licensing server

URL of the central licensing server

Optional parameter

HTTP(S) proxy server address

Requested entitlement count

Token Id generated in smart licensing server


GUI BASED CONFIGURATION

Option to enable or disable licensing agent

Requested Entitlement Count URL of the central licensing server



Optional parameter

HTTP(S) proxy server address


MESSAGE FLOW

vCUSPSmart

Software Manager

Registration Request

Device Certificate

MMI(Auth) Request

Authorization Response

Auth Renew (every 30 days)

Authorization Response


q Registration request• Token (hash generated for the customer account in smart manager)• Software Tag Identifier(CUSP software ID)• [UDI|SN# *] ( CUSP will generate 11 char random string for SN)• Certificate Signing Request

q Registration Message Response• PEM-encoded Device ID certificate• Product Instance Identifier• Cisco Signing Certificate• Signature [ signed by Cisco Signing Cert]

q Device ID Certificate• Common Name = GUID • SN=PID:<PID> SN:<SN>• Domain=hash(logical account name)• Validity Period = 360 days

SMART LICENSING MESSAGE CONTENTS


q MMI(Mother May I Request) Message

• Capability[ entitlement tags and counts]• Client Nonce • Product Instance Identifier• Cisco Signing Cert SN#• signature [MMI signed by ID cert]

q MMI Response

• Signature• Status• Expiry• Entitlement Tag

SMART LICENSING MESSAGE CONTENTS


q Show license smart udise-9-41-12-29# show license smart udi

UDI: UC_CUSP:VJQ6q77nQodSerial Number: VJQ6q77nQodProduct ID: UC_CUSP

q Show license smart summary se-10-104-45-238# show license smart summary

Smart Agent is Enabled: trueCurrent State of the Agent: UNIDENTIFIEDIs Evaluation Mode: trueRequested license count: 25Entitlement tag: CUSP-5-TAG-1Configured destination address:https://tools.cisco.com/its/service/oddce/services/DDCEServiceTransport Mode: TransportCallHomeEnforcement Mode: EvalEvaluation period : 1890

q Show license smart status application CUSPse-10-104-45-238# show license smart status application cusp

Smart Agent is Enabled: trueSmart Agent current state: UNIDENTIFIED

SHOW COMMANDS


qUnconfigured: Smart licensing is not configured/Disabled.

All call will be rejected in this state.

qUnidentified: CUSP is configured for licensing and not registered.

qRegistered: CUSP has successfully registered with Smart manager.

qAuthorized: CUSP entitlement request succeeds authorization, it is in

authorized state.

CUSP LICENSING STATES


qEval: When CUSP is unidentified state or registered state, enforcement mode is eval.

Evaluation period for 90 days by default.

q Incompliance: License count requested to the server is within the purchase limits

qOut of compliance: License count request is more than what is available purchased in

Cisco Smart Manager.Requested is honored here and calls are

allowed. There is no impact on call handling

qEval Expired: Evaluation period has expired. Calls will not be allowed in this mode.

qAuthorization Expired: Authorization period has expired. Call will not be allowed in

this mode.

CUSP ENFORCEMWNT MODES


LICENSING STATE MACHINE


CUSP CALL PROCESSING


CUSP CALL PROCESSING MODEL

IncomingRequest Pre-

Norm

alization

RoutingPost-

Norm

alization

SelectPolicy

SelectPolicy

SelectPolicy

OutgoingRequest

Route per pre-configured

policies

Modify header fields

Triggers

Modify header fields


qNETWORK

qROUTING

qNORMALIZATION

qPOLICY

qTIGGERS

KEY CONFIGURATION


q A logical collection of local interfaces which can be treated the same for general routing purposes.

q Each SIP network has following properties • Listen Points• SIP timers retransmission counts • Via headers stripping for topology

hiding.q SIP messages on arrival are associated

with the network on which the messages are received(Incoming network).

q Outgoing network is set as part of routing logic of WSP and the messages are forwarded sent on the set network.• Record Route

q Here is an example

sip listen Net-PSTN udp 14.128.100.169 5060

!sip network Net-PSTN standard

no non-invite-provisionalallow-connectionsretransmit-count invite-client-transaction 3retransmit-count invite-server-transaction 5retransmit-count non-invite-client-

transaction 3retransmit-timer T1 500retransmit-timer T2 4000retransmit-timer T4 5000retransmit-timer TU1 5000retransmit-timer TU2 32000retransmit-timer clientTn 64000retransmit-timer serverTn 64000tcp connection-setup-timeout 1000udp max-datagram-size 1500end network

!

NETWORK


q A trigger is set of conditions used in order to determine which routing and normalization policy is applied to an SIP request.

q A trigger condition defines matching rules against certain headers or fields within as SIP message, network and transport type CUDP,TCP,TLS(Transport Layer Security).

q A trigger is evaluated as either true or false for each received request.

q If the condition is true, then preset behaviors are invoked.

q The AND operation is achieved by specifying headers or fields in a single trigger condition command.

q The OR operation is achieved with several trigger-condition, each identified by a sequence number.

q The condition are evaluated in ascending order based on sequence number.

TRIGGERSq Here is an example

trigger condition TC-from-CUCMsequence 1in-network Net-CUCMmethod INVITEend sequence

sequence 2in-network Net-PSTNlocal-port 5060end sequence

end trigger condition


q Each routing policy is expressed as a sequence of step and each is specified in order to ‘perform a lookup in a table.

q CUSP will order execute each step in order• Each step has a selectable key• If the step produces a route, that route is used.• If the step results in no match, the next step is tried.

q Multi-layer route advance within a route group with configurable failover SIP response codes.q Table based routing is used

• Support for large number of routes in a table(10000+)• Routes in a table can be populated via CLI or a route file.• Lookup keys : Calling and called number, carrier codes, location routing numbers etc.• Flexible rule matching (Longest prefix matching etc.)

ROUTING LOOKUP POLICY


CUSP ROUTING FLOW


q Route group specifies multiple routes a SIP request can take.

q Route advance between elements can be controlled on SIP response received(failover response).

q CUSP supports there actions within a RG

Ø Time based routing

• Route SIP requests according to time of day.

Ø Percentage / Weight-based routing

• Allows for load balancing based on preset weight.

• Priority / least cost routing based on q-value.

CUSP ROUTE GROUP FLOW


CUSP ROUTE GROUP FLOW


q Server group is a cluster of downstream elements that CUSP treats as a single logical.

q Server group members are homogenous.

q Requests routed to a server group

• Load-balancing amongst members.

• Members health monitoring(ping)

• Alarming on member failure.

• Automatic restoration on member recovery.

q Priority of each member(element) in a server group is assigned by q-value(0.0 - 0.1)

CUSP SERVER GROUP FLOW


CUSP SERVER GROUP FLOW EXAMPLE !server-group sip group SG-CUCM.ajeet.com Net-CUCMelement ip-address 14.128.64.191 5060 udp q-value 1.0 weight 50element ip-address 14.128.64.192 5060 udp q-value 1.0 weight 100failover-resp-codes 503lbtype globalpingend server-group

!


q SIP headers are normalization based on a configure policy

q Normalization involves the addition, modification and removal of SIP headers

q Solve incompatibilities or interoperation issues between different SIP severs.

q Normalization is performed before or/and after routing logic is executed (pre and post Normalization)

q Normalization logic• Normalization policy : Defines changes to be made to SIP message • Normalization Triggers : Define how a normalization policy is chosen

q Policy consists of steps each steps specifying a single change to the SIP message.

EXAMPLES:• Number normalization • TEL/SIP concessions• Domain conversions • Regular-expression processing

NORMALIZATION POLICY


qPre Normalization is the modification of SIP message before routing decisions.

qPre-Normalization example :• Number Normalization

CUSP PRE NORMALIZATION !trigger pre-normalization sequence 1 policy CUCM-Prefix-408 condition TC-from-CUCM!policy normalization CUCM-Prefix-408uri-component update request-uri user 2022222

4082022222end policy

!


qPost Normalization is the modification of SIP messages before they are forwarded to the next hop.

qPost Normalization example• Number Normalization

q In this example, the user portion of the SIP URI Request is replaced by 85224044444 if the value that exists is 4444:

CUSP POST-NORMALIZATION

trigger post-normalization sequence 1 policy UC520-Four-to-Fullcondition TC-UC520-to-PSTN!policy normalization UC520-Four-to-Fulluri-component update request-uri user 4444 85224044444end policy!


MONITORING


• Ping mechanism in CUSP help monitoring the element status • Methods available for Element Monitoring

§ OPTIONS (default)§ PING§ INFO

• PING TYPE§ Reactive PING§ Proactive PING§ Adaptive PING

ELEMENT MONITORING


• Reactive PING : PINGING is performed only to down elements at an

interval set by us.

• Proactive PING : PINGING is performed to both up and down elements at

the same interval.

• Adaptive PING : PINGING is performed to both up and down elements at

different intervals.


You also need to know to enable PING Mechanisms

• Network : Name of the SIP PING network

• Port : The VDP port that listens for responses to the SIP pings valid range is 1024 to 65535

Default value is 4000

CAUTION: Port number should be different from server’s SIP listen point

• Up Interval : Specifies the consecution ping interval for up element

Default value is 5000 milliseconds

• Down Interval : Specifies the consecution ping interval for down elements


• PING Timeout : Specifies the maximum time before the ping is considered unsuccessful

Minimum value allowed is 0



q Enable SIP Ping at global level through GUI

configure> server group> general setting

CONFIGURATION THROUGH GUI


• Ensure ‘Pinging allowed’ checked


• Configure PING server group for the corresponding network

choose configure >servergroup > SIP Ping

• Click Add

• Configure the network , SIP method, Ping type and Interval parameters

• Click Add


q Server-group sip global - ping • To enable global pinging for all SIP server group

Se-10-0-0(cusp-config)>server- group sip global ping

q Ping (SIP-server group)• To enable pinging for the server group

se-10-0-0(cusp-config)>server-group sip group’sg’se-10-0-0(cusp-config-sg)ping

q Server-group sip ping-options • To configure and enter SIP server group ping-options configuration mode.

se-10-0-0(cusp-config)server- group sip ping-option ‘network’ ‘ip-address’

CONFIGURATION THROUGH CLI


qMethod (SIP server group ping-optins)• To configure request method for SIP server group

se-10-0-0(cusp-config)>server-group sip-options ‘network’ ‘ip-address’se-10-0-0(cusp-config-ping)>method PING

q Ping –type• To configure PING-type and interval for a SIP server group

se-10-0-0(cusp-config)>server-group sip ping-options ‘network’ ‘ip-address’se-10-0-0(cusp-config-ping)>ping-type reactive 1000

q Time out• To configure the ping timeout interval for SIP server group

se-10-0-0(cusp-config)>server-group sip-ping-options ‘network’ ‘ip-address’se-10-0-0(cusp-config-ping)>timeout 500


SIP INFO• Configuration sample:

server-group sip group SG-CUCM Net-CUCMelement ip-address 172.16.184.120 5060 tcp q-value 1.0 weight 0element ip-address 172.16.184.121 5060 tcp q-value 1.0 weight 0failover-resp-codes 503lbtype globalpingend server-group!!server-group sip ping-options Net-CUCM 172.16.184.251 4000method INFOping-type adaptive 5000 5000timeout 500end ping!server-group sip global-ping

Message sample:DEBUG 2013.08.15 10:28:43:234 DsPings.PingThread - Sending adaptiveping to the up element Net-CUCM:172.16.184.121:5060:2 numTries=1[TCP/TLS Pinging Queue.0] DEBUG 2013.08.15 10:28:43:234 DsPings.DsPingsSipInterfaceImpl - Endpoint(Net-CUCM:172.16.184.121:5060:2 numTries=1): Sent TCP ping requestINFO sip:172.16.184.121:5060 SIP/2.0Via: SIP/2.0/TCP 172.16.184.251:4000;branch=z9hG4bK43TaRjR6f1ZqX45ctXM69g~~24Max-Forwards: 0To: pingTo <sip:[email protected]:5060>From: pingFrom <sip:[email protected]:4000>Contact: sip:[email protected]:4000Call-ID: 1376587723234@Net-CUCM:172.16.184.121:5060:2CSeq: 1 INFOContent-Length: 0


SIP PING • Configuration sample:

server-group sip group SG-CUCM Net-CUCMelement ip-address 172.16.184.120 5060 tcp q-value 1.0 weight 0element ip-address 172.16.184.121 5060 tcp q-value 1.0 weight 0failover-resp-codes 503lbtype globalpingend server-group!!server-group sip ping-options Net-CUCM 172.16.184.251 4000method PINGping-type adaptive 5000 5000timeout 500end ping!server-group sip global-ping

Message sample:

[TCP/TLS Pinging Queue.0] DEBUG 2013.08.15 10:45:05:191 DsPings.DsPingsSipInterfaceImpl -Endpoint(Net-CUCM:172.16.184.121:5060:2 numTries=0): Sent TCP ping requestPING sip:172.16.184.121:5060 SIP/2.0Via: SIP/2.0/TCP 172.16.184.251:4000;branch=z9hG4bK43TaRjR6f1ZqX45ctXM69g~~330Max-Forwards: 0To: pingTo <sip:[email protected]:5060>From: pingFrom <sip:[email protected]:4000>Contact: sip:[email protected]:4000Call-ID: 1376588705190@Net-CUCM:172.16.184.121:5060:2CSeq: 1 PINGContent-Length: 0


SIP OPTIONS • Configuration sample:

server-group sip group SG-CUCM Net-CUCMelement ip-address 172.16.184.120 5060 tcp q-value 1.0 weight 0element ip-address 172.16.184.121 5060 tcp q-value 1.0 weight 0failover-resp-codes 503lbtype globalpingend server-group!!server-group sip ping-options Net-CUCM 172.16.184.251 4000method OPTIONSping-type adaptive 5000 5000timeout 500end ping!server-group sip global-ping

Message sample:

[TCP/TLS Pinging Queue.0] DEBUG 2013.08.15 10:42:17:347 DsPings.DsPingsSipInterfaceImpl -Endpoint(Net-CUCM:172.16.184.121:5060:2 numTries=1): Sent TCP ping requestOPTIONS sip:172.16.184.121:5060 SIP/2.0Via: SIP/2.0/TCP 172.16.184.251:4000;branch=z9hG4bK43TaRjR6f1ZqX45ctXM69g~~279Max-Forwards: 0To: pingTo <sip:[email protected]:5060>From: pingFrom <sip:[email protected]:4000>Contact: sip:[email protected]:4000Call-ID: 1376588537347@Net-CUCM:172.16.184.121:5060:2CSeq: 1 OPTIONSContent-Length: 0


CUSP LOGGING


qCUSP has three different types of logging mechanisms• Trace Logs• SIP Logs• Peg counting

qDifferent set of information is captured for diagnosing issues.

qTurning any of these commands ON will have a performance hit.

qLogs and traces can be accessed by FTP.

LOGGING MECHANISMS


q Trace logs captures the proxy application level logging

q Trace enable is used to enable trace logging

q Level can be set for various categories

q The major levels of logging available in CUSP• Info : Brief history of the function calls• Debug : Verbose level of logging for troubleshooting issues.• Default : Error debugs. Default is equal to warn level tracing

q Show trace options will display the levels for each category

q File rotates every 10 MB

q CUSP now support 5GB of trace logging (on vCUSP).

but default – logging size is 200MB

q Location FIP ping to module pfs://cusp/log/trace

q “show trace log” will display the trace logs

q Trace logging steps• Enable trace logging through GUI and CLI• Trace log collection through GUI or CLI or from PFS (Public File System)

TRACE LOGGING


q From the GUI

1. Navigate to troubleshoot>trace

2. Check the Enable Tracing box

3. Set the level to debug for required components

4. Click update

ENABLE TRACE LOGS


q From the CLI

1. Execute the trace enable command CUSP (cusp)# trace enable

2. Set the trace level to debug for required component

3. Repeat the same command to enable for multiple components

4. Show trace options command show current trace setting


q FROM THE GUI

1. Navigate to troubleshoot>Log File

2. Select download Log File

TRACE LOG COLLECTION


q From the CLI1. Use show trace log to display the content of log

2. Press CTRL+C in order to break the scrolling 3. Use show trace log | p command for page-by-page content


q PFS is another way to collect the trace logs 1. Create a username and assign the PFS privilege to this user

2. Access this VRL with the above credentials 3. You can download log file from

ftp://<IP of CUSP>/cusp/log/trace/

FROM PUBLIC FILE SYSTEM (PFS)


qOff by default; logs all SIP message that go through the CUSP

qEnable SIP logging through (cusp-config)#sip logging.

qFile rotates every 10MB or every night

qLocation FIPing to module pfs://cusp/log/sipmsg/

qshow SIP message log will display the sip logs

SIP LOGGING


q To enable SIP message Logs • Navigate to troubleshoot >SIP message logs >controls

q To view SIP message logs • Navigate to troubleshoot >SIP message logs>search calls

ENABLE SIP MESSAGE LOGGING


CUSP (cusp) # trace logsize 5000 filecount 500

q LogSize: Total logsize in MB, minimum value in 200MB

maximum is 500MB

CUSP (cusp) # trace logsize ?

Default : Restore the default logsize 200MB

<200-500>: Logsize in MB, default 200MB (min),maximum value 500MB

Filecount: Number of file for the give total log size, default calculation is such that file size is 10MB (logsize/10)

CUSP (cusp) # trace logsize 5000 filecount ?

<200-500>: Number if trace file to be generated, more the number of file with less size (recommended 10MB for each file),better the performance

LOG STORAGE INFORMATION


qOff by default ;counts all response that go through the blade during a specified interval.

qMinimum interval for peg counting is 60 sec.

qFile rotates every 10MB or every night

qLocation FIPing to module pfs://cusp/log/pegcount

qshow sip peg- counting log will display the peg counting logs

SIP PEG-COUNTING


TROUBLESHOOTING


qCPU Graph Definitions for Cisco Unified SIP ProxyqCisco Unified SIP Proxy captures average and peak CPU utilization

data (with resolution in seconds) and updates the following graphs:• CPU per Second• CPU per Minute• CPU per Hour

TROUBLESHOOTING HIGH CPU ISSUES



qMajorly average CPU utilization on CUSP spikes during the following scenarios:• Calls Per Second (CPS) crossing the license limit• Tracing set to debug levels• GUI-based SIP logging• Network issues causing socket level exceptions in CUSP

HIGH CPU UTILIZATION SCENARIOR ON CUSP


q Calls Per Second (CPS) crossing the license limit.

• If CPS crosses the license limit condition, following set of information is seen in default trace logs:• license.LicenseChecker – Average Request Rate exceeded the licensed limit of 100.0/sec• license.LicenseChecker – Current Average Request Rate: 123.24/sec• license.LicenseChecker – Request Rate calculated for last 300 seconds divided into 10 blocks of 30 seconds each• license.LicenseChecker – 9019 0 0 0 9239 0 0 6183 0 11242 à Calls received in 30 seconds windows• license.LicenseChecker – Dropping requests until the average request rate is 100.0 or less

q Tracing set to debug levels

Trace logging set to debug level on CUSP can lead to high CPU utilization (due to logging activity) for the following components:• Proxy-core• Proxy-transactions• Routing• Base-Tracing

q GUI-based SIP logging

• Enabling the logging from GUI store logs in Postgres database• Recommend not using GUI based SIP logging since database operations on CPU are intensive

q Network issues causing socket level exceptions in CUSP

Some of the commonly seen cases where CPU utilization is high with CPS less than the minimum value are:• Socket level exceptions related to remote element connections• Network connection flapping and network elements going up and down• Remote element not responding in the same rate as it is receiving requests

• For example, DsSipLlApi.Connection - Exception while accessing the socket channel: closing it and java.io.IOException: socket read error.


q Symptoms

In genuine cases where average CPU goes high, the following behavior is expected from CUSP:• No response to incoming requests• Delay in call routing

q Debugging CUSP with High CPU Utilization

No debugs for handling high CPU utilization. To verify • Check the performance data using “show performance-data cps”• Check short duration packet capture on CUSP• Check the default trace logs on CUSP

q Limitations• Information on process-level CPU utilization on CUSP is not available. • No existing TCP or TLS connection to understand any hung or open connections• Enabling debug traces lead to CPU issues• SIP logging enablement from CLI and GUI is not in sync and there is no option for user to

enable PFS-based SIP logging from GUI. Refer to DDTS (CSCus98850) for more details.


Q & A


THANK YOU

Documents

vCUSP Webinar Slides - Cisco · •SIP trunk aggregation CUCM,CUCME,SP trunk, CVP •Flexible routing and normalization policies qCUSP offers the following benefits • Simplified