Cisco Systems H.323 manual Parameter Example Value Configuration Example

Chapter 3 Provisioning the Cisco HSI

HSI Feature Configuration

If a non-preferred G.726 data rate is selected over a higher-preference codec, the HSI will continue with the call using the non-preferred data rate. This is preferable to the alternative (aborting the media stream, invoking an empty capability exchange followed by a re-negotiation of codecs and new OLC messaging). The alternative causes call processing delay and overhead associated with switching media streams.

Note The g726-cisco method avoids impaired or delayed processing because it advertises the data rate in the TCS messaging.

Refer to the Cisco H.323 Signaling Interface User Guide for information about Cisco HSI MML commands.

Table 3-18presents examples of configuration commands that may be required to implement a particular G.726 configuration.

Table 3-18 Configuring G.726

G.726 Parameter	Example Value	Configuration Example
Configuring the Payload Type for the MGCP
sys_config_static, UseG726StaticPayload	“enabled”,	prov-add:name=sys_config_static,
	“true”,	UseG726StaticPayload="enabled"
	“”	prov-ed:name=sys_config_static,
		UseG726StaticPayload=""
	Note If this parameter is
	set to any text value,
	the Cisco HSI uses
	static payload value
	'2' to represent
	G.726 32kbit/sec to
	the MGCP gateway.
	If the parameter is
	deleted or is set to an
	empty string (“”),
	the HSI uses the
	default, dynamic-
	payload behavior.
Configuring Cisco HSI g726-cisco
H245, caps.table[i].audio.g726-cisco	“G726r16”,	prov-add:name=h245,
	“G726r24”,	caps.table[5].audio.g726-cisco="G726r16"
	“G726r32”,	prov-add:name=h245,
		caps.table[6].audio.g726-cisco="G726r24"
	“G726r40”
	Note These string values
	are case-sensitive,
	and must be entered
	exactly as displayed
	in the commands in
	this table.

	Cisco H.323 Signaling Interface User Guide
3-28	OL-4806-01 Rev. A14