Provision a device template for unified communications

Updated: April 24, 2026

Want to summarize with AI?

This task allows you to select UC-specific feature templates and set up the voice policy to include with a device template. This process applies the configured Unified Communications settings to your devices.

A device template bundles various feature templates and policies, enabling consistent and scalable deployment of configurations across multiple devices. This task is the final step in preparing your UC voice services for deployment.

Before you begin

Ensure that all necessary UC-specific feature templates (Voice Card, Call Routing, SRST, DSPFarm) and voice policies have been previously created and configured.

Follow these steps to provision a device template for Unified Communications:

Procedure

	1.	From the Cisco SD-WAN Manager menu, choose Configuration > Templates.
	2.	Click Device Templates, and click Create Template. Note In Cisco vManage Release 20.7.1 and earlier releases, Device Templates is called Device.
	3.	From the Create Template drop-down list, select From Feature Template.
	4.	From the Device Model drop-down list, select the type of supported device to which you want to attach the UC-specific feature templates and map the voice policy.
	5.	Click Unified Communications.
	6.	To select UC-specific feature templates to include with the device template, perform these actions: From the Voice Card drop-down list, select the voice card feature template. From the Call Routing drop-down list, select the call routing feature template. From the SRST drop-down list, select the SRST feature template. From the DSPFarm drop-down list, select the DSPFarm template.
	7.	To set up the voice policy to include with the device template, perform these actions: From the Voice Policy drop-down list, select the voice policy. Click Mapping. From the list of endpoint types in the left pane of the screen that displays, select the type of endpoint that contains the subpolicies that you want to map to specific endpoints. From the list of subpolicies that displays, click …, and select Mapping for the subpolicy that you want to map to specific endpoints. In the list of endpoints that displays, select each endpoint to which you want to map the subpolicy Click Map. Click Save. When you map subpolicies to endpoints, the system generates the CLI commands. See Generated CLI commands for subpolicies to endpoints mapping.
	8.	To create the device template, click Create.

A device template for Unified Communications is successfully provisioned, including the selected UC-specific feature templates and voice policy mappings.

What to do next

The device template is now ready to be attached to devices to deploy the Unified Communications configurations.

Generated CLI commands for subpolicies to endpoints mapping

This reference topic describes the CLI commands that are automatically generated when subpolicies are mapped to specific endpoints within a device template. This table provides insight into the underlying configuration applied by the Cisco SD-WAN Manager.

Table 1. Generated CLI commands for subpolicies to endpoints mapping
Endpoint	Subpolicy	Cisco IOS CLI Application Mapping	Remarks
Voice Port FXO Voice Port FXS Voice Port FXS DID Voice Port PRI ISDN POTS Dial Peer SIP Dial Peer	Translation profile	translation-profile incoming profile-name translation-profile outgoing profile-name	A translation profile policy is applied to a dial peer or a voice profile.
SRST Phone SIP Dial Peer	Media profile	voice register pool number voice-class codec number dtmf-relay {[[sip-notify] [sip-kpml] [rtp-nte]]}	A media profile policy includes voice class codec and DTMF relay configurations. This policy is applied to an incoming SIP dial peer, an outgoing SIP dial peer, or an SRST phone profile.
Voice Port FXO	Supervisory disconnect	voice port number supervisory custom-cptone cptone-name supervisory dualtone-detect=params tag	A supervisory disconnect policiy such as custom-cptone or dualtone-detect-params is applied to FXO voice interfaces.
Voice Port FXO Voice Port FXS Voice Port FXS DID Voice Port PRI ISDN POTS Dial Peer	Trunk group	trunk-group name [preference-num] voice-port number trunk-group name [preference-num] interface serial slot/sub-slot/port:{15 \| 23} dial-peer voice tag pots trunkgroup name preference-num	If more than one interface is assigned to the same trunk group, the preference-num value determines the order in which the trunk group uses the interfaces. A preference-num value of 1 is the highest preference, so an interface with that value is used first. A value of 64 is the lowest preference so an interface with that value is used last.
SIP Dial Peer	Modem pass-through	None: no modem passthrough G.711 ulaw: modem passthrough nse codec g711ulaw G.711 alaw: modem passthrough nse codec g711alaw	—
SIP Dial Peer	Fax protocol	fax protocol {none \| pass-through {g711ulaw \| g711alaw} [fallback none] \| t38 [nse [force]] [version {0 \| 3}] [ls-redundancy value [hs-redundancy value]] [fallback {none \| pass-through {g711ulaw \| g711alaw}}]}	—

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.