{"id":1151,"date":"2026-04-13T11:11:07","date_gmt":"2026-04-13T11:11:07","guid":{"rendered":"https:\/\/www.vos3000.com\/blog\/?p=1151"},"modified":"2026-04-13T11:11:19","modified_gmt":"2026-04-13T11:11:19","slug":"vos3000-dtmf-configuration-rfc2833-vs-sip","status":"publish","type":"post","link":"https:\/\/www.vos3000.com\/blog\/vos3000-dtmf-configuration-rfc2833-vs-sip\/","title":{"rendered":"VOS3000 DTMF Configuration: RFC2833 vs SIP INFO Important Setup Guide"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\" id=\"vos-3000-dtmf-configuration-rfc-2833-vs-sip-info-setup-guide\">VOS3000 DTMF Configuration: RFC2833 vs SIP INFO Setup Guide<\/h1>\n\n\n\n<p>Proper <strong>VOS3000 DTMF configuration<\/strong> 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.<\/p>\n\n\n\n<p>The challenge with VOS3000 DTMF configuration is that there are three different DTMF transport methods \u2014 RFC2833, SIP INFO, and Inband \u2014 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 <strong>+8801911119966<\/strong>.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#vos-3000-dtmf-configuration-rfc-2833-vs-sip-info-setup-guide\">VOS3000 DTMF Configuration: RFC2833 vs SIP INFO Setup Guide<\/a><ul><li><a href=\"#understanding-vos-3000-dtmf-configuration-methods\">Understanding VOS3000 DTMF Configuration Methods<\/a><ul><li><a href=\"#rfc-2833-dtmf-method\">RFC2833 DTMF Method<\/a><\/li><li><a href=\"#sip-info-dtmf-method\">SIP INFO DTMF Method<\/a><\/li><li><a href=\"#inband-dtmf-method\">Inband DTMF Method<\/a><\/li><\/ul><\/li><li><a href=\"#configuring-vos-3000-dtmf-configuration-on-routing-gateway\">Configuring VOS3000 DTMF Configuration on Routing Gateway<\/a><ul><li><a href=\"#dtmf-receive-setting\">DTMF Receive Setting<\/a><\/li><li><a href=\"#use-peer-rfc-2833-ability-setting\">Use Peer RFC2833 Ability Setting<\/a><\/li><li><a href=\"#dtmf-payload-value\">DTMF Payload Value<\/a><\/li><li><a href=\"#dtmf-send-settings\">DTMF Send Settings<\/a><\/li><\/ul><\/li><li><a href=\"#configuring-vos-3000-dtmf-configuration-on-mapping-gateway\">Configuring VOS3000 DTMF Configuration on Mapping Gateway<\/a><ul><li><a href=\"#mapping-gateway-dtmf-for-ivr-applications\">Mapping Gateway DTMF for IVR Applications<\/a><\/li><\/ul><\/li><li><a href=\"#vos-3000-dtmf-configuration-with-transcode-module\">VOS3000 DTMF Configuration with Transcode Module<\/a><ul><li><a href=\"#dtmf-conversion-with-media-proxy-enabled\">DTMF Conversion with Media Proxy Enabled<\/a><\/li><li><a href=\"#dtmf-passthrough-without-media-proxy\">DTMF Passthrough Without Media Proxy<\/a><\/li><\/ul><\/li><li><a href=\"#troubleshooting-vos-3000-dtmf-configuration-issues\">Troubleshooting VOS3000 DTMF Configuration Issues<\/a><ul><li><a href=\"#issue-1-ivr-does-not-respond-to-keypad-presses\">Issue 1: IVR Does Not Respond to Keypad Presses<\/a><\/li><li><a href=\"#issue-2-duplicate-dtmf-digits-received\">Issue 2: Duplicate DTMF Digits Received<\/a><\/li><li><a href=\"#issue-3-dtmf-works-with-g-711-but-not-g-729\">Issue 3: DTMF Works with G711 But Not G729<\/a><\/li><\/ul><\/li><li><a href=\"#best-practices-for-vos-3000-dtmf-configuration\">Best Practices for VOS3000 DTMF Configuration<\/a><ul><li><a href=\"#recommended-dtmf-configuration-by-scenario\">Recommended DTMF Configuration by Scenario<\/a><\/li><li><a href=\"#testing-dtmf-after-configuration\">Testing DTMF After Configuration<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udd17-related-resources\">\ud83d\udd17 Related Resources &#8211; VOS3000 DTMF Configuration<\/a><\/li><li><a href=\"#frequently-asked-questions-about-vos-3000-dtmf-configuration\">Frequently Asked Questions About VOS3000 DTMF Configuration<\/a><ul><li><a href=\"#\u2753-which-dtmf-method-should-i-use-in-vos-3000\">\u2753 Which DTMF method should I use in VOS3000?<\/a><\/li><li><a href=\"#\u2753-why-does-my-ivr-not-respond-to-keypad-presses\">\u2753 Why does my IVR not respond to keypad presses?<\/a><\/li><li><a href=\"#\u2753-what-is-the-dtmf-payload-value-and-should-i-change-it\">\u2753 What is the DTMF payload value and should I change it?<\/a><\/li><li><a href=\"#\u2753-does-vos-3000-dtmf-work-with-g-729-codec\">\u2753 Does VOS3000 DTMF work with G729 codec?<\/a><\/li><li><a href=\"#\u2753-how-do-i-fix-duplicate-dtmf-digits-in-vos-3000\">\u2753 How do I fix duplicate DTMF digits in VOS3000?<\/a><\/li><li><a href=\"#\u2753-where-can-i-get-help-with-vos-3000-dtmf-configuration\">\u2753 Where can I get help with VOS3000 DTMF configuration?<\/a><\/li><\/ul><\/li><li><a href=\"#get-expert-help-with-vos-3000-dtmf-configuration\">Get Expert Help with VOS3000 DTMF Configuration<\/a><\/li><li><a href=\"#\ud83d\udcde-need-call-center-setup-support\">\ud83d\udcde Need Professional VOS3000 Setup Support?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"understanding-vos-3000-dtmf-configuration-methods\">Understanding VOS3000 DTMF Configuration Methods<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"rfc-2833-dtmf-method\">RFC2833 DTMF Method<\/h3>\n\n\n\n<p>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 <code>a=rtpmap:101 telephone-event\/8000<\/code>. The payload type number (commonly 101) is negotiated during call setup. According to the VOS3000 Transcode Module documentation (Section 2.3), &#8220;RFC2833 signals are carried in separate RTP packets, identified in the SDP by a=rtpmap:101 telephone-event\/8000.&#8221;<\/p>\n\n\n\n<p>RFC2833 is the recommended DTMF method for most VOS3000 deployments because:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reliability:<\/strong> DTMF signals are transmitted as separate RTP events, not embedded in audio, so they survive codec compression without distortion<\/li>\n\n\n\n<li><strong>Compatibility:<\/strong> Supported by virtually all modern SIP devices and gateways<\/li>\n\n\n\n<li><strong>Accuracy:<\/strong> DTMF digits are precisely represented with start and end events, ensuring accurate detection at the receiving end<\/li>\n\n\n\n<li><strong>Works with compressed codecs:<\/strong> Unlike Inband, RFC2833 works perfectly with G729, G723, and other low-bitrate codecs<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"sip-info-dtmf-method\">SIP INFO DTMF Method<\/h3>\n\n\n\n<p>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), &#8220;SIP INFO belongs to independent signaling, where key presses are carried in separate signaling messages.&#8221; Each DTMF key press generates a separate SIP INFO message containing the digit information.<\/p>\n\n\n\n<p>SIP INFO has specific advantages and limitations:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Advantage:<\/strong> Works even when media proxy is disabled, because DTMF travels in the signaling channel<\/li>\n\n\n\n<li><strong>Advantage:<\/strong> Does not depend on RTP connectivity between endpoints<\/li>\n\n\n\n<li><strong>Limitation:<\/strong> Some SIP devices do not support SIP INFO for DTMF<\/li>\n\n\n\n<li><strong>Limitation:<\/strong> Timing information is less precise than RFC2833, which can cause issues with some IVR systems<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"inband-dtmf-method\">Inband DTMF Method<\/h3>\n\n\n\n<p>Inband DTMF transmits dual-tone signals as actual audio within the RTP voice stream. The DTMF tones are generated by the phone&#8217;s keypad and embedded in the audio packets just like speech. According to the VOS3000 Transcode Module documentation (Section 2.4), &#8220;Inband key presses are carried in the RTP as a continuous segment of voice.&#8221; This is the oldest DTMF method and works with any telephony equipment, but it has significant limitations.<\/p>\n\n\n\n<p>Critical limitations of Inband DTMF:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Codec dependency:<\/strong> 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<\/li>\n\n\n\n<li><strong>Detection difficulty:<\/strong> Even with G711, background noise and echo can interfere with Inband DTMF detection<\/li>\n\n\n\n<li><strong>Not recommended for VOS3000:<\/strong> Use Inband only when the far-end device does not support RFC2833 or SIP INFO<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udccb Feature<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udd35 RFC2833<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udfe2 SIP INFO<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udfe1 Inband<\/th><\/tr><tr><td>Transport channel<\/td><td>RTP (media)<\/td><td>SIP (signaling)<\/td><td>RTP (audio)<\/td><\/tr><tr><td>Codec compatibility<\/td><td>All codecs<\/td><td>All codecs<\/td><td>G711 only<\/td><\/tr><tr><td>Reliability<\/td><td>High<\/td><td>Medium<\/td><td>Low<\/td><\/tr><tr><td>Media proxy required<\/td><td>Recommended<\/td><td>No<\/td><td>Recommended<\/td><\/tr><tr><td>Device support<\/td><td>Universal<\/td><td>Most SIP devices<\/td><td>All devices<\/td><\/tr><tr><td>Recommended for VOS3000<\/td><td>\u2705 Yes (primary)<\/td><td>\u26a0\ufe0f Specific cases<\/td><td>\u274c Last resort<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"configuring-vos-3000-dtmf-configuration-on-routing-gateway\">Configuring VOS3000 DTMF Configuration on Routing Gateway<\/h2>\n\n\n\n<p>The DTMF settings for routing gateways are found in the Additional Settings &gt; Protocol &gt; DTMF section. Navigate to <strong>Operation Management &gt; Gateway Operation &gt; Routing Gateway<\/strong>, 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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"dtmf-receive-setting\">DTMF Receive Setting<\/h3>\n\n\n\n<p>The &#8220;DTMF receive&#8221; setting specifies how VOS3000 accepts incoming DTMF signals from the gateway. According to the VOS3000 Manual, &#8220;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.&#8221;<\/p>\n\n\n\n<p>Available DTMF receive options:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>All:<\/strong> 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<\/li>\n\n\n\n<li><strong>RFC2833 only:<\/strong> Accept only RFC2833 DTMF signals. Use this when you know the gateway only sends RFC2833<\/li>\n\n\n\n<li><strong>SIP INFO only:<\/strong> Accept only SIP INFO DTMF. Use this when the gateway only supports SIP INFO<\/li>\n\n\n\n<li><strong>Inband only:<\/strong> Accept only Inband DTMF. Rarely recommended due to reliability issues<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"use-peer-rfc-2833-ability-setting\">Use Peer RFC2833 Ability Setting<\/h3>\n\n\n\n<p>The &#8220;Use peer RFC2833 ability&#8221; checkbox determines how VOS3000 advertises its RFC2833 capability in SDP. According to the VOS3000 Transcode Module documentation (Section 2.5), when checked, &#8220;VOS uses the RFC2833 support capability of the opposite end (caller), otherwise, VOS3000 declares to support RFC2833 capability.&#8221; In practical terms:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Checked:<\/strong> 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<\/li>\n\n\n\n<li><strong>Unchecked:<\/strong> 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&#8217;s capabilities<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"dtmf-payload-value\">DTMF Payload Value<\/h3>\n\n\n\n<p>The &#8220;Payload&#8221; field specifies the RTP payload type number used for RFC2833 DTMF events. According to the VOS3000 Manual, &#8220;For example, if the payload is 97, then the payload value of RFC2833 message must be 97.&#8221; The default and most common value is 101, matching the standard SDP attribute <code>a=rtpmap:101 telephone-event\/8000<\/code>. Only change this value if your gateway uses a non-standard payload type for RFC2833, which is rare but possible with some older equipment.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">\u2699\ufe0f Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">\u2705 Recommended Value<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udcdd When to Change<\/th><\/tr><tr><td>DTMF receive<\/td><td>All<\/td><td>Only when gateway uses single method<\/td><\/tr><tr><td>Use peer RFC2833 ability<\/td><td>Checked<\/td><td>Uncheck if gateway needs RFC2833 forced<\/td><\/tr><tr><td>Payload<\/td><td>101<\/td><td>Only if gateway uses non-standard value<\/td><\/tr><tr><td>DTMF send (H323)<\/td><td>Auto<\/td><td>Specific method if Auto fails<\/td><\/tr><tr><td>DTMF send (SIP)<\/td><td>Auto<\/td><td>Specific method if Auto fails<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"dtmf-send-settings\">DTMF Send Settings<\/h3>\n\n\n\n<p>The &#8220;DTMF send (H323)&#8221; and &#8220;DTMF send (SIP)&#8221; settings control how VOS3000 transmits DTMF signals to the routing gateway. Both default to &#8220;Auto&#8221;, which means VOS3000 determines the best DTMF sending method based on the receiver&#8217;s capabilities. According to the VOS3000 Manual (Page 46), &#8220;It is set to &#8216;Auto&#8217; by default, indicating that the system would determine the best way to send DTMFs based on the receiver&#8217;s capacity. If the receiver provides no capacity set, the system will send according to the default mode.&#8221;<\/p>\n\n\n\n<p>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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"configuring-vos-3000-dtmf-configuration-on-mapping-gateway\">Configuring VOS3000 DTMF Configuration on Mapping Gateway<\/h2>\n\n\n\n<p>The mapping gateway (customer-side gateway) has identical DTMF configuration options to the routing gateway. Navigate to <strong>Operation Management &gt; Gateway Operation &gt; Mapping Gateway<\/strong> and access the Additional Settings &gt; Protocol &gt; DTMF section (VOS3000 Manual Section 2.5.1.2, Page 60). The same principles apply: use &#8220;All&#8221; for DTMF receive, check &#8220;Use peer RFC2833 ability&#8221; for standard deployments, and set DTMF send to &#8220;Auto&#8221;.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"mapping-gateway-dtmf-for-ivr-applications\">Mapping Gateway DTMF for IVR Applications<\/h3>\n\n\n\n<p>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&#8217;s DTMF receive setting is too restrictive, IVR interactions will fail.<\/p>\n\n\n\n<p>For IVR deployments, the recommended VOS3000 DTMF configuration is:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>DTMF receive:<\/strong> Set to &#8220;All&#8221; to accept DTMF in any format from the customer&#8217;s device<\/li>\n\n\n\n<li><strong>Use peer RFC2833 ability:<\/strong> Checked to properly negotiate RFC2833 with the customer&#8217;s SIP device<\/li>\n\n\n\n<li><strong>DTMF send (SIP):<\/strong> Set to &#8220;Auto&#8221; to let VOS3000 choose the best method for sending DTMF to the IVR system<\/li>\n\n\n\n<li><strong>Media proxy:<\/strong> Set to &#8220;Auto&#8221; or &#8220;On&#8221; to ensure VOS3000 can convert between DTMF methods if needed<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"vos-3000-dtmf-configuration-with-transcode-module\">VOS3000 DTMF Configuration with Transcode Module<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"dtmf-conversion-with-media-proxy-enabled\">DTMF Conversion with Media Proxy Enabled<\/h3>\n\n\n\n<p>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), &#8220;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.&#8221;<\/p>\n\n\n\n<p>This means that when media proxy is on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VOS3000 terminates all incoming DTMF (RFC2833, SIP INFO, or Inband) from the caller<\/li>\n\n\n\n<li>VOS3000 regenerates DTMF signals according to the DTMF send settings configured for the routing gateway<\/li>\n\n\n\n<li>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<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"dtmf-passthrough-without-media-proxy\">DTMF Passthrough Without Media Proxy<\/h3>\n\n\n\n<p>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&#8217;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.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">\u2699\ufe0f Scenario<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udd35 Media Proxy ON<\/th><th class=\"has-text-align-left\" data-align=\"left\">\u26aa Media Proxy OFF<\/th><\/tr><tr><td>DTMF method conversion<\/td><td>\u2705 Yes (e.g., SIP INFO \u2192 RFC2833)<\/td><td>\u274c No (passthrough only)<\/td><\/tr><tr><td>DTMF payload modification<\/td><td>\u2705 VOS controls payload value<\/td><td>\u274c Original payload passthrough<\/td><\/tr><tr><td>Inband DTMF detection<\/td><td>\u2705 VOS can detect and convert<\/td><td>\u274c Not possible<\/td><\/tr><tr><td>Mixed method handling<\/td><td>\u2705 First detected type only<\/td><td>\u274c Both arrive at peer<\/td><\/tr><tr><td>Server resource usage<\/td><td>Higher (RTP processing)<\/td><td>Lower (signaling only)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"troubleshooting-vos-3000-dtmf-configuration-issues\">Troubleshooting VOS3000 DTMF Configuration Issues<\/h2>\n\n\n\n<p>DTMF problems in VOS3000 can be complex because they involve multiple components: the caller&#8217;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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"issue-1-ivr-does-not-respond-to-keypad-presses\">Issue 1: IVR Does Not Respond to Keypad Presses<\/h3>\n\n\n\n<p>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&#8217;s device and the IVR system.<\/p>\n\n\n\n<p>Diagnostic steps:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Check the current call details:<\/strong> Use the Current Call view (right-click any gateway > Current Call) and check the &#8220;Caller DTMF&#8221; and &#8220;Callee DTMF&#8221; columns. These show which DTMF mode each side is using (VOS3000 Manual Section 2.5.4, Page 95)<\/li>\n\n\n\n<li><strong>Verify DTMF receive setting:<\/strong> Ensure both mapping gateway and routing gateway have DTMF receive set to &#8220;All&#8221;<\/li>\n\n\n\n<li><strong>Check media proxy:<\/strong> If DTMF methods differ between caller and callee, media proxy must be enabled for VOS3000 to convert between them<\/li>\n\n\n\n<li><strong>Verify RFC2833 in SDP:<\/strong> Check if the caller&#8217;s SIP INVITE includes the telephone-event attribute in SDP. If not, the device may not support RFC2833<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"issue-2-duplicate-dtmf-digits-received\">Issue 2: Duplicate DTMF Digits Received<\/h3>\n\n\n\n<p>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), &#8220;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.&#8221; Setting DTMF receive to &#8220;All&#8221; activates this first-detected-type locking mechanism, which prevents duplicate DTMF detection.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"issue-3-dtmf-works-with-g-711-but-not-g-729\">Issue 3: DTMF Works with G711 But Not G729<\/h3>\n\n\n\n<p>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 &#8220;Use peer RFC2833 ability&#8221; setting and ensure that both the caller&#8217;s device and the gateway support RFC2833.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">\u26a0\ufe0f Problem<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udd0d Likely Cause<\/th><th class=\"has-text-align-left\" data-align=\"left\">\u2705 Solution<\/th><\/tr><tr><td>IVR no response<\/td><td>DTMF method mismatch<\/td><td>Enable media proxy + set DTMF to All<\/td><\/tr><tr><td>Duplicate digits<\/td><td>Dual method (SIP INFO + RFC2833)<\/td><td>Set DTMF receive to All (auto-locks type)<\/td><\/tr><tr><td>DTMF fails with G729<\/td><td>Inband DTMF with compressed codec<\/td><td>Use RFC2833 instead of Inband<\/td><\/tr><tr><td>Partial DTMF digits<\/td><td>Payload mismatch<\/td><td>Match payload value with gateway SDP<\/td><\/tr><tr><td>DTMF delay<\/td><td>SIP INFO over congested link<\/td><td>Switch to RFC2833 for faster delivery<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"best-practices-for-vos-3000-dtmf-configuration\">Best Practices for VOS3000 DTMF Configuration<\/h2>\n\n\n\n<p>Following these best practices will prevent the majority of DTMF issues in your VOS3000 deployment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"recommended-dtmf-configuration-by-scenario\">Recommended DTMF Configuration by Scenario<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">\ud83c\udfaf Scenario<\/th><th class=\"has-text-align-left\" data-align=\"left\">\u2699\ufe0f DTMF Receive<\/th><th class=\"has-text-align-left\" data-align=\"left\">\u2699\ufe0f DTMF Send<\/th><th class=\"has-text-align-left\" data-align=\"left\">\ud83d\udd27 Media Proxy<\/th><\/tr><tr><td>Standard SIP to SIP<\/td><td>All<\/td><td>Auto<\/td><td>Auto<\/td><\/tr><tr><td>IVR \/ Calling Card<\/td><td>All<\/td><td>Auto (or RFC2833)<\/td><td>On<\/td><\/tr><tr><td>G729 Codec with DTMF<\/td><td>All<\/td><td>RFC2833<\/td><td>On<\/td><\/tr><tr><td>SIP to H323 conversion<\/td><td>All<\/td><td>Auto<\/td><td>On<\/td><\/tr><tr><td>Low traffic (no transcode)<\/td><td>All<\/td><td>Auto<\/td><td>Auto<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"testing-dtmf-after-configuration\">Testing DTMF After Configuration<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<p>For comprehensive call testing instructions, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-pin-test-sip-account-vos3000-call-test\/\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 PIN test and call test guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd17-related-resources\">\ud83d\udd17 Related Resources &#8211; VOS3000 DTMF Configuration<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/vos3000-dialer-call-test-no-voice-one-way-audio-vos3000-pin-call-no-audio\/\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 One-Way Audio and No Voice Troubleshooting<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/vos3000-pin-test-sip-account-vos3000-call-test\/\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 PIN Test and SIP Account Call Testing<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/callee-rewrite-rule-prefix-conversion-clients-vendor-prefix-settings-in-vos3000\/\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 Prefix Conversion and Routing Configuration<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/faster-support-for-vos3000-easy-troubleshoot-for-problems\/\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 Troubleshooting and Support Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udce5 <a href=\"https:\/\/www.vos3000.com\/downloads.php\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 Downloads &#8211; Manual and Software<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"frequently-asked-questions-about-vos-3000-dtmf-configuration\">Frequently Asked Questions About VOS3000 DTMF Configuration<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-which-dtmf-method-should-i-use-in-vos-3000\">\u2753 Which DTMF method should I use in VOS3000?<\/h3>\n\n\n\n<p>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 &#8220;All&#8221; for maximum compatibility and let VOS3000 automatically select the best method. Only use SIP INFO or Inband when specific gateway requirements demand it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-why-does-my-ivr-not-respond-to-keypad-presses\">\u2753 Why does my IVR not respond to keypad presses?<\/h3>\n\n\n\n<p>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 &#8220;All&#8221;. Use the Current Call view to check which DTMF mode is active on both sides of the call.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-is-the-dtmf-payload-value-and-should-i-change-it\">\u2753 What is the DTMF payload value and should I change it?<\/h3>\n\n\n\n<p>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&#8217;s SDP with a different number in the a=rtpmap line.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-does-vos-3000-dtmf-work-with-g-729-codec\">\u2753 Does VOS3000 DTMF work with G729 codec?<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-how-do-i-fix-duplicate-dtmf-digits-in-vos-3000\">\u2753 How do I fix duplicate DTMF digits in VOS3000?<\/h3>\n\n\n\n<p>Duplicate DTMF occurs when both RFC2833 and SIP INFO are sent simultaneously for the same key press. Set DTMF receive to &#8220;All&#8221; which activates VOS3000&#8217;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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-where-can-i-get-help-with-vos-3000-dtmf-configuration\">\u2753 Where can I get help with VOS3000 DTMF configuration?<\/h3>\n\n\n\n<p>Our VOS3000 specialists can diagnose and fix any DTMF configuration issue remotely. Contact us on WhatsApp at <strong>+8801911119966<\/strong> for expert assistance. We can optimize your DTMF settings for IVR compatibility, troubleshoot DTMF problems, and configure your VOS3000 platform for reliable keypad interaction.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"get-expert-help-with-vos-3000-dtmf-configuration\">Get Expert Help with VOS3000 DTMF Configuration<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<p><strong>\ud83d\udcf1 Contact us on WhatsApp: +8801911119966<\/strong><\/p>\n\n\n\n<p>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.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcde-need-call-center-setup-support\">\ud83d\udcde Need Professional VOS3000 Setup Support?<\/h2>\n\n\n\n<p>For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:<\/p>\n\n\n\n<p>\ud83d\udcf1 <strong>WhatsApp:<\/strong> <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noopener\">+8801911119966<\/a><br>\ud83c\udf10 <strong>Website:<\/strong> <a href=\"https:\/\/www.vos3000.com\">www.vos3000.com<\/a><br>\ud83c\udf10 <strong>Blog:<\/strong> <a href=\"https:\/\/multahost.com\/blog\" target=\"_blank\" rel=\"noopener\">multahost.com\/blog<\/a><br>\ud83d\udce5 <strong>Downloads:<\/strong> <a href=\"https:\/\/www.vos3000.com\/downloads.php\">VOS3000 Downloads<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-7-1024x683.png\" alt=\"VOS3000 P-Asserted-Identity, VOS3000 Web Manager, VOS3000 DTMF Configuration, VOS3000 Agent Account, VOS3000 Transcoding\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-9-1024x576.png\" alt=\"VOS3000 P-Asserted-Identity, VOS3000 Web Manager, VOS3000 DTMF Configuration, VOS3000 Agent Account, VOS3000 Transcoding\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-7-1024x683.png\" alt=\"VOS3000 P-Asserted-Identity, VOS3000 Web Manager, VOS3000 DTMF Configuration, VOS3000 Agent Account, VOS3000 Transcoding\"><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>VOS3000 DTMF configuration guide comparing RFC2833, SIP INFO, and Inband methods. Step-by-step setup for IVR, DTMF relay, and troubleshooting DTMF issues in VoIP.<\/p>\n","protected":false},"author":1,"featured_media":1147,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_kadence_starter_templates_imported_post":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[2],"tags":[5524,5525,5520,5499,5526,2087,5528,5509,5495,5519,5527,3714,5510,5490,5512,5529,5491,5496,5487,5492,5515,5498,5497,5504,5488,5493,5494,5522,5502,5506,5516,5511,5505,5521,5523,5486,5507,5501,5517,5518,5503,5489,5500,5514,5508,5513],"class_list":["post-1151","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vos3000","tag-vos3000-2-1-8-05-dtmf","tag-vos3000-2-1-9-07-dtmf","tag-vos3000-call-card-dtmf","tag-vos3000-codec-dtmf","tag-vos3000-dtmf-best-practices","tag-vos3000-dtmf-configuration","tag-vos3000-dtmf-configuration-tutorial","tag-vos3000-dtmf-conversion","tag-vos3000-dtmf-detection","tag-vos3000-dtmf-fix","tag-vos3000-dtmf-guide","tag-vos3000-dtmf-mode","tag-vos3000-dtmf-passthrough","tag-vos3000-dtmf-payload","tag-vos3000-dtmf-payload-value","tag-vos3000-dtmf-problem-solve","tag-vos3000-dtmf-relay","tag-vos3000-dtmf-send-receive","tag-vos3000-dtmf-setup","tag-vos3000-dtmf-troubleshooting","tag-vos3000-dual-tone-multi-frequency","tag-vos3000-g711-dtmf","tag-vos3000-g729-dtmf","tag-vos3000-gateway-dtmf","tag-vos3000-inband-dtmf","tag-vos3000-ivr-dtmf","tag-vos3000-ivr-problem","tag-vos3000-ivr-prompt","tag-vos3000-keypad-not-working","tag-vos3000-mapping-gateway-dtmf","tag-vos3000-media-proxy-dtmf","tag-vos3000-peer-rfc2833","tag-vos3000-phone-dtmf","tag-vos3000-pin-dtmf","tag-vos3000-professional-dtmf-setup","tag-vos3000-rfc2833","tag-vos3000-routing-gateway-dtmf","tag-vos3000-rtp-dtmf","tag-vos3000-rtpmap-telephone-event","tag-vos3000-sdp-dtmf","tag-vos3000-signaling-dtmf","tag-vos3000-sip-info","tag-vos3000-telephone-event","tag-vos3000-touch-tone","tag-vos3000-transcode-dtmf","tag-vos3000-voip-dtmf"],"acf":[],"jetpack_featured_media_url":"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3.png","blog_post_layout_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-150x150.png",150,150,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3.png",1536,1024,false]},"categories_names":{"2":{"name":"VOS3000`","link":"https:\/\/www.vos3000.com\/blog\/category\/vos3000\/"}},"tags_names":{"5524":{"name":"VOS3000 2.1.8.05 DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-2-1-8-05-dtmf\/"},"5525":{"name":"VOS3000 2.1.9.07 DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-2-1-9-07-dtmf\/"},"5520":{"name":"VOS3000 call card DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-call-card-dtmf\/"},"5499":{"name":"VOS3000 codec DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-codec-dtmf\/"},"5526":{"name":"VOS3000 DTMF best practices","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-best-practices\/"},"2087":{"name":"VOS3000 DTMF configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-configuration\/"},"5528":{"name":"VOS3000 DTMF configuration tutorial","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-configuration-tutorial\/"},"5509":{"name":"VOS3000 DTMF conversion","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-conversion\/"},"5495":{"name":"VOS3000 DTMF detection","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-detection\/"},"5519":{"name":"VOS3000 DTMF fix","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-fix\/"},"5527":{"name":"VOS3000 DTMF guide","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-guide\/"},"3714":{"name":"VOS3000 DTMF mode","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-mode\/"},"5510":{"name":"VOS3000 DTMF passthrough","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-passthrough\/"},"5490":{"name":"VOS3000 DTMF payload","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-payload\/"},"5512":{"name":"VOS3000 DTMF payload value","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-payload-value\/"},"5529":{"name":"VOS3000 DTMF problem solve","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-problem-solve\/"},"5491":{"name":"VOS3000 DTMF relay","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-relay\/"},"5496":{"name":"VOS3000 DTMF send receive","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-send-receive\/"},"5487":{"name":"VOS3000 DTMF setup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-setup\/"},"5492":{"name":"VOS3000 DTMF troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dtmf-troubleshooting\/"},"5515":{"name":"VOS3000 dual tone multi frequency","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-dual-tone-multi-frequency\/"},"5498":{"name":"VOS3000 G711 DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-g711-dtmf\/"},"5497":{"name":"VOS3000 G729 DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-g729-dtmf\/"},"5504":{"name":"VOS3000 gateway DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-gateway-dtmf\/"},"5488":{"name":"VOS3000 Inband DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-inband-dtmf\/"},"5493":{"name":"VOS3000 IVR DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-dtmf\/"},"5494":{"name":"VOS3000 IVR problem","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-problem\/"},"5522":{"name":"VOS3000 IVR prompt","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-prompt\/"},"5502":{"name":"VOS3000 keypad not working","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-keypad-not-working\/"},"5506":{"name":"VOS3000 mapping gateway DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-mapping-gateway-dtmf\/"},"5516":{"name":"VOS3000 media proxy DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-media-proxy-dtmf\/"},"5511":{"name":"VOS3000 peer RFC2833","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-peer-rfc2833\/"},"5505":{"name":"VOS3000 phone DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-phone-dtmf\/"},"5521":{"name":"VOS3000 PIN DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-pin-dtmf\/"},"5523":{"name":"VOS3000 professional DTMF setup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-professional-dtmf-setup\/"},"5486":{"name":"VOS3000 RFC2833","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-rfc2833\/"},"5507":{"name":"VOS3000 routing gateway DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-routing-gateway-dtmf\/"},"5501":{"name":"VOS3000 RTP DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-rtp-dtmf\/"},"5517":{"name":"VOS3000 rtpmap telephone event","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-rtpmap-telephone-event\/"},"5518":{"name":"VOS3000 SDP DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-sdp-dtmf\/"},"5503":{"name":"VOS3000 signaling DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-signaling-dtmf\/"},"5489":{"name":"VOS3000 SIP INFO","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-sip-info\/"},"5500":{"name":"VOS3000 telephone event","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-telephone-event\/"},"5514":{"name":"VOS3000 touch tone","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-touch-tone\/"},"5508":{"name":"VOS3000 transcode DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-transcode-dtmf\/"},"5513":{"name":"VOS3000 VoIP DTMF","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-voip-dtmf\/"}},"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-150x150.png",150,150,true],"cvmm-medium":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-300x300.png",300,300,true],"cvmm-medium-plus":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-305x207.png",305,207,true],"cvmm-portrait":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-400x600.png",400,600,true],"cvmm-medium-square":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-600x600.png",600,600,true],"cvmm-large":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-1024x1024.png",1024,1024,true],"cvmm-small":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3-130x95.png",130,95,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding-3.png",1536,1024,false]},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/comments?post=1151"}],"version-history":[{"count":1,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1151\/revisions"}],"predecessor-version":[{"id":1158,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1151\/revisions\/1158"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media\/1147"}],"wp:attachment":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media?parent=1151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/categories?post=1151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/tags?post=1151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}