Global SIP Configurations

You can perform the global SIP configuration, using the voice-service-voip configuration mode. The voice-service-voip mode is a part of Cisco-IOS-XE-voice module. The following operations are allowed in the voice-service-voip mode.

Prerequisites for voice-service-voip configuration

The type field is the KEY for voice-service-voip configuration. This is a mandatory field to configure other SIP services at global level.

Select VoIP Service Configuration Mode

To enter into the voice-service-voip configuration mode, follow the x-path provided in the below table.

Newly Added YANG Models in Release 17.14.1a

YANG models was added for the following CLI:

• Voice Service VoIP Configurations:

  • nat media-keepalive interval

• Voice Class TLS Cipher Configurations:

  • cipher cipher-list

• Voice Class Tenant Configurations:

  • nat media-keepalive interval

Newly Added YANG Models in Release 17.10.1a

The following YANG models are supported from Cisco IOS XE 17.10.1a:

• Voice Class Codec Configurations:

  • preference codec-type g729br8
  • preference codec-type gsmamr-nb
  • video codec codec-type h261
  • video codec codec-type mpeg4

• Voice Class Tenant Configurations:

  • disable-early-media
  • conn-reuse
  • error-code-override 
  • g729-annexb
  • host-registrar
  • random-contact
  • max-forwards
  • handle-replaces
  • nat
  • notify
  • permit hostname
  • reason-header
  • retry
  • srtp negotiate
  • xfer target
  • timers

• Stun Configurations:

  • stun flowdata shared-secret

Newly Added YANG Models in Release Cisco IOS XE 17.8.1a

YANG models were added for the following CLIs:

• Voice Class Tenant Configurations
  • tls-profile
  • listen-port secure
  • listen-port non-secure

Newly Added YANG Models in Release Cisco IOS XE 17.7.1

The following YANG models are supported from Cisco IOS XE 17.7.1:

• media-address range
• media bulk-stats
• media disable-detailed-stats
• media statistics
• midcal-signalling
• min-se
• conn:reuse
• remote-party-id
• rtpc all-passthru
• rtcp keepalive
• rtp-port range
• supplementary-service media-renegotiate
• localhost
• outbound proxy
• audio forced
• address hiding
• asserted id
• asymmetric payload
• block
• call-route
• call monitor
• call-threshold
• call spike
• call treatment
• codec profile
• contact-passing
• connection reuse
• dtmf-interworking
• gcid
• g729 annexb-override
• http client
• notify
• referto-passing
• rtp-ssrc multiplex
• rtp-medialoop count
• session refresh
• bind
• pass-thru content custom-sdp
• sip-profile
• copy-list
• anat
• options-ping
• early-media update block
• error-code-override
• emergency
• rtp-port range
• authentication
• credentials (SIP UA)
• connection-reuse
• clid
• cpa
• early-offer forced
• header-passing
• host registrar
• error-passthru
• session transport
• set pstn cause
• set sip status
• set sip request
• silent discard
• sip-server
• srtp
• stun usage
• privacy
• privacy-policy
• rel1xx
• url
• untrusted
• requri-passing
• update-callerid
• redirection
• redirect
• registrar
• retry
• codec
• video
• voice class stun-usage
• voice cause-code
• voice iec syslog
• voice class srtp-crypto
• voice statistics iec
• voice class codec
• voice class uri sip preference
• voice class e164-pattern-map
• voice class media
• voice class dpg
• voice class sip-hdr-passthrulist
• voice class sip-event-list
• voice class sip-profiles
• voice class sip-copylist

Basic SIP Configurations

The voice-service-voip configuration mode allows you to perform the following SIP configurations at global level.

Basic SIP Configurations and X-path details

IP Address Trusted List Configuration

Configuring a Trusted IP Address List for Toll-Fraud Prevention.

SIP Configurations

Configuring Session Initiation Protocol (SIP) registrar and other related values.

Voice Translation Rule Configurations

Voice Class Media Configurations

Voice Class Sip-Event-list Configurations

Voice Class Tenant Configurations

Voice Class SIP Headers Passthrough Configurations

Voice Class Server Group Configurations

