Genel Bakış

Webex Calling currently supports two versions of Local Gateway:

  • Yerel Ağ Geçidi

  • Local Gateway for Webex for Government

Key considerations

  • Before you begin, understand the premises-based Public Switched Telephone Network (PSTN) and Local Gateway (LGW) requirements for Webex Calling. Daha fazla bilgi için Bkz. Hızlı Webex Calling Cisco Tercih Edilen Mimari.

  • Bu makale, mevcut ses yapılandırmasıyla özel bir Yerel Ağ Geçidi platformunun olduğunu varsayer. 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.

The procedures contain links to command reference documentation where you can learn more about the individual command options. All command reference links go to the Webex Managed Gateways Command Reference unless stated otherwise (in which case, the command links go to Cisco IOS Voice Command Reference). You can access all these guides at Cisco Unified Border Element Command References.

For information on the supported third-party SBCs, refer to the respective product reference documentation.

Configure your Local Gateway

Ana bilgisayar siteniz için Yerel Ağ Geçidini yapılandırmak üzere iki Webex Calling vardır:

  • Kayıt tabanlı trunk

  • Sertifika tabanlı 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. Komut Satırı Arayüzünü (CLI) kullanarak Yerel Ağ Geçidinde aşağıdaki adımları uygulayın. 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.

Key considerations

Local Gateway for Webex for Government doesn’t support the following:

  • STUN/ICE-Lite for media path optimization

  • Fax (T.38)

Configure your Local Gateway for Webex for Government

To configure Local Gateway for your Webex Calling trunk in Webex for Government, use the following option:

  • Sertifika tabanlı 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.

Webex for Government doesn’t support registration-based Local Gateway.

Design overview

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

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.

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.

Throughout this document, the host names, IP addresses, and interfaces illustrated in the following image are used.

Use the configuration guidance in the rest of this document to complete your Local Gateway configuration as follows:

  • Adım 1: Configure router baseline connectivity and security

  • Adım 2: Configure Webex Calling Trunk

    Depending on your required architecture, follow either:

  • 3. Adım: Configure Local Gateway with SIP PSTN trunk

  • 4. Adım: Configure Local Gateway with existing Unified CM environment

    Veya:

  • 3. Adım: Configure Local Gateway with TDM PSTN trunk

Configure connectivity and security

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

    • User authentication and remote access

    • DNS

    • IP yönlendirme

    • IP addresses

  • The network toward Webex Calling must use an IPv4 address.

  • Upload the Cisco root CA bundle to the Local Gateway.

Yapılandırma

1

Ensure that you assign valid and routable IP addresses to any Layer 3 interfaces, for example:

 interface GigabitEthernet0/0/0 description Interface facing PSTN and/or CUCM ip address 10.80.13.12 255.255.255.0 ! interface GigabitEthernet0/0/1 description Interface facing Webex Calling (Private address) ip address 192.51.100.1 255.255.255.240

2

Protect registration and STUN credentials on the router using symmetric encryption. Configure the primary encryption key and encryption type as follows:

 key config-key password-encrypt YourPassword password encryption aes

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.
 crypto pki trustpoint EmptyTP revocation-check none
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.

  1. Set tcp-retry count to 1000 (5-msec multiples = 5 seconds).

  2. The timer connection establish command allows you to tune how long the LGW waits to set up a connection with a proxy before considering the next available option. The default for this timer is 20 seconds and the minimum 5 seconds. Start with a low value and increase if necessary to accommodate network conditions.

 sip-ua timers connection establish tls 5 transport tcp tls v1.2 crypto signaling default trustpoint EmptyTP cn-san-validate server tcp-retry 1000

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
 ip http client source-interface GigabitEthernet0/0/1 crypto pki trustpool import clean url https://www.cisco.com/security/pki/trs/ios_core.p7b
Configure Webex Calling registration-based trunk
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:

 voice service voip ip address trusted list ipv4 x.x.x.x y.y.y.y mode border-element media statistics media bulk-stats allow-connections sip to sip no supplementary-service sip refer stun stun flowdata agent-id 1 boot-count 4 stun flowdata shared-secret 0 Password123$ sip asymmetric payload full early-offer forced

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

 ip address trusted list  ipv4 x.x.x.x y.y.y.y

  • To protect against toll fraud, the trusted address list defines a list of hosts and networks from which the Local Gateway expects legitimate VoIP calls.

  • By default, Local Gateway blocks all incoming VoIP messages from IP addresses not in its trusted list. Statically configured dial-peers with “session target IP” or server group IP addresses are trusted by default, so do not need to be added to the trusted list.

  • When configuring your Local Gateway, add the IP subnets of your regional Webex Calling data center to the list. Daha fazla bilgi için bkz. Webex Calling için Port Referans Bilgileri. Also, add address ranges for Unified Communications Manager servers (if used) and PSTN trunk gateways.

    If your LGW is behind a firewall with restricted cone NAT, you may prefer to disable the IP address trusted list on the Webex Calling facing interface. Güvenlik duvarı zaten sizi istenmeyen gelen çağrılara karşı VoIP. Devre dışı bırakma işlemi, Webex Calling eşlerin adreslerinin sabit bırak bırakıldığından ve her durumda eşler için güvenlik duvarınızı yapılandırmanız gerekmektedir olduğundan, uzun vadeli yapılandırma yüklerinizi azaltır.

mode border-element

Enables Cisco Unified Border Element (CUBE) features on the platform.

media statistics

Yerel Ağ Geçidinde medya izlemeyi sağlar.

media bulk-stats

Toplu çağrı istatistikleri için veri anketlerini ankete ekleme kontrolünü sağlar.

For more information on these commands, see Media.

sip'e bağlantı sip izin ver

Enable 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).

stun

Enables STUN (Session Traversal of UDP through NAT) globally.

  • Bir Webex Calling kullanıcısına (örneğin, hem arayan hem de arayan taraf) çağrıyı aboneleri Webex Calling ve Webex Calling SBC'de ortam yer imlerine çıpalarsanız İğne açık değil olarak ortam Yerel Ağ Geçidine akış akar.

  • The STUN bindings feature on the Local Gateway allows locally generated STUN requests to be sent over the negotiated media path. This helps to open the pinhole in the firewall.

For more information, see stun flowdata agent-id and stun flowdata shared-secret.

asymmetric payload full

Configures SIP asymmetric payload support for both DTMF and dynamic codec payloads. For more information on this command, see asymmetric payload.

erken teklif zorlama

Forces 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.

 voice class codec 100 codec preference 1 opus codec preference 2 g711ulaw codec preference 3 g711alaw

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class codec 100

Used 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.

 voice class stun-usage 100 stun usage firewall-traversal flowdata stun usage ice lite

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

stun usage ice lite

Used 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.

 voice class srtp-crypto 100 crypto 1 AES_CM_128_HMAC_SHA1_80

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class srtp-crypto 100

Specifies 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: 

 voice class uri 100 sip pattern dtg=Dallas1463285401_LGU

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class uri 100 sip

Defines 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.

 voice class sip-profiles 100 rule 10 request ANY sip-header SIP-Req-URI modify "sips:" "sip:" rule 20 request ANY sip-header To modify "<sips:" "<sip:" rule 30 request ANY sip-header From modify "<sips:" "<sip:" rule 40 request ANY sip-header Contact modify "<sips:(.*)>" "<sip:\1;transport=tls>" rule 50 response ANY sip-header To modify "<sips:" "<sip:" rule 60 response ANY sip-header From modify "<sips:" "<sip:" rule 70 response ANY sip-header Contact modify "<sips:" "<sip:" rule 80 request ANY sip-header From modify ">" ";otg=dallas1463285401_lgu>" rule 90 request ANY sip-header P-Asserted-Identity modify "sips:" "sip:"

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

  • rule 10 to 70 and 90

    Ensures that SIP headers used for call signaling use the sip, rather than sips scheme, which is required by Webex proxies. Configuring CUBE to use sips ensures that secure registration is used.

  • rule 80

    Modifies the From header to include the trunk group OTG/DTG identifier from Control Hub to uniquely identify a Local Gateway site within an enterprise.

8

