Use this task flow to configure local gateways for your Webex Calling deployment. The steps that follow are performed on the CLI interface itself. The trunk between the local gateway and Webex Calling is always secured using SIP TLS transport and SRTP for media between Local gateway and the Webex Calling Access SBC.
Before you begin
-
Meet the local gateway requirements for Webex Calling.
-
Create a local gateway in Control Hub.
-
The configuration guidelines provided in this document assume that a dedicated local gateway platform is in place with no existing voice configuration. If an existing PSTN gateway or CUBE enterprise deployment is being modified to also use the local gateway function for Webex Calling, pay careful attention to the configuration applied and make sure existing call flows and functionality are not interrupted as a result of changes that you make.
Command or Action | Purpose | |
---|---|---|
1 |
Parameter Mapping Between Cisco Webex Control Hub and Cisco Unified Border Element |
Use this table as a reference for the parameters that come from Control Hub and where they map onto the local gateway. |
2 |
Implement these steps as a common global configuration for the local gateway. The configuration includes baseline platform configuration and a trust pool update. |
|
3 | ||
4 |
Choose one, depending on your deployment: |
Call Routing on the local gateway is based on the Webex Calling deployment option that you chose. This section assumes that IP PSTN termination is on the same platform as the local gateway. The configuration that follows is for one of these options on the local gateway:
|
Control Hub |
Local Gateway |
---|---|
Registrar Domain: Control Hub should parse the domain from the LinePort that is received from UCAPI. example.com |
registrar example.com |
Trunk Group OTG/DTG |
sip profiles: rule <rule-number> request ANY sip-header From modify ">" ";otg=otgDtgId>" |
Line/Port user@example.com |
number: user |
Outbound Proxy |
outbound proxy (DNS name – SRV of the Access SBC) |
SIP Username |
username |
SIP Password |
password |
Before you begin
-
Ensure that baseline platform configuration such as NTPs, ACLs, enable passwords, primary password, IP routing, IP Addresses, and so on are configured according to your organization's policies and procedures.
-
Latest of IOS-XE 16.12 or IOS-XE 17.3 required for all LGW deployments.
1 |
Ensure that any layer 3 interfaces have valid and routable IP addresses assigned:
|
2 |
You must preconfigure a master key for the password using the commands shown below before it can be used in the credentials and shared secrets. Type 6 passwords are encrypted using AES cypher and user-defined master key.
|
3 |
Configure IP Name Server to enable DNS lookup and ensure it is reachable by pinging it:
|
4 |
Enable TLS 1.2 Exclusivity and a default Dummy Trustpoint:
|
5 |
Update Local Gateway Trustpool: The default trustpool bundle does not include the “DigiCert Root CA” certificate needed for validating the server side certificate during TLS connection establishment to Webex Calling. The trustpool bundle must be updated by downloading the latest “Cisco Trusted Core Root Bundle” from http://www.cisco.com/security/pki/. |
Before you begin
Ensure that you completed the steps in Control Hub to create a location and add a local gateway. In the example local gateway shown here, the information was obtained from Control Hub.
1 |
Enter these commands to turn on the local gateway application (see the Port Reference Information for Cisco Webex Calling for the latest IP subnets that need to be added to the trust list):
Explanation of commands:
|
||||
2 |
Configure “SIP Profile 200”.
These rules are Explanation of commands:
|
||||
3 |
Configure Codec Profile, STUN definition, and SRTP Crypto suite.
Explanation of commands:
|
||||
4 |
Map Control Hub parameters to local gateway configuration: Webex Calling is added as a tenant within the local gateway. The configuration required to register the local gateway is defined under voice class tenant 200. You must obtain the elements of that configuration from the local gateway administration page within the Control Hub as shown in this screenshot. This is an example to display what fields map to the respective local gateway CLI. Tenant 200 is then applied to all the Webex Calling facing dial-peers (2xx tag) within the local gateway configuration. The voice class tenant feature allows for grouping and configuring of SIP trunk parameters otherwise done under voice service voip and sip-ua. When a tenant is configured and applied under a dial-peer, the IOS-XE configurations are applied in the following order of preference:
|
||||
5 |
Configure voice class tenant 200 to enable Trunk Registration from LGW to Webex Calling based on the parameters you've obtained from Control Hub:
Explanation of commands:
|
After tenant 200 is defined within the local gateway and a SIP VoIP dial-peer is configured, the gateway then initiates a TLS connection towards Webex Calling, at which point the Access SBC presents its certificate to the local gateway. The local gateway validates the Webex Calling Access SBC certificate using the CA root bundle updated earlier. A persistent TLS session is established between the local gateway and Webex Calling Access SBC. The Local gateway then sends a REGISTER to the Access SBC which is challenged. Registration AOR is number@domain. The number is taken from credentials “number” parameter and domain from the “registrar dns:<fqdn>”. When the Registration is challenged, the username, password and realm parameters from credentials are used to build the header and sip-profile 200 converts SIPS URL back to SIP. Registration is successful once 200 OK is received from the Access SBC.
The following configuration on the local gateway is required for this deployment option:
-
Voice class tenants—First we will create additional tenants for dial-peers facing ITSP similar to tenant 200 that we created for Webex Calling facing dial-peers.
-
Voice class URIs—Patterns defining host IP addresses/ports for various trunks terminating on Local Gateway: Webex Calling to LGW; and PSTN SIP trunk termination on LGW.
-
Outbound dial-peers—To route outbound call legs from LGW to ITSP SIP trunk and Webex Calling.
-
Voice class DPG—Target outbound dial-peers invoked from an inbound dial-peer.
-
Inbound dial-peers—To accept inbound call legs from ITSP and Webex Calling.
Configuration in this section can be used for either partner-hosted local gateway setup, as shown below, or local customer site gateway.
1 |
Configure the following voice class tenants: |
2 |
Configure the following voice class URI: |
3 |
Configure the following outbound dial peers: |
4 |
Configure the following dial-peer groups (DPG): |
5 |
Configure the following Inbound dial-peers: |
- PSTN to Webex Calling
-
All incoming IP PSTN call legs on the local gateway are matched on dial-peer 100 as it defines a match criteria for the VIA header with the IP PSTN’s IP address. Outbound dial-peer selection is dictated by DPG 200 that directly invokes outgoing dial-peer 200201, which has the Webex Calling server listed as the target destination.
- Webex Calling to PSTN
-
All incoming Webex Calling call legs on the local gateway are matched on dial-peer 200201 as it meets a match criteria for the REQUEST URI header pattern with the TrunkGroup OTG/DTG parameter, unique to this local gateway deployment. Outbound dial-peer selection is dictated by DPG 100 that directly invokes outgoing dial-peer 101, which has the IP PSTN IP address listed as the target destination.
For this deployment option, the following configuration on the local gateway is required:
-
Voice class tenants—You must create additional tenants for dial-peers facing Unified CM and ITSP, similar to tenant 200 that we created for Webex Calling facing dial-peers.
-
Voice class URIs—Patterns defining host IP addresses/ports for various trunks terminating on the LGW: from Unified CM to LGW for PSTN destinations; Unified CM to LGW for Webex Calling destinations; Webex Calling to LGW; and PSTN SIP trunk termination on LGW.
-
Voice class server-group—Target IP addresses/ports for outbound trunks from LGW to Unified CM, LGW to Webex Calling, and LGW to PSTN SIP trunk.
-
Outbound dial-peers—To route outbound call legs from LGW to Unified CM, ITSP SIP trunk, and/or Webex Calling.
-
Voice class DPG—Target outbound dial-peer(s) invoked from an inbound dial-peer.
-
Inbound dial-peers —To accept inbound call legs from Unified CM, ITSP, and/or Webex Calling.
1 |
Configure the following voice class tenants: |
2 |
Configure the following voice class URIs: |
3 |
Configure the following voice class server-groups: |
4 |
Configure the following outbound dial-peers: |
5 |
Configure the following DPG: |
6 |
Configure the following inbound dial-peers: |
IP PSTN to Unified CM PSTN Trunk
Webex Calling Platform to Unified CM Webex Calling Trunk
Unified CM PSTN Trunk to IP PSTN
Unified CM Webex Calling Trunk to Webex Calling Platform
Diagnostic Signatures (DS) proactively detects commonly observed issues in the IOS XE based local gateway and generates email, syslog or terminal message notification of the event. You can also install the DS to automate diagnostics data collection and transfer collected data to the Cisco TAC case to accelerate resolution time.
Diagnostic Signatures (DS) are XML files that contain information about problem trigger events and actions to be taken to inform, troubleshoot and remediate the issue. The problem detection logic is defined using syslog messages, SNMP events and through periodic monitoring of specific show command outputs. The action types include collecting show command outputs, generating a consolidated log file and uploading the file to a user provided network location such as HTTPS, SCP, FTP server. DS files are authored by TAC engineers and are digitally signed for integrity protection. Each DS file has a unique numerical ID assigned by the system. Diagnostic Signatures Lookup Tool (DSLT) is a single source to find applicable signatures for monitoring and troubleshooting a variety of problems.
Before you begin:
-
Do not edit the DS file downloaded from DSLT. Modified files will fail installation due to integrity check error.
-
A Simple Mail Transfer Protocol (SMTP) server is required for the local gateway to send out email notifications.
-
Ensure that the local gateway is running IOS XE 17.3.2 or higher if you wish to use secure SMTP server for email notifications.
Prerequisites
Local Gateway running IOS XE 17.3.2 or higher
-
Diagnostic Signatures is enabled by default.
-
Configure the secure email server to be used to send proactive notification if the device is running IOS XE 17.3.2 or higher.
LocalGateway#configure terminal LocalGateway(config)#call-home LocalGateway(cfg-call-home)#mail-server <username>:<pwd>@<email server> priority 1 secure tls LocalGateway(config)#end
-
Configure the environment variable ds_email with the email address of the administrator to be notified.
LocalGateway#configure terminal LoclGateway(config)#call-home LocalGateway(cfg-call-home)#diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_email <email address> LocalGateway(config)#end
Local Gateway running IOS XE 16.11.1 or higher
-
Diagnostic Signatures is enabled by default.
-
Configure the email server to be used to send proactive notifications if the device is running a version earlier than 17.3.2.
LocalGateway#configure terminal LocalGateway(config)#call-home LocalGateway(cfg-call-home)#mail-server <email server> priority 1 LocalGateway(config)#end
-
Configure the environment variable ds_email with the email address of the administrator to be notified.
LocalGateway#configure terminal LoclGateway(config)#call-home LocalGateway(cfg-call-home)#diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_email <email address> LocalGateway(config)#end
Local Gateway running 16.9.x version
-
Enter the following commands to enable Diagnostic Signatures.
LocalGateway#configure terminal LocalGateway(config)#call-home reporting contact-email-addr sch-smart-licensing@cisco.com LocalGateway(config)#end
-
Configure the email server to be used to send proactive notifications if the device is running a version earlier than 17.3.2.
LocalGateway#configure terminal LocalGateway(config)#call-home LocalGateway(cfg-call-home)#mail-server <email server> priority 1 LocalGateway(config)#end
-
Configure the environment variable ds_email with the email address of the administrator to be notified.
LocalGateway#configure terminal LoclGateway(config)#call-home LocalGateway(cfg-call-home)#diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_email <email address> LocalGateway(config)#end
The following shows an example configuration of a local gateway running IOS XE 17.3.2 to send the proactive notifications to tacfaststart@gmail.com using Gmail as the secure SMTP server:
call-home
mail-server tacfaststart:password@smtp.gmail.com priority 1 secure tls
diagnostic-signature
environment ds_email "tacfaststart@gmail.com"
Local gateway running IOS XE software is not a typical web-based Gmail client that supports OAuth, so we need to configure a specific Gmail account setting and provide specific permission to have the email from the device processed correctly: |
-
Go to Less secure app access setting.
and turn on -
Answer “Yes, it was me” when you receive an email from Gmail stating “Google prevented someone from signing in to your account using a non-Google app.”
Install Diagnostic Signatures for Proactive Monitoring
Monitoring High CPU Utilization
This DS tracks 5 seconds CPU utilization using the SNMP OID 1.3.6.1.4.1.9.2.1.56. When the utilization reaches 75% or more, it will disable all debugs and uninstall all diagnostic signatures installed in the local gateway. Use these steps below to install the signature.
-
Ensure SNMP is enabled using the command show snmp. If it is not enabled, configure the “snmp-server manager” command.
LocalGateway# show snmp %SNMP agent not enabled LocalGateway# LocalGateway# LocalGateway# config t LocalGateway(config)# snmp-server manager LocalGateway(config)#end LocalGateway# LocalGateway# show snmp Chassis: ABCDEFGHIGK 149655 SNMP packets input 0 Bad SNMP version errors 1 Unknown community name 0 Illegal operation for community name supplied 0 Encoding errors 37763 Number of requested variables 2 Number of altered variables 34560 Get-request PDUs 138 Get-next PDUs 2 Set-request PDUs 0 Input queue packet drops (Maximum queue size 1000) 158277 SNMP packets output 0 Too big errors (Maximum packet size 1500) 20 No such name errors 0 Bad values errors 0 General errors 7998 Response PDUs 10280 Trap PDUs Packets currently in SNMP process input queue: 0 SNMP global trap: enabled .... .... LocalGateway#
-
Download DS 64224 using the following drop-down options in Diagnostic Signatures Lookup Tool:
LocalGateway# copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:
Field Name
Field Value
Platform
Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series
Product
CUBE Enterprise in Webex Calling Solution
Problem Scope
Performance
Problem Type
High CPU Utilization with Email Notification
-
Copy the DS XML file to the Local Gateway flash.
LocalGateway# copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:
The following shows an example of copying the file from a FTP server to the Local Gateway.
LocalGateway# copy ftp://user:pwd@192.0.2.12/DS_64224.xml bootflash: Accessing ftp://*:*@ 192.0.2.12/DS_64224.xml...! [OK - 3571/4096 bytes] 3571 bytes copied in 0.064 secs (55797 bytes/sec) LocalGateway #
-
Install the DS XML file in the Local Gateway.
LocalGateway# call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success LocalGateway#
-
Verify that the signature is successfully installed using show call-home diagnostic-signature. The status column should have a “registered” value.
LocalGateway# show call-home diagnostic-signature Current diagnostic-signature settings: Diagnostic-signature: enabled Profile: CiscoTAC-1 (status: ACTIVE) Downloading URL(s): https://tools.cisco.com/its/service/oddce/services/DDCEService Environment variable: ds_email: username@gmail.com
Download DSes:
DS ID
DS Name
Revision
Status
Last Update (GMT+00:00)
64224
DS_LGW_CPU_MON75
0.0.10
Registered
2020-11-07 22:05:33
LocalGateway#
When triggered, this signature uninstalls all running DSs including itself. If required, please reinstall DS 64224 to continue monitoring high CPU utilization on the local gateway.
Monitoring SIP Trunk Registration
This DS checks for un-registration of a local gateway SIP Trunk with Cisco Webex Calling cloud every 60 seconds. Once the un-registration event is detected, it generates an email and syslog notification and uninstalls itself after two un-registration occurrences. Please use the steps below to install the signature.
-
Download DS 64117 using the following drop-down options in Diagnostic Signatures Lookup Tool:
Field Name
Field Value
Platform
Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series
Product
CUBE Enterprise in Webex Calling Solution
Problem Scope
SIP-SIP
Problem Type
SIP Trunk Un-registration with Email Notification
-
Copy the DS XML file to the Local Gateway.
LocalGateway# copy ftp://username:password@<server name or ip>/DS_64117.xml bootflash:
-
Install the DS XML file in the Local Gateway.
LocalGateway# call-home diagnostic-signature load DS_64117.xml Load file DS_64117.xml success LocalGateway#
-
Verify that the signature is successfully installed using show call-home diagnostic-signature. The status column should have a “registered” value.
Monitoring Abnormal Call Disconnects
This DS uses SNMP polling every 10 minutes to detect abnormal call disconnect with SIP errors 403, 488 and 503. If the error count increment is greater than or equal to 5 from the last poll, it will generate a syslog and email notification. Please use the steps below to install the signature.
-
Check whether SNMP is enabled using the command show snmp. If it is not enabled, configure the “snmp-server manager” command.
LocalGateway# show snmp %SNMP agent not enabled LocalGateway# LocalGateway# LocalGateway# config t LocalGateway(config)# snmp-server manager LocalGateway(config)#end LocalGateway# LocalGateway# show snmp Chassis: ABCDEFGHIGK 149655 SNMP packets input 0 Bad SNMP version errors 1 Unknown community name 0 Illegal operation for community name supplied 0 Encoding errors 37763 Number of requested variables 2 Number of altered variables 34560 Get-request PDUs 138 Get-next PDUs 2 Set-request PDUs 0 Input queue packet drops (Maximum queue size 1000) 158277 SNMP packets output 0 Too big errors (Maximum packet size 1500) 20 No such name errors 0 Bad values errors 0 General errors 7998 Response PDUs 10280 Trap PDUs Packets currently in SNMP process input queue: 0 SNMP global trap: enabled .... .... LocalGateway#
-
Download DS 65221 using the following options in Diagnostic Signatures Lookup Tool:
Field Name
Field Value
Platform
Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series
Product
CUBE Enterprise in Webex Calling Solution
Problem Scope
Performance
Problem Type
SIP abnormal call disconnect detection with Email and Syslog Notification
-
Copy the DS XML file to the Local Gateway.
LocalGateway# copy ftp://username:password@<server name or ip>/DS_65221.xml bootflash:
-
Install the DS XML file in the Local Gateway.
LocalGateway# call-home diagnostic-signature load DS_65221.xml Load file DS_65221.xml success LocalGateway#
-
Verify that the signature is successfully installed using show call-home diagnostic-signature. The status column should have a “registered” value.
Install Diagnostic Signatures to Troubleshoot a Problem
Diagnostic Signatures (DS) can also be used to resolve issues quickly. Cisco TAC engineers have authored several signatures that enable the necessary debugs required to troubleshoot a given problem, detect the problem occurrence, collect the right set of diagnostic data and transfer the data automatically to the Cisco TAC case. This eliminates the need to manually check for the problem occurrence and makes troubleshooting of intermittent and transient issues a lot easier.
You can use the Diagnostic Signatures Lookup Tool to find the applicable signatures and install them to self-solve a given issue or you can install the signature recommended by the TAC engineer as part of the support engagement.
Here is an example of how to find and install a DS to detect the occurrence “%VOICE_IEC-3-GW: CCAPI: Internal Error (call spike threshold): IEC=1.1.181.1.29.0" syslog and automate diagnostic data collection using the steps shown below.
-
Configure an additional DS environment variable ds_fsurl_prefix which is the CiscoTAC file server path (cxd.cisco.com) to which the collected diagnostics data are uploaded. The username in the file path is the case number and the password is the file upload token which can be retrieved from Support Case Manager as shown below. The file upload token can be generated in the Attachments section of the Support Case Manager, as needed.
LocalGateway#configure terminal LocalGateway(config)#call-home LocalGateway(cfg-call-home)#diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_fsurl_prefix "scp://<case number>:<file upload token>@cxd.cisco.com" LocalGateway(config)#end
Example:
call-home diagnostic-signature environment ds_fsurl_prefix " environment ds_fsurl_prefix "scp://612345678:abcdefghijklmnop@cxd.cisco.com"
-
Ensure SNMP is enabled using the command show snmp. If it is not enabled, configure the “snmp-server manager” command.
LocalGateway# show snmp %SNMP agent not enabled LocalGateway# LocalGateway# LocalGateway# config t LocalGateway(config)# snmp-server manager LocalGateway(config)#end LocalGateway#
-
It is recommended to install the High CPU monitoring DS 64224 as a proactive measure to disable all debugs and diagnostics signatures during the time of high cpu utilization. Download DS 64224 using the following options in Diagnostic Signatures Lookup Tool:
Field Name
Field Value
Platform
Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series
Product
CUBE Enterprise in Webex Calling Solution
Problem Scope
Performance
Problem Type
High CPU Utilization with Email Notification
-
Download DS 65095 using the following options in Diagnostic Signatures Lookup Tool:
Field Name
Field Value
Platform
Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series
Product
CUBE Enterprise in Webex Calling Solution
Problem Scope
Syslogs
Problem Type
Syslog - %VOICE_IEC-3-GW: CCAPI: Internal Error (Call spike threshold): IEC=1.1.181.1.29.0
-
Copy the DS XML files to the Local Gateway.
LocalGateway# copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash: LocalGateway# copy ftp://username:password@<server name or ip>/DS_65095.xml bootflash:
-
Install the High CPU monitoring DS 64224 and then DS 65095 XML file in the Local Gateway.
LocalGateway# call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success LocalGateway# LocalGateway# call-home diagnostic-signature load DS_65095.xml Load file DS_65095.xml success LocalGateway#
-
Verify that the signature is successfully installed using show call-home diagnostic-signature. The status column should have a “registered” value.
LocalGateway# show call-home diagnostic-signature Current diagnostic-signature settings: Diagnostic-signature: enabled Profile: CiscoTAC-1 (status: ACTIVE) Downloading URL(s): https://tools.cisco.com/its/service/oddce/services/DDCEService Environment variable: ds_email: username@gmail.com ds_fsurl_prefix: scp://612345678:abcdefghijklmnop@cxd.cisco.com
Downloaded DSes:
DS ID
DS Name
Revision
Status
Last Update (GMT+00:00)
64224
00:07:45
DS_LGW_CPU_MON75
0.0.10
Registered
2020-11-08:00:07:45
65095
00:12:53
DS_LGW_IEC_Call_spike_threshold
0.0.12
Registered
2020-11-08:00:12:53
LocalGateway#
Verify Diagnostic Signatures Execution
As shown below, the “Status” column of the command show call-home diagnostic-signature will change to “running” while the local gateway is executing the action defined within the signature. The output of show call-home diagnostic-signature statistics is the best way to verify whether a diagnostic signature has detected an event of interest and executed the action. The “Triggered/Max/Deinstall” column indicates the number of times the given signature has triggered an event, the maximum number of times it is defined to detect an event and whether the signature will automatically deinstall itself after detecting the maximum number of triggered events.
LocalGateway# show call-home diagnostic-signature
Current diagnostic-signature settings:
Diagnostic-signature: enabled
Profile: CiscoTAC-1 (status: ACTIVE)
Downloading URL(s): https://tools.cisco.com/its/service/oddce/services/DDCEService
Environment variable:
ds_email: carunach@cisco.com
ds_fsurl_prefix: scp://612345678:abcdefghijklmnop@cxd.cisco.com
Downloaded DSes:
DS ID |
DS Name |
Revision |
Status |
Last Update (GMT+00:00) |
---|---|---|---|---|
64224 |
DS_LGW_CPU_MON75 |
0.0.10 |
Registered |
2020-11-08 00:07:45 |
65095 |
DS_LGW_IEC_Call_spike_threshold |
0.0.12 |
Running |
2020-11-08 00:12:53 |
LocalGateway#
LocalGateway# show call-home diagnostic-signature statistics
DS ID |
DS Name |
Triggered/Max/Deinstall |
Average Run Time (seconds) |
Max Run Time (seconds) |
---|---|---|---|---|
64224 |
DS_LGW_CPU_MON75 |
0/0/N |
0.000 |
0.000 |
65095 |
DS_LGW_IEC_Call_spike_threshold |
1/20/Y |
23.053 |
23.053 |
LocalGateway#
The notification email sent during Diagnostic Signature execution contains key information such as issue type, device details, software version, running configuration and show command outputs that are relevant to troubleshoot the given problem.

Uninstall Diagnostic Signatures
Diagnostic signatures that are used for troubleshooting purposes are typically defined to uninstall after detection of a certain number of problem occurrences. If you would like to uninstall a signature manually, retrieve the DS ID from the output of show call-home diagnostic-signature and run the command shown below.
LocalGateway# call-home diagnostic-signature deinstall <DS ID>
LocalGateway#
Example:
LocalGateway# call-home diagnostic-signature deinstall 64224
LocalGateway#
New signatures are added to Diagnostics Signatures Lookup Tool periodically, based on issues commonly observed in deployments. TAC currently doesn’t support requests to create new custom signatures. |