{"id":1549,"date":"2026-04-30T04:50:42","date_gmt":"2026-04-30T04:50:42","guid":{"rendered":"https:\/\/www.vos3000.com\/blog\/?p=1549"},"modified":"2026-04-30T04:50:52","modified_gmt":"2026-04-30T04:50:52","slug":"vos3000-ivr-call-state-udp","status":"publish","type":"post","link":"https:\/\/www.vos3000.com\/blog\/vos3000-ivr-call-state-udp\/","title":{"rendered":"VOS3000 IVR Call State UDP Reporting Reliable Real-Time Notification"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\" id=\"vos-3000-ivr-call-state-udp-reporting-reliable-real-time-notification\">VOS3000 IVR Call State UDP Reporting: Reliable Real-Time Notification<\/h1>\n\n\n\n<p>\ud83d\udce1 How does your VOS3000 IVR system notify external applications about call state changes in real time? When a callback is ringing, answered, or hung up, how can your monitoring system or billing platform know immediately? The answer is the <strong>VOS3000 IVR call state UDP<\/strong> reporting feature \u2014 a set of four parameters that enable the IVR to send real-time UDP datagrams to an external server whenever a call state changes. \ud83c\udfaf<\/p>\n\n\n\n<p>\ud83d\udccb According to the official VOS3000 V2.1.9.07 Manual, Section 4.3.5.3 (Audio Service Parameter), the IVR call state UDP reporting is configured through four parameters: <strong>IVR_CALL_REPORT_IP<\/strong> (target IP address for call state notifications), <strong>IVR_CALL_REPORT_PORT<\/strong> (default: 8000, the UDP port for reporting), <strong>IVR_CALL_REPORT_RETRY<\/strong> (default: 6, retry times), and <strong>IVR_CALL_REPORT_RETRY_INTERVAL<\/strong> (default: 3, retry interval in seconds). \ud83d\udd04<\/p>\n\n\n\n<p>\ud83d\udd27 All data in this guide is sourced exclusively from the official VOS3000 V2.1.9.07 Manual, Section 4.3.5.3 \u2014 no fabricated values, no guesswork. For expert assistance with your VOS3000 deployment, contact us on WhatsApp at <strong>+8801911119966<\/strong>. \ud83d\udca1<\/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-ivr-call-state-udp-reporting-reliable-real-time-notification\">VOS3000 IVR Call State UDP Reporting: Reliable Real-Time Notification<\/a><ul><li><a href=\"#\ud83d\udce1-what-is-vos-3000-ivr-call-state-udp-reporting\">\ud83d\udce1 What Is VOS3000 IVR Call State UDP Reporting?<\/a><ul><li><a href=\"#\ud83c\udfaf-why-vos-3000-ivr-call-state-udp-reporting-matters\">\ud83c\udfaf Why VOS3000 IVR Call State UDP Reporting Matters<\/a><\/li><\/ul><\/li><li><a href=\"#\u2699\ufe0f-udp-payload-format-request-and-response\">\u2699\ufe0f UDP Payload Format \u2014 Request and Response<\/a><\/li><li><a href=\"#\ud83d\udccb-retry-mechanism-ensuring-reliable-delivery\">\ud83d\udccb Retry Mechanism \u2014 Ensuring Reliable Delivery<\/a><\/li><li><a href=\"#\ud83d\udcca-configuration-parameters-complete-reference\">\ud83d\udcca Configuration Parameters \u2014 Complete Reference (VOS3000 IVR Call State)<\/a><\/li><li><a href=\"#\ud83d\udee1\ufe0f-common-call-state-udp-problems-and-solutions\">\ud83d\udee1\ufe0f Common VOS3000 IVR Call State UDP Problems and Solutions<\/a><ul><li><a href=\"#\u274c-problem-1-external-server-not-receiving-udp-notifications\">\u274c Problem 1: External Server Not Receiving UDP Notifications<\/a><\/li><li><a href=\"#\u274c-problem-2-duplicate-call-state-notifications-received\">\u274c Problem 2: Duplicate Call State Notifications Received<\/a><\/li><li><a href=\"#\u274c-problem-3-notifications-delayed-by-several-seconds\">\u274c Problem 3: Notifications Delayed by Several Seconds<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-vos-3000-ivr-call-state-udp-configuration-checklist\">\ud83d\udcca VOS3000 IVR Call State UDP Configuration Checklist<\/a><\/li><li><a href=\"#\u2753-frequently-asked-questions\">\u2753 Frequently Asked Questions<\/a><ul><li><a href=\"#\u2753-what-is-vos-3000-ivr-call-state-udp-reporting\">\u2753 What is VOS3000 IVR call state UDP reporting?<\/a><\/li><li><a href=\"#\u2753-what-are-the-call-state-values-in-udp-notifications\">\u2753 What are the call state values in UDP notifications?<\/a><\/li><li><a href=\"#\u2753-how-does-the-retry-mechanism-work\">\u2753 How does the retry mechanism work?<\/a><\/li><li><a href=\"#\u2753-what-is-the-default-udp-port-for-call-state-reporting\">\u2753 What is the default UDP port for call state reporting?<\/a><\/li><li><a href=\"#\u2753-does-call-state-reporting-affect-ivr-call-performance\">\u2753 Does call state reporting affect IVR call performance?<\/a><\/li><li><a href=\"#\u2753-can-i-send-call-state-notifications-to-multiple-servers\">\u2753 Can I send call state notifications to multiple servers?<\/a><\/li><\/ul><\/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=\"\ud83d\udce1-what-is-vos-3000-ivr-call-state-udp-reporting\">\ud83d\udce1 What Is VOS3000 IVR Call State UDP Reporting?<\/h2>\n\n\n\n<p>\ud83d\udd04 The <strong>VOS3000 IVR call state UDP<\/strong> reporting feature sends real-time notifications about IVR call state changes to an external server via UDP datagrams. This enables external systems \u2014 such as monitoring dashboards, billing platforms, CRM systems, or fraud detection engines \u2014 to receive immediate updates when IVR calls change state, without polling or querying the VOS3000 database. \ud83d\udccb<\/p>\n\n\n\n<p>\ud83d\udccc According to the official VOS3000 V2.1.9.07 Manual, Section 4.3.5.3:<\/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\">Parameter<\/th><th class=\"has-text-align-left\" data-align=\"left\">Default<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><\/tr><tr><td><strong>IVR_CALL_REPORT_IP<\/strong><\/td><td>\u2014<\/td><td>Send IVR second line&#8217;s call state. Target IP address for UDP notifications<\/td><\/tr><tr><td><strong>IVR_CALL_REPORT_PORT<\/strong><\/td><td>8000<\/td><td>Report UDP Port \u2014 destination port for call state notifications<\/td><\/tr><tr><td><strong>IVR_CALL_REPORT_RETRY<\/strong><\/td><td>6<\/td><td>Call State Notify Retry Times \u2014 how many times to retry if notification fails<\/td><\/tr><tr><td><strong>IVR_CALL_REPORT_RETRY_INTERVAL<\/strong><\/td><td>3<\/td><td>Call State Notify Retry Interval \u2014 seconds between retry attempts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>\ud83d\udca1 <strong>Key insight:<\/strong> The manual specifies the UDP payload format for call state notifications. The request format includes: &#8220;Call ID, Serial Number, Call State, Caller Number, Callee Number, Forward Number, Menu ID, Menu Name.&#8221; The response format is simpler: &#8220;Call ID, Serial Number.&#8221; The Call State values are: <strong>Ringing (180\/183) \/ OK \/ Bye<\/strong>. This structured format enables external systems to parse and process call state events programmatically. \ud83d\udd12<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83c\udfaf-why-vos-3000-ivr-call-state-udp-reporting-matters\">\ud83c\udfaf Why VOS3000 IVR Call State UDP Reporting Matters<\/h3>\n\n\n\n<p>\u26a0\ufe0f Without real-time call state reporting, several operational challenges arise:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udcca <strong>Blind operations:<\/strong> Administrators cannot monitor IVR callback activity in real time \u2014 they must query the database or CDR files after the fact<\/li>\n\n\n\n<li>\ud83d\udcde <strong>Delayed fraud detection:<\/strong> Unusual calling patterns on IVR callbacks cannot be detected until CDR records are analyzed, by which time significant losses may have occurred<\/li>\n\n\n\n<li>\ud83d\udd04 <strong>No CRM integration:<\/strong> Customer-facing systems cannot update call status in real time \u2014 agents see stale data when customers call back<\/li>\n\n\n\n<li>\ud83d\udee1\ufe0f <strong>Missed billing events:<\/strong> Real-time billing platforms that need immediate call state notifications cannot function without UDP push events<\/li>\n\n\n\n<li>\ud83d\udccb <strong>Poor troubleshooting:<\/strong> When IVR callbacks fail, engineers lack real-time visibility into which call state the failure occurred at<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\u2699\ufe0f-udp-payload-format-request-and-response\">\u2699\ufe0f UDP Payload Format \u2014 Request and Response<\/h2>\n\n\n\n<p>\ud83d\udd04 The <strong>VOS3000 IVR call state UDP<\/strong> reporting uses a structured payload format for both the request (sent by IVR to external server) and the response (sent by external server back to IVR). Understanding this format is essential for building the receiving application. \ud83d\udce1<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">\ud83d\udce1 VOS3000 IVR Call State UDP \u2014 Payload Format:\n\nREQUEST (IVR \u2192 External Server):\n\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n\u2502  Fields:                                                            \u2502\n\u2502  \u2022 Call ID          \u2014 Unique identifier for this call               \u2502\n\u2502  \u2022 Serial Number    \u2014 Sequence number for this notification        \u2502\n\u2502  \u2022 Call State       \u2014 Current state: Ringing(180\/183) \/ OK \/ Bye   \u2502\n\u2502  \u2022 Caller Number    \u2014 Number of the calling party                  \u2502\n\u2502  \u2022 Callee Number    \u2014 Number of the called party                   \u2502\n\u2502  \u2022 Forward Number   \u2014 Forwarding destination (if applicable)       \u2502\n\u2502  \u2022 Menu ID          \u2014 IVR menu identifier                          \u2502\n\u2502  \u2022 Menu Name        \u2014 IVR menu name                                \u2502\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n\nRESPONSE (External Server \u2192 IVR):\n\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n\u2502  Fields:                                                            \u2502\n\u2502  \u2022 Call ID          \u2014 Same Call ID from the request                \u2502\n\u2502  \u2022 Serial Number    \u2014 Same Serial Number from the request          \u2502\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n<\/pre>\n\n\n\n<p>\ud83d\udcca <strong>Call State values:<\/strong> The manual specifies three possible call states: <strong>Ringing (180\/183)<\/strong> \u2014 the call is alerting the destination, indicated by SIP 180 Ringing or 183 Session Progress responses; <strong>OK<\/strong> \u2014 the call has been answered and is now active (SIP 200 OK); <strong>Bye<\/strong> \u2014 the call has been terminated (SIP BYE message). These correspond directly to the SIP signaling states, enabling the external system to track the complete call lifecycle. For help implementing the UDP receiver, reach us on WhatsApp at <strong>+8801911119966<\/strong>. \ud83d\udcf1<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udccb-retry-mechanism-ensuring-reliable-delivery\">\ud83d\udccb Retry Mechanism \u2014 Ensuring Reliable Delivery<\/h2>\n\n\n\n<p>\ud83d\udd11 UDP is a connectionless protocol \u2014 datagrams can be lost in transit. The <strong>VOS3000 IVR call state UDP<\/strong> reporting includes a built-in retry mechanism to improve delivery reliability. According to the manual, IVR_CALL_REPORT_RETRY (default: 6) controls how many times the system retries a failed notification, and IVR_CALL_REPORT_RETRY_INTERVAL (default: 3) controls the interval between retry attempts in seconds. \ud83d\udee0\ufe0f<\/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\">Retry Attempt<\/th><th class=\"has-text-align-left\" data-align=\"left\">Timing (from initial send)<\/th><th class=\"has-text-align-left\" data-align=\"left\">Action<\/th><\/tr><tr><td>1st send<\/td><td>0 seconds (immediate)<\/td><td>Initial UDP notification sent<\/td><\/tr><tr><td>1st retry<\/td><td>3 seconds<\/td><td>Retry if no response received<\/td><\/tr><tr><td>2nd retry<\/td><td>6 seconds<\/td><td>Second retry attempt<\/td><\/tr><tr><td>3rd\u20136th retry<\/td><td>9, 12, 15, 18 seconds<\/td><td>Continue retrying up to 6 times total<\/td><\/tr><tr><td>After 6 retries<\/td><td>18 seconds elapsed<\/td><td>Give up \u2014 notification considered failed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>\ud83d\udca1 <strong>Important:<\/strong> The retry mechanism requires the external server to send a response back to the IVR with the matching Call ID and Serial Number. If the IVR receives a valid response, it considers the notification delivered and does not retry further. If no response is received after all retry attempts are exhausted, the notification is discarded \u2014 the call continues normally, but the external system will have a gap in its call state tracking. \ud83d\udcd6<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-configuration-parameters-complete-reference\">\ud83d\udcca Configuration Parameters \u2014 Complete Reference (VOS3000 IVR Call State)<\/h2>\n\n\n\n<p>\ud83c\udfe2 Here is the complete reference for all four <strong>VOS3000 IVR call state UDP<\/strong> parameters with recommended values for different deployment scenarios: \ud83d\udca1<\/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\">Parameter<\/th><th class=\"has-text-align-left\" data-align=\"left\">Default<\/th><th class=\"has-text-align-left\" data-align=\"left\">Recommended<\/th><th class=\"has-text-align-left\" data-align=\"left\">Notes<\/th><\/tr><tr><td><strong>IVR_CALL_REPORT_IP<\/strong><\/td><td>Not set<\/td><td>Your monitoring server IP<\/td><td>MUST be configured to enable call state reporting<\/td><\/tr><tr><td><strong>IVR_CALL_REPORT_PORT<\/strong><\/td><td>8000<\/td><td>8000 (or custom port)<\/td><td>Must match the port your UDP receiver is listening on<\/td><\/tr><tr><td><strong>IVR_CALL_REPORT_RETRY<\/strong><\/td><td>6<\/td><td>3-6<\/td><td>6 retries provides good reliability; reduce to 3 for low-latency networks<\/td><\/tr><tr><td><strong>IVR_CALL_REPORT_RETRY_INTERVAL<\/strong><\/td><td>3<\/td><td>2-3 seconds<\/td><td>3 seconds is appropriate for most networks; use 2 for LAN deployments<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udee1\ufe0f-common-call-state-udp-problems-and-solutions\">\ud83d\udee1\ufe0f Common VOS3000 IVR Call State UDP Problems and Solutions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-1-external-server-not-receiving-udp-notifications\">\u274c Problem 1: External Server Not Receiving UDP Notifications<\/h3>\n\n\n\n<p>\ud83d\udd0d <strong>Symptom:<\/strong> The IVR is configured with the IVR_CALL_REPORT_IP, but the external server never receives any call state notifications.<\/p>\n\n\n\n<p>\ud83d\udca1 <strong>Cause:<\/strong> The IVR_CALL_REPORT_IP may be incorrect, a firewall may be blocking UDP traffic on the configured port, or the external server&#8217;s UDP listener is not running.<\/p>\n\n\n\n<p>\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udccb Verify the IVR_CALL_REPORT_IP address is correct and reachable from the VOS3000 server<\/li>\n\n\n\n<li>\ud83d\udee1\ufe0f Check firewall rules on both VOS3000 server and external server \u2014 UDP port 8000 (or configured port) must be allowed<\/li>\n\n\n\n<li>\ud83d\udd0d Confirm the external server has a UDP listener running on the configured IVR_CALL_REPORT_PORT<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-2-duplicate-call-state-notifications-received\">\u274c Problem 2: Duplicate Call State Notifications Received<\/h3>\n\n\n\n<p>\ud83d\udd0d <strong>Symptom:<\/strong> The external server receives the same call state notification multiple times.<\/p>\n\n\n\n<p>\ud83d\udca1 <strong>Cause:<\/strong> The external server is not sending the response back to the IVR, so the IVR retries the notification according to the retry mechanism.<\/p>\n\n\n\n<p>\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udccb Ensure the external server sends a response with matching Call ID and Serial Number for each notification received<\/li>\n\n\n\n<li>\ud83d\udd0d Verify the response is being sent back to the correct VOS3000 IP and port<\/li>\n\n\n\n<li>\ud83d\udcca Implement deduplication on the external server using the Call ID and Serial Number fields<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-3-notifications-delayed-by-several-seconds\">\u274c Problem 3: Notifications Delayed by Several Seconds<\/h3>\n\n\n\n<p>\ud83d\udd0d <strong>Symptom:<\/strong> Call state notifications arrive at the external server with significant delay \u2014 sometimes 10-20 seconds after the actual call state change.<\/p>\n\n\n\n<p>\ud83d\udca1 <strong>Cause:<\/strong> The IVR_CALL_REPORT_RETRY_INTERVAL is set too high, or the notification is being retried multiple times because the initial send failed, causing cumulative delays.<\/p>\n\n\n\n<p>\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u23f1\ufe0f Reduce IVR_CALL_REPORT_RETRY_INTERVAL to 2 seconds for faster retry cycles<\/li>\n\n\n\n<li>\ud83d\udccb Ensure the external server responds quickly to each notification to prevent unnecessary retries<\/li>\n\n\n\n<li>\ud83d\udd0d Check network latency between VOS3000 and the external server<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-vos-3000-ivr-call-state-udp-configuration-checklist\">\ud83d\udcca VOS3000 IVR Call State UDP Configuration Checklist<\/h2>\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\">Check<\/th><th class=\"has-text-align-left\" data-align=\"left\">Action<\/th><th class=\"has-text-align-left\" data-align=\"left\">Status<\/th><\/tr><tr><td>\ud83d\udccc 1<\/td><td>Set IVR_CALL_REPORT_IP to the IP address of your external monitoring server<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 2<\/td><td>Set IVR_CALL_REPORT_PORT to match your UDP listener port (default: 8000)<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 3<\/td><td>Configure IVR_CALL_REPORT_RETRY and RETRY_INTERVAL for your network reliability<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 4<\/td><td>Deploy and test the UDP listener application on the external server<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 5<\/td><td>Test by making an IVR callback and verifying notifications are received for Ringing, OK, and Bye states<\/td><td>\u2610<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>\ud83d\udcde For expert guidance on VOS3000 IVR call state UDP configuration, reach us on WhatsApp at <strong>+8801911119966<\/strong>. \ud83d\udca1<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\u2753-frequently-asked-questions\">\u2753 Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-is-vos-3000-ivr-call-state-udp-reporting\">\u2753 What is VOS3000 IVR call state UDP reporting?<\/h3>\n\n\n\n<p>\ud83d\udce1 <strong>VOS3000 IVR call state UDP<\/strong> reporting is a feature that sends real-time UDP datagrams to an external server whenever an IVR call changes state. According to the VOS3000 V2.1.9.07 Manual (Section 4.3.5.3), it sends &#8220;IVR second line&#8217;s call state&#8221; via UDP with a payload containing: Call ID, Serial Number, Call State (Ringing(180\/183)\/OK\/Bye), Caller Number, Callee Number, Forward Number, Menu ID, and Menu Name. The external server responds with the matching Call ID and Serial Number. The feature is configured through four parameters: IVR_CALL_REPORT_IP, IVR_CALL_REPORT_PORT (default: 8000), IVR_CALL_REPORT_RETRY (default: 6), and IVR_CALL_REPORT_RETRY_INTERVAL (default: 3). \ud83d\udccb<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-are-the-call-state-values-in-udp-notifications\">\u2753 What are the call state values in UDP notifications?<\/h3>\n\n\n\n<p>\ud83d\udcde The VOS3000 manual specifies three call state values: <strong>Ringing (180\/183)<\/strong> \u2014 the call is alerting the destination (SIP 180 Ringing or 183 Session Progress); <strong>OK<\/strong> \u2014 the call has been answered and is active (SIP 200 OK); <strong>Bye<\/strong> \u2014 the call has been terminated (SIP BYE). These three states represent the complete call lifecycle: setup \u2192 active \u2192 termination. The external server can track each call from initial ringing through answer to hangup by processing these state change events in sequence. \ud83d\udd27<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-how-does-the-retry-mechanism-work\">\u2753 How does the retry mechanism work?<\/h3>\n\n\n\n<p>\ud83d\udd04 When the IVR sends a call state UDP notification, it waits for a response from the external server containing the matching Call ID and Serial Number. If no response is received, the IVR retries the notification up to <strong>IVR_CALL_REPORT_RETRY<\/strong> times (default: 6), with <strong>IVR_CALL_REPORT_RETRY_INTERVAL<\/strong> seconds (default: 3) between each retry. If the external server responds before all retries are exhausted, no further retries are sent. If all retries fail, the notification is discarded and the call continues normally. \ud83d\udca1<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-is-the-default-udp-port-for-call-state-reporting\">\u2753 What is the default UDP port for call state reporting?<\/h3>\n\n\n\n<p>\ud83d\udccb The default IVR_CALL_REPORT_PORT is <strong>8000<\/strong>, according to the VOS3000 V2.1.9.07 Manual (Section 4.3.5.3). This is the &#8220;Report UDP Port&#8221; \u2014 the destination port on the external server where call state notifications are sent. Your UDP listener application must be configured to listen on this port (or you must change this parameter to match your application&#8217;s listening port). Ensure that firewall rules allow UDP traffic on this port between the VOS3000 server and the external monitoring server. \ud83d\udce1<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-does-call-state-reporting-affect-ivr-call-performance\">\u2753 Does call state reporting affect IVR call performance?<\/h3>\n\n\n\n<p>\ud83d\udcca The <strong>VOS3000 IVR call state UDP<\/strong> reporting uses a lightweight UDP protocol that has minimal impact on call performance. UDP is connectionless and does not block the call flow \u2014 the notification is sent asynchronously, and the retry mechanism does not delay call processing. Even if all retries fail, the call continues normally. The only resource consideration is the small amount of network bandwidth consumed by the UDP datagrams and the processing overhead on the IVR server for generating and sending notifications. For high-volume deployments, ensure your external server can handle the notification rate. \ud83d\udee1\ufe0f<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-can-i-send-call-state-notifications-to-multiple-servers\">\u2753 Can I send call state notifications to multiple servers?<\/h3>\n\n\n\n<p>\ud83d\udd04 The VOS3000 manual specifies a single IVR_CALL_REPORT_IP parameter, which suggests that call state notifications are sent to one destination server at a time. If you need to send notifications to multiple servers, you would typically configure a single receiving server that then distributes the events to other systems \u2014 acting as a call state event broker. Alternatively, you could implement a UDP relay or message queue on the receiving server to fan out notifications to multiple downstream consumers. For integration guidance, reach us on WhatsApp at <strong>+8801911119966<\/strong>. \ud83d\udcf1<\/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-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-VOS3000-IVR-Voicemail-System-2-1024x1024.png\" alt=\"VOS3000 Authorization Type Hierarchy, VOS3000 Reverse Charging, VOS3000 DID DDI Numbers, VOS3000 Call Forwarding Types, VOS3000 Do Not Disturb Mode, VOS3000 Display Caller ID Forwarding, VOS3000 Monthly Consumption Limits, VOS3000 IVR Callback Timing, VOS3000 IVR Call State UDP Reporting, VOS3000 IVR Codec Priority, VOS3000 IVR Voicemail Navigation, VOS3000 IVR Custom Ringback Tone, VOS3000 IVR DTMF Parse Mode, VOS3000 IVR Voicemail System, VOS3000 authorization type hierarchy, VOS3000 reverse charging configuration, VOS3000 DID DDI numbers, VOS3000 call forwarding types, VOS3000 do not disturb mode, VOS3000 display caller ID forwarding, VOS3000 monthly consumption limits, VOS3000 IVR callback timing, VOS3000 IVR call state UDP, VOS3000 IVR codec priority, VOS3000 IVR inband DTMF detection, VOS3000 IVR DTMF parse mode, VOS3000 IVR voicemail system, VOS3000 IVR voice alarm configuration, VOS3000 IVR custom ringback tone, VOS3000 IVR voicemail navigation\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-VOS3000-IVR-Voicemail-System-2-1024x1024.png\" alt=\"VOS3000 Authorization Type Hierarchy, VOS3000 Reverse Charging, VOS3000 DID DDI Numbers, VOS3000 Call Forwarding Types, VOS3000 Do Not Disturb Mode, VOS3000 Display Caller ID Forwarding, VOS3000 Monthly Consumption Limits, VOS3000 IVR Callback Timing, VOS3000 IVR Call State UDP Reporting, VOS3000 IVR Codec Priority, VOS3000 IVR Voicemail Navigation, VOS3000 IVR Custom Ringback Tone, VOS3000 IVR DTMF Parse Mode, VOS3000 IVR Voicemail System, VOS3000 authorization type hierarchy, VOS3000 reverse charging configuration, VOS3000 DID DDI numbers, VOS3000 call forwarding types, VOS3000 do not disturb mode, VOS3000 display caller ID forwarding, VOS3000 monthly consumption limits, VOS3000 IVR callback timing, VOS3000 IVR call state UDP, VOS3000 IVR codec priority, VOS3000 IVR inband DTMF detection, VOS3000 IVR DTMF parse mode, VOS3000 IVR voicemail system, VOS3000 IVR voice alarm configuration, VOS3000 IVR custom ringback tone, VOS3000 IVR voicemail navigation\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-VOS3000-IVR-Voicemail-System-2-1024x1024.png\" alt=\"VOS3000 Authorization Type Hierarchy, VOS3000 Reverse Charging, VOS3000 DID DDI Numbers, VOS3000 Call Forwarding Types, VOS3000 Do Not Disturb Mode, VOS3000 Display Caller ID Forwarding, VOS3000 Monthly Consumption Limits, VOS3000 IVR Callback Timing, VOS3000 IVR Call State UDP Reporting, VOS3000 IVR Codec Priority, VOS3000 IVR Voicemail Navigation, VOS3000 IVR Custom Ringback Tone, VOS3000 IVR DTMF Parse Mode, VOS3000 IVR Voicemail System, VOS3000 authorization type hierarchy, VOS3000 reverse charging configuration, VOS3000 DID DDI numbers, VOS3000 call forwarding types, VOS3000 do not disturb mode, VOS3000 display caller ID forwarding, VOS3000 monthly consumption limits, VOS3000 IVR callback timing, VOS3000 IVR call state UDP, VOS3000 IVR codec priority, VOS3000 IVR inband DTMF detection, VOS3000 IVR DTMF parse mode, VOS3000 IVR voicemail system, VOS3000 IVR voice alarm configuration, VOS3000 IVR custom ringback tone, VOS3000 IVR voicemail navigation\"><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Master VOS3000 IVR call state UDP reporting: configure IVR_CALL_REPORT_IP, PORT, RETRY, and RETRY_INTERVAL. Send real-time call state notifications Ringing OK Bye to external servers.<\/p>\n","protected":false},"author":1,"featured_media":1530,"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":[1],"tags":[10478,10538,10522,10529,10513,10539,10546,10510,10541,10544,10527,10514,10516,10547,10521,10531,10532,10518,10530,10535,10507,10528,10540,10519,10525,10534,10524,10517,10545,10523,10488,10537,10536,10526,10520,10533,10542,10515,10543,10508,10509,10511,10512],"class_list":["post-1549","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vos3000-softswitch","tag-vos3000-ivr-audio-service-parameter","tag-vos3000-ivr-call-event-monitoring","tag-vos3000-ivr-call-id-serial-number","tag-vos3000-ivr-call-monitoring","tag-vos3000-ivr-call-state-bye","tag-vos3000-ivr-call-state-configuration","tag-vos3000-ivr-call-state-deployment","tag-vos3000-ivr-call-state-external-server","tag-vos3000-ivr-call-state-faq","tag-vos3000-ivr-call-state-integration","tag-vos3000-ivr-call-state-manual","tag-vos3000-ivr-call-state-notification","tag-vos3000-ivr-call-state-ok","tag-vos3000-ivr-call-state-parameters","tag-vos3000-ivr-call-state-payload-format","tag-vos3000-ivr-call-state-retry-6","tag-vos3000-ivr-call-state-retry-interval-3","tag-vos3000-ivr-call-state-ringing","tag-vos3000-ivr-call-state-setup-guide","tag-vos3000-ivr-call-state-troubleshooting","tag-vos3000-ivr-call-state-udp","tag-vos3000-ivr-call-state-v2-1-9-07","tag-vos3000-ivr-call-state-voip","tag-vos3000-ivr-callback-state-reporting","tag-vos3000-ivr-caller-number-callee-number","tag-vos3000-ivr-external-integration","tag-vos3000-ivr-forward-number-menu-id","tag-vos3000-ivr-real-time-call-state","tag-vos3000-ivr-real-time-monitoring","tag-vos3000-ivr-second-line-call-state","tag-vos3000-ivr-section-4-3-5-3","tag-vos3000-ivr-softswitch-call-state","tag-vos3000-ivr-udp-best-practices","tag-vos3000-ivr-udp-configuration","tag-vos3000-ivr-udp-datagram","tag-vos3000-ivr-udp-default-port-8000","tag-vos3000-ivr-udp-payload","tag-vos3000-ivr-udp-reporting","tag-vos3000-ivr-udp-reporting-guide","tag-vos3000-ivr_call_report_ip","tag-vos3000-ivr_call_report_port","tag-vos3000-ivr_call_report_retry","tag-vos3000-ivr_call_report_retry_interval"],"acf":[],"jetpack_featured_media_url":"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode.png","blog_post_layout_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-150x150.png",150,150,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode.png",1536,1024,false]},"categories_names":{"1":{"name":"VOS3000 Softswitch","link":"https:\/\/www.vos3000.com\/blog\/category\/vos3000-softswitch\/"}},"tags_names":{"10478":{"name":"VOS3000 IVR audio service parameter","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-audio-service-parameter\/"},"10538":{"name":"VOS3000 IVR call event monitoring","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-event-monitoring\/"},"10522":{"name":"VOS3000 IVR call ID serial number","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-id-serial-number\/"},"10529":{"name":"VOS3000 IVR call monitoring","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-monitoring\/"},"10513":{"name":"VOS3000 IVR call state Bye","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-bye\/"},"10539":{"name":"VOS3000 IVR call state configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-configuration\/"},"10546":{"name":"VOS3000 IVR call state deployment","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-deployment\/"},"10510":{"name":"VOS3000 IVR call state external server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-external-server\/"},"10541":{"name":"VOS3000 IVR call state FAQ","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-faq\/"},"10544":{"name":"VOS3000 IVR call state integration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-integration\/"},"10527":{"name":"VOS3000 IVR call state manual","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-manual\/"},"10514":{"name":"VOS3000 IVR call state notification","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-notification\/"},"10516":{"name":"VOS3000 IVR call state OK","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-ok\/"},"10547":{"name":"VOS3000 IVR call state parameters","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-parameters\/"},"10521":{"name":"VOS3000 IVR call state payload format","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-payload-format\/"},"10531":{"name":"VOS3000 IVR call state retry 6","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-retry-6\/"},"10532":{"name":"VOS3000 IVR call state retry interval 3","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-retry-interval-3\/"},"10518":{"name":"VOS3000 IVR call state Ringing","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-ringing\/"},"10530":{"name":"VOS3000 IVR call state setup guide","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-setup-guide\/"},"10535":{"name":"VOS3000 IVR call state troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-troubleshooting\/"},"10507":{"name":"VOS3000 IVR call state UDP","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-udp\/"},"10528":{"name":"VOS3000 IVR call state V2.1.9.07","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-v2-1-9-07\/"},"10540":{"name":"VOS3000 IVR call state VoIP","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-call-state-voip\/"},"10519":{"name":"VOS3000 IVR callback state reporting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-callback-state-reporting\/"},"10525":{"name":"VOS3000 IVR caller number callee number","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-caller-number-callee-number\/"},"10534":{"name":"VOS3000 IVR external integration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-external-integration\/"},"10524":{"name":"VOS3000 IVR forward number menu ID","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-forward-number-menu-id\/"},"10517":{"name":"VOS3000 IVR real-time call state","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-real-time-call-state\/"},"10545":{"name":"VOS3000 IVR real-time monitoring","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-real-time-monitoring\/"},"10523":{"name":"VOS3000 IVR second line call state","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-second-line-call-state\/"},"10488":{"name":"VOS3000 IVR section 4.3.5.3","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-section-4-3-5-3\/"},"10537":{"name":"VOS3000 IVR softswitch call state","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-softswitch-call-state\/"},"10536":{"name":"VOS3000 IVR UDP best practices","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-best-practices\/"},"10526":{"name":"VOS3000 IVR UDP configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-configuration\/"},"10520":{"name":"VOS3000 IVR UDP datagram","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-datagram\/"},"10533":{"name":"VOS3000 IVR UDP default port 8000","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-default-port-8000\/"},"10542":{"name":"VOS3000 IVR UDP payload","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-payload\/"},"10515":{"name":"VOS3000 IVR UDP reporting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-reporting\/"},"10543":{"name":"VOS3000 IVR UDP reporting guide","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr-udp-reporting-guide\/"},"10508":{"name":"VOS3000 IVR_CALL_REPORT_IP","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr_call_report_ip\/"},"10509":{"name":"VOS3000 IVR_CALL_REPORT_PORT","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr_call_report_port\/"},"10511":{"name":"VOS3000 IVR_CALL_REPORT_RETRY","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr_call_report_retry\/"},"10512":{"name":"VOS3000 IVR_CALL_REPORT_RETRY_INTERVAL","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ivr_call_report_retry_interval\/"}},"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-150x150.png",150,150,true],"cvmm-medium":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-300x300.png",300,300,true],"cvmm-medium-plus":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-305x207.png",305,207,true],"cvmm-portrait":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-400x600.png",400,600,true],"cvmm-medium-square":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-600x600.png",600,600,true],"cvmm-large":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-1024x1024.png",1024,1024,true],"cvmm-small":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode-130x95.png",130,95,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-IVR-Callback-Timing-VOS3000-IVR-Call-State-UDP-Reporting-VOS3000-IVR-Codec-Priority-VOS3000-IVR-Voicemail-Navigation-VOS3000-IVR-Custom-Ringback-Tone-VOS3000-IVR-DTMF-Parse-Mode.png",1536,1024,false]},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1549","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=1549"}],"version-history":[{"count":1,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1549\/revisions"}],"predecessor-version":[{"id":1558,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1549\/revisions\/1558"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media\/1530"}],"wp:attachment":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media?parent=1549"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/categories?post=1549"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/tags?post=1549"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}