Configure Webex Calling trunk:

  1. Create voice class tenant 100 to define and group configurations required specifically for the Webex Calling trunk. In particular, the trunk registration details provided in Control Hub earlier will be used in this step as detailed below. Dial-peers associated with this tenant later will inherit these configurations.

    The following example uses the values illustrated in Step 1 for the purpose of this guide (shown in bold). Replace these with values for your trunk in your configuration.

     voice class tenant 100 registrar dns:98027369.us10.bcld.webex.com scheme sips expires 240 refresh-ratio 50 tcp tls credentials number Dallas1171197921_LGU username Dallas1463285401_LGU password 0 9Wt[M6ifY+ realm BroadWorks authentication username Dallas1463285401_LGU password 0 9Wt[M6ifY+ realm BroadWorks authentication username Dallas1463285401_LGU password 0 9Wt[M6ifY+ realm 98027369.us10.bcld.webex.com no remote-party-id sip-server dns:98027369.us10.bcld.webex.com connection-reuse srtp-crypto 100 session transport tcp tls url sips error-passthru asserted-id pai bind control source-interface GigabitEthernet0/0/1 bind media source-interface GigabitEthernet0/0/1 no pass-thru content custom-sdp sip-profiles 100 outbound-proxy dns:dfw04.sipconnect-us.bcld.webex.com privacy-policy passthru

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    voice class tenant 100

    Defines a set of configuration parameters that will be used only for the Webex Calling trunk. For more information, see voice class tenant.

    registrar dns:98027369.us10.bcld.webex.com scheme sips expires 240 refresh-ratio 50 tcp tls

    Kayıt iki dakikada bir (240 saniyenin %50'si) yenilenecek şekilde ayarlanmış Yerel Ağ Geçidi için kayıt şirketi sunucusu. For more information, see registrar.

    Ensure that you use the Register Domain value from Control Hub here.

    credentials number Dallas1171197921_LGU username Dallas1463285401_LGU password 0 9Wt[M6ifY+ realm BroadWorks

    Trunk kayıt zoru için kimlik bilgileri. For more information, see credentials (SIP UA).

    Ensure that you use the Line/Port host, Authentication Username and Authentication Password values respectively from Control Hub here.

    authentication username Dallas1171197921_LGU password 0 9Wt[M6ifY+ realm BroadWorks
    authentication username Dallas1171197921_LGU password 0 9Wt[M6ifY+ realm 98027369.us10.bcld.webex.com

    Çağrılar için kimlik doğrulama sınaması. For more information, see authentication (dial-peer).

    Ensure that you use the Authentication Username, Authentication Password and Registrar Domain values respectively from Control Hub here.

    uzak taraf kimliği yok

    Disable SIP Remote-Party-ID (RPID) header as Webex Calling supports PAI, which is enabled using CIO asserted-id pai. For more information, see remote-party-id.

    sip-server dns:us25.sipconnect.bcld.webex.com

    Configures the target SIP server for the trunk. Use the edge proxy SRV address provided in Control Hub when you created your trunk.

    bağlantı-yeniden

    Kayıt ve çağrı işleme için aynı kalıcı bağlantıyı kullanır. For more information, see connection-reuse.

    srtp-crypto 100

    Configures the preferred cipher-suites for the SRTP call leg (connection) (specified in step 5). For more information, see voice class srtp-crypto.

    oturum taşıma tcp tls

    Taşımayı TLS olarak ayarlar. For more information, see session-transport.

    url sips

    SRV erişim SBC tarafından desteklenen SPS'ler olmalı; tüm diğer mesajlar, sip profili 200'e göre SIP olarak değiştirilir.

    hata-passthru

    SIP hata yanıt geçiş işlevini belirtir. For more information, see error-passthru.

    asserted-id pai

    Yerel Ağ Geçidi'nde PAI işlemeyi döner. For more information, see asserted-id.

    bind control source-interface GigabitEthernet0/0/1

    Configures the source interface and associated IP address for messages sent to WebexCalling. For more information, see bind.

    bind media source-interface GigabitEthernet0/0/1

    Configures the source interface and associated IP address for media sent to WebexCalling. For more information, see bind.

    geçiş içeriği özel sdp yok

    Kiracı altında varsayılan komut. For more information on this command, see pass-thru content.

    sip-profiles 100

    Changes SIPs to SIP and modify Line/Port for INVITE and REGISTER messages as defined in sip-profiles 100. For more information, see voice class sip-profiles.

    outbound-proxy dns:dfw04.sipconnect-us.bcld.webex.com

    Webex Calling SBC'ye erişin. Insert the Outbound Proxy Address provided in Control Hub when you created your trunk. For more information, see outbound-proxy.

    gizlilik-politika geçişi

    Configures the privacy header policy options for the trunk to pass privacy values from the received message to the next call leg. For more information, see privacy-policy.

  2. Configure the Webex Calling trunk dial-peer. 

     dial-peer voice 100 voip description Inbound/Outbound Webex Calling max-conn 250 destination-pattern BAD.BAD session protocol sipv2 session target sip-server incoming uri request 100 voice-class codec 100 dtmf-relay rtp-nte voice-class stun-usage 100 no voice-class sip localhost voice-class sip tenant 100 srtp no vad

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

     dial-peer voice 100 voip  description Inbound/Outbound Webex Calling

    100 VoIP etiketine sahip bir ağ eşlemi tanımlar ve yönetim ve sorun giderme kolaylığı için anlamlı bir açıklama sağlar.

    max-conn 250

    Restricts the number of concurrent inbound and outbound calls between the LGW and Webex Calling. For registration trunks, the maximum value configured should be 250. Usea lower value if that would be more appropriate for your deployment. For more information on concurrent call limits for Local Gateway, refer to the Get started with Local Gateway document.

    hedef şablon BAD. Kötü

    A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. Any valid destination pattern may be used in this case.

    oturum protokolü sipv2

    Çağrı eş 100'un SIP çağrı ayaklarıyla iş ele alanı olduğunu belirtir. For more information, see session protocol (dial-peer).

    oturum hedefi sip sunucusu

    Indicates that the SIP server defined in tenant 100 is inherited and used for the destination for calls from this dial peer.

    incoming uri request 100

    To specify the voice class used to match a VoIP dial peer to the uniform resource identifier (URI) of an incoming call. For more information, see incoming uri.

    voice-class codec 100

    Configures the dial-peer to use the common codec filter list 100. For more information, see voice-class codec.

    voice-class stun-usage 100

    Allows locally generated STUN requests on the Local Gateway to be sent over the negotiated media path. STUN helps to open a firewall pinhole for media traffic.

    ses sınıfı sip yerel sahibi yok

    Giden mesajların Gelen, Çağrı Kimliği ve Uzak Taraf Kimliği üst bilgilerinde fiziksel IP adresi yerine DNS yerel ana bilgisayar adının yerine değiştirmesini devre dışı bırakmıştır.

    voice-class sip tenant 100

    The dial-peer inherits all parameters configured globally and in tenant 100. Parameters may be overridden at the dial-peer level.

    srtp

    Çağrı ayağı için SRTP'yi sağlar.

    yok devam

    Ses etkinliği algılamayı devre dışı bırakıyor.

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.

Configure Local Gateway with a SIP PSTN 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:

 voice class uri 200 sip host ipv4:192.168.80.13

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class uri 200 sip

Defines 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:

 dial-peer voice 200 voip description Inbound/Outbound IP PSTN trunk destination-pattern BAD.BAD session protocol sipv2 session target ipv4:192.168.80.13 incoming uri via 200 voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 voice-class codec 100 dtmf-relay rtp-nte no vad

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

 dial-peer voice 200 voip  description Inbound/Outbound IP PSTN trunk

200 VoIP etiketine sahip bir ağ eşlemesi tanımlar ve yönetim ve sorun gidermenin kolaylığı için anlamlı bir açıklama sağlar. For more information, see dial-peer voice.

hedef şablon BAD. Kötü

A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface).

oturum protokolü sipv2

Çağrı eş 200'un SIP çağrı ayaklarıyla iş ele alanı olduğunu belirtir. For more information, see session protocol (dial peer).

oturum hedefi ipv4:192.168.80.13

Çağrı ayağı göndermek için hedefin hedef IPv4 adresini gösterir. Buradaki oturum hedefi ITSP'nin IP adresidir. For more information, see  session target (VoIP dial peer).

incoming uri via 200

IP adresinin IP adresiyle VIA üstbilgisi için eşleşme PSTN tanımlar. 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/0

Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see  bind.

bind media source-interface GigabitEthernet0/0/0

Configures the source interface and associated IP address for media sent to PSTN. For more information, see  bind.

ses sınıfı kodek 100

Configures the dial-peer to use the common codec filter list 100. For more information, see voice-class codec.

dtmf-relay rtp-nte

RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. For more information, see DTMF Relay (Voice over IP).

yok devam

Ses etkinliği algılamayı devre dışı bırakıyor. 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.

  1. Create dial-peer groups to route calls towards Webex Calling or the PSTN. Define DPG 100 with outbound dial-peer 100 toward Webex Calling. DPG 100 is applied to the incoming dial-peer from the PSTN. Similarly, define DPG 200 with outbound dial-peer 200 toward the PSTN. DPG 200 is applied to the incoming dial-peer from Webex.

     voice class dpg 100 description Route calls to Webex Calling dial-peer 100 voice class dpg 200 description Route calls to PSTN dial-peer 200

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    dial-peer 100

    Associates an outbound dial-peer with a dial-peer group. For more information, see  voice-class dpg.

  2. Apply dial-peer groups to route calls from Webex to the PSTN and from the PSTN to Webex: 

     dial-peer voice 100 destination dpg 200 dial-peer voice 200 destination dpg 100

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    hedef dpg 200

    Specifies which dial-peer group, and therefore dial-peer should be used for the outbound treatment for calls presented to this incoming dial-peer.

    This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features are configured.

Configure Local Gateway with a TDM PSTN trunk

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.

If you do not require IP media optimization, follow the configuration steps for a SIP PSTN trunk. Use a voice port and POTS dial-peer (as shown in Steps 2 and 3) instead of the PSTN VoIP dial-peer.
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:

 voice translation-rule 100 rule 1 /^\+/ /A2A/ voice translation-profile 100 translate called 100 voice translation-rule 200 rule 1 /^/ /A1A/ voice translation-profile 200 translate called 200 voice translation-rule 11 rule 1 /^A1A/ // voice translation-profile 11 translate called 11 voice translation-rule 12 rule 1 /^A2A44/ /0/ rule 2/^A2A/ /00/ voice translation-profile 12 translate called 12

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice translation-rule

Uses 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:

 card type e1 0 2 isdn switch-type primary-net5 controller E1 0/2/0 pri-group timeslots 1-31
3

Configure the following TDM PSTN dial-peer:

 dial-peer voice 200 pots description Inbound/Outbound PRI PSTN trunk destination-pattern BAD.BAD translation-profile incoming 200 direct-inward-dial port 0/2/0:15

Yapılandırmaya ilişkin alanların açıklaması şöyledir: 

 dial-peer voice 200 pots  description Inbound/Outbound PRI PSTN trunk

200 VoIP etiketine sahip bir ağ eşlemi tanımlar ve yönetimin ve sorun gidermenin kolaylığı için anlamlı bir açıklama verir. For more information, see dial-peer voice.

hedef şablon BAD. Kötü

A 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 200

Assigns the translation profile that will add a call routing tag to the incoming called number.

direct-inward-dial

Routes the call without providing a secondary dial-tone. For more information, see direct-inward-dial.

port 0/2/0:15

The 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.

 dial-peer voice 10 voip description Outbound loop-around leg destination-pattern BAD.BAD session protocol sipv2 session target ipv4:192.168.80.14 voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711alaw no vad dial-peer voice 11 voip description Inbound loop-around leg towards Webex translation-profile incoming 11 session protocol sipv2 incoming called-number A1AT voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711alaw no vad dial-peer voice 12 voip description Inbound loop-around leg towards PSTN translation-profile incoming 12 session protocol sipv2 incoming called-number A2AT voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711alaw no vad

Yapılandırmaya ilişkin alanların açıklaması şöyledir: 

 dial-peer voice 10 pots  description Outbound loop-around leg

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 11

Applies the translation profile defined earlier to remove the call routing tag before passing to the outbound trunk.

hedef şablon BAD. Kötü

A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface).

oturum protokolü sipv2

Specifies that this dial-peer handles SIP call legs. For more information, see  session protocol (dial peer).

session target 192.168.80.14

Specifies 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/0

Configures 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/0

Configures the source interface and associated IP address for media sent through the loop-back. For more information, see  bind.

dtmf-relay rtp-nte

RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. 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.

yok devam

Ses etkinliği algılamayı devre dışı bırakıyor. For more information, see  vad (dial peer).

5

Add the following call routing configuration:

  1. Create dial-peer groups to route calls between the PSTN and Webex trunks, via the loop-back.

     voice class dpg 100 description Route calls to Webex Calling dial-peer 100 voice class dpg 200 description Route calls to PSTN dial-peer 200 voice class dpg 10 description Route calls to Loopback dial-peer 10

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    dial-peer 100

    Associates an outbound dial-peer with a dial-peer group. For more information, see  voice-class dpg.

  2. Apply dial-peer groups to route calls.

     dial-peer voice 100 destination dpg 10 dial-peer voice 200 destination dpg 10 dial-peer voice 11 destination dpg 100 dial-peer voice 12 destination dpg 200

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    destination dpg 200

    Specifies which dial-peer group, and therefore dial-peer should be used for the outbound treatment for calls presented to this incoming dial-peer.

This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features are configured.
Mevcut bir Unified CM ortamıyla Yerel Ağ Geçidi'ni yapılandırma

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.

1

Aşağıdaki ses sınıfı URI'lerini yapılandırın:

  1. Classifies Unified CM to Webex calls using SIP VIA port:

     sesli sınıf uri 300 sip 
 modeli:5065

  2. Classifies Unified CM to PSTN calls using SIP via port:

     voice class uri 400 sip pattern 192\.168\.80\.6[0-5]:5060

    Classify incoming messages from the UCM towards the PSTN trunk using one or more patterns that describe the originating source addresses and port number. Regular expressions may be used to define matching patterns if required.

    In the example above, a regular expression is used to match any IP address in the range 192.168.80.60 to 65 and port number 5060.

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.

 ip host ucmpub.mydomain.com 192.168.80.60 ip host ucmsub1.mydomain.com 192.168.80.61 ip host ucmsub2.mydomain.com 192.168.80.62 ip host ucmsub3.mydomain.com 192.168.80.63 ip host ucmsub4.mydomain.com 192.168.80.64 ip host ucmsub5.mydomain.com 192.168.80.65 ip host _sip._udp.wxtocucm.io srv 0 1 5065 ucmpub.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub1.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub2.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub3.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub4.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub5.mydomain.com ip host _sip._udp.pstntocucm.io srv 0 1 5060 ucmpub.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub1.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub2.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub3.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub4.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub5.mydomain.com

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

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. Örneğin:

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:

  1. Dial-peer for calls between Unified CM and Webex Calling:

     dial-peer voice 300 voip description UCM-Webex Calling trunk destination-pattern BAD.BAD session protocol sipv2 session target dns:wxtocucm.io incoming uri via 300 voice-class codec 100 voice-class sip bind control source-interface GigabitEthernet 0/0/0 voice-class sip bind media source-interface GigabitEthernet 0/0/0 dtmf-relay rtp-nte no vad

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

     dial-peer voice 300 voip  description UCM-Webex Calling trunk

    Defines a VoIP dial-peer with a tag 300 and gives a meaningful description for ease of management and troubleshooting.

    hedef şablon BAD. Kötü

    A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. Any valid destination pattern may be used in this case.

    oturum protokolü sipv2

    Specifies that dial-peer 300 handles SIP call legs. For more information, see  session protocol (dial-peer).

    session target dns:wxtocucm.io

    Defines the session target of multiple Unified CM nodes through DNS SRV resolution. In this case, the locally defined SRV record wxtocucm.io is used to direct calls.

    300 üzerinden gelen uri

    Uses voice class URI 300 to direct all incoming traffic from Unified CM using source port 5065 to this dial-peer. For more information, see  incoming uri.

    voice-class codec 100

    Indicates codec filter list for calls to and from Unified CM. For more information, see  voice class codec.

    bind control source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see  bind.

    bind media source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for media sent to PSTN. For more information, see  bind.

    dtmf-relay rtp-nte

    RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. For more information, see  DTMF Relay (Voice over IP).

    yok devam

    Ses etkinliği algılamayı devre dışı bırakıyor. For more information, see  vad (dial peer).

  2. Dial-peer for calls between Unified CM and the PSTN:

     dial-peer voice 400 voip description UCM-PSTN trunk destination-pattern BAD.BAD session protocol sipv2 session target dns:pstntocucm.io incoming uri via 400 voice-class codec 100 voice-class sip bind control source-interface GigabitEthernet 0/0/0 voice-class sip bind media source-interface GigabitEthernet 0/0/0 dtmf-relay rtp-nte no vad

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

     dial-peer voice 400 voip  description UCM-PSTN trunk

    400 VoIP etiketine sahip bir ağ eşlemesi tanımlar ve yönetim ve sorun gidermenin kolaylığı için anlamlı bir açıklama sağlar.

    hedef şablon BAD. Kötü

    A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. Any valid destination pattern may be used in this case.

    oturum protokolü sipv2

    Specifies that dial-peer 400 handles SIP call legs. For more information, see  session protocol (dial-peer).

    session target dns:pstntocucm.io

    Defines the session target of multiple Unified CM nodes through DNS SRV resolution. In this case, the locally defined SRV record pstntocucm.io is used to direct calls.

    incoming uri via 400

    Uses voice class URI 400 to direct all incoming traffic from the specified Unified CM hosts using source port 5060 to this dial-peer. For more information, see  incoming uri.

    voice-class codec 100

    Indicates codec filter list for calls to and from Unified CM. For more information, see  voice class codec.

    bind control source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see  bind.

    bind media source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for media sent to PSTN. For more information, see  bind.

    dtmf-relay rtp-nte

    RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. For more information, see  DTMF Relay (Voice over IP).

    yok devam

    Ses etkinliği algılamayı devre dışı bırakıyor. For more information, see  vad (dial peer).

4

Add call routing using the following configurations:

  1. Create dial-peer groups to route calls between Unified CM and Webex Calling. Define DPG 100 with outbound dial-peer 100 towards Webex Calling. DPG 100 is applied to the associated incoming dial-peer from Unified CM. Similarly, define DPG 300 with outbound dial-peer 300 toward Unified CM. DPG 300 is applied to the incoming dial-peer from Webex.

     voice class dpg 100 description Route calls to Webex Calling dial-peer 100 voice class dpg 300 description Route calls to Unified CM Webex Calling trunk dial-peer 300

  2. Create a dial-peer groups to route calls between Unified CM and the PSTN. Define DPG 200 with outbound dial-peer 200 toward the PSTN. DPG 200 is applied to the associated incoming dial-peer from Unified CM. Similarly, define DPG 400 with outbound dial-peer 400 toward Unified CM. DPG 400 is applied to the incoming dial-peer from the PSTN.

     voice class dpg 200 description Route calls to PSTN dial-peer 200 voice class dpg 400 description Route calls to Unified CM PSTN trunk dial-peer 400

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    dial-peer  100

    Associates an outbound dial-peer with a dial-peer group. For more information, see  voice-class dpg.

  3. Apply dial-peer groups to route calls from Webex to Unified CM and from Unified CM to Webex: 

     dial-peer voice 100 destination dpg 300 dial-peer voice 300 destination dpg 100

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    destination dpg 300

    Specifies which dial-peer group, and therefore dial-peer should be used for the outbound treatment for calls presented to this incoming dial-peer.

  4. Apply dial-peer groups to route calls from the PSTN to Unified CM and from Unified CM to the PSTN:

     dial-peer voice 200 destination dpg 400 dial-peer voice 400 destination dpg 200

    This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features have been configured.

Tanılama imzaları ile Yerel Ağ Geçidi'ni izleme ve sorun giderme

Tanılama İmzaları (DS), IOS XE tabanlı Yerel Ağ Geçidi'de sık gözlemlenen sorunları proaktif olarak algılar ve etkinliğin e-posta, syslog veya terminal mesajı bildirimini oluşturan. You can also install the DS to automate diagnostics data collection and transfer-collected data to the Cisco TAC case to accelerate resolution time.

Tanılama İmzaları (DS), sorunu bildirmek, gidermek ve sorunu düzeltmek için gereken olayları ve işlemleri içeren XML dosyalarıdır. You can define the problem detection logic using syslog messages, SNMP events and through periodic monitoring of specific show command outputs.

Eylem türleri, show command çıkışlarını toplamayı içerir:

  • Birleştirilmiş bir günlük dosyası oluşturma

  • Uploading the file to a user-provided network location such as HTTPS, SCP, FTP server.

TAC mühendisleri DS dosyalarını yazar ve bütünlüğü koruma için dijital olarak imzalar. Her bir DS'nin sistem tarafından atanmış benzersiz bir kimlik numarası vardır. Diagnostic Signatures Lookup Tool (DSLT) is a single source to find applicable signatures for monitoring and troubleshooting various problems.

Başlamadan önce:

  • DSLT'den indiren DS dosyasını düzenlemeyin . Değiştir işleminiz, bütünlüğü kontrol hatası nedeniyle yükleme başarısız oldu.

  • Yerel Ağ Geçidi'nin e-posta bildirimlerini göndermesi için gerekli olan Basit Posta Aktarım Protokolü (SMTP) sunucusu.

  • E-posta bildirimleri için güvenli SMTP sunucusunu kullanmak isterseniz Yerel Ağ Geçidi'nin IOS XE 17.6.1 veya daha yüksek bir alanı çalıştır olduğundan emin olun.

Cisco WebEx Meeting Center Yapılandırma Kılavuzları

Local Gateway running IOS XE 17.6.1a or higher

  1. Tanı İmzalarının varsayılan olarak etkinleştirilmesi.

  2. 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

  3. 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"

Cisco IOS XE Yazılımında çalışan Yerel Ağ Geçidi, OAuth'u destekleyen tipik bir web tabanlı Gmail istemcisi değildir, bu nedenle belirli bir Gmail hesap ayarını yapılandırmamız ve cihazdan gelen e-postanın doğru şekilde işlenmesi için belirli bir izin sağlamamız gerekir:

  1. Go to Manage Google Account > Security and turn on the Less secure app access setting.

  2. Gmail'den "Google, google olmayan bir uygulama kullanarak birinin hesabınızla oturum açmasını engelledi" şeklinde bir e-posta alırsanız "Evet, bu ben istiyorum" yanıtını alın.

Proaktif izleme için tanılama imzalarını yükleyin

Yüksek CPU kullanımını izleme

This DS tracks CPU utilization for five seconds using the SNMP OID 1.3.6.1.4.1.9.2.1.56. Kullanım %75 veya daha fazlaya ulaştığında, tüm hata ayıklamaları devre dışı kaldırır ve Yerel Ağ Geçidi'ne yüklü tüm tanılama imzalarını kaldırır. İmzayı yüklemek için aşağıdaki işlemleri yapın.

  1. 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 küresel neden: etkin

  2. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki açılır menü seçenekleriyle DS 64224'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Series or Cisco CSR 1000V Series

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Performans

    Sorun Türü

    E-posta Bildirimi ile Yüksek CPU Kullanımı.

  3. DS XML dosyasını Yerel Ağ Geçidi flash belleğine kopyalayın.

    LocalGateway# copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:

    Aşağıdaki örnek, dosyanın FTP sunucusundan Yerel Ağ Geçidine kopya olduğunu gösterir. 

    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)

  4. DS XML dosyasını Yerel Ağ Geçidine yükleyin.

    call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success

  5. İmzanın başarıyla yük çalıştığını doğrulamak için çağrı ev tanılama imzasını göster komutunu kullanın. Durum sütununda "kayıtlı" bir değer olmalıdır. 

    show call-home diagnostic-signature Current diagnostic-signature settings:  Tanılama imzası: Etkinleştirildi 
 Profil: CiscoTAC-1 (durum: ACTIVE) 
 URL'leri indirme:  https://tools.cisco.com/its/service/oddce/services/DDCEService Environment variable: ds_email: username@gmail.com

    İndirilen DS'ler:

    DS Kimliği

    DS Adı

    Revizyon

    Durum

    Son Güncelleme (GMT+00:00)

    64224

    DS_LGW_CPU_MON75

    0.0.10

    Kayıtlı

    2020-11-07 22:05:33

    Bu imza başlatıldığında, kendisi dahil olmak üzere çalışan tüm DS'leri kaldırır. If necessary, reinstall DS 64224 to continue monitoring high CPU utilization on the Local Gateway.

SIP merkezi kaydını izleme

Bu DS, bulutla yerel ağ geçidi ağ geçidi SIP Santrali 60 Webex Calling kaydın siliyor. 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:

  1. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki açılır menü seçenekleriyle DS 64117'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Serisi veya Cisco CSR 1000V Serisi

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    SIP-SIP

    Sorun Türü

    SIP Santrali e-posta Bildirimiyle Kaydı sildi.

  2. DS XML dosyasını Yerel Ağ Geçidine kopyalayın.

    copy ftp://username:password@<server name or ip>/DS_64117.xml bootflash:

  3. DS XML dosyasını Yerel Ağ Geçidine yükleyin. 

    call-home diagnostic-signature load DS_64117.xml Load file DS_64117.xml success LocalGateway#

  4. İmzanın başarıyla yük çalıştığını doğrulamak için çağrı ev tanılama imzasını göster komutunu kullanın. Durum sütunu "kayıtlı" değerine sahip olmalı.

Anormal arama bağlantılarının izlenmesi

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.

  1. 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 küresel neden: etkin

  2. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki seçeneklerle DS 65221'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Serisi veya Cisco CSR 1000V Serisi

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Performans

    Sorun Türü

    E-posta ve Syslog Bildirimi ile SIP anormal çağrı bağlantısı bağlantısı algılama.

  3. DS XML dosyasını Yerel Ağ Geçidine kopyalayın. 

    copy ftp://username:password@<server name or ip>/DS_65221.xml bootflash:

  4. DS XML dosyasını Yerel Ağ Geçidine yükleyin. 

    call-home diagnostic-signature load DS_65221.xml Load file DS_65221.xml success

  5. İmzanın başarıyla yük çalıştığını doğrulamak için çağrı ev tanılama imzasını göster komutunu kullanın. Durum sütunu "kayıtlı" değerine sahip olmalı.

Bir sorunu gidermek için tanılama imzalarını yükleyin

Sorunları hızla çözmek için Tanılama İmzalarını (DS) kullanın. Cisco TAC mühendisleri, belirli bir sorunu tespit etmek, sorun oluşumunu algılamak, doğru tanılama verileri toplamak ve verileri Cisco TAC durumuna otomatik olarak aktaran gerekli hata ayıklamaları etkinleştiren birkaç imzaya izin verdi. Diagnostic Signatures (DS) eliminate the need to manually check for the problem occurrence and makes troubleshooting of intermittent and transient issues a lot easier.

Tanılama İmzaları Arama Aracı'nı kullanarak uygun imzaları bulabilir ve bir sorunu kendi kendine çözmek için yükleyebilir veya destek etkileşimin bir parçası olarak TAC mühendisi tarafından önerilen imzayı yükleyebilirsiniz.

Aşağıdaki örnekte, “%VOICE_IEC-3-GW: CCAPI: Dahili Hata (çağrı ani artış eşiği): IEC=1.1.181.1.29.0" syslog ve otomatik tanılama veri toplama aşağıdaki adımları takip edin:

  1. 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

    Örnek: 

    call-home diagnostic-signature environment ds_fsurl_prefix " environment ds_fsurl_prefix "scp://612345678:abcdefghijklmnop@cxd.cisco.com"

  2. 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

  3. Yüksek CPU kullanımı sırasında tüm hata ayıklama ve tanılama imzalarını devre dışı bırakmak için proaktif bir önlem olarak Yüksek CPU izleme DS 64224'ü yükleyin. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki seçeneklerle DS 64224'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Serisi veya Cisco CSR 1000V Serisi

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Performans

    Sorun Türü

    E-posta Bildirimi ile Yüksek CPU Kullanımı.

  4. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki seçeneklerle DS 65095'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Serisi veya Cisco CSR 1000V Serisi

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Syslog'lar

    Sorun Türü

    Syslog - %VOICE_IEC-3-GW: CCAPI: Dahili Hata (çağrı ani artış eşiği): IEC=1.1.181.1.29.0

  5. DS XML dosyalarını Yerel Ağ Geçidine kopyalayın.

    copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:  copy ftp://username:password@<server name or ip>/DS_65095.xml bootflash:

  6. Yerel Ağ Geçidine Yüksek CPU izleme DS 64224 ve sonra DS 65095 XML dosyasını kurun. 

    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

  7. Verify that the signature is successfully installed using the show call-home diagnostic-signature command. Durum sütunu "kayıtlı" değerine sahip olmalı. 

    show call-home diagnostic-signature Current diagnostic-signature settings:  Tanılama imzası: Etkinleştirildi 
 Profil: CiscoTAC-1 (durum: ACTIVE) 
 URL'leri indirme:  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

    İndirilen DS'ler:

    DS Kimliği

    DS Adı

    Revizyon

    Durum

    Son Güncelleme (GMT+00:00)

    64224

    00:07:45

    DS_LGW_CPU_MON75

    0.0.10

    Kayıtlı

    2020-11-08

    65095

    00:12:53

    DS_LGW_IEC_Call_spike_threshold

    0.0.12

    Kayıtlı

    2020-11-08

Tanılama imzası yürütmeyi doğrula

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. Arama-ev tanılama imzası istatistiklerini göstermenin çıktısı, tanılama imzasının ilgi gösterme olayı algı arayıp algılamasını ve eylemi gerçekleştirip yürütme çalıştığını doğrulamanın en iyi yolu değildir. "Tetiklenen/Maks./Stall" sütunu, söz dizisinde belirtilen imzanın bir etkinliği kaç kez tetikledikten sonra tetikledikten sonra bir etkinliği algılamak için maksimum sayıda kez tanımlandığı ve maksimum tetiklenen etkinlik sayısını algılayan imzanın kendi kendine install olduğunu gösterir. 

show call-home diagnostic-signature Current diagnostic-signature settings:  Tanılama imzası: Etkinleştirildi 
 Profil: CiscoTAC-1 (durum: ACTIVE) 
 URL'leri indirme:  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

İndirilen DS'ler:

DS Kimliği

DS Adı

Revizyon

Durum

Son Güncelleme (GMT+00:00)

64224

DS_LGW_CPU_MON75

0.0.10

Kayıtlı

2020-11-08 00:07:45

65095

DS_LGW_IEC_Call_spike_threshold

0.0.12

Çalışıyor

2020-11-08 00:12:53

ev arama tanılama imzası istatistiklerini göster

DS Kimliği

DS Adı

Triggered/Max/Deinstall

Ortalama Çalışma Süresi (saniye)

Maksimum Çalışma Süresi (saniye)

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

Tanılama bildirim e-postası yürütme sırasında gönderilen ses dosyası; sorun türü, cihaz ayrıntıları, yazılım sürümü, çalışan yapılandırma gibi önemli bilgileri içerir ve söz konusu sorunu gidermek için uygun komut çıkışlarını gösterir.

Tanılama imzalarını kaldır

Sorun giderme amaçları için Tanılama imzalarını kullanın, genellikle bazı sorun meydana gelen durumlarda tespit edildikten sonra kaldırmak üzere tanımlanır. 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>

Örnek:

call-home diagnostic-signature deinstall 64224

Dağıtımlarda yaygın olarak gözlemlenen sorunlar temel alınarak Tanılama İmzaları Arama Aracına düzenli olarak yeni imzalar eklenir. TAC şu anda yeni özel imza oluşturma taleplerini desteklememektedir.

Manage and validate Cisco IOS XE Gateways through Control Hub

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:

Design overview

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

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.

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.

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.

Use the configuration guidance in the rest of this document to complete your Local Gateway configuration as follows:

  • Adım 1: Configure router baseline connectivity and security

  • Adım 2: Configure Webex Calling Trunk

    Depending on your required architecture, follow either:

  • 3. Adım: Configure Local Gateway with SIP PSTN trunk

  • 4. Adım: Configure Local Gateway with existing Unified CM environment

    Veya:

  • 3. Adım: Configure Local Gateway with TDM PSTN trunk

Configure connectivity and security

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

    • User authentication and remote access

    • DNS

    • IP yönlendirme

    • 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. Örneğin:

      • 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. Kayıt adresinin (CNAME, SRV veya IP Adresi) çözümleyene kayıtları SAN'da isteğe bağlıdır.

      • 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.

  • Sertifikaların istemci ve sunucu kullanımı için imzalanmış olduğundan emin olun.

  • Upload the Cisco root CA bundle to the Local Gateway.

Yapılandırma

1

Ensure that you assign valid and routable IP addresses to any Layer 3 interfaces, for example:

 interface GigabitEthernet0/0/0 description Interface facing PSTN and/or CUCM ip address 192.168.80.14 255.255.255.0 ! interface GigabitEthernet0/0/1 description Interface facing Webex Calling (Public address) ip address 198.51.100.1 255.255.255.240

2

Protect STUN credentials on the router using symmetric encryption. Configure the primary encryption key and encryption type as follows:

 key config-key password-encrypt YourPassword password encryption aes
3

Create an encryption trustpoint with a certificate signed by your preferred Certificate Authority (CA).

  1. Create an RSA key pair using the following exec command.

    crypto key generate rsa general-keys exportable label lgw-key modulus 4096

  2. When using cube1.lgw.com as the fqdn for the trunk, create a trustpoint for the signed certificate with the following configuration commands: 

     crypto pki trustpoint LGW_CERT enrollment terminal pem fqdn cube1.lgw.com subject-name cn=cube1.lgw.com subject-alt-name cube1.lgw.com revocation-check none rsakeypair lgw-key

  3. Generate Certificate Signing Request (CSR) with the following exec or configuration command and use it to request a signed certificate from a supported CA provider:

    crypto pki enroll LGW_CERT

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:

 crypto pki authenticate LGW_CERT <paste Intermediate X.509 base 64 based certificate here>

5

Import a signed host certificate using the following exec or configuration command:

 crypto pki import LGW_CERT certificate <paste CUBE host X.509 base 64 certificate here>

6

Enable TLS1.2 exclusivity and specify the default trustpoint using the following configuration commands:

 sip-ua crypto signaling default trustpoint LGW_CERT transport tcp tls v1.2

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
 ip http client source-interface GigabitEthernet0/0/1 crypto pki trustpool import clean url https://www.cisco.com/security/pki/trs/ios_core.p7b
Configure Webex Calling certificate-based trunk
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:

 voice service voip ip address trusted list ipv4 x.x.x.x y.y.y.y mode border-element allow-connections sip to sip no supplementary-service sip refer stun stun flowdata agent-id 1 boot-count 4 stun flowdata shared-secret 0 Password123$ sip asymmetric payload full early-offer forced sip-profiles inbound

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

 ip address trusted list  ipv4 x.x.x.x y.y.y.y

  • To protect against toll fraud, the trusted address list defines a list of hosts and networks entities from which the Local Gateway expects legitimate VoIP calls.

  • By default, Local Gateway blocks all incoming VoIP messages from IP addresses not in its trusted list. Statically configured dial-peers with “session target IP” or server group IP addresses are trusted by default so do not need to be added to the trusted list.

  • When configuring your Local Gateway, add the IP subnets for your regional Webex Calling data center to the list, see Port Reference Information for Webex Calling for more information. Also, add address ranges for Unified Communications Manager servers (if used) and PSTN trunk gateways.

  • For more information on how to use an IP address trusted list to prevent toll fraud, see IP address trusted.

mode border-element

Enables Cisco Unified Border Element (CUBE) features on the platform.

sip'e bağlantı sip izin ver

Enable 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).

stun

Enables STUN (Session Traversal of UDP through NAT) globally.

These global stun commands are only required when deploying your Local Gateway behind NAT.

  • Bir Webex Calling kullanıcısına (örneğin, hem arayan hem de arayan taraf) çağrıyı aboneleri Webex Calling ve Webex Calling SBC'de ortam yer imlerine çıpalarsanız İğne açık değil olarak ortam Yerel Ağ Geçidine akış akar.

  • The STUN bindings feature on the Local Gateway allows locally generated STUN requests to be sent over the negotiated media path. This helps to open the pinhole in the firewall.

For more information, see  stun flowdata agent-id and  stun flowdata shared-secret.

asymmetric payload full

Configures SIP asymmetric payload support for both DTMF and dynamic codec payloads. For more information on this command, see asymmetric payload.

erken teklif zorlama

Forces 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 inbound

Enables 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.

 voice class codec 100 codec preference 1 opus codec preference 2 g711ulaw codec preference 3 g711alaw

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class codec 100

Used 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)

 voice class stun-usage 100 stun usage firewall-traversal flowdata stun usage ice lite

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

stun usage ice lite

Used 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)

 voice class srtp-crypto 100 crypto 1 AES_CM_128_HMAC_SHA1_80

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class srtp-crypto 100

Specifies 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). 

 voice class srtp-crypto 100 crypto 1 AEAD_AES_256_GCM

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class srtp-crypto 100

