Voice Register Configurations

You can perform the voice register global and pool configurations, using the ios-voice:register configuration mode. The ios-voice:register configuration mode is a part of Cisco-IOS-XE-voice module. The following operations are allowed in the ios-voice:register configuration mode.

Select Voice Register Configuration Mode

To enter into the ios-voice:register configuration mode, follow the x-path provided in the below table.

Configuration Recommendations

• The max-dn, max-pool value range is limited by the platform that is being configured.
• There is a dependency between voice class codec and voice register pool configuration.
• Ensure that there is no voice register pool that is associated with a voice class codec that is deleted.

Voice Register Global Configuration

The ios-voice:register configuration mode allows you to perform the following global configurations:

Voice Register Configurations and X-path details

Voice Register Pool Configuration

The voice register pool configuration allows you to control which phone registrations are accepted or rejected by a Cisco Unified SIP SRST device.

Prerequisites for 'ios-voice:register' configuration

• The pool-tag field is the KEY for ios-voice:register pool configuration. This is a mandatory field to configure other pool configurations at global level.

The ios-voice:register configuration mode allows you to perform the following pool configurations:

Voice Register Pool configurations and X-path details

Examples: Voice Register Configurations

Following are the examples for Voice Register Global and Pool 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:1cec4992-d3e5-42d0-994a-361ac2148e93">
  <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">
          <register>
            <global>
              <max-dn/>
              <max-pool/>
            </global>
          </register>
        </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:1cec4992-d3e5-42d0-994a-361ac2148e93">
  <data>
    <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
      <voice xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
        <register>
          <global>
            <max-dn>10</max-dn>
            <max-pool>10</max-pool>
          </global>
        </register>
      </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:49bcfa87-4bbf-461f-b488-7ef5c345de8a">
  <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">
          <register>
            <global>
              <max-dn>20</max-dn>
              <max-pool>30</max-pool>
              <system>
                <message>test</message>
              </system>
            </global>
          </register>
        </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:ae5ec0fb-ca45-4c8b-a984-c3fe8c6aac61">
  <ok/>
</rpc-reply>