Voice Class Uri Configurations

Voice Class E164 Pattern Map Configurations

Voice Class Sip Options Keepalive

Voice Class Custom-cptone Configurations

Voice Class TLS Cipher Configurations

You can perform the TLS cipher configurations required for a TLS session, using the ios-voice:tls-cipher configuration mode under ios-voice:class configuration mode. The ios-voice:tls-cipher configuration mode is a part of Cisco-IOS-XE-voice module. The following operations are allowed in the ios-voice:class:tls-cipher configuration mode.

Select Voice Class TLS Cipher Configuration Mode

To enter into the ios-voice:tls-cipher configuration mode, follow the X-path provided in the following table.

Updated YANG Models in Release 17.14.1a

YANG models were updated for the following CLIs:

• cipher cipher-list

Configuration Recommendation

The tls-cipher id field is the KEY for ios-voice:tls-cipher configuration. This is a mandatory field that is required to associate TLS cipher with TLS profile configurations.

Voice TLS Cipher Configurations and X-path Details

Examples: Voice Class TLS Cipher Configurations

Example for edit-config operation:

Request

<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7bfbbf38-ea5f-42ee-a7f6-7a1e1e29c222">
  <nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
          <class>
            <tls-cipher nc:operation="create">
              <id>10</id>
              <cipher>
                <preference>1</preference>
                <type>DHE_RSA_AES128_GCM_SHA256</type>
              </cipher>
            </tls-cipher>
          </class>
        </voice>
      </native>
    </nc:config>
  </nc:edit-config>
</nc:rpc>

Response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7bfbbf38-ea5f-42ee-a7f6-7a1e1e29c222">
  <ok/>
</rpc-reply>

Voice Class TLS Profile Configurations

You can perform the TLS profile configurations required for a TLS session, using the ios-voice:tls-profile configuration mode under ios-voice:class configuration mode. The ios-voice:tls-profile configuration mode is a part of Cisco-IOS-XE-voice module. The following operations are allowed in the ios-voice:class:tls-profile configuration mode.

Select Voice Class TLS Profile Configuration Mode

To enter into the ios-voice:tls-profile configuration mode, follow the x-path provided in the following table.

Newly Added YANG Models in Release 17.10.1

YANG models were added for the following CLIs:

• voice class tls-profile
  • cipher cipher-list

Newly Added YANG Models in Release 17.8.1

YANG models were added for the following CLIs:

• Voice Class Tenant Configurations

  • tls-profile
  • listen-port secure
  • listen-port non-secure

• voice class tls-profile

  • cn-san validate client
  • cn-san validate bodirectional
  • cn-san tag

Configuration Recommendation

The tls-profile id field is the KEY for ios-voice:tls-profile configuration. This is a mandatory field that is required to associate TLS profile configurations.

The ios-voice:tls-profile configuration mode allows you to perform the following configurations:

Voice TLS Profile Configurations and X-path details

Examples: Voice Class TLS Profile Configurations

Following are the examples for TLS Profile Configurations.

Example for edit-config operation:

Request

Sending:

# 637
<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:18cb23f3-d75e-4050-a4e0-4913bc2a4495">
  <nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
          <class>
            <tls-profile>
              <id>12</id>
              <description>cisco</description>
              <trustpoint>cisco</trustpoint>
              <client-vtp>cisco</client-vtp>
              <cn-san>
                <validate>
                  <server/>
                </validate>
              </cn-san>
              <cipher>
                <strict-cipher/>
              </cipher>
              <sni>
                <send/>
              </sni>
            </tls-profile>
          </class>
        </voice>
      </native>
    </nc:config>
  </nc:edit-config>
</nc:rpc>

##

Response

Received:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:18cb23f3-d75e-4050-a4e0-4913bc2a4495">
  <ok/>
</rpc-reply>

Example for get-config operation:

Request

Sending:

# 445
<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7256ded2-4dec-40d6-a7b2-334d4fd902e5">
  <nc:get-config>
    <nc:source>
      <nc:running/>
    </nc:source>
    <nc:filter>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
          <class>
            <tls-profile>
              <id>12</id>
            </tls-profile>  
          </class>
        </voice>
      </native>
    </nc:filter>
  </nc:get-config>