Specifies 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:

 voice class uri 100 sip pattern cube1.lgw.com

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class uri 100 sip

Defines 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:

 voice class sip-profiles 100 rule 10 request ANY sip-header Contact modify "@.*:" "@cube1.lgw.com:" rule 20 response ANY sip-header Contact modify "@.*:" "@cube1.lgw.com:"

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

rules 10 and 20

To 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 
 voice class sip-profiles 100 rule 10 request ANY sip-header Contact modify "@.*:" "@cube1.lgw.com:" rule 20 response ANY sip-header Contact modify "@.*:" "@cube1.lgw.com:" rule 30 response ANY sdp-header Audio-Attribute modify "(a=candidate:1 1.*) 10.80.13.12" "\1 192.65.79.20" rule 31 response ANY sdp-header Audio-Attribute modify "(a=candidate:1 2.*) 10.80.13.12" "\1 192.65.79.20" rule 40 response ANY sdp-header Audio-Connection-Info modify "IN IP4 10.80.13.12" "IN IP4 192.65.79.20" rule 41 request ANY sdp-header Audio-Connection-Info modify "IN IP4 10.80.13.12" "IN IP4 192.65.79.20" rule 50 request ANY sdp-header Connection-Info modify "IN IP4 10.80.13.12" "IN IP4 192.65.79.20" rule 51 response ANY sdp-header Connection-Info modify "IN IP4 10.80.13.12" "IN IP4 192.65.79.20" rule 60 response ANY sdp-header Session-Owner modify "IN IP4 10.80.13.12" "IN IP4 192.65.79.20" rule 61 request ANY sdp-header Session-Owner modify "IN IP4 10.80.13.12" "IN IP4 192.65.79.20" rule 70 request ANY sdp-header Audio-Attribute modify "(a=rtcp:.*) 10.80.13.12" "\1 192.65.79.20" rule 71 response ANY sdp-header Audio-Attribute modify "(a=rtcp:.*) 10.80.13.12" "\1 192.65.79.20 rule 80 request ANY sdp-header Audio-Attribute modify "(a=candidate:1 1.*) 10.80.13.12" "\1 192.65.79.20" rule 81 request ANY sdp-header Audio-Attribute modify "(a=candidate:1 2.*) 10.80.13.12" "\1 192.65.79.20"

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

