VOS3000 DTMF Configuration: RFC2833 vs SIP INFO Setup Guide

Proper VOS3000 DTMF configuration is essential for every VoIP deployment that uses IVR systems, calling cards, PIN authentication, or any feature where callers press keypad buttons during a call. When DTMF (Dual-Tone Multi-Frequency) signals are not correctly configured, callers press buttons but the system does not respond, IVR menus do not work, calling card PINs are not recognized, and your customers become frustrated. This is one of the most common and costly problems in VOS3000 deployments, yet it is entirely preventable with the correct configuration.

The challenge with VOS3000 DTMF configuration is that there are three different DTMF transport methods — RFC2833, SIP INFO, and Inband — and each gateway, phone, and vendor may use a different method. VOS3000 must be configured to handle DTMF correctly on both the calling and called sides, converting between methods when necessary. This guide covers every aspect of DTMF configuration in VOS3000, based on the official VOS3000 V2.1.9.07 Manual and the VOS3000 Transcode Module documentation. For expert assistance, contact us on WhatsApp at +8801911119966.

Understanding VOS3000 DTMF Configuration Methods

Before configuring anything, you must understand the three DTMF transport methods available in VOS3000 and when each should be used. Choosing the wrong method is the root cause of most DTMF problems.

RFC2833 DTMF Method

RFC2833 (now superseded by RFC4733) transmits DTMF signals as special RTP packets within the media stream. The DTMF digits are encoded as telephone-event payloads, identified in the SDP by the attribute a=rtpmap:101 telephone-event/8000. The payload type number (commonly 101) is negotiated during call setup. According to the VOS3000 Transcode Module documentation (Section 2.3), “RFC2833 signals are carried in separate RTP packets, identified in the SDP by a=rtpmap:101 telephone-event/8000.”

RFC2833 is the recommended DTMF method for most VOS3000 deployments because:

• Reliability: DTMF signals are transmitted as separate RTP events, not embedded in audio, so they survive codec compression without distortion
• Compatibility: Supported by virtually all modern SIP devices and gateways
• Accuracy: DTMF digits are precisely represented with start and end events, ensuring accurate detection at the receiving end
• Works with compressed codecs: Unlike Inband, RFC2833 works perfectly with G729, G723, and other low-bitrate codecs

SIP INFO DTMF Method

SIP INFO transmits DTMF signals as separate SIP INFO messages within the signaling channel, completely outside the RTP media stream. According to the VOS3000 Transcode Module documentation (Section 2.2), “SIP INFO belongs to independent signaling, where key presses are carried in separate signaling messages.” Each DTMF key press generates a separate SIP INFO message containing the digit information.

SIP INFO has specific advantages and limitations:

• Advantage: Works even when media proxy is disabled, because DTMF travels in the signaling channel
• Advantage: Does not depend on RTP connectivity between endpoints
• Limitation: Some SIP devices do not support SIP INFO for DTMF
• Limitation: Timing information is less precise than RFC2833, which can cause issues with some IVR systems

Inband DTMF Method

Inband DTMF transmits dual-tone signals as actual audio within the RTP voice stream. The DTMF tones are generated by the phone’s keypad and embedded in the audio packets just like speech. According to the VOS3000 Transcode Module documentation (Section 2.4), “Inband key presses are carried in the RTP as a continuous segment of voice.” This is the oldest DTMF method and works with any telephony equipment, but it has significant limitations.

Critical limitations of Inband DTMF:

• Codec dependency: Inband DTMF only works reliably with G711 (PCMA/PCMU) codec. Low-bitrate codecs like G729 and G723 compress the audio and distort the DTMF tones, making them unrecognizable
• Detection difficulty: Even with G711, background noise and echo can interfere with Inband DTMF detection
• Not recommended for VOS3000: Use Inband only when the far-end device does not support RFC2833 or SIP INFO

Configuring VOS3000 DTMF Configuration on Routing Gateway

