SIP Dial Peer Configurations

Newly Added YANG Models in Release Cisco IOS XE 17.14.1a

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

• voice-class sip nat media-keepalive interval
• voice-class sip srtp negotiate cisco
• voice-class sip conn-reuse

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:

• audio forced
• assert-id
• asymmetric payload
• block
• call-route
• contact-passing
• codec transparent
• cor custom
• cor list
• destination dpg
• early-offer forced
• local host
• referto-passing
• requri-passing
• rel1xx
• rtp payload-type
• reason-header
• redirection
• ios qos dscp
• max-conn
• media profile recorder
• media profile asp
• media profile nr
• media profile video
• media profile steam service
• notify
• progress_ind
• pass-thru content custom sdp
• signaling forward
• sip-hdr-passthrulist
• sip-event-list
• sip profiles
• sip-copylist
• anat
• answer-address
• early-media update block
• error-code override
• outbound-proxy
• update-callerid
• url
• voice-class stun-usage
• voice class uri
• voice class e164 pattern-map
• voice class sip-options keepalive
• voice class server group
• voice class media

Dial-Peer Voice Configurations

You can perform the SIP dial-peer configuration, using the dial-peer voice (tag) voip configuration mode. The dial-peer voice (tag) voip configuration mode is a part of Cisco-IOS-XE-voice module. The following operations are allowed in the dial-peer voice (tag) voip configuration mode.

Select VoIP Service Configuration Mode

To enter into the dial-peer voice (tag) voip configuration mode, follow the x-path provided in the below table.

Prerequisites for dial-peer voice (tag) voip configuration

The dialpeertag field is the KEY for dial-peer voice (tag) voip configuration. This is a mandatory field to configure other SIP services at dial-peer level.

Configuration Recommendations

• The dial-peer (tag) value must not overlap with the dynamic dial-peer range.
• The dial-peer (tag) range: 1 to 1073741823
• It is mandatory to configure session protocol sipv2.
• The dtmf-relay configuration allows only to enable the DTMF types.

The dial-peer voice (tag) voip configuration mode allows you to perform the following SIP dial-peer configurations.

Basic SIP Dial-Peer Configurations and X-path details

Voice Class SIP Configurations

Voice SIP-Register Configurations

Voice Class Stun Usage Configurations

Dial-Peer COR Configurations

The following operations are allowed in the dial-peer COR configuration mode:

Select COR Configuration Mode

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

Prerequisites for Dial-Peer COR Configuration

dial-peer cor list member is dependent on dial-peer cor custom name. Hence, member created under dial-peer cor list should be the same as name created under dial-peer cor custom.

Configuration Recommendations

• You need to configure "name" of type string under "dial-peer cor custom" before configuring "dial-peer cor list".
• list_name under dial-peer cor list must follow the [0-9,A-Z,a-z-]*T? pattern.
• Configure "member" under "dial-peer cor list" after you configure "name" under "dial-peer cor custom".

COR Dial-Peer Configurations and X-Path details

Examples: SIP Dial-Peer Configurations

Following are the examples for SIP Dial-Peer Configurations.

Example for get-config operation:

Request

Sending:

<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7b2fccdd-db09-4e09-b485-8b04e4b6a806">
  <nc:get-config>
    <nc:source>
      <nc:running/>
    </nc:source>
    <nc:filter>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <dial-peer xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-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:7b2fccdd-db09-4e09-b485-8b04e4b6a806">
  <data>
    <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
      <dial-peer xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
        <voice>
          <dialpeertag>11</dialpeertag>
          <type>voip</type>
          <incoming>
            <called-number>1002</called-number>
          </incoming>
          <session>
            <transport>
              <tcp/>
            </transport>
            <protocol>sipv2</protocol>
          </session>
        </voice>
        <voice>
          <dialpeertag>12</dialpeertag>
          <type>voip</type>
          <destination-pattern>1002</destination-pattern>
          <session>
            <transport>
              <tcp/>
            </transport>
            <protocol>sipv2</protocol>
            <target>
              <address>ipv4:10.77.91.212</address>
            </target>
          </session>
        </voice>
        <voice>
          <dialpeertag>1000</dialpeertag>
          <type>voip</type>
          <session>
            <protocol>sipv2</protocol>
          </session>
        </voice>
      </dial-peer>
    </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:9252a862-55d8-4d4a-8de8-ada770eeba2e">
  <nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
        <dial-peer xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
          <voice>
            <dialpeertag>11</dialpeertag>
            <type>voip</type>
            <description>test description</description>
            <incoming>
              <called-number>1223</called-number>
            </incoming>
          </voice>
        </dial-peer>
      </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:9252a862-55d8-4d4a-8de8-ada770eeba2e">
  <ok/>
</rpc-reply>