rules 10 and 20

To 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 81

Convert 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 
 voice class sip-profiles 110 rule 10 response ANY sdp-header Video-Connection-Info modify "192.65.79.20" "10.80.13.12" rule 20 response ANY sip-header Contact modify "@.*:" "@cube1.lgw.com:" rule 30 response ANY sdp-header Connection-Info modify "192.65.79.20" "10.80.13.12" rule 40 response ANY sdp-header Audio-Connection-Info modify "192.65.79.20" "10.80.13.12" rule 50 response ANY sdp-header Session-Owner modify "192.65.79.20" "10.80.13.12" rule 60 response ANY sdp-header Audio-Attribute modify "(a=candidate:1 1.*) 192.65.79.20" "\1 10.80.13.12" rule 70 response ANY sdp-header Audio-Attribute modify "(a=candidate:1 2.*) 192.65.79.20" "\1 10.80.13.12" rule 80 response ANY sdp-header Audio-Attribute modify "(a=rtcp:.*) 192.65.79.20" "\1 10.80.13.12"

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

rules 10 to 80

Convert 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.

 voice class sip-profiles 115 rule 10 request OPTIONS sip-header Contact modify "<sip:.*:" "<sip:cube1.lgw.com:" rule 30 request ANY sip-header Via modify "(SIP.*) 10.80.13.12" "\1 192.65.79.20" rule 40 response ANY sdp-header Connection-Info modify "10.80.13.12" "192.65.79.20" rule 50 response ANY sdp-header Audio-Connection-Info modify "10.80.13.12" "192.65.79.20" ! voice class sip-options-keepalive 100 description Keepalive for Webex Calling up-interval 5 transport tcp tls sip-profiles 115

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class sip-options-keepalive 100