The DTMF settings for routing gateways are found in the Additional Settings > Protocol > DTMF section. Navigate to Operation Management > Gateway Operation > Routing Gateway, double-click a gateway, and access the DTMF configuration (VOS3000 Manual Section 2.5.1.1, Page 46). These settings control how VOS3000 receives and sends DTMF signals to the vendor side.

DTMF Receive Setting

The “DTMF receive” setting specifies how VOS3000 accepts incoming DTMF signals from the gateway. According to the VOS3000 Manual, “The option is recommended, which asks the system to accept all kinds of DTMFs. Once a certain kind of DTMF is received, this channel will accept the same kind of DTMFs only, thus effectively avoiding duplicate receptions.”

Available DTMF receive options:

• All: Accept RFC2833, SIP INFO, and Inband DTMF. Once the first DTMF type is detected, only that type is accepted for the remainder of the call. This is the recommended setting for maximum compatibility
• RFC2833 only: Accept only RFC2833 DTMF signals. Use this when you know the gateway only sends RFC2833
• SIP INFO only: Accept only SIP INFO DTMF. Use this when the gateway only supports SIP INFO
• Inband only: Accept only Inband DTMF. Rarely recommended due to reliability issues

Use Peer RFC2833 Ability Setting

The “Use peer RFC2833 ability” checkbox determines how VOS3000 advertises its RFC2833 capability in SDP. According to the VOS3000 Transcode Module documentation (Section 2.5), when checked, “VOS uses the RFC2833 support capability of the opposite end (caller), otherwise, VOS3000 declares to support RFC2833 capability.” In practical terms:

• Checked: VOS3000 includes RFC2833 in SDP only if the calling party also includes it. If the caller does not advertise RFC2833 support, VOS3000 will not advertise it to the routing gateway either
• Unchecked: VOS3000 always includes RFC2833 capability in its SDP, regardless of what the caller supports. This is useful when you want to ensure the routing gateway uses RFC2833 regardless of the caller’s capabilities

DTMF Payload Value (VOS3000 DTMF Configuration)

The “Payload” field specifies the RTP payload type number used for RFC2833 DTMF events. According to the VOS3000 Manual, “For example, if the payload is 97, then the payload value of RFC2833 message must be 97.” The default and most common value is 101, matching the standard SDP attribute a=rtpmap:101 telephone-event/8000. Only change this value if your gateway uses a non-standard payload type for RFC2833, which is rare but possible with some older equipment.

DTMF Send Settings

The “DTMF send (H323)” and “DTMF send (SIP)” settings control how VOS3000 transmits DTMF signals to the routing gateway. Both default to “Auto”, which means VOS3000 determines the best DTMF sending method based on the receiver’s capabilities. According to the VOS3000 Manual (Page 46), “It is set to ‘Auto’ by default, indicating that the system would determine the best way to send DTMFs based on the receiver’s capacity. If the receiver provides no capacity set, the system will send according to the default mode.”

The Auto mode typically selects RFC2833 as the preferred send method when the gateway supports it, falling back to SIP INFO or Inband as needed. Only change from Auto to a specific method if you are experiencing DTMF issues that the Auto mode cannot resolve.

Configuring VOS3000 DTMF Configuration on Mapping Gateway

The mapping gateway (customer-side gateway) has identical DTMF configuration options to the routing gateway. Navigate to Operation Management > Gateway Operation > Mapping Gateway and access the Additional Settings > Protocol > DTMF section (VOS3000 Manual Section 2.5.1.2, Page 60). The same principles apply: use “All” for DTMF receive, check “Use peer RFC2833 ability” for standard deployments, and set DTMF send to “Auto”.

Mapping Gateway DTMF for IVR Applications

When your mapping gateway customers use IVR systems (such as calling card platforms or voice mail systems), the DTMF configuration becomes especially critical. The IVR system must receive DTMF signals correctly to navigate menus, enter PINs, and select options. If the mapping gateway’s DTMF receive setting is too restrictive, IVR interactions will fail.

For IVR deployments, the recommended VOS3000 DTMF configuration is:

