You are here: CSP Developer’s Guide: Internet Protocols > 3 IP Network Interface Series 2 Card > Voice Attributes
Introduction
You can configure the following voice attributes with the Resource Attribute Configure (0x00E3) message:
RTP Payload Type
The RTP payload type indicates the algorithm used for compressing the data or payload portion of the packet. For an active connection, the only configuration change you can make is between G.723 5.3 Kbps and G.723 6.3 Kbps.
Default: G.711µ-Law
Use TLV: 0x0100 RTP Payload Type
RTP payload sizes can be changed in multiples of the specified RTP Payload Type's base packetization rate. On the IP Network Interface Series 2 card, the RTP payload size is tightly coupled with RTP payload type. Changing the default RTP payload type also changes the default RTP payload size to its applicable value (unless a new default RTP payload size is also specified). Using the non-default RTP Payload Type during call establishment results in the default RTP Payload Size not being used. If the RTP Payload Size is not provided, the default for the specific payload type is used.
For the IP Network Interface Series 2 card, refer to VDAC-ONE Resource Profile Terminal Capabilities for each payload type's base packetization rate (for example,1 x payload size), its default payload size and maximum payload size.
Default: 4x (G.711µ-Law 20ms)
Use TLV: 0x0101 RTP Payload Size
During a normal voice conversation, much of the time is wasted on silence from one or both ends. Ethernet bandwidth can be conserved if, during these periods of silence, RTP packets are sent with silence-encoded, compressed payloads.
You can enable or disable Silence Suppression on an established connection.
Default: Disabled
TLV: 0x0102 RTP Silence Suppression
(Do not send to an active call that is in fax/modem mode.)
In compliance with ITU G.168, this feature eliminates echo introduced by impedance mismatched hybrids. You can enable and disable Echo Cancellation on an established connection.
Default: Enabled
TLV: 0x0103 RTP Echo Cancellation
You can set the redundancy level for RTP using the RTP Payload Redundancy TLV. See RFC 2198.
Default: Disabled
TLV: 0x01D1 RTP Payload Redundancy
During call setup, the Connection Mode is automatically determined according to the presence of destination and source addresses in the Route Control (0x00E8) or Outseize Control (0x002C) message.
Source Address Only - Receive Only
Source and Destination Address - Transmit and Receive
To change the Connection Mode after a call is established using Resource Attribute Configure (0x00E3) message, send the Connection Mode (0x01DB) TLV with the appropriate mode set.
In hold mode, no voice is transmitted or received.
Example: After a two-way call has been established to a Call Center, the caller is put on hold and connected to music. The Connection Mode of the Call Center line is changed to Transmit Only. If callers enable the mute feature on their phone, the Connection Mode on their line is changed to Receive Only.
There is no default Connection mode. If you query the Module Connection Mode, it is reported as 0xFF. This is a generic value and does not indicate a specific mode. You cannot set the Connection Mode to this value.
TLV: 0x01DB Connection Mode
Important! Source Address (IP/RTP Port) is always required in Route Control or Outseize Control messages.
This TLV allows DTMF signals to be relayed within the VoIP media stream, using a special RFC 2833-compliant packet format. Low bit-rate audio codecs (such as G.729 or G.723.1) can compromise the signal integrity of DTMF digits (and other telephony tones and signals), causing inaccurate detection and recognition of the DTMF digits on the recipient side. When this feature is enabled, the detected incoming DTMF digits (PSTN side) are removed from the audio stream by the IP Network Interface Series 2 card. The information for the detected and removed DTMF digits is embedded within the RTP stream, using a special RFC 2833-compliant packet format. The IP Network Interface Series 2 card on the receiving side decodes this special RTP payload carrying DTMF information, and regenerates the DTMF digits toward the receiving PSTN side. This TLV cannot be set for an active call. It can be configured only before or during the setup of the IP Network Interface Series 2 card call.
Because the VDAC-ONE card allows up to 30 milliseconds of a digit through before blocking it, the distant end might hear a very short audible sound.
Important! The Excel platform does NOT support RFC 2833 via H.323 signaling.
Default: Disabled
TLV: 0x01E2 RFC 2833 Enable
RTP Suppression for H.245 Signaling Tones
The EXS API has been updated to allow you to configure how DTMF digits are transmitted to the IP network.
Important! This feature is for Clear Channel calls only.
This feature extends the RFC2833 Enable (0x01E2) TLV as follows:
• The new value 0x02 removes the digit from the voice stream and drops the digit.
• If you are using the VDAC card, this TLV can be configured only before or during the call establishment. It cannot be set during an active call. If you are using the IP Networking Series 2 card, this TLV can be configure on the fly while the call is active.
Source RTCP Port
This TLV is used to specify the local RTCP port number. If this port is not specified by the host during the IP Network Interface Series 2 card call setup, the source RTCP port is set one higher than the source RTP port, per RFC 1889. This TLV can be set during an active call.
Default: No default
TLV: 0x01E8 Source RTCP Port
This TLV is used to specify the remote RTCP port number. If this port is not specified by the host during the IP Network Interface Series 2 card call setup, the destination RTCP port is set to one higher than the destination RTP port, per RFC 1889. This TLV can be set during an active call.
Default: No default
TLV: 0x01E9 Destination RTCP Port
You configure the Minimum Jitter Buffer Delay by using the Minimum Jitter Buffer Delay TLV in the Resource Attribute Configure (0x00E3) message. The range of valid values is 0 - 150 milliseconds.
Default: 75 milliseconds
TLV: 0x1C2 Minimum Jitter Buffer Delay
Important! You cannot configure the Minimum Jitter Buffer Delay on an established connection.
You configure the Maximum Jitter Buffer Delay by using the Maximum Jitter Buffer Delay TLV in the Resource Attribute Configure (0x00E3) message. The range of valid values is 150-300 milliseconds.
Default: 150 milliseconds
TLV: 0x1C3 Maximum Jitter Buffer Delay
Important! You cannot configure the Maximum Jitter Buffer Delay on an established connection.
RFC 2198 (RTP Redundancy) Dynamic Payload Negotiation
The VDAC-ONE card and the IP Network Interface Series 2 card allows RFC 2198 dynamic payload negotiation for clear channel calls only.
You first must enable RFC 2198 with the RTP Payload Redundancy TLV (0x01D1) in the Resource Attribute Configuration (0x00E3) message.
You can configure the default value at configuration time or change this value per call as follows:
• To configure the default RFC 2198 Codec Type, use the RFC 2198 Dynamic Payload Type TLV (0x01F2) in the Resource Attribute Configuration (0x00E3) message.
• To change the default RFC 2198 per call, use the TLV above within the Generic PPL ICB (0x1E) in the Route Control (0x00E8) or Outseize Control (0x002C) messages.
Default: 104
TLV: 0x01F2