Configures 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:

  1. Create voice class tenant 100 to define and group configurations required specifically for the Webex Calling trunk. Dial-peers associated with this tenant later will inherit these configurations:

    The following example uses the values illustrated in Step 1 for the purpose of this guide (shown in bold). Replace these with values for your trunk in your configuration.

     voice class tenant 100 no remote-party-id sip-server dns:us25.sipconnect.bcld.webex.com srtp-crypto 100 localhost dns:cube1.lgw.com session transport tcp tls no session refresh error-passthru bind control source-interface GigabitEthernet0/0/1 bind media source-interface GigabitEthernet0/0/1 no pass-thru content custom-sdp sip-profiles 100 sip-profiles 110 inbound privacy-policy passthru !

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    voice class tenant 100

    We recommend that you use tenants to configure trunks which have their own TLS certificate, and CN or SAN validation list. Here, the tls-profile associated with the tenant contains the trust point to be used to accept or create new connections, and has the CN or SAN list to validate the incoming connections. For more information, see voice class tenant.

    uzak taraf kimliği yok

    Disable SIP Remote-Party-ID (RPID) header as Webex Calling supports PAI, which is enabled using CIO asserted-id pai. For more information, see remote-party-id.

    sip-server dns:us25.sipconnect.bcld.webex.com

    Configures the target SIP server for the trunk. Use the edge proxy SRV address provided in Control Hub when you created your trunk

    srtp-crypto 100

    Configures the preferred cipher-suites for the SRTP call leg (connection) (specified in Step 5). For more information, see voice class srtp-crypto.

    localhost dns: cube1.lgw.com

    Configures CUBE to replace the physical IP address in the From, Call-ID, and Remote-Party-ID headers in outgoing messages with the provided FQDN.

    oturum taşıma tcp tls

    Sets transport to TLS for associated dial-peers. For more information, see session-transport.

    no session refresh

    Disables SIP session refresh globally.

    hata-passthru

    SIP hata yanıt geçiş işlevini belirtir. For more information, see error-passthru.

    bind control source-interface GigabitEthernet0/0/1

    Configures the source interface and associated IP address for messages sent to Webex Calling. For more information, see bind.

    bind media source-interface GigabitEthernet0/0/1

    Configures the source interface and associated IP address for media sent to Webex Calling. For more information, see bind.

    voice-class sip profiles 100

    Applies the header modification profile (Public IP or NAT addressing) to use for outbound messages. For more information, see voice-class sip profiles.

    voice-class sip profiles 110 inbound

    Applies the header modification profile (NAT addressing only) to use for inbound messages. For more information, see voice-class sip profiles.

    privacy-policy passthru

    Configures the privacy header policy options for the trunk to pass privacy values from the received message to the next call leg. For more information, see privacy-policy.

  2. Configure the Webex Calling trunk dial-peer.

     dial-peer voice 100 voip description Inbound/Outbound Webex Calling destination-pattern BAD.BAD session protocol sipv2 session target sip-server incoming uri request 100 voice-class codec 100 voice-class stun-usage 100 voice-class sip rel1xx disable voice-class sip asserted-id pai voice-class sip tenant 100 voice-class sip options-keepalive profile 100 dtmf-relay rtp-nte srtp no vad

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

     dial-peer voice 100 voip  description Inbound/Outbound Webex Calling

    100 VoIP etiketine sahip bir ağ eşlemesi tanımlar ve yönetim ve sorun gidermenin kolaylığı için anlamlı bir açıklama sağlar. For more information, see dial-peer voice.

    hedef şablon BAD. Kötü

    A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. Any valid destination pattern may be used in this case.

    oturum protokolü sipv2

    Çağrı eş 100'un SIP çağrı ayaklarıyla iş ele alanı olduğunu belirtir. For more information, see session protocol (dial-peer).

    oturum hedefi sip sunucusu

    Indicates that the SIP server defined in tenant 100 is inherited and used for the destination for calls from this dial peer.

    incoming uri request 100

    To specify the voice class used to match a VoIP dial peer to the uniform resource identifier (URI) of an incoming call. For more information, see  incoming uri.

    voice-class codec 100

    Indicates codec filter list for calls to and from Webex Calling. For more information, see voice class codec.

    ses sınıfı stun kullanım 100

    Allows locally generated STUN requests on the Local Gateway to be sent over the negotiated media path. STUN help to open a firewall pinhole for media traffic.

    voice-class sip asserted-id pai

    Sets the outgoing calling information using the privacy asserted ID (PAI) header. For more information, see voice-class sip asserted-id.

    voice-class sip tenant 100

    The dial-peer inherits all parameters configured globally and in tenant 100. Parameters may overridden at the dial-peer level. For more information, see  voice-class sip tenant.

    voice-class sip options-keepalive profile 100

    This command is used to monitor the availability of a group of SIP servers or endpoints using a specific profile (100).

    srtp

    Çağrı ayağı için SRTP'yi sağlar.