1. DTMF receive: Set to “All” to accept DTMF in any format from the customer’s device
2. Use peer RFC2833 ability: Checked to properly negotiate RFC2833 with the customer’s SIP device
3. DTMF send (SIP): Set to “Auto” to let VOS3000 choose the best method for sending DTMF to the IVR system
4. Media proxy: Set to “Auto” or “On” to ensure VOS3000 can convert between DTMF methods if needed

VOS3000 DTMF Configuration with Transcode Module

When your VOS3000 deployment includes the transcode module, DTMF handling becomes more sophisticated because VOS3000 can actively convert between DTMF methods. The VOS3000 Transcode Module documentation provides important details about DTMF behavior during transcoding.

DTMF Conversion with Media Proxy Enabled

When media proxy is enabled (which is necessary for transcoding), VOS3000 terminates the RTP stream from the caller, processes the DTMF signals, and then regenerates the appropriate DTMF signals on the callee side. According to the VOS3000 Transcode Module documentation (Section 2.6), “If media forwarding is enabled, the RFC2833 payload and 0-16 key support type received from the far-end SDP is terminated by VOS, and VOS integrates and sends the values set in VOS DTMF configuration to the peer end.”

This means that when media proxy is on:

• VOS3000 terminates all incoming DTMF (RFC2833, SIP INFO, or Inband) from the caller
• VOS3000 regenerates DTMF signals according to the DTMF send settings configured for the routing gateway
• The payload type and key support range in the SDP sent to the routing gateway are determined by VOS3000, not passed through from the caller

DTMF Passthrough Without Media Proxy

When media proxy is disabled, VOS3000 does not intercept the RTP stream and DTMF signals pass through directly between the endpoints. This means RFC2833 DTMF events travel directly from the caller’s device to the called gateway without modification. While this reduces server load, it also means VOS3000 cannot convert between DTMF methods, so both endpoints must support the same DTMF method for it to work correctly.

Troubleshooting VOS3000 DTMF Configuration Issues

DTMF problems in VOS3000 can be complex because they involve multiple components: the caller’s device, the mapping gateway, the VOS3000 softswitch, the routing gateway, and the called endpoint. Here are the most common VOS3000 DTMF configuration issues and their solutions.

Issue 1: IVR Does Not Respond to Keypad Presses

This is the most common DTMF complaint. The caller presses buttons but the IVR system on the other end does not respond. The root cause is almost always a DTMF method mismatch between the caller’s device and the IVR system.

Diagnostic steps:

1. Check the current call details: Use the Current Call view (right-click any gateway > Current Call) and check the “Caller DTMF” and “Callee DTMF” columns. These show which DTMF mode each side is using (VOS3000 Manual Section 2.5.4, Page 95)
2. Verify DTMF receive setting: Ensure both mapping gateway and routing gateway have DTMF receive set to “All”
3. Check media proxy: If DTMF methods differ between caller and callee, media proxy must be enabled for VOS3000 to convert between them
4. Verify RFC2833 in SDP: Check if the caller’s SIP INVITE includes the telephone-event attribute in SDP. If not, the device may not support RFC2833

Issue 2: Duplicate DTMF Digits Received (VOS3000 DTMF Configuration)

When the far-end sends both SIP INFO and RFC2833 simultaneously for the same key press, VOS3000 may detect duplicate digits. According to the VOS3000 Transcode Module documentation (Section 2.6), “When the far-end sends both SIP INFO and RFC2833, VOS will only recognize the first detected key press type, and all subsequent different key press types will not be processed.” Setting DTMF receive to “All” activates this first-detected-type locking mechanism, which prevents duplicate DTMF detection.

Issue 3: DTMF Works with G711 But Not G729

This confirms that the DTMF is being sent Inband rather than via RFC2833 or SIP INFO. Inband DTMF tones are distorted by G729 compression and become unrecognizable. The solution is to configure the gateway to use RFC2833 for DTMF instead of Inband. Check the “Use peer RFC2833 ability” setting and ensure that both the caller’s device and the gateway support RFC2833.

