Konfigurer lokal gateway på Cisco IOS XE til Webex Calling
Når du har konfigureret Webex-opkald for din organisation, kan du konfigurere en trunk til at tilslutte din lokale gateway til Webex-opkald. SIP TLS-transport sikrer trunk mellem den lokale gateway og Webex-cloud. Mediet mellem den lokale gateway og Webex-opkald bruger SRTP.
Overblik
Webex Calling currently supports two versions of Local Gateway:
-
Lokal gateway
-
Local Gateway for Webex for Government
-
Before you begin, understand the premises-based Public Switched Telephone Network (PSTN) and Local Gateway (LGW) requirements for Webex Calling. Se Ciscos foretrukne arkitektur Webex-opkald for yderligere oplysninger.
-
Denne artikel tager udgangspunkt i, at en dedikeret lokal gateway-platform er på plads uden en eksisterende stemmekonfiguration. If you modify an existing PSTN gateway or CUBE Enterprise deployment to use as the Local Gateway function for Webex Calling, then pay careful attention to the configuration. Ensure that you don't interrupt the existing call flows and functionality because of the changes that you make.
For information on the supported third-party SBCs, refer to the respective product reference documentation.
Der er to valgmuligheder til at konfigurere den lokale gateway til din Webex-opkald trunk:
-
Registreringsbaseret trunk
-
Certifikatbaseret trunk
Use the task flow either under the Registration-based Local Gateway or Certificate-based Local Gateway to configure Local Gateway for your Webex Calling trunk.
See Get started with Local Gateway for more information on different trunk types. Udfør følgende trin på selve den lokale gateway ved hjælp af kommandolinjegrænsefladen (CLI). We use Session Initiation Protocol (SIP) and Transport Layer Security (TLS) transport to secure the trunk and Secure Real Time Protocol (SRTP) to secure the media between the Local Gateway and Webex Calling.
-
Select CUBE as your Local Gateway. Webex for Government doesn’t currently support any third-party Session Border Controllers (SBCs). To review the latest list, see Get started with Local Gateway.
- Install Cisco IOS XE Dublin 17.12.1a or later versions for all Webex for Government Local Gateways.
-
To review the list of root Certificate Authorities (CAs) that Webex for Government support, see Root certificate authorities for Webex for Government.
-
For details on the external port ranges for Local Gateway in Webex for Government, see Network requirements for Webex for Government (FedRAMP).
Local Gateway for Webex for Government doesn’t support the following:
-
STUN/ICE-Lite for media path optimization
-
Fax (T.38)
To configure Local Gateway for your Webex Calling trunk in Webex for Government, use the following option:
-
Certifikatbaseret trunk
Use the task flow under the Certificate-based Local Gateway to configure the Local Gateway for your Webex Calling trunk. For more details on how to configure a certificate-based Local Gateway, see Configure Webex Calling certificate-based trunk.
It’s mandatory to configure FIPS-compliant GCM ciphers to support Local Gateway for Webex for Government. If not, the call setup fails. For configuration details, see Configure Webex Calling certificate-based trunk.
This section describes how to configure a Cisco Unified Border Element (CUBE) as a Local Gateway for Webex Calling, using a registering SIP trunk. The first part of this document illustrates how to configure a simple PSTN gateway. In this case, all calls from the PSTN are routed to Webex Calling and all calls from Webex Calling are routed to the PSTN. The image below highlights this solution and the high-level call routing configuration that will be followed.
In this design, the following principal configurations are used:
-
voice class tenants: Used to create trunk specific configurations.
-
voice class uri: Used to classify SIP messages for the selection of an inbound dial-peer.
-
inbound dial-peer: Provides treatment for inbound SIP messages and determines the outbound route with a dial-peer group.
-
dial-peer group: Defines the outbound dial-peers used for onward call routing.
-
outbound dial-peer: Provides treatment for outbound SIP messages and routes them to the required target.
![Call routing from/to PSTN to/from Webex Calling configuration solution](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/470001-480000/479001-480000/479480.png)
While IP and SIP have become the default protocols for PSTN trunks, TDM (Time Division Multiplexing) ISDN circuits are still widely used and are supported with Webex Calling trunks. To enable media optimization of IP paths for Local Gateways with TDM-IP call flows, it is currently necessary to use a two-leg call routing process. This approach modifies the call routing configuration shown above, by introducing a set of internal loop-back dial-peers between Webex Calling and PSTN trunks as illustrated in the image below.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/480001-490000/482001-483000/482796.png)
When connecting an on-premises Cisco Unified Communications Manager solution with Webex Calling, you can use the simple PSTN gateway configuration as a baseline for building the solution illustrated in the following diagram. In this case, Unified Communications Manager provides centralized routing and treatment of all PSTN and Webex Calling calls.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/470001-480000/479001-480000/479481.png)
Throughout this document, the host names, IP addresses, and interfaces illustrated in the following image are used.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/480001-490000/482001-483000/482562.png)
Use the configuration guidance in the rest of this document to complete your Local Gateway configuration as follows:
-
Trin 1: Configure router baseline connectivity and security
-
Trin 2: Configure Webex Calling Trunk
Depending on your required architecture, follow either:
-
Trin 3: Configure Local Gateway with SIP PSTN trunk
-
Trin 4: Configure Local Gateway with existing Unified CM environment
Eller:
-
Trin 3: Configure Local Gateway with TDM PSTN trunk
Baseline configuration
The first step in preparing your Cisco router as a Local Gateway for Webex Calling is to build a baseline configuration that secures your platform and establishes connectivity.
-
All registration-based Local Gateway deployments require Cisco IOS XE 17.6.1a or later versions. For the recommended versions, see the Cisco Software Research page. Search for the platform and select one of the suggested releases.
-
ISR4000 series routers must be configured with both Unified Communications and Security technology licenses.
-
Catalyst Edge 8000 series routers fitted with voice cards or DSPs require DNA Advantage licensing. Routers without voice cards or DSPs require a minimum of DNA Essentials licensing.
-
-
Build a baseline configuration for your platform that follows your business policies. In particular, configure the following and verify the working:
-
NTP
-
Acl'er
-
User authentication and remote access
-
DNS
-
IP-routing
-
IP addresses
-
-
The network toward Webex Calling must use an IPv4 address.
-
Upload the Cisco root CA bundle to the Local Gateway.
Konfiguration
1 |
Ensure that you assign valid and routable IP addresses to any Layer 3 interfaces, for example:
|
2 |
Protect registration and STUN credentials on the router using symmetric encryption. Configure the primary encryption key and encryption type as follows:
|
3 |
Create a placeholder PKI trustpoint. Requires this trustpoint to configure TLS later. For registration-based trunks, this trustpoint doesn't require a certificate - as would be required for a certificate-based trunk. |
4 |
Enable TLS1.2 exclusivity and specify the default trustpoint using the following configuration commands. Transport parameters should also be updated to ensure a reliable secure connection for registration: The cn-san-validate server command ensures that the Local Gateway permits a connection if the host name configured in tenant 200 is included in either the CN or SAN fields of the certificate received from the outbound proxy.
|
5 |
Install the Cisco root CA bundle, which includes the DigiCert CA certificate used by Webex Calling. Use the crypto pki trustpool import clean url command to download the root CA bundle from the specified URL, and to clear the current CA trustpool, then install the new bundle of certificates: If you need to use a proxy for access to the internet using HTTPS, add the following configuration before importing the CA bundle: ip http client proxy-server yourproxy.com proxy-port 80 |
1 |
Create a registration based PSTN trunk for an existing location in Control Hub. Make a note of the trunk information that is provided once the trunk has been created. These details, as highlighted in the following illustration, will be used in the configuration steps in this guide. For more information, see Configure trunks, route groups, and dial plans for Webex Calling. ![]() |
2 |
Enter the following commands to configure CUBE as a Webex Calling Local Gateway: Her er en forklaring af felterne til konfigurationen:
Enables Cisco Unified Border Element (CUBE) features on the platform. media statisticsAktiverer medieovervågning på den lokale gateway. media bulk-statsGør det muligt for kontrol at indsamle data til meningsmåling for masseopkaldsstatistikker. For more information on these commands, see Media. tillad-forbindelser sip til sipEnable CUBE basic SIP back-to-back user agent functionality. For more information, see Allow connections. By default, T.38 fax transport is enabled. For more information, see fax protocol t38 (voice-service). Enables STUN (Session Traversal of UDP through NAT) globally.
For more information, see stun flowdata agent-id and stun flowdata shared-secret. asymmetric payload fullConfigures SIP asymmetric payload support for both DTMF and dynamic codec payloads. For more information on this command, see asymmetric payload. tidlig tilbud tvungetForces the Local Gateway to send SDP information in the initial INVITE message instead of waiting for acknowledgment from the neighboring peer. For more information on this command, see early-offer. |
3 |
Configure voice class codec 100 filter for the trunk. In this example, the same codec filter is used for all trunks. You can configure filters for each trunk for precise control. Her er en forklaring af felterne til konfigurationen: voice class codec 100Used to only allow preferred codecs for calls through SIP trunks. For more information, see voice class codec. Opus codec is supported only for SIP-based PSTN trunks. If the PSTN trunk uses a voice T1/E1 or analog FXO connection, exclude codec preference 1 opus from the voice class codec 100 configuration. |
4 |
Configure voice class stun-usage 100 to enable ICE on the Webex Calling trunk. Her er en forklaring af felterne til konfigurationen: stun usage ice liteUsed to enable ICE-Lite for all Webex Calling facing dial-peers to allow media-optimization whenever possible. For more information, see voice class stun usage and stun usage ice lite. You require stun usage of ICE-lite for call flows using media path optimization. To provide media-optimization for a SIP to TDM gateway, configure a loopback dial-peer with ICE-Lite enabled on the IP-IP leg. For further technical details, contact the Account or TAC teams |
5 |
Configure the media encryption policy for Webex traffic. Her er en forklaring af felterne til konfigurationen: voice class srtp-crypto 100Specifies SHA1_80 as the only SRTP cipher-suite CUBE offers in the SDP in offer and answer messages. Webex Calling only supports SHA1_80. For more information, see voice class srtp-crypto. |
6 |
Configure a pattern to uniquely identify calls to a Local Gateway trunk based on its destination trunk parameter: Her er en forklaring af felterne til konfigurationen: voice class uri 100 sipDefines a pattern to match an incoming SIP invite to an incoming trunk dial-peer. When entering this pattern, use dtg= followed by the Trunk OTG/DTG value provided in Control Hub when the trunk was created. For more information, see voice class uri. |
7 |
Configure sip profile 100, which will be used to modify SIP messages before they are sent to Webex Calling.
Her er en forklaring af felterne til konfigurationen:
|
8 |
Configure Webex Calling trunk: |
After you define tenant 100 and configure a SIP VoIP dial-peer, the gateway initiates a TLS connection toward Webex Calling. At this 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 that was updated earlier. If the certificate is recognised, a persistent TLS session is established between the Local Gateway and Webex Calling access SBC. The Local Gateway is then able to use this secure connection to register with the Webex access SBC. When the registration is challenged for authentication:
-
The username, password, and realm parameters from the credentials configuration is used in the response.
-
The modification rules in sip profile 100 are used to convert SIPS URL back to SIP.
Registration is successful when a 200 OK is received from the access SBC.
Having built a trunk towards Webex Calling above, use the following configuration to create a non-encrypted trunk towards a SIP based PSTN provider:
If your Service Provider offers a secure PSTN trunk, you may follow a similar configuration as detailed above for the Webex Calling trunk. Secure to secure call routing is supported by CUBE.
If you are using a TDM / ISDN PSTN trunk, skip to next section Configure Local Gateway with TDM PSTN trunk.
To configure TDM interfaces for PSTN call legs on the Cisco TDM-SIP Gateways, see Configuring ISDN PRI.
1 |
Configure the following voice class uri to identify inbound calls from the PSTN trunk: Her er en forklaring af felterne til konfigurationen: voice class uri 200 sipDefines a pattern to match an incoming SIP invite to an incoming trunk dial-peer. When entering this pattern, use the IP address of you IP PSTN gateway. For more information, see voice class uri. |
2 |
Configure the following IP PSTN dial-peer: Her er en forklaring af felterne til konfigurationen: Definerer en VoIP dial-peer med et tag på 200 og giver en meningsfuld beskrivelse af brugervenlighed i forbindelse med administration og fejlfinding. For more information, see dial-peer voice. destinationsmønster DÅRLIG. DårligA dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface). session protokol sipv2Angiver, at dial-peer 200 håndterer SIP-call legs. For more information, see session protocol (dial peer). sessions mål ipv4:192.168.80.13Angiver destinationens mål-IPv4-adresse til at sende opkaldsbenet. Sessionsmålet her er ITSP's IP-adresse. For more information, see session target (VoIP dial peer). incoming uri via 200Definerer et sammenfald for VIA-headeren med IP PSTN's IP-adresse. Matches all incoming IP PSTN call legs on the Local Gateway with dial-peer 200. For more information, see incoming url. bind control source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see bind. bind media source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for media sent to PSTN. For more information, see bind. stemmeklasse-codec 100Configures the dial-peer to use the common codec filter list 100. For more information, see voice-class codec. dtmf-relay rtp-nteDefinerer RTP-NTE (RFC2833) som DTMF-evnen forventet på opkaldsbenet. For more information, see DTMF Relay (Voice over IP). ingen toneDeaktiverer stemmeaktivitetsregistrering. For more information, see vad (dial peer). |
3 |
If you are configuring your Local Gateway to only route calls between Webex Calling and the PSTN, add the following call routing configuration. If you are configuring your Local Gateway with a Unified Communications Manager platform, skip to the next section. |
Having built a trunk towards Webex Calling, use the following configuration to create a TDM trunk for your PSTN service with loop-back call routing to allow media optimization on the Webex call leg.
1 |
The loop-back dial-peer configuration uses dial-peer groups and call routing tags to ensure that calls pass correctly between Webex and the PSTN, without creating call routing loops. Configure the following translation rules that will be used to add and remove the call routing tags: Her er en forklaring af felterne til konfigurationen: voice translation-ruleUses regular expressions defined in rules to add or remove call routing tags. Over-decadic digits (‘A’) are used to add clarity for troubleshooting. In this configuration, the tag added by translation-profile 100 is used to guide calls from Webex Calling towards the PSTN via the loopback dial-peers. Similarly, the tag added by translation-profile 200 is used to guide calls from the PSTN towards Webex Calling. Translation-profiles 11 and 12 remove these tags before delivering calls to the Webex and PSTN trunks respectively. This example assumes that called numbers from Webex Calling are presented in +E.164 format. Rule 100 removes the leading + to maintain a valid called number. Rule 12 then adds a national or international routing digit(s) when removing the tag. Use digits that suit your local ISDN national dial plan. If Webex Calling presents numbers in national format, adjust rules 100 and 12 to simply add and remove the routing tag respectively. For more information, see voice translation-profile and voice translation-rule. |
2 |
Configure TDM voice interface ports as required by the trunk type and protocol used. For more information, see Configuring ISDN PRI. For example, the basic configuration of a Primary Rate ISDN interface installed in NIM slot 2 of a device might include the following: |
3 |
Configure the following TDM PSTN dial-peer: Her er en forklaring af felterne til konfigurationen: Definerer en VoIP med et tag på 200 og giver en meningsfuld beskrivelse af hensyn til brugervenlighed i administration og fejlfinding. For more information, see dial-peer voice. destinationsmønster DÅRLIG. DårligA dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface). translation-profile incoming 200Assigns the translation profile that will add a call routing tag to the incoming called number. direct-inward-dialRoutes the call without providing a secondary dial-tone. For more information, see direct-inward-dial. port 0/2/0:15The physical voice port associated with this dial-peer. |
4 |
To enable media optimization of IP paths for Local Gateways with TDM-IP call flows, you can modify the call routing by introducing a set of internal loop-back dial-peers between Webex Calling and PSTN trunks. Configure the following loop-back dial-peers. In this case, all incoming calls will be routed initially to dial-peer 10 and from there to either dial-peer 11 or 12 based on the applied routing tag. After removal of the routing tag, calls will be routed to the outbound trunk using dial-peer groups. Her er en forklaring af felterne til konfigurationen: Defines a VoIP dial-peer and gives a meaningful description for ease of management and troubleshooting. For more information, see dial-peer voice. translation-profile incoming 11Applies the translation profile defined earlier to remove the call routing tag before passing to the outbound trunk. destinationsmønster DÅRLIG. DårligA dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface). session protokol sipv2Specifies that this dial-peer handles SIP call legs. For more information, see session protocol (dial peer). session target 192.168.80.14Specifies the local router interface address as the call target to loop-back. For more information, see session target (voip dial peer). bind control source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for messages sent through the loop-back. For more information, see bind. bind media source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for media sent through the loop-back. For more information, see bind. dtmf-relay rtp-nteDefinerer RTP-NTE (RFC2833) som DTMF-evnen forventet på opkaldsbenet. For more information, see DTMF Relay (Voice over IP). codec g711alaw Forces all PSTN calls to use G.711. Select a-law or u-law to match the companding method used by your ISDN service. ingen toneDeaktiverer stemmeaktivitetsregistrering. For more information, see vad (dial peer). |
5 |
Add the following call routing configuration: This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features are configured.
|
The PSTN-Webex Calling configuration in the previous sections may be modified to include additional trunks to a Cisco Unified Communications Manager (UCM) cluster. In this case, all calls are routed via Unified CM. Calls from UCM on port 5060 are routed to the PSTN and calls from port 5065 are routed to Webex Calling. The following incremental configurations may be added to include this calling scenario.
When creating the Webex Calling trunk in Unified CM, ensure that you configure the incoming port in the SIP Trunk Security Profile settings to 5065. This allows incoming messages on port 5065 and populate the VIA header with this value when sending messages to the Local Gateway.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/480001-490000/483001-484000/483179.png)
1 |
Konfigurer følgende stemmeklasse-URI-adresser: |
2 |
Configure the following DNS records to specify SRV routing to Unified CM hosts: IOS XE uses these records for locally determining target UCM hosts and ports. With this configuration, it is not required to configure records in your DNS system. If you prefer to use your DNS, then these local configurations are not required. Her er en forklaring af felterne til konfigurationen: The following command creates a DNS SRV resource record. Create a record for each UCM host and trunk: ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub5.mydomain.com _sip._udp.pstntocucm.io: SRV resource record name 2: The SRV resource record priority 1: The SRV resource record weight 5060: The port number to use for the target host in this resource record ucmsub5.mydomain.com: The resource record target host To resolve the resource record target host names, create local DNS A records. For eksempel: ip host ucmsub5.mydomain.com 192.168.80.65 ip host: Creates a record in the local IOS XE database. ucmsub5.mydomain.com: The A record host name. 192.168.80.65: The host IP address. Create the SRV resource records and A records to reflect your UCM environment and preferred call distribution strategy. |
3 |
Configure the following dial-peers: |
4 |
Add call routing using the following configurations: |
Diagnosticeringssignaturer (DS) påviser proaktivt almindeligt observerede problemer i den IOS XE-baserede lokale gateway og genererer e-mail-, syslog- eller terminalmeddelelsesunderretning om begivenheden. You can also install the DS to automate diagnostics data collection and transfer-collected data to the Cisco TAC case to accelerate resolution time.
Diagnosticeringssignaturer (DS) er XML-filer, der indeholder oplysninger om problemudløserbegivenheder og handlinger, der skal foretages for at informere, fejlfinde og udbedre problemet. You can define the problem detection logic using syslog messages, SNMP events and through periodic monitoring of specific show command outputs.
Handlingstyperne inkluderer indsamling af vis kommandooutputs:
-
Genererer en konsolideret logfil
-
Uploading the file to a user-provided network location such as HTTPS, SCP, FTP server.
TAC-ingeniører skriver DS-filerne og signerer dem digitalt for integritetsbeskyttelse. Hver DS-fil får tildelt et entydigt numerisk id af systemet. Diagnostic Signatures Lookup Tool (DSLT) is a single source to find applicable signatures for monitoring and troubleshooting various problems.
Før du begynder:
-
Rediger ikke DS-filen, som du downloader fra DSLT. De filer, du modificerer, installeres ikke på grund af fejl i integritetskontrollen.
-
En enkel Mail Transfer Protocol (SMTP)-server, som du kræver, at den lokale gateway sender e-mailunderretninger.
-
Sørg for, at den lokale gateway kører IOS XE 17.6.1 eller nyere, hvis du vil bruge den sikre SMTP-server til e-mailunderretninger.
Forudsætninger
Local Gateway running IOS XE 17.6.1a or higher
-
Diagnosticeringssignaturer er aktiveret som standard.
-
Configure the secure email server to be used to send proactive notification if the device is running Cisco IOS XE 17.6.1a or higher.
configure terminal call-home mail-server <username>:<pwd>@<email server> priority 1 secure tls end
-
Configure the environment variable ds_email with the email address of the administrator to notify you.
configure terminal call-home diagnostic-signature environment ds_email <email address> end
The following shows an example configuration of a Local Gateway running on Cisco IOS XE 17.6.1a or higher to send the proactive notifications to tacfaststart@gmail.com using Gmail as the secure SMTP server:
We recommend you to use the Cisco IOS XE Bengaluru 17.6.x or later versions.
call-home mail-server tacfaststart:password@smtp.gmail.com priority 1 secure tls diagnostic-signature environment ds_email "tacfaststart@gmail.com"
En lokal gateway, der kører på Cisco IOS XE-software, er ikke en typisk webbaseret Gmail-klient, der understøtter OAuth, så vi skal konfigurere en specifik Gmail-kontoindstilling og give specifik tilladelse til at få e-mailen fra enheden behandlet korrekt:
-
Go to Less secure app access setting.
and turn on the -
Svar "Ja, det var mig", når du modtager en e-mail fra Gmail, der angiver "Google forhindrede en person i at logge ind på din konto ved hjælp af en ikke-Google-app".
Installer diagnostiske signaturer til proaktiv overvågning
Monitorer høj CPU-udnyttelse
This DS tracks CPU utilization for five seconds using the SNMP OID 1.3.6.1.4.1.9.2.1.56. Når udnyttelsen når 75 % eller mere, deaktiverer den alle fejlfindinger og afinstallerer alle diagnostiske signaturer, der er installeret i den lokale gateway. Følg trinene nedenfor for at installere signaturen.
-
Use the show snmp command to enable SNMP. If you do not enable, then configure the snmp-server manager command.
show snmp %SNMP agent not enabled config t snmp-server manager end 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 indlogning: aktiveret
-
Download DS 64224 ved hjælp af følgende valgmuligheder i rullemenuen i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Ydeevne
Problemtype
Høj CPU-udnyttelse med e-mailmeddelelse.
-
Kopiér DS XML-filen til den lokale gateways flash.
LocalGateway# copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:
Følgende eksempel viser kopiering af filen fra en FTP-server til den lokale gateway.
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)
-
Installer DS XML-filen på den lokale gateway.
call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success
-
Brug kommandoen vis call-home diagnostic-signature til at bekræfte, at signaturen er installeret korrekt. Statuskolonnen skal have værdien "registreret".
show call-home diagnostic-signature Current diagnostic-signature settings: Diagnosticeringssignatur: aktiveret profil: CiscoTAC-1 (status: AKTIV) Downloader URL(er): https://tools.cisco.com/its/service/oddce/services/DDCEService Environment variable: ds_email: username@gmail.com
Download diagnosticeringssignaturer:
DS-id
DS-navn
Revision
Status
Seneste opdatering (GMT+00:00)
64224
DS_LGW_CPU_MON75
0.0.10
Tilmeldt
2020-11-07 22:05:33
Når denne signatur udløses, afinstallerer den alle kørende diagnosticeringssignaturer, inklusive sig selv. If necessary, reinstall DS 64224 to continue monitoring high CPU utilization on the Local Gateway.
Monitorer registrering af SIP-trunk
Denne DS kontrollerer afrapportering af en lokal gateway-SIP-trunk med Webex-opkald cloud hvert 60. sekunder. Once the unregistration event is detected, it generates an email and syslog notification and uninstalls itself after two unregistration occurrences. Use the steps below to install the signature:
-
Download DS 64117 ved hjælp af følgende valgmuligheder i rullemenuen i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR-serien eller Cisco CSR 1000V-serien
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
SIP-SIP
Problemtype
SIP-trunk afmelding med e-mailmeddelelse.
-
Kopiér DS XML-filen til den lokale gateway.
copy ftp://username:password@<server name or ip>/DS_64117.xml bootflash:
-
Installer DS XML-filen på den lokale gateway.
call-home diagnostic-signature load DS_64117.xml Load file DS_64117.xml success LocalGateway#
-
Brug kommandoen vis call-home diagnostic-signature til at bekræfte, at signaturen er installeret korrekt. Statuskolonnen skal have en "registreret" værdi.
Overvågning af unormale opkald afbryder
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 generates a syslog and email notification. Please use the steps below to install the signature.
-
Use the show snmp command to check whether SNMP is enabled. If it is not enabled, configure the snmp-server manager command.
show snmp %SNMP agent not enabled config t snmp-server manager end 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 indlogning: aktiveret
-
Download DS 65221 ved hjælp af følgende valgmuligheder i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR-serien eller Cisco CSR 1000V-serien
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Ydeevne
Problemtype
Registrering af SIP-unormalt opkaldsopkald med e-mail- og Syslog-underretning.
-
Kopiér DS XML-filen til den lokale gateway.
copy ftp://username:password@<server name or ip>/DS_65221.xml bootflash:
-
Installer DS XML-filen på den lokale gateway.
call-home diagnostic-signature load DS_65221.xml Load file DS_65221.xml success
-
Brug kommandoen vis call-home diagnostic-signature til at bekræfte, at signaturen er installeret korrekt. Statuskolonnen skal have en "registreret" værdi.
Installer diagnostiske signaturer for at fejlse et problem
Brug diagnostiske signaturer (DS) til at løse problemer hurtigt. Cisco TAC-ingeniører har oprettet flere signaturer, der aktiverer de nødvendige fejlfinding, der er påkrævet for at fejlfinde et givet problem, registrere problemhændelsen, indsamle det rigtige sæt diagnostiske data og overføre data automatisk til Cisco TAC-sagen. Diagnostic Signatures (DS) eliminate the need to manually check for the problem occurrence and makes troubleshooting of intermittent and transient issues a lot easier.
Du kan bruge diagnosticeringssignaturopslagsopslagsværktøjet til at finde de relevante signaturer og installere dem til selv at løse et givet problem, eller du kan installere signaturen, som anbefales af TAC-teknikeren som en del af supportengagementet.
Her er et eksempel på, hvordan du finder og installerer en diagnosticeringssignatur for at påvise hændelsen “%VOICE_IEC-3-GW: CCAPI: Intern fejl (tærskel for opkaldsudsving): UDFØRING=1.1.181.1.29.0" syslog og automatisere diagnosticeringsdataindsamling ved hjælp af følgende trin:
-
Configure an additional DS environment variable ds_fsurl_prefix which is the Cisco TAC 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 in the following command. The file upload token can be generated in the Attachments section of the Support Case Manager, as needed.
configure terminal call-home diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_fsurl_prefix "scp://<case number>:<file upload token>@cxd.cisco.com" end
Eksempel:
call-home diagnostic-signature environment ds_fsurl_prefix " environment ds_fsurl_prefix "scp://612345678:abcdefghijklmnop@cxd.cisco.com"
-
Ensure that SNMP is enabled using the show snmp command. If it is not enabled, configure the snmp-server manager command.
show snmp %SNMP agent not enabled config t snmp-server manager end
-
Sørg for at installere High CPU-monitorering DS 64224 som et proaktivt mål for at deaktivere alle fejl og diagnosticeringssignaturer i løbet af den høje CPU-udnyttelse. Download DS 64224 ved hjælp af følgende valgmuligheder i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR-serien eller Cisco CSR 1000V-serien
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Ydeevne
Problemtype
Høj CPU-udnyttelse med e-mailmeddelelse.
-
Download DS 65095 ved hjælp af følgende valgmuligheder i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR-serien eller Cisco CSR 1000V-serien
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Systemlogfiler
Problemtype
Systemlogfiler – %VOICE_IEC-3-GW: CCAPI: Intern fejl (tærskel for opkaldsudsving): IEC=1.1.181.1.29.0
-
Kopiér DS XML-filer til den lokale gateway.
copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash: copy ftp://username:password@<server name or ip>/DS_65095.xml bootflash:
-
Installer DS 64224 til overvågning af højt CPU-forbrug og derefter DS 65095 XML-filen på den lokale gateway.
call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success call-home diagnostic-signature load DS_65095.xml Load file DS_65095.xml success
-
Verify that the signature is successfully installed using the show call-home diagnostic-signature command. Statuskolonnen skal have en "registreret" værdi.
show call-home diagnostic-signature Current diagnostic-signature settings: Diagnosticeringssignatur: aktiveret profil: CiscoTAC-1 (status: AKTIV) Downloader URL(er): 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
Downloadede diagnosticeringssignaturer:
DS-id
DS-navn
Revision
Status
Seneste opdatering (GMT+00:00)
64224
00:07:45
DS_LGW_CPU_MON75
0.0.10
Tilmeldt
2020-11-08
65095
00:12:53
DS_LGW_IEC_Call_spike_threshold
0.0.12
Tilmeldt
2020-11-08
Bekræft afvikling af diagnostiske signaturer
In the following command, the “Status” column of the show call-home diagnostic-signature command changes to “running” while the Local Gateway executes the action defined within the signature. Resultatet af show call-home diagnostic-signature statistics er den bedste måde til at verificere, om en diagnosesignatur påviser en begivenhed af interesse og udfører handlingen. Kolonnen "Udløst/Maks./Afinstaller" angiver antallet af gange, den angivne signatur har udløst en begivenhed, det maksimale antal gange, den er defineret til at påvise en begivenhed, og om signaturen afinstallerer sig selv efter at påvise det maksimale antal udløste begivenheder.
show call-home diagnostic-signature Current diagnostic-signature settings: Diagnosticeringssignatur: aktiveret
profil: CiscoTAC-1 (status: AKTIV)
Downloader URL(er): 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
Downloadede diagnosticeringssignaturer:
DS-id |
DS-navn |
Revision |
Status |
Seneste opdatering (GMT+00:00) |
---|---|---|---|---|
64224 |
DS_LGW_CPU_MON75 |
0.0.10 |
Tilmeldt |
2020-11-08 00:07:45 |
65095 |
DS_LGW_IEC_Call_spike_threshold |
0.0.12 |
Kører |
2020-11-08 00:12:53 |
vis call-home diagnostisk-signatur-statistik
DS-id |
DS-navn |
Triggered/Max/Deinstall |
Gennemsnitlig kørselstid (sekunder) |
Maks. kørselstid (sekunder) |
---|---|---|---|---|
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 |
Den e-mailunderretning, der sendes under afvikling af diagnosesignatur, indeholder vigtige oplysninger, såsom problemtype, enhedsoplysninger, softwareversion, kørende konfiguration og viser kommandooutputs, der er relevante for fejlfinding af det givne problem.
Afinstaller diagnostiske signaturer
Brug diagnostiske signaturer til fejlfindingsformål defineres typisk til afinstallation efter påvisning af nogle problemhændelser. If you want to uninstall a signature manually, retrieve the DS ID from the output of the show call-home diagnostic-signature command and run the following command:
call-home diagnostic-signature deinstall <DS ID>
Eksempel:
call-home diagnostic-signature deinstall 64224
Nye signaturer føjes regelmæssigt til værktøjet Diagnosticeringssignaturopslag, baseret på problemer, der normalt opstår under udrulninger. TAC understøtter i øjeblikket ikke anmodninger om at oprette nye brugertilpassede signaturer.
For better management of Cisco IOS XE Gateways, we recommend that you enroll and manage the gateways through the Control Hub. It is an optional configuration. When enrolled, you can use the configuration validation option in the Control Hub to validate your Local Gateway configuration and identify any configuration issues. Currently, only registration-based trunks support this functionality.
For more information, refer the following:
This section describes how to configure a Cisco Unified Border Element (CUBE) as a Local Gateway for Webex Calling, using certificate-based mutual TLS (mTLS) SIP trunk. The first part of this document illustrates how to configure a simple PSTN gateway. In this case, all calls from the PSTN are routed to Webex Calling and all calls from Webex Calling are routed to the PSTN. The following image highlights this solution and the high-level call routing configuration that will be followed.
In this design, the following principal configurations are used:
-
voice class tenants: Used to create trunk specific configurations.
-
voice class uri: Used to classify SIP messages for the selection of an inbound dial-peer.
-
inbound dial-peer: Provides treatment for inbound SIP messages and determines the outbound route with a dial-peer group.
-
dial-peer group: Defines the outbound dial-peers used for onward call routing.
-
outbound dial-peer: Provides treatment for outbound SIP messages and routes them to the required target.
![Call routing from/to PSTN to/from Webex Calling configuration solution](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/470001-480000/479001-480000/479480.png)
While IP and SIP have become the default protocols for PSTN trunks, TDM (Time Division Multiplexing) ISDN circuits are still widely used and are supported with Webex Calling trunks. To enable media optimization of IP paths for Local Gateways with TDM-IP call flows, it is currently necessary to use a two-leg call routing process. This approach modifies the call routing configuration shown above, by introducing a set of internal loop-back dial-peers between Webex Calling and PSTN trunks as illustrated in the image below.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/480001-490000/482001-483000/482796.png)
When connecting an on-premises Cisco Unified Communications Manager solution with Webex Calling, you can use the simple PSTN gateway configuration as a baseline for building the solution illustrated in the following diagram. In this case, Unified Communications Manager provides centralized routing and treatment of all PSTN and Webex Calling calls.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/470001-480000/479001-480000/479481.png)
Throughout this document, the host names, IP addresses, and interfaces illustrated in the following image are used. Options are provided for public or private (behind NAT) addressing. SRV DNS records are optional, unless load balancing across multiple CUBE instances.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/470001-480000/479001-480000/479482.png)
Use the configuration guidance in the rest of this document to complete your Local Gateway configuration as follows:
-
Trin 1: Configure router baseline connectivity and security
-
Trin 2: Configure Webex Calling Trunk
Depending on your required architecture, follow either:
-
Trin 3: Configure Local Gateway with SIP PSTN trunk
-
Trin 4: Configure Local Gateway with existing Unified CM environment
Eller:
-
Trin 3: Configure Local Gateway with TDM PSTN trunk
Baseline configuration
The first step in preparing your Cisco router as a Local Gateway for Webex Calling is to build a baseline configuration that secures your platform and establishes connectivity.
-
All certificate-based Local Gateway deployments require Cisco IOS XE 17.9.1a or later versions. For the recommended versions, see the Cisco Software Research page. Search for the platform and select one of the suggested releases.
-
ISR4000 series routers must be configured with both Unified Communications and Security technology licenses.
-
Catalyst Edge 8000 series routers fitted with voice cards or DSPs require DNA Essentials licensing. Routers without voice cards or DSPs require a minimum of DNA Essentials licensing.
-
For high-capacity requirements, you may also require a High Security (HSEC) license and additional throughput entitlement.
Refer to Authorization Codes for further details.
-
-
Build a baseline configuration for your platform that follows your business policies. In particular, configure the following and verify the working:
-
NTP
-
Acl'er
-
User authentication and remote access
-
DNS
-
IP-routing
-
IP addresses
-
-
The network toward Webex Calling must use a IPv4 address. Local Gateway Fully Qualified Domain Names (FQDN) or Service Record (SRV) addresses must resolve to a public IPv4 address on the internet.
-
All SIP and media ports on the Local Gateway interface facing Webex must be accessible from the internet, either directly or via static NAT. Ensure that you update your firewall accordingly.
-
Install a signed certificate on the Local Gateway (the following provides detailed configuration steps).
-
A public Certificate Authority (CA) as detailed in What Root Certificate Authorities are Supported for Calls to Cisco Webex Audio and Video Platforms? must sign the device certificate.
-
The FQDN configured in the Control Hub when creating a trunk must be the Common Name (CN) or Subject Alternate Name (SAN) certificate of the router. For eksempel:
-
If a configured trunk in the Control Hub of your organization has cube1.lgw.com:5061 as FQDN of the Local Gateway, then the CN or SAN in the router certificate must contain cube1.lgw.com.
-
If a configured trunk in the Control Hub of your organization has lgws.lgw.com as the SRV address of the Local Gateway(s) reachable from the trunk, then the CN or SAN in the router certificate must contain lgws.lgw.com. De poster, som SRV adressen går til (CNAME, A Record, eller IP-adresse), er valgfrie i SAN.
-
Whether you use an FQDN or SRV for the trunk, the contact address for all new SIP dialogs from your Local Gateway uses the name configured in the Control Hub.
-
-
-
Sørg for, at certifikater er signeret til klient- og serverbrug.
-
Upload the Cisco root CA bundle to the Local Gateway.
Konfiguration
1 |
Ensure that you assign valid and routable IP addresses to any Layer 3 interfaces, for example:
|
2 |
Protect STUN credentials on the router using symmetric encryption. Configure the primary encryption key and encryption type as follows: |
3 |
Create an encryption trustpoint with a certificate signed by your preferred Certificate Authority (CA). |
4 |
Authenticate your new certificate using your intermediate (or root) CA certificate, then import the certificate (Step 4). Enter the following exec or configuration command:
|
5 |
Import a signed host certificate using the following exec or configuration command:
|
6 |
Enable TLS1.2 exclusivity and specify the default trustpoint using the following configuration commands:
|
7 |
Install the Cisco root CA bundle, which includes the DigiCert CA certificate used by Webex Calling. Use the crypto pki trustpool import clean url command to download the root CA bundle from the specified URL, and to clear the current CA trustpool, then install the new bundle of certificates: If you need to use a proxy for access to the internet using HTTPS, add the following configuration before importing the CA bundle: ip http client proxy-server yourproxy.com proxy-port 80 |
1 |
Create a CUBE certificate-based PSTN trunk for an existing location in Control Hub. For more information, see Configure trunks, route groups, and dial plans for Webex Calling. Make a note of the trunk information that is provided once the trunk is created. These details, as highlighted in the following illustration, will be used in the configuration steps in this guide. ![]() |
2 |
Enter the following commands to configure CUBE as a Webex Calling Local Gateway: Her er en forklaring af felterne til konfigurationen:
Enables Cisco Unified Border Element (CUBE) features on the platform. tillad-forbindelser sip til sipEnable CUBE basic SIP back to back user agent functionality. For more information, see Allow connections. By default, T.38 fax transport is enabled. For more information, see fax protocol t38 (voice-service). Enables STUN (Session Traversal of UDP through NAT) globally. These global stun commands are only required when deploying your Local Gateway behind NAT.
For more information, see stun flowdata agent-id and stun flowdata shared-secret. asymmetric payload fullConfigures SIP asymmetric payload support for both DTMF and dynamic codec payloads. For more information on this command, see asymmetric payload. tidlig tilbud tvungetForces the Local Gateway to send SDP information in the initial INVITE message instead of waiting for acknowledgment from the neighboring peer. For more information on this command, see early-offer. sip-profiles inboundEnables CUBE to use SIP profiles to modify messages as they are received. Profiles are applied via dial-peers or tenants. |
3 |
Configure voice class codec 100 codec filter for the trunk. In this example, the same codec filter is used for all trunks. You can configure filters for each trunk for precise control. Her er en forklaring af felterne til konfigurationen: voice class codec 100Used to only allow preferred codecs for calls through SIP trunks. For more information, see voice class codec. Opus codec is supported only for SIP-based PSTN trunks. If the PSTN trunk uses a voice T1/E1 or analog FXO connection, exclude codec preference 1 opus from the voice class codec 100 configuration. |
4 |
Configure voice class stun-usage 100 to enable ICE on the Webex Calling trunk. (This step is not applicable for Webex for Government) Her er en forklaring af felterne til konfigurationen: stun usage ice liteUsed to enable ICE-Lite for all Webex Calling facing dial-peers to allow media-optimization whenever possible. For more information, see voice class stun usage and stun usage ice lite. The stun usage firewall-traversal flowdata command is only required when deploying your Local Gateway behind NAT. You require stun usage of ICE-lite for call flows using media path optimization. To provide media-optimization for a SIP to TDM gateway, configure a loopback dial-peer with ICE-Lite enabled on the IP-IP leg. For further technical details, contact the Account or TAC teams. |
5 |
Configure the media encryption policy for Webex traffic. (This step is not applicable for Webex for Government) Her er en forklaring af felterne til konfigurationen: voice class srtp-crypto 100Specifies SHA1_80 as the only SRTP cipher-suite CUBE offers in the SDP in offer and answer messages. Webex Calling only supports SHA1_80. For more information, see voice class srtp-crypto. |
6 |
Configure FIPS-compliant GCM ciphers (This step is applicable only for Webex for Government). Her er en forklaring af felterne til konfigurationen: voice class srtp-crypto 100Specifies GCM as the cipher-suite that CUBE offers. It is mandatory to configure GCM ciphers for Local Gateway for Webex for Government. |
7 |
Configure a pattern to uniquely identify calls to a Local Gateway trunk based on its destination FQDN or SRV: Her er en forklaring af felterne til konfigurationen: voice class uri 100 sipDefines a pattern to match an incoming SIP invite to an incoming trunk dial-peer. When entering this pattern, use LGW FQDN or SRV configured in Control Hub while creating a trunk. |
8 |
Configure SIP message manipulation profiles. If your gateway is configured with a public IP address, configure a profile as follows or skip to the next step if you are using NAT. In this example, cube1.lgw.com is the FQDN configured for the Local Gateway and "198.51.100.1" is the public IP address of the Local Gateway interface facing Webex Calling: Her er en forklaring af felterne til konfigurationen: rules 10 and 20To allow Webex to authenticate messages from your local gateway, the 'Contact' header in SIP request and responses messages must contain the value provisioned for the trunk in Control Hub. This will either be the FQDN of a single host, or the SRV domain name used for a cluster of devices. Skip the next step if you have configured your Local Gateway with public IP addresses. |
9 |
If your gateway is configured with a private IP address behind static NAT, configure inbound and outbound SIP profiles as follows. In this example, cube1.lgw.com is the FQDN configured for the Local Gateway, "10.80.13.12" is the interface IP address facing Webex Calling and "192.65.79.20" is the NAT public IP address. SIP profiles for outbound messages to Webex Calling
Her er en forklaring af felterne til konfigurationen: rules 10 and 20To allow Webex to authenticate messages from your local gateway, the 'Contact' header in SIP request and responses messages must contain the value provisioned for the trunk in Control Hub. This will either be the FQDN of a single host, or the SRV domain name used for a cluster of devices. rules 30 to 81Convert private address references to the external public address for the site, allowing Webex to correctly interpret and route subsequent messages. SIP profile for inbound messages from Webex Calling Her er en forklaring af felterne til konfigurationen: rules 10 to 80Convert public address references to the configured private address, allowing messages from Webex to be correctly processed by CUBE. For more information, see voice class sip-profiles. |
10 |
Configure a SIP Options keepalive with header modification profile. Her er en forklaring af felterne til konfigurationen: voice class sip-options-keepalive 100Configures a keepalive profile and enters voice class configuration mode. You can configure the time (in seconds) at which an SIP Out of Dialog Options Ping is sent to the dial-target when the heartbeat connection to the endpoint is in UP or Down status. This keepalive profile is triggered from the dial-peer configured towards Webex. To ensure that the contact headers include the SBC fully qualified domain name, SIP profile 115 is used. Rules 30, 40, and 50 are required only when the SBC is configured behind static NAT. In this example, cube1.lgw.com is the FQDN selected for the Local Gateway and if static NAT is used, "10.80.13.12" is the SBC interface IP address towards Webex Calling and "192.65.79.20" is the NAT public IP address. |
11 |
Configure Webex Calling trunk: |
Having built a trunk towards Webex Calling above, use the following configuration to create a non-encrypted trunk towards a SIP based PSTN provider:
If your Service Provider offers a secure PSTN trunk, you may follow a similar configuration as detailed above for the Webex Calling trunk. Secure to secure call routing is supported by CUBE.
If you are using a TDM / ISDN PSTN trunk, skip to next section Configure Local Gateway with TDM PSTN trunk.
To configure TDM interfaces for PSTN call legs on the Cisco TDM-SIP Gateways, see Configuring ISDN PRI.
1 |
Configure the following voice class uri to identify inbound calls from the PSTN trunk: Her er en forklaring af felterne til konfigurationen: voice class uri 200 sipDefines a pattern to match an incoming SIP invite to an incoming trunk dial-peer. When entering this pattern, use the IP address of you IP PSTN gateway. For more information, see voice class uri. |
2 |
Configure the following IP PSTN dial-peer: Her er en forklaring af felterne til konfigurationen: Definerer en VoIP dial-peer med et tag på 200 og giver en meningsfuld beskrivelse af brugervenlighed i forbindelse med administration og fejlfinding. For more information, see dial-peer voice. destinationsmønster DÅRLIG. DårligA dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface). session protokol sipv2Angiver, at dial-peer 200 håndterer SIP-call legs. For more information, see session protocol (dial peer). sessions mål ipv4:192.168.80.13Angiver destinationens mål-IPv4-adresse til at sende opkaldsbenet. Sessionsmålet her er ITSP's IP-adresse. For more information, see session target (VoIP dial peer). incoming uri via 200Definerer et sammenfald for VIA-headeren med IP PSTN's IP-adresse. Matches all incoming IP PSTN call legs on the Local Gateway with dial-peer 200. For more information, see incoming url. bind control source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see bind. bind media source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for media sent to PSTN. For more information, see bind. stemmeklasse-codec 100Configures the dial-peer to use the common codec filter list 100. For more information, see voice-class codec. dtmf-relay rtp-nteDefinerer RTP-NTE (RFC2833) som DTMF-evnen forventet på opkaldsbenet. For more information, see DTMF Relay (Voice over IP). ingen toneDeaktiverer stemmeaktivitetsregistrering. For more information, see vad (dial peer). |
3 |
If you are configuring your Local Gateway to only route calls between Webex Calling and the PSTN, add the following call routing configuration. If you are configuring your Local Gateway with a Unified Communications Manager platform, skip to the next section. |
Having built a trunk towards Webex Calling, use the following configuration to create a TDM trunk for your PSTN service with loop-back call routing to allow media optimization on the Webex call leg.
1 |
The loop-back dial-peer configuration uses dial-peer groups and call routing tags to ensure that calls pass correctly between Webex and the PSTN, without creating call routing loops. Configure the following translation rules that will be used to add and remove the call routing tags: Her er en forklaring af felterne til konfigurationen: voice translation-ruleUses regular expressions defined in rules to add or remove call routing tags. Over-decadic digits (‘A’) are used to add clarity for troubleshooting. In this configuration, the tag added by translation-profile 100 is used to guide calls from Webex Calling towards the PSTN via the loopback dial-peers. Similarly, the tag added by translation-profile 200 is used to guide calls from the PSTN towards Webex Calling. Translation-profiles 11 and 12 remove these tags before delivering calls to the Webex and PSTN trunks respectively. This example assumes that called numbers from Webex Calling are presented in +E.164 format. Rule 100 removes the leading + to maintain a valid called number. Rule 12 then adds a national or international routing digit(s) when removing the tag. Use digits that suit your local ISDN national dial plan. If Webex Calling presents numbers in national format, adjust rules 100 and 12 to simply add and remove the routing tag respectively. For more information, see voice translation-profile and voice translation-rule. |
2 |
Configure TDM voice interface ports as required by the trunk type and protocol used. For more information, see Configuring ISDN PRI. For example, the basic configuration of a Primary Rate ISDN interface installed in NIM slot 2 of a device might include the following: |
3 |
Configure the following TDM PSTN dial-peer: Her er en forklaring af felterne til konfigurationen: Definerer en VoIP med et tag på 200 og giver en meningsfuld beskrivelse af hensyn til brugervenlighed i administration og fejlfinding. For more information, see dial-peer voice. destinationsmønster DÅRLIG. DårligA dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface). translation-profile incoming 200Assigns the translation profile that will add a call routing tag to the incoming called number. direct-inward-dialRoutes the call without providing a secondary dial-tone. For more information, see direct-inward-dial. port 0/2/0:15The physical voice port associated with this dial-peer. |
4 |
To enable media optimization of IP paths for Local Gateways with TDM-IP call flows, you can modify the call routing by introducing a set of internal loop-back dial-peers between Webex Calling and PSTN trunks. Configure the following loop-back dial-peers. In this case, all incoming calls will be routed initially to dial-peer 10 and from there to either dial-peer 11 or 12 based on the applied routing tag. After removal of the routing tag, calls will be routed to the outbound trunk using dial-peer groups. Her er en forklaring af felterne til konfigurationen: Defines a VoIP dial-peer and gives a meaningful description for ease of management and troubleshooting. For more information, see dial-peer voice. translation-profile incoming 11Applies the translation profile defined earlier to remove the call routing tag before passing to the outbound trunk. destinationsmønster DÅRLIG. DårligA dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface). session protokol sipv2Specifies that this dial-peer handles SIP call legs. For more information, see session protocol (dial peer). session target 192.168.80.14Specifies the local router interface address as the call target to loop-back. For more information, see session target (voip dial peer). bind control source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for messages sent through the loop-back. For more information, see bind. bind media source-interface GigabitEthernet0/0/0Configures the source interface and associated IP address for media sent through the loop-back. For more information, see bind. dtmf-relay rtp-nteDefinerer RTP-NTE (RFC2833) som DTMF-evnen forventet på opkaldsbenet. For more information, see DTMF Relay (Voice over IP). codec g711alaw Forces all PSTN calls to use G.711. Select a-law or u-law to match the companding method used by your ISDN service. ingen toneDeaktiverer stemmeaktivitetsregistrering. For more information, see vad (dial peer). |
5 |
Add the following call routing configuration: This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features are configured.
|
The PSTN-Webex Calling configuration in the previous sections may be modified to include additional trunks to a Cisco Unified Communications Manager (UCM) cluster. In this case, all calls are routed via Unified CM. Calls from UCM on port 5060 are routed to the PSTN and calls from port 5065 are routed to Webex Calling. The following incremental configurations may be added to include this calling scenario.
1 |
Konfigurer følgende stemmeklasse-URI-adresser: |
2 |
Configure the following DNS records to specify SRV routing to Unified CM hosts: IOS XE uses these records for locally determining target UCM hosts and ports. With this configuration, it is not required to configure records in your DNS system. If you prefer to use your DNS, then these local configurations are not required. Her er en forklaring af felterne til konfigurationen: The following command creates a DNS SRV resource record. Create a record for each UCM host and trunk: ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub5.mydomain.com _sip._udp.pstntocucm.io: SRV resource record name 2: The SRV resource record priority 1: The SRV resource record weight 5060: The port number to use for the target host in this resource record ucmsub5.mydomain.com: The resource record target host To resolve the resource record target host names, create local DNS A records. For eksempel: ip host ucmsub5.mydomain.com 192.168.80.65 ip host: Creates a record in the local IOS XE database. ucmsub5.mydomain.com: The A record host name. 192.168.80.65: The host IP address. Create the SRV resource records and A records to reflect your UCM environment and preferred call distribution strategy. |
3 |
Configure the following dial-peers: |
4 |
Add call routing using the following configurations: |
Diagnosticeringssignaturer (DS) påviser proaktivt almindeligt observerede problemer i den lokale Cisco IOS XE-baserede gateway og genererer e-mail-, syslog- eller terminalmeddelelsesunderretning om begivenheden. Du kan også installere diagnosticeringssignaturer for at automatisere indsamling af diagnosticeringsdata og overføre indsamlede data til Cisco TAC-sagen, så problemer hurtigere kan blive løst.
Diagnosticeringssignaturer (DS) er XML-filer, der indeholder oplysninger om problemudløserbegivenheder og -handlinger til at informere, fejlfinde og udbedre problemet. Brug syslog-meddelelser, SNMP-begivenheder og gennem periodiske overvågning af specifikke vis kommandooutputs til at definere logikken for problemregistrering. Handlingstyperne inkluderer:
-
Indsamler vis kommandooutputs
-
Genererer en konsolideret logfil
-
Overførsel af filen til en netværksplacering, som f.eks. HTTPS, SCP, FTP-server
TAC-ingeniører forfatter DS-filer og digitalt underskrive den for integritetsbeskyttelse. Hver DS-fil har det unikke numeriske id tildelt af systemet. Diagnostic Signatures Lookup Tool (DSLT) is a single source to find applicable signatures for monitoring and troubleshooting various problems.
Før du begynder:
-
Rediger ikke DS-filen, som du downloader fra DSLT. De filer, du modificerer, installeres ikke på grund af fejl i integritetskontrollen.
-
En enkel Mail Transfer Protocol (SMTP)-server, som du kræver, at den lokale gateway sender e-mailunderretninger.
-
Sørg for, at den lokale gateway kører IOS XE 17.6.1 eller nyere, hvis du vil bruge den sikre SMTP-server til e-mailunderretninger.
Forudsætninger
Lokal gateway med IOS XE 17.6.1 eller nyere
-
Diagnosticeringssignaturer er aktiveret som standard.
-
Configure the secure email server that you use to send proactive notification if the device is running IOS XE 17.6.1 or higher.
configure terminal call-home mail-server <username>:<pwd>@<email server> priority 1 secure tls end
-
Konfigurer miljøvariablen ds_email med e-mailadressen på administratoren, så du kan underrette dig.
configure terminal call-home diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_email <email address> end
Installer diagnostiske signaturer til proaktiv overvågning
Monitorer høj CPU-udnyttelse
Denne DS sporer 5-sekunders CPU-udnyttelse ved hjælp af SNMP OID 1.3.6.1.4.1.9.2.1.56. Når udnyttelsen når 75 % eller mere, deaktiverer den alle fejlfindinger og afinstallerer alle diagnostiske signaturer, som du installerer i den lokale gateway. Følg trinene nedenfor for at installere signaturen.
-
Sørg for, at du aktiverede SNMP ved hjælp af kommandoen vis snmp. If SNMP is not enabled, then configure the snmp-server manager command.
show snmp %SNMP agent not enabled config t snmp-server manager end 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 indlogning: aktiveret
Download DS 64224 ved hjælp af følgende valgmuligheder i rullemenuen i værktøjet til opslag af diagnosticeringssignaturer:
copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software
Produkt
CUBE Enterprise in Webex Calling solution
Problemomfang
Ydeevne
Problemtype
Højt CPU-forbrug med e-mailmeddelelse
-
Kopiér DS XML-filen til den lokale gateways flash.
copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:
Følgende eksempel viser kopiering af filen fra en FTP-server til den lokale gateway.
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)
-
Installer DS XML-filen på den lokale gateway.
call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success
-
Brug kommandoen vis call-home diagnostic-signature til at bekræfte, at signaturen er installeret korrekt. Statuskolonnen skal have en "registreret" værdi.
show call-home diagnostic-signature Current diagnostic-signature settings: Diagnosticeringssignatur: aktiveret profil: CiscoTAC-1 (status: AKTIV) Downloader URL(er): https://tools.cisco.com/its/service/oddce/services/DDCEService Environment variable: ds_email: username@gmail.com
Download diagnosticeringssignaturer:
DS-id
DS-navn
Revision
Status
Seneste opdatering (GMT+00:00)
64224
DS_LGW_CPU_MON75
0.0.10
Tilmeldt
2020-11-07 22:05:33
Når denne signatur udløses, afinstallerer den alle kørende diagnosticeringssignaturer, inklusive sig selv. Hvis det er nødvendigt, skal du geninstallere DS 64224 for at fortsætte med at overvåge høj CPU-udnyttelse på den lokale gateway.
Overvågning af unormale opkald afbryder
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 generates a syslog and email notification. Please use the steps below to install the signature.
-
Kontroller, at SNMP er aktiveret ved hjælp af kommandoen vis snmp. If SNMP is not enabled, configure the snmp-server manager command.
show snmp %SNMP agent not enabled config t snmp-server manager end 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 indlogning: aktiveret
-
Download DS 65221 ved hjælp af følgende valgmuligheder i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Ydeevne
Problemtype
Registrering af SIP-unormalt opkaldsopkald med e-mail- og Syslog-underretning.
-
Kopiér DS XML-filen til den lokale gateway.
copy ftp://username:password@<server name or ip>/DS_65221.xml bootflash:
-
Installer DS XML-filen på den lokale gateway.
call-home diagnostic-signature load DS_65221.xml Load file DS_65221.xml success
-
Use the command show call-home diagnostic-signature to verify that the signature is successfully installed. Statuskolonnen skal have værdien "registreret".
Installer diagnostiske signaturer for at fejlse et problem
Du kan også bruge diagnosticeringssignaturer (DS) til at løse problemer hurtigt. Cisco TAC-ingeniører har oprettet flere signaturer, der aktiverer de nødvendige fejlfinding, der er påkrævet for at fejlfinde et givet problem, registrere problemhændelsen, indsamle det rigtige sæt diagnostiske data og overføre data automatisk til Cisco TAC-sagen. Dette fjerner behovet for at kontrollere problemhændelsen manuelt og gør fejlfinding af periodiske og kortvarige problemer meget nemmere.
Du kan bruge diagnosticeringssignaturopslagsopslagsværktøjet til at finde de relevante signaturer og installere dem til selv at løse et givet problem, eller du kan installere signaturen, som anbefales af TAC-teknikeren som en del af supportengagementet.
Her er et eksempel på, hvordan du finder og installerer en diagnosticeringssignatur for at påvise hændelsen “%VOICE_IEC-3-GW: CCAPI: Intern fejl (tærskel for opkaldsudsving): UDFØRING=1.1.181.1.29.0" syslog og automatisere diagnosticeringsdataindsamling ved hjælp af følgende trin:
Configure another DS environment variable ds_fsurl_prefix as the Cisco TAC file server path (cxd.cisco.com) to upload the diagnostics data. 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 in the following. The file upload token can be generated in the Attachments section of the Support Case Manager, as required.
configure terminal call-home diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_fsurl_prefix "scp://<case number>:<file upload token>@cxd.cisco.com" end
Eksempel:
call-home diagnostic-signature environment ds_fsurl_prefix " environment ds_fsurl_prefix "scp://612345678:abcdefghijklmnop@cxd.cisco.com"
-
Kontroller, at SNMP er aktiveret ved hjælp af kommandoen vis snmp. If SNMP not enabled, configure the snmp-server manager command.
show snmp %SNMP agent not enabled config t snmp-server manager end
-
Vi anbefaler, at du installerer High CPU monitoring DS 64224 som et proaktivt mål for at deaktivere alle fejlfindinger og diagnosticeringssignaturer i løbet af den høje CPU-udnyttelse. Download DS 64224 ved hjælp af følgende valgmuligheder i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Ydeevne
Problemtype
Høj CPU-udnyttelse med e-mailmeddelelse.
-
Download DS 65095 ved hjælp af følgende valgmuligheder i værktøjet til opslag af diagnosticeringssignaturer:
Feltnavn
Feltværdi
Platform
Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software
Produkt
CUBE Enterprise i Webex Calling-løsning
Problemomfang
Systemlogfiler
Problemtype
Systemlogfiler – %VOICE_IEC-3-GW: CCAPI: Intern fejl (tærskel for opkaldsudsving): IEC=1.1.181.1.29.0
-
Kopiér DS XML-filer til den lokale gateway.
copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash: 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.
call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success call-home diagnostic-signature load DS_65095.xml Load file DS_65095.xml success
-
Bekræft, at signaturen blev installeret ved hjælp af show call-home diagnostic-signature. Statuskolonnen skal have værdien "registreret".
show call-home diagnostic-signature Current diagnostic-signature settings: Diagnosticeringssignatur: aktiveret profil: CiscoTAC-1 (status: AKTIV) Downloader URL(er): 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
Downloadede diagnosticeringssignaturer:
DS-id
DS-navn
Revision
Status
Seneste opdatering (GMT+00:00)
64224
00:07:45
DS_LGW_CPU_MON75
0.0.10
Tilmeldt
2020-11-08:00:07:45
65095
00:12:53
DS_LGW_IEC_Call_spike_threshold
0.0.12
Tilmeldt
2020-11-08:00:12:53
Bekræft afvikling af diagnostiske signaturer
I følgende kommando, kolonnen "Status" for kommandoen vis call-home diagnostisk-signatur ændringer til "kører", mens den lokale gateway udfører den handling, der er defineret i signaturen. Resultatet af show call-home diagnostic-signature statistics er den bedste måde til at verificere, om en diagnostisk signatur registrerer en begivenhed af interesse og udførte handlingen. Kolonnen "Udløst/Maks./Afinstaller" angiver antallet af gange, den angivne signatur har udløst en begivenhed, det maksimale antal gange, den er defineret til at påvise en begivenhed, og om signaturen afinstallerer sig selv efter at påvise det maksimale antal udløste begivenheder.
show call-home diagnostic-signature Current diagnostic-signature settings: Diagnosticeringssignatur: aktiveret
profil: CiscoTAC-1 (status: AKTIV)
Downloader URL(er): 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
Downloadede diagnosticeringssignaturer:
DS-id |
DS-navn |
Revision |
Status |
Seneste opdatering (GMT+00:00) |
---|---|---|---|---|
64224 |
DS_LGW_CPU_MON75 |
0.0.10 |
Tilmeldt |
2020-11-08 00:07:45 |
65095 |
DS_LGW_IEC_Call_spike_threshold |
0.0.12 |
Kører |
2020-11-08 00:12:53 |
vis call-home diagnostisk-signatur-statistik
DS-id |
DS-navn |
Triggered/Max/Deinstall |
Gennemsnitlig kørselstid (sekunder) |
Maks. kørselstid (sekunder) |
---|---|---|---|---|
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 |
Den e-mailunderretning, der sendes under afvikling af diagnosesignatur, indeholder vigtige oplysninger, såsom problemtype, enhedsoplysninger, softwareversion, kørende konfiguration og vis kommandooutputs, der er relevante for fejlfinding af det givne problem.
![](https://cisco-api.ingeniuxondemand.com/DITA/content/en/us/td/i/400001-500000/450001-460000/456001-457000/456090.jpg)
Afinstaller diagnostiske signaturer
Brug de diagnostiske signaturer til fejlfindingsformål, der typisk defineres til afinstallation efter påvisning af nogle problemhændelser. Hvis du vil afinstallere en signatur manuelt, skal du hente DS-id'et fra resultatet af vis call-home diagnosticeringssignatur og køre følgende kommando:
call-home diagnostic-signature deinstall <DS ID>
Eksempel:
call-home diagnostic-signature deinstall 64224
Nye signaturer tilføjes regelmæssigt til værktøjet Diagnosticeringssignaturopslag på baggrund af problemer, der observeres i udrulninger. TAC understøtter i øjeblikket ikke anmodninger om at oprette nye brugertilpassede signaturer.