Configure Local Gateway with a SIP PSTN 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:

 voice class uri 200 sip host ipv4:192.168.80.13

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice class uri 200 sip

Defines 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:

 dial-peer voice 200 voip description Inbound/Outbound IP PSTN trunk destination-pattern BAD.BAD session protocol sipv2 session target ipv4:192.168.80.13 incoming uri via 200 voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 voice-class codec 100 dtmf-relay rtp-nte no vad

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

 dial-peer voice 200 voip  description Inbound/Outbound IP PSTN trunk

200 VoIP etiketine sahip bir ağ eşlemesi tanımlar ve yönetim ve sorun gidermenin kolaylığı için anlamlı bir açıklama sağlar. For more information, see dial-peer voice.

hedef şablon BAD. Kötü

A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface).

oturum protokolü sipv2

Çağrı eş 200'un SIP çağrı ayaklarıyla iş ele alanı olduğunu belirtir. For more information, see session protocol (dial peer).

oturum hedefi ipv4:192.168.80.13

Çağrı ayağı göndermek için hedefin hedef IPv4 adresini gösterir. Buradaki oturum hedefi ITSP'nin IP adresidir. For more information, see  session target (VoIP dial peer).

incoming uri via 200

IP adresinin IP adresiyle VIA üstbilgisi için eşleşme PSTN tanımlar. 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/0

Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see  bind.

bind media source-interface GigabitEthernet0/0/0

Configures the source interface and associated IP address for media sent to PSTN. For more information, see  bind.

ses sınıfı kodek 100

Configures the dial-peer to use the common codec filter list 100. For more information, see voice-class codec.

dtmf-relay rtp-nte

RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. For more information, see DTMF Relay (Voice over IP).

yok devam

Ses etkinliği algılamayı devre dışı bırakıyor. 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.

  1. Create dial-peer groups to route calls towards Webex Calling or the PSTN. Define DPG 100 with outbound dial-peer 100 toward Webex Calling. DPG 100 is applied to the incoming dial-peer from the PSTN. Similarly, define DPG 200 with outbound dial-peer 200 toward the PSTN. DPG 200 is applied to the incoming dial-peer from Webex.

     voice class dpg 100 description Route calls to Webex Calling dial-peer 100 voice class dpg 200 description Route calls to PSTN dial-peer 200

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    dial-peer 100

    Associates an outbound dial-peer with a dial-peer group. For more information, see  voice-class dpg.

  2. Apply dial-peer groups to route calls from Webex to the PSTN and from the PSTN to Webex: 

     dial-peer voice 100 destination dpg 200 dial-peer voice 200 destination dpg 100

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    hedef dpg 200

    Specifies which dial-peer group, and therefore dial-peer should be used for the outbound treatment for calls presented to this incoming dial-peer.

    This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features are configured.

Configure Local Gateway with a TDM PSTN trunk

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.

If you do not require IP media optimization, follow the configuration steps for a SIP PSTN trunk. Use a voice port and POTS dial-peer (as shown in Steps 2 and 3) instead of the PSTN VoIP dial-peer.
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:

 voice translation-rule 100 rule 1 /^\+/ /A2A/ voice translation-profile 100 translate called 100 voice translation-rule 200 rule 1 /^/ /A1A/ voice translation-profile 200 translate called 200 voice translation-rule 11 rule 1 /^A1A/ // voice translation-profile 11 translate called 11 voice translation-rule 12 rule 1 /^A2A44/ /0/ rule 2/^A2A/ /00/ voice translation-profile 12 translate called 12

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

voice translation-rule

Uses 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:

 card type e1 0 2 isdn switch-type primary-net5 controller E1 0/2/0 pri-group timeslots 1-31
3

Configure the following TDM PSTN dial-peer:

 dial-peer voice 200 pots description Inbound/Outbound PRI PSTN trunk destination-pattern BAD.BAD translation-profile incoming 200 direct-inward-dial port 0/2/0:15

Yapılandırmaya ilişkin alanların açıklaması şöyledir: 

 dial-peer voice 200 pots  description Inbound/Outbound PRI PSTN trunk

200 VoIP etiketine sahip bir ağ eşlemi tanımlar ve yönetimin ve sorun gidermenin kolaylığı için anlamlı bir açıklama verir. For more information, see dial-peer voice.

hedef şablon BAD. Kötü

A 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 200

Assigns the translation profile that will add a call routing tag to the incoming called number.

direct-inward-dial

Routes the call without providing a secondary dial-tone. For more information, see direct-inward-dial.

port 0/2/0:15

The 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.

 dial-peer voice 10 voip description Outbound loop-around leg destination-pattern BAD.BAD session protocol sipv2 session target ipv4:192.168.80.14 voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711alaw no vad dial-peer voice 11 voip description Inbound loop-around leg towards Webex translation-profile incoming 11 session protocol sipv2 incoming called-number A1AT voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711alaw no vad dial-peer voice 12 voip description Inbound loop-around leg towards PSTN translation-profile incoming 12 session protocol sipv2 incoming called-number A2AT voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711alaw no vad

Yapılandırmaya ilişkin alanların açıklaması şöyledir: 

 dial-peer voice 10 pots  description Outbound loop-around leg

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 11

Applies the translation profile defined earlier to remove the call routing tag before passing to the outbound trunk.

hedef şablon BAD. Kötü

A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. For more information, see destination-pattern (interface).

oturum protokolü sipv2

Specifies that this dial-peer handles SIP call legs. For more information, see  session protocol (dial peer).

session target 192.168.80.14

Specifies 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/0

Configures 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/0

Configures the source interface and associated IP address for media sent through the loop-back. For more information, see  bind.

dtmf-relay rtp-nte

RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. 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.

yok devam

Ses etkinliği algılamayı devre dışı bırakıyor. For more information, see  vad (dial peer).

5