Best Practices for VOS3000 DTMF Configuration

Following these best practices will prevent the majority of DTMF issues in your VOS3000 deployment.

Recommended DTMF Configuration by Scenario

Testing DTMF After Configuration

After making any DTMF configuration changes, always test with actual calls before considering the work complete. Use a SIP phone or softphone to place a test call through your VOS3000 platform and verify that DTMF key presses are recognized on the far end. Test with both G711 and G729 codecs if your deployment uses multiple codecs. Check the Current Call view to verify that the correct DTMF mode is being used on both the caller and callee sides.

For comprehensive call testing instructions, see our VOS3000 PIN test and call test guide.

🔗 Related Resources – VOS3000 DTMF Configuration

• 📖 VOS3000 One-Way Audio and No Voice Troubleshooting
• 📖 VOS3000 PIN Test and SIP Account Call Testing
• 📖 VOS3000 Prefix Conversion and Routing Configuration
• 📖 VOS3000 Troubleshooting and Support Guide
• 📥 VOS3000 Downloads – Manual and Software

Frequently Asked Questions About VOS3000 DTMF Configuration

❓ Which DTMF method should I use in VOS3000?

RFC2833 is the recommended primary DTMF method for VOS3000 because it works reliably with all codecs, is universally supported by modern SIP devices, and provides precise timing information. Set DTMF receive to “All” for maximum compatibility and let VOS3000 automatically select the best method. Only use SIP INFO or Inband when specific gateway requirements demand it.

❓ Why does my IVR not respond to keypad presses?

This is almost always caused by a DTMF method mismatch. Check that media proxy is enabled (Auto or On) so VOS3000 can convert between DTMF methods. Verify that both the mapping gateway and routing gateway have DTMF receive set to “All”. Use the Current Call view to check which DTMF mode is active on both sides of the call.

❓ What is the DTMF payload value and should I change it?

The DTMF payload value is the RTP payload type number used for RFC2833 telephone-event packets. The default and most common value is 101. You should only change this if your gateway uses a non-standard payload type, which would be indicated in the gateway’s SDP with a different number in the a=rtpmap line.

❓ Does VOS3000 DTMF work with G729 codec?

Yes, VOS3000 DTMF works with G729 codec when using RFC2833 or SIP INFO methods. Only Inband DTMF fails with G729 because the codec compresses the audio and distorts the DTMF tones. If you need DTMF with G729, ensure RFC2833 is configured and media proxy is enabled so VOS3000 can properly handle the DTMF signals.

❓ How do I fix duplicate DTMF digits in VOS3000?

Duplicate DTMF occurs when both RFC2833 and SIP INFO are sent simultaneously for the same key press. Set DTMF receive to “All” which activates VOS3000’s first-detected-type locking mechanism. Once the first DTMF type is detected, VOS3000 ignores all other types for the remainder of that call, preventing duplicate digit detection.

❓ Where can I get help with VOS3000 DTMF configuration?

Our VOS3000 specialists can diagnose and fix any DTMF configuration issue remotely. Contact us on WhatsApp at +8801911119966 for expert assistance. We can optimize your DTMF settings for IVR compatibility, troubleshoot DTMF problems, and configure your VOS3000 platform for reliable keypad interaction.

Get Expert Help with VOS3000 DTMF Configuration

DTMF configuration problems can be frustrating and time-consuming to resolve, especially when they involve multiple gateways and endpoints with different DTMF capabilities. The configuration options in VOS3000 are powerful, but they must be set correctly for your specific deployment to achieve reliable DTMF performance.

📱 Contact us on WhatsApp: +8801911119966

Our team provides complete VOS3000 DTMF configuration services, from initial setup to troubleshooting complex DTMF issues. We can optimize your settings for IVR compatibility, calling card systems, and any other DTMF-dependent features in your VoIP platform.

📞 Need Professional VOS3000 Setup Support?

For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:

📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
📥 Downloads: VOS3000 Downloads