Number Expansion Configurations

The following operations are allowed in the num-exp config mode:

Operations	X-path
get, get-config, edit-config	/native/ios-voice:num-exp

Select Num-Exp Configuration Mode

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

Object	X-path
voice num-exp	/native/ios-voice:num-exp

Configuration Recommendations

In num-exp <num1> <num2>:

<num1> <num2> should be of string type and follow the ^((+)?([0-9,#*A-F.]|(\*))+)$ pattern.
Maximum value of <num1> is 128.

Num-Exp Configurations and X-path Details

Object	Description	X-path	Value	Prerequisites	Remarks
num-exp	To define a telephone extension number into a particular destination pattern.	`/native/ios-voice:num-exp`	A regular expression string	N/A	N/A
id	To define a telephone extension number into a particular destination pattern.	`/native/ios-voice:num-exp/ios-voice:id`	String	N/A	N/A
dialled-pattern	To define one or more digits that define the expanded telephone number or destination pattern for the extension number listed.	`/native/ios-voice:num-exp/ios-voice:dialled-pattern`	String	N/A	N/A

Examples: Num-Exp Configurations

Following are the examples for dial-peer cor custom configurations.

Example for get-config operation:

Request

Sending:

# 448
<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:e676cafb-4d75-4e57-bb25-b10482118b40">
<nc:edit-config>
<nc:target>
<nc:running/>
</nc:target>
<nc:config>
<native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
<num-exp xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-voice">
<id>123</id>
<dialled-pattern>456</dialled-pattern>
</num-exp>
</native>
</nc:config>
</nc:edit-config>
</nc:rpc>

Response

Received message from host
<?xml version="1.0" ?>
<rpc-reply message-id="urn:uuid:e676cafb-4d75-4e57-bb25-b10482118b40" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>