Add the following call routing configuration:

  1. Create dial-peer groups to route calls between the PSTN and Webex trunks, via the loop-back.

     voice class dpg 100 description Route calls to Webex Calling dial-peer 100 voice class dpg 200 description Route calls to PSTN dial-peer 200 voice class dpg 10 description Route calls to Loopback dial-peer 10

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    dial-peer 100

    Associates an outbound dial-peer with a dial-peer group. For more information, see  voice-class dpg.

  2. Apply dial-peer groups to route calls.

     dial-peer voice 100 destination dpg 10 dial-peer voice 200 destination dpg 10 dial-peer voice 11 destination dpg 100 dial-peer voice 12 destination dpg 200

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    destination dpg 200

    Specifies which dial-peer group, and therefore dial-peer should be used for the outbound treatment for calls presented to this incoming dial-peer.

This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features are configured.
Mevcut bir Unified CM ortamıyla Yerel Ağ Geçidi'ni yapılandırma

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

Aşağıdaki ses sınıfı URI'lerini yapılandırın:

  1. Classifies Unified CM to Webex calls using SIP VIA port:

     sesli sınıf uri 300 sip 
 modeli:5065

  2. Classifies Unified CM to PSTN calls using SIP via port:

     voice class uri 400 sip pattern 192\.168\.80\.6[0-5]:5060

    Classify incoming messages from the UCM towards the PSTN trunk using one or more patterns that describe the originating source addresses and port number. Regular expressions may be used to define matching patterns if required.

    In the example above, a regular expression is used to match any IP address in the range 192.168.80.60 to 65 and port number 5060.

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.

 ip host ucmpub.mydomain.com 192.168.80.60 ip host ucmsub1.mydomain.com 192.168.80.61 ip host ucmsub2.mydomain.com 192.168.80.62 ip host ucmsub3.mydomain.com 192.168.80.63 ip host ucmsub4.mydomain.com 192.168.80.64 ip host ucmsub5.mydomain.com 192.168.80.65 ip host _sip._udp.wxtocucm.io srv 0 1 5065 ucmpub.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub1.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub2.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub3.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub4.mydomain.com ip host _sip._udp.wxtocucm.io srv 2 1 5065 ucmsub5.mydomain.com ip host _sip._udp.pstntocucm.io srv 0 1 5060 ucmpub.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub1.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub2.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub3.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub4.mydomain.com ip host _sip._udp.pstntocucm.io srv 2 1 5060 ucmsub5.mydomain.com

Yapılandırmaya ilişkin alanların açıklaması şöyledir:

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. Örneğin:

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:

  1. Dial-peer for calls between Unified CM and Webex Calling:

     dial-peer voice 300 voip description UCM-Webex Calling trunk destination-pattern BAD.BAD session protocol sipv2 session target dns:wxtocucm.io incoming uri via 300 voice-class codec 100 voice-class sip bind control source-interface GigabitEthernet 0/0/0 voice-class sip bind media source-interface GigabitEthernet 0/0/0 dtmf-relay rtp-nte no vad

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

     dial-peer voice 300 voip  description UCM-Webex Calling trunk

    Defines a VoIP dial-peer with a tag 300 and gives a meaningful description for ease of management and troubleshooting.

    hedef şablon BAD. Kötü

    A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. Any valid destination pattern may be used in this case.

    oturum protokolü sipv2

    Specifies that dial-peer 300 handles SIP call legs. For more information, see  session protocol (dial-peer).

    session target dns:wxtocucm.io

    Defines the session target of multiple Unified CM nodes through DNS SRV resolution. In this case, the locally defined SRV record wxtocucm.io is used to direct calls.

    300 üzerinden gelen uri

    Uses voice class URI 300 to direct all incoming traffic from Unified CM using source port 5065 to this dial-peer. For more information, see  incoming uri.

    voice-class codec 100

    Indicates codec filter list for calls to and from Unified CM. For more information, see  voice class codec.

    bind control source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see  bind.

    bind media source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for media sent to PSTN. For more information, see  bind.

    dtmf-relay rtp-nte

    RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. For more information, see  DTMF Relay (Voice over IP).

    yok devam

    Ses etkinliği algılamayı devre dışı bırakıyor. For more information, see  vad (dial peer).

  2. Dial-peer for calls between Unified CM and the PSTN:

     dial-peer voice 400 voip description UCM-PSTN trunk destination-pattern BAD.BAD session protocol sipv2 session target dns:pstntocucm.io incoming uri via 400 voice-class codec 100 voice-class sip bind control source-interface GigabitEthernet 0/0/0 voice-class sip bind media source-interface GigabitEthernet 0/0/0 dtmf-relay rtp-nte no vad

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

     dial-peer voice 400 voip  description UCM-PSTN trunk

    400 VoIP etiketine sahip bir ağ eşlemesi tanımlar ve yönetim ve sorun gidermenin kolaylığı için anlamlı bir açıklama sağlar.

    hedef şablon BAD. Kötü

    A dummy destination pattern is required when routing outbound calls using an inbound dial-peer group. Any valid destination pattern may be used in this case.

    oturum protokolü sipv2

    Specifies that dial-peer 400 handles SIP call legs. For more information, see  session protocol (dial-peer).

    session target dns:pstntocucm.io

    Defines the session target of multiple Unified CM nodes through DNS SRV resolution. In this case, the locally defined SRV record pstntocucm.io is used to direct calls.

    incoming uri via 400

    Uses voice class URI 400 to direct all incoming traffic from the specified Unified CM hosts using source port 5060 to this dial-peer. For more information, see  incoming uri.

    voice-class codec 100

    Indicates codec filter list for calls to and from Unified CM. For more information, see  voice class codec.

    bind control source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for messages sent to the PSTN. For more information, see  bind.

    bind media source-interface GigabitEthernet0/0/0

    Configures the source interface and associated IP address for media sent to PSTN. For more information, see  bind.

    dtmf-relay rtp-nte

    RTP-NTE (RFC2833) özelliğini çağrı ayağında beklenen DTMF özelliği olarak tanımlar. For more information, see  DTMF Relay (Voice over IP).

    yok devam

    Ses etkinliği algılamayı devre dışı bırakıyor. For more information, see  vad (dial peer).

4

Add call routing using the following configurations:

  1. Create dial-peer groups to route calls between Unified CM and Webex Calling. Define DPG 100 with outbound dial-peer 100 towards Webex Calling. DPG 100 is applied to the associated incoming dial-peer from Unified CM. Similarly, define DPG 300 with outbound dial-peer 300 toward Unified CM. DPG 300 is applied to the incoming dial-peer from Webex.

     voice class dpg 100 description Route calls to Webex Calling dial-peer 100 voice class dpg 300 description Route calls to Unified CM Webex Calling trunk dial-peer 300

  2. Create a dial-peer groups to route calls between Unified CM and the PSTN. Define DPG 200 with outbound dial-peer 200 toward the PSTN. DPG 200 is applied to the associated incoming dial-peer from Unified CM. Similarly, define DPG 400 with outbound dial-peer 400 toward Unified CM. DPG 400 is applied to the incoming dial-peer from the PSTN.

     voice class dpg 200 description Route calls to PSTN dial-peer 200 voice class dpg 400 description Route calls to Unified CM PSTN trunk dial-peer 400

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    dial-peer  100

    Associates an outbound dial-peer with a dial-peer group. For more information, see  voice-class dpg.

  3. Apply dial-peer groups to route calls from Webex to Unified CM and from Unified CM to Webex: 

     dial-peer voice 100 destination dpg 300 dial-peer voice 300 destination dpg 100

    Yapılandırmaya ilişkin alanların açıklaması şöyledir:

    destination dpg 300

    Specifies which dial-peer group, and therefore dial-peer should be used for the outbound treatment for calls presented to this incoming dial-peer.

  4. Apply dial-peer groups to route calls from the PSTN to Unified CM and from Unified CM to the PSTN:

     dial-peer voice 200 destination dpg 400 dial-peer voice 400 destination dpg 200

    This concludes your Local Gateway configuration. Save the configuration and reload the platform if this is the first time CUBE features have been configured.

Tanılama imzaları ile Yerel Ağ Geçidi'ni izleme ve sorun giderme

Tanılama İmzaları (DS), Cisco IOS XE tabanlı Yerel Ağ Geçidi'nde sık gözlemlenen sorunları proaktif olarak algılar ve etkinliğin e-posta, syslog veya terminal mesajı bildirimini oluşturan. DS'yi, çözüm süresini kısaltmak amacıyla tanı verisi toplama işlemini otomatikleştirmek ve toplanan verileri Cisco TAC vakasına aktarmak için de yükleyebilirsiniz.

Tanılama İmzaları (DS), sorunu bildirme, sorun giderme ve sorunu giderme işlemleri hakkında bilgi içeren XML dosyalarıdır. Sorun algılama mantığı tanımlamak için syslog mesajlarını, SNMP olaylarını ve belirli show command çıkışlarının periyodik izleme yoluyla kullanın. Eylem türleri şunları içerir:

  • Show komut çıkışları toplayarak

  • Birleştirilmiş bir günlük dosyası oluşturma

  • Dosyanın https, SCP, FTP sunucusu gibi bir ağ konumu tarafından sağlanan kullanıcıya yükleme

TAC mühendisleri DS dosyalarını yazar ve bütünlüğü koruma için dijital olarak imzalar. Her DS dosyasında, sistem tarafından atanan benzersiz sayısal kimlik vardır. Diagnostic Signatures Lookup Tool (DSLT) is a single source to find applicable signatures for monitoring and troubleshooting various problems.

Başlamadan önce:

  • DSLT'den indiren DS dosyasını düzenlemeyin . Değiştir işleminiz, bütünlüğü kontrol hatası nedeniyle yükleme başarısız oldu.

  • Yerel Ağ Geçidi'nin e-posta bildirimlerini göndermesi için gerekli olan Basit Posta Aktarım Protokolü (SMTP) sunucusu.

  • E-posta bildirimleri için güvenli SMTP sunucusunu kullanmak isterseniz Yerel Ağ Geçidi'nin IOS XE 17.6.1 veya daha yüksek bir alanı çalıştır olduğundan emin olun.

Cisco WebEx Meeting Center Yapılandırma Kılavuzları