</nc:rpc>

##

Response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7256ded2-4dec-40d6-a7b2-334d4fd902e5">
  <data>
    <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
      <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
        <class>
          <tls-profile>
            <id>12</id>
            <description>cisco</description>
            <trustpoint>cisco</trustpoint>
            <client-vtp>cisco</client-vtp>
            <cn-san>
              <validate>
                <server/>
              </validate>
            </cn-san>
            <cipher>
              <ecdsa-cipher>
                <curve-size>384</curve-size>
              </ecdsa-cipher>
            </cipher>
            <sni>
              <send/>
            </sni>
          </tls-profile>
        </class>
      </voice>
    </native>
  </data>
</rpc-reply>

### Voice Class Codec Configurations ###

Voice Class SIP Profiles Configurations

Voice Class Dualtone Detect Parameters Configurations

Voice Class Codec Configurations

Voice Class SIP Copylist Configurations

Voice Class Dial-Peer Group Configurations

Voice Class Stun Usage Configurations

Voice Class srtp-crypto Configurations

Voice Statistics Configuration

You can configure voice statistics.

'stun' Configuration

The voice-service-voip configuration mode allows you to configure stun parameters, which will help you to configure firewall traversal parameters for VoIP communications.

You can perform the following stun flowdata configurations.

'clid' Configuration

The voice-service-voip configuration mode allows you to configure clid parameters. The clid configuration allows you to pass the network-provided ISDN numbers in an ISDN calling party information element screening indicator field, and remove the calling party name and number from the calling-line identifier in voice service voip configuration mode, or allow a presentation of the calling number by substituting for the missing Display Name field in the Remote-Party-ID and From headers.

You can perform the following clid configurations.

mode border-element license periodicity Configuration

The ios-voice:mode mode allows you to configure license periodicity for the Cisco Unified Border Element (CUBE).

License Periodicity Configuration

You can perform the following license periodicity configurations for the Cisco Unified Border Element (UBE).

Examples: Global SIP Configurations

Following are the examples for 'allow-connections' configuration under Global SIP Configuration.

Example for get-config operation:

Request

Sending:

<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:dba4732b-8e8b-432e-8ac0-b04af2d566e4">
  <nc:get-config>
    <nc:source>
      <nc:running/>
    </nc:source>
    <nc:filter>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
          <service>
            <type>voip</type>
            <media-recording/>
            <allow-connections/>
            <media/>
            <supplementary-service/>
            <sip>
              <call/>
              <g729/>
            </sip>
            <fax/>
          </service>
        </voice>
      </native>
    </nc:filter>
  </nc:get-config>
</nc:rpc>

##

Response

Received:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:dba4732b-8e8b-432e-8ac0-b04af2d566e4">
  <data>
    <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
      <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
        <service>
          <type xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">voip</type>
          <allow-connections>
            <sip>
              <to>
                <sip/>
              </to>
            </sip>
          </allow-connections>
          <media>
            <bulk-stats/>
          </media>
          <supplementary-service>
            <sip>
              <handle-replaces/>
              <moved-temporarily/>
              <refer/>
            </sip>
          </supplementary-service>
          <sip>
            <g729>
              <annexb-all/>
            </g729>
          </sip>
        </service>
      </voice>
    </native>
  </data>
</rpc-reply>

Example for edit-config operation:

Request

Sending:

<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:11de8ac8-5685-483c-8e6d-6d218cea8877">
  <nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
          <service>
            <type>voip</type>
            <supplementary-service>
              <sip nc:operation="delete">
                <handle-replaces nc:operation="delete"/>
                <moved-temporarily nc:operation="delete"/>
                <refer nc:operation="delete"/>
              </sip>
            </supplementary-service>
            <sip>
              <g729 nc:operation="delete">
                <annexb-all nc:operation="delete"/>
              </g729>
            </sip>
          </service>
        </voice>
      </native>
    </nc:config>
  </nc:edit-config>
</nc:rpc>

Response

Received:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:11de8ac8-5685-483c-8e6d-6d218cea8877">
  <ok/>
</rpc-reply>