IOS XE 17.6.1 veya daha yüksek bir ağ geçidini çalıştıran Yerel Ağ Geçidi

  1. Tanı İmzalarının varsayılan olarak etkinleştirilmesi.

  2. 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

  3. Bilgilendir adrese sahip ds_email ortam değişkenlerini yöneticinin e-posta adresiyle yapılandırabilirsiniz.

     configure terminal call-home diagnostic-signature LocalGateway(cfg-call-home-diag-sign)environment ds_email <email address> end

Proaktif izleme için tanılama imzalarını yükleyin

Yüksek CPU kullanımını izleme

Bu DS, SNMP OID 1.3.6.1.4.1.9.2.1.56 kullanarak 5 saniyelik CPU kullanımını izler. Kullanım %75 veya daha fazlaya ulaştığında, tüm hata ayıklamaları devre dışı kaldırır ve Yerel Ağ Geçidi'ne yüklemiş olduğunu tüm tanılama imzalarını kaldırır. İmzayı yüklemek için aşağıdaki işlemleri yapın.

  1. Show snmp komutunu kullanarak SNMP'nin etkinleştirildiğinden emin olun. 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 küresel neden: etkin

  2. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki açılır menü seçenekleriyle DS 64224'ü indirin:

    copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software

    Ürün

    CUBE Enterprise in Webex Calling solution

    Sorun Kapsamı

    Performans

    Sorun Türü

    E-posta Bildirimiyle Yüksek CPU Kullanımı

  3. DS XML dosyasını Yerel Ağ Geçidi flash belleğine kopyalayın.

    copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:

    Aşağıdaki örnek, dosyanın FTP sunucusundan Yerel Ağ Geçidine kopya olduğunu gösterir.

    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)

  4. DS XML dosyasını Yerel Ağ Geçidine yükleyin.

     call-home diagnostic-signature load DS_64224.xml Load file DS_64224.xml success

  5. İmzanın başarıyla yük çalıştığını doğrulamak için çağrı ev tanılama imzasını göster komutunu kullanın. Durum sütunu "kayıtlı" değerine sahip olmalı. 

     show call-home diagnostic-signature Current diagnostic-signature settings:   Tanılama imzası: Etkinleştirildi 
 Profil: CiscoTAC-1 (durum: ACTIVE) 
 URL'leri indirme:  https://tools.cisco.com/its/service/oddce/services/DDCEService Environment variable: ds_email: username@gmail.com

    İndirilen DS'ler:

    DS Kimliği

    DS Adı

    Revizyon

    Durum

    Son Güncelleme (GMT+00:00)

    64224

    DS_LGW_CPU_MON75

    0.0.10

    Kayıtlı

    2020-11-07 22:05:33

    Bu imza başlatıldığında, kendisi dahil olmak üzere çalışan tüm DS'leri kaldırır. Gerekirse Yerel Ağ Geçidi'nde yüksek CPU kullanımını izlemek için lütfen DS 64224'ü yeniden yükleyin.

Anormal arama bağlantılarının izlenmesi

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.

  1. SNMP'nin show snmp komutunu kullanarak etkinleştirildiğinden emin olun. 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 küresel neden: etkin

  2. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki seçeneklerle DS 65221'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Performans

    Sorun Türü

    E-posta ve Syslog Bildirimi ile SIP anormal çağrı bağlantısı bağlantısı algılama.

  3. DS XML dosyasını Yerel Ağ Geçidine kopyalayın.

    copy ftp://username:password@<server name or ip>/DS_65221.xml bootflash:

  4. DS XML dosyasını Yerel Ağ Geçidine yükleyin. 

     call-home diagnostic-signature load DS_65221.xml Load file DS_65221.xml success

  5. Use the command show call-home diagnostic-signature to verify that the signature is successfully installed. Durum sütununda "kayıtlı" bir değer olmalıdır.

Bir sorunu gidermek için tanılama imzalarını yükleyin

Sorunları hızla çözmek için Tanılama İmzalarını (DS) de kullanabilirsiniz. Cisco TAC mühendisleri, belirli bir sorunu tespit etmek, sorun oluşumunu algılamak, doğru tanılama verileri toplamak ve verileri Cisco TAC durumuna otomatik olarak aktaran gerekli hata ayıklamaları etkinleştiren birkaç imzaya izin verdi. Bu da, sorunun gerçekleşip gerçekleşmediğini manuel olarak kontrol etme ihtiyacını ortadan kaldırarak aralıklı ve geçici sorunların tespit edilmesini çok daha kolay bir hale getirmektedir.

Geçerli imzaları bulmak ve bir sorunu kendi kendine gidermek için bunları yüklemek için Tanılama İmzaları Arama Aracı'nı kullanabilir veya destek etkileşimin bir parçası olarak TAC mühendisi tarafından önerilen imzayı yükleyebilirsiniz.

Aşağıdaki örnekte, “%VOICE_IEC-3-GW: CCAPI: Dahili Hata (çağrı ani artış eşiği): IEC=1.1.181.1.29.0" syslog ve otomatik tanılama veri toplama aşağıdaki adımları takip edin:

  1. 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

    Örnek: 

     call-home diagnostic-signature environment ds_fsurl_prefix " environment ds_fsurl_prefix "scp://612345678:abcdefghijklmnop@cxd.cisco.com"

  2. SNMP'nin show snmp komutunu kullanarak etkinleştirildiğinden emin olun. If SNMP not enabled, configure the snmp-server manager command.

     show snmp %SNMP agent not enabled config t snmp-server manager end

  3. Yüksek CPU kullanımı sırasında tüm hata ayıklama ve tanılama imzalarını devre dışı bırakmak için proaktif bir önlem olarak Yüksek CPU izleme DS 64224'ü yüklemenizi öneririz. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki seçeneklerle DS 64224'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Performans

    Sorun Türü

    E-posta Bildirimi ile Yüksek CPU Kullanımı.

  4. Tanı İmzaları Arama Aracı'nda bulunan aşağıdaki seçeneklerle DS 65095'ü indirin:

    Alan Adı

    Alan Değeri

    Platform

    Cisco 4300, 4400 ISR Series, or Catalyst 8000V Edge Software

    Ürün

    Webex Calling Çözümünde CUBE Enterprise

    Sorun Kapsamı

    Syslog'lar

    Sorun Türü

    Syslog - %VOICE_IEC-3-GW: CCAPI: Dahili Hata (çağrı ani artış eşiği): IEC=1.1.181.1.29.0

  5. DS XML dosyalarını Yerel Ağ Geçidine kopyalayın.

     copy ftp://username:password@<server name or ip>/DS_64224.xml bootflash:  copy ftp://username:password@<server name or ip>/DS_65095.xml bootflash:

  6. 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

  7. show call-home diagnostic-signature komutunu kullanarak imzanın başarıyla yüklendiğini doğrulayın. Durum sütununda "kayıtlı" bir değer olmalıdır. 

     show call-home diagnostic-signature Current diagnostic-signature settings:   Tanılama imzası: Etkinleştirildi 
 Profil: CiscoTAC-1 (durum: ACTIVE) 
 URL'leri indirme:  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

    İndirilen DS'ler:

    DS Kimliği

    DS Adı

    Revizyon

    Durum

    Son Güncelleme (GMT+00:00)

    64224

    00:07:45

    DS_LGW_CPU_MON75

    0.0.10

    Kayıtlı

    2020-11-08:00:07:45

    65095

    00:12:53

    DS_LGW_IEC_Call_spike_threshold

    0.0.12

    Kayıtlı

    2020-11-08:00:12:53

Tanılama imzası yürütmeyi doğrula

Aşağıdaki komutta, komutun "Durum" sütununda, Yerel Ağ Geçidi imzada tanımlanan işlemi yürütürken çağrı ana bilgisayar tanılama imzasının "çalışıyor" olarak değişir. Arama-ev tanılama imzası istatistiklerini göstermenin çıktısı, tanılama imzasının ilgi gösterme ve işlemi yürüten bir etkinlik algı edip olmadığını doğrulamanın en iyi yolu değildir. "Tetiklenen/Maks./Stall" sütunu, söz dizisinde belirtilen imzanın bir etkinliği kaç kez tetikledikten sonra tetikledikten sonra bir etkinliği algılamak için maksimum sayıda kez tanımlandığı ve maksimum tetiklenen etkinlik sayısını algılayan imzanın kendi kendine install olduğunu gösterir. 

show call-home diagnostic-signature Current diagnostic-signature settings:   Tanılama imzası: Etkinleştirildi 
 Profil: CiscoTAC-1 (durum: ACTIVE) 
 URL'leri indirme:  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

İndirilen DS'ler:

DS Kimliği

DS Adı

Revizyon

Durum

Son Güncelleme (GMT+00:00)
64224

DS_LGW_CPU_MON75

0.0.10

Kayıtlı

2020-11-08 00:07:45

65095

DS_LGW_IEC_Call_spike_threshold

0.0.12

Çalışıyor

2020-11-08 00:12:53

ev arama tanılama imzası istatistiklerini göster

DS Kimliği

DS Adı

Triggered/Max/Deinstall

Ortalama Çalışma Süresi (saniye)

Maksimum Çalışma Süresi (saniye)
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

Tanılama bildirim e-postası sırasında gönderilen ses dosyası; sorun türü, cihaz ayrıntıları, yazılım sürümü, çalışan yapılandırma ve söz konusu sorunu gidermek için uygun komut çıkışlarını gösterme gibi önemli bilgileri içerir.

Tanılama imzalarını kaldır

Sorun giderme amaçları için tanılama imzalarını kullanın genellikle bazı sorun oluşumları tespit edildikten sonra kaldırmak için tanımlanır. İmzayı manuel olarak kaldırmak isterseniz çağrı ev tanılama imzasını göster çıkışından DS kimliğini alın ve aşağıdaki komutu çalıştırın:

call-home diagnostic-signature deinstall <DS ID>

Örnek:

call-home diagnostic-signature deinstall 64224

Dağıtımlarda gözlemlenen sorunlar temel alınarak Tanılama İmzaları Arama Aracına düzenli aralıklarla yeni imzalar eklenir. TAC şu anda yeni özel imza oluşturma taleplerini desteklememektedir.