{"id":1390,"date":"2026-04-26T07:09:06","date_gmt":"2026-04-26T07:09:06","guid":{"rendered":"https:\/\/www.vos3000.com\/blog\/?p=1390"},"modified":"2026-04-26T07:09:19","modified_gmt":"2026-04-26T07:09:19","slug":"vos3000-cdr-end-direction","status":"publish","type":"post","link":"https:\/\/www.vos3000.com\/blog\/vos3000-cdr-end-direction\/","title":{"rendered":"VOS3000 CDR End Direction Critical Call Termination Party Detection"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\" id=\"vos-3000-cdr-end-direction-critical-call-termination-party-detection\">VOS3000 CDR End Direction Critical Call Termination Party Detection<\/h1>\n\n\n\n<p>\ud83d\udcde Knowing <strong>who hung up the call<\/strong> is not just a curiosity \u2014 it is a critical data point that affects billing disputes, quality analysis, fraud detection, and network performance optimization. The <strong>VOS3000 CDR end direction<\/strong> field records exactly which party initiated the call termination: the caller (0), the callee (1), or the VOS3000 server itself (2). This three-code system, documented in the official VOS3000 manual \u00a74.4 (page 242), provides the definitive answer to &#8220;who ended this call?&#8221; \u2014 and that answer has far-reaching implications for your VoIP business. \ud83d\udd0d<\/p>\n\n\n\n<p>\u2699\ufe0f Consider the billing dispute scenario: A customer claims they were overcharged because &#8220;the call dropped after only a few seconds.&#8221; Without the endDirection field, you have no way to prove whether the customer hung up normally, the far end hung up, or the server terminated the call due to a timeout or balance exhaustion. With endDirection = 2 (server), you can explain that the server terminated the call because the prepaid balance was depleted \u2014 resolving the dispute with evidence. Without it, you are relying on guesswork. \ud83d\udcca<\/p>\n\n\n\n<p>\ud83c\udfaf This guide provides a comprehensive reference for the VOS3000 CDR end direction field, covering all three codes (0, 1, 2), their meanings, how they interact with other CDR fields like endReason and billingMode, and practical analysis techniques for using end direction data in billing, quality monitoring, and security applications. All definitions are sourced from the official VOS3000 2.1.8.0\/2.1.9.07 English manual \u00a74.4 (page 242). \ud83d\udcd8<\/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-cdr-end-direction-critical-call-termination-party-detection\">VOS3000 CDR End Direction Critical Call Termination Party Detection<\/a><ul><li><a href=\"#\ud83d\udd10-what-is-vos-3000-cdr-end-direction\">\ud83d\udd10 What Is VOS3000 CDR End Direction?<\/a><ul><li><a href=\"#\ud83d\udccb-official-manual-definition\">\ud83d\udccb Official Manual Definition<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-end-direction-code-0-caller-hangup\">\ud83d\udcca End Direction Code 0: Caller Hangup<\/a><ul><li><a href=\"#\ud83d\udccb-analysis-implications-of-caller-hangup\">\ud83d\udccb Analysis Implications of Caller Hangup<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-end-direction-code-1-callee-hangup\">\ud83d\udcca End Direction Code 1: Callee Hangup<\/a><ul><li><a href=\"#\ud83d\udccb-analysis-implications-of-callee-hangup\">\ud83d\udccb Analysis Implications of Callee Hangup<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-end-direction-code-2-server-hangup\">\ud83d\udcca End Direction Code 2: Server Hangup<\/a><ul><li><a href=\"#\ud83d\udccb-when-does-server-hangup-occur\">\ud83d\udccb When Does Server Hangup Occur?<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udccb-end-direction-and-billing-dispute-resolution\">\ud83d\udccb End Direction and Billing Dispute Resolution<\/a><\/li><li><a href=\"#\ud83d\udcca-end-direction-and-call-quality-analysis\">\ud83d\udcca End Direction and Call Quality Analysis<\/a><ul><li><a href=\"#\ud83d\udccb-end-direction-distribution-analysis\">\ud83d\udccb End Direction Distribution Analysis<\/a><\/li><li><a href=\"#\ud83d\udccb-end-direction-by-gateway-analysis\">\ud83d\udccb End Direction by Gateway Analysis<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udccb-end-direction-and-session-timer-interaction\">\ud83d\udccb End Direction and Session Timer Interaction<\/a><\/li><li><a href=\"#\ud83d\udee1\ufe0f-common-end-direction-analysis-problems-and-solutions\">\ud83d\udee1\ufe0f Common End Direction Analysis Problems and Solutions<\/a><ul><li><a href=\"#\u274c-problem-1-excessive-server-hangups-end-direction-2\">\u274c Problem 1: Excessive Server Hangups (endDirection = 2)<\/a><\/li><li><a href=\"#\u274c-problem-2-billing-disputes-where-customer-claims-call-dropped\">\u274c Problem 2: Billing Disputes Where Customer Claims Call Dropped<\/a><\/li><li><a href=\"#\u274c-problem-3-short-callee-hangups-indicating-traffic-quality-issues\">\u274c Problem 3: Short Callee Hangups Indicating Traffic Quality Issues<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udca1-end-direction-best-practices\">\ud83d\udca1 End Direction Best Practices<\/a><\/li><li><a href=\"#\u2753-frequently-asked-questions\">\u2753 Frequently Asked Questions<\/a><ul><li><a href=\"#\u2753-what-does-vos-3000-cdr-end-direction-2-mean\">\u2753 What does VOS3000 CDR end direction 2 mean?<\/a><\/li><li><a href=\"#\u2753-how-do-i-determine-why-a-server-hangup-occurred\">\u2753 How do I determine why a server hangup occurred?<\/a><\/li><li><a href=\"#\u2753-does-end-direction-affect-billing-calculations\">\u2753 Does endDirection affect billing calculations?<\/a><\/li><li><a href=\"#\u2753-can-the-end-direction-value-be-incorrect\">\u2753 Can the endDirection value be incorrect?<\/a><\/li><li><a href=\"#\u2753-how-is-end-direction-different-from-end-reason-in-vos-3000-cdr\">\u2753 How is endDirection different from endReason in VOS3000 CDR?<\/a><\/li><li><a href=\"#\u2753-should-i-always-record-cd-rs-for-server-initiated-hangups\">\u2753 Should I always record CDRs for server-initiated hangups?<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcde-need-expert-help-with-vos-3000-cdr-end-direction\">\ud83d\udcde Need Expert Help with VOS3000 CDR End Direction?<\/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=\"\ud83d\udd10-what-is-vos-3000-cdr-end-direction\">\ud83d\udd10 What Is VOS3000 CDR End Direction?<\/h2>\n\n\n\n<p>\ud83d\udccb The <strong>VOS3000 CDR end direction<\/strong> (also called &#8220;hangup side&#8221; in the manual) is Field 7 in the pipe-delimited CDR format. It records which party initiated the termination of the call by sending the SIP BYE message, H.323 EndSessionCommand, or equivalent call teardown signal. This is not about which party <em>originated<\/em> the call \u2014 it is specifically about which party <em>ended<\/em> it.<\/p>\n\n\n\n<p>\ud83d\udccd <strong>CDR field location:<\/strong> Position 7 in the pipe-delimited CDR format, between the endReason (Field 6) and callerGatewayId (Field 8) fields, as documented in the VOS3000 manual \u00a74.4.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-official-manual-definition\">\ud83d\udccb Official Manual Definition<\/h3>\n\n\n\n<p>\ud83d\udcd6 The VOS3000 2.1.8.0\/2.1.9.07 English manual \u00a74.4 (page 242) defines the endDirection field as:<\/p>\n\n\n\n<p><strong>&#8220;endDirection \u2014 Hangup side\uff080-caller\uff0c1-callee\uff0c2-server\uff09&#8221;<\/strong><\/p>\n\n\n\n<p>\ud83d\udcdd This is the complete and official definition. The three possible values and their meanings are:<\/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\">Code<\/th><th class=\"has-text-align-left\" data-align=\"left\">Party<\/th><th class=\"has-text-align-left\" data-align=\"left\">Meaning<\/th><th class=\"has-text-align-left\" data-align=\"left\">SIP Signal<\/th><\/tr><tr><td>0<\/td><td>\ud83d\udd14 Caller<\/td><td>The calling party initiated the hangup<\/td><td>BYE from caller side<\/td><\/tr><tr><td>1<\/td><td>\ud83d\udcde Callee<\/td><td>The called party initiated the hangup<\/td><td>BYE from callee side<\/td><\/tr><tr><td>2<\/td><td>\ud83d\udda5\ufe0f Server<\/td><td>The VOS3000 server initiated the hangup<\/td><td>BYE generated by VOS3000<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-end-direction-code-0-caller-hangup\">\ud83d\udcca End Direction Code 0: Caller Hangup<\/h2>\n\n\n\n<p>\ud83d\udd14 When the <strong>VOS3000 CDR end direction<\/strong> is <strong>0<\/strong>, it means the <strong>calling party<\/strong> initiated the call termination. In SIP terms, the BYE message originated from the caller&#8217;s side of the call leg. This is the most common end direction for normal completed calls \u2014 the person who made the call decides they are done talking and hangs up.<\/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\">Attribute<\/th><th class=\"has-text-align-left\" data-align=\"left\">Detail<\/th><\/tr><tr><td>\ud83d\udccc Code<\/td><td>0<\/td><\/tr><tr><td>\ud83d\udcdd Party<\/td><td>Caller (calling party)<\/td><\/tr><tr><td>\ud83d\udd04 Typical Scenario<\/td><td>Normal call completion \u2014 caller hangs up after conversation<\/td><\/tr><tr><td>\ud83d\udcca Expected Proportion<\/td><td>50\u201380% of connected calls in most deployments<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-analysis-implications-of-caller-hangup\">\ud83d\udccb Analysis Implications of Caller Hangup<\/h3>\n\n\n\n<p>\ud83d\udca1 <strong>What caller hangup tells you:<\/strong> When endDirection = 0, the call followed a normal pattern \u2014 the calling party placed the call, the conversation took place, and the caller ended it when finished. This is the expected behavior for the majority of outbound calls. However, if you notice an unusually high percentage of caller hangups with very short hold times (under 3 seconds), it may indicate that callers are reaching the wrong number or encountering audio problems and hanging up immediately.<\/p>\n\n\n\n<p>\ud83d\udcca <strong>Quality correlation:<\/strong> Pair endDirection = 0 with short holdTime values to identify potential audio quality issues. If callers consistently hang up within the first few seconds, there may be a one-way audio problem or incorrect number routing. Cross-reference with the <a href=\"https:\/\/multahost.com\/blog\/vos3000-call-termination-reasons\/\" target=\"_blank\" rel=\"noopener\">endReason codes<\/a> to get the full picture \u2014 a normal SIP 200 OK with endDirection = 0 and holdTime under 2000ms suggests a quick hangup after audio issues rather than a failed call.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-end-direction-code-1-callee-hangup\">\ud83d\udcca End Direction Code 1: Callee Hangup<\/h2>\n\n\n\n<p>\ud83d\udcde When the <strong>VOS3000 CDR end direction<\/strong> is <strong>1<\/strong>, it means the <strong>called party<\/strong> initiated the call termination. The BYE message came from the callee&#8217;s side. This typically happens when the person who received the call decides to end the conversation.<\/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\">Attribute<\/th><th class=\"has-text-align-left\" data-align=\"left\">Detail<\/th><\/tr><tr><td>\ud83d\udccc Code<\/td><td>1<\/td><\/tr><tr><td>\ud83d\udcdd Party<\/td><td>Callee (called party)<\/td><\/tr><tr><td>\ud83d\udd04 Typical Scenario<\/td><td>Called party hangs up after conversation ends<\/td><\/tr><tr><td>\ud83d\udcca Expected Proportion<\/td><td>15\u201340% of connected calls in most deployments<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-analysis-implications-of-callee-hangup\">\ud83d\udccb Analysis Implications of Callee Hangup<\/h3>\n\n\n\n<p>\ud83d\udca1 <strong>What callee hangup tells you:<\/strong> An endDirection of 1 is perfectly normal for many call scenarios \u2014 the called party simply ends the conversation. However, a high proportion of callee hangups, especially combined with short hold times, may indicate that the called parties are not expecting the call (possible spam or unsolicited traffic), or that the audio from the caller side is not reaching the callee properly.<\/p>\n\n\n\n<p>\ud83d\udd0d <strong>Wholesale traffic quality indicator:<\/strong> In wholesale VoIP operations, monitoring the ratio of callee hangups to caller hangups on specific routes helps assess traffic quality. A route with a high percentage of callee hangups and short durations may indicate that the terminating carrier&#8217;s end users are rejecting or quickly ending calls \u2014 a sign of potential CLI (Caller Line Identification) issues or unwanted traffic. This data supports decisions about <a href=\"https:\/\/multahost.com\/blog\/vos3000-call-routing\/\" target=\"_blank\" rel=\"noopener\">route optimization<\/a> and carrier selection.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-end-direction-code-2-server-hangup\">\ud83d\udcca End Direction Code 2: Server Hangup<\/h2>\n\n\n\n<p>\ud83d\udda5\ufe0f When the <strong>VOS3000 CDR end direction<\/strong> is <strong>2<\/strong>, it means the <strong>VOS3000 server itself<\/strong> initiated the call termination. This is the most operationally significant of the three codes, because it indicates the softswitch actively intervened to end the call \u2014 and the reasons for that intervention directly impact billing, customer experience, and system health. \ud83d\udea8<\/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\">Attribute<\/th><th class=\"has-text-align-left\" data-align=\"left\">Detail<\/th><\/tr><tr><td>\ud83d\udccc Code<\/td><td>2<\/td><\/tr><tr><td>\ud83d\udcdd Party<\/td><td>Server (VOS3000 softswitch)<\/td><\/tr><tr><td>\ud83d\udd04 Typical Scenario<\/td><td>Server-initiated call termination for policy, timeout, or balance reasons<\/td><\/tr><tr><td>\ud83d\udcca Expected Proportion<\/td><td>5\u201320% of connected calls, depending on prepaid ratio<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-when-does-server-hangup-occur\">\ud83d\udccb When Does Server Hangup Occur?<\/h3>\n\n\n\n<p>\ud83d\udda5\ufe0f There are several important scenarios where VOS3000 terminates a call from the server side, each with different operational implications:<\/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\">Scenario<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><th class=\"has-text-align-left\" data-align=\"left\">End Reason<\/th><th class=\"has-text-align-left\" data-align=\"left\">Impact<\/th><\/tr><tr><td>\ud83d\udcb0 Balance exhaustion<\/td><td>Prepaid account runs out of funds during active call<\/td><td>Various (may show session timeout code)<\/td><td>Customer may dispute charges<\/td><\/tr><tr><td>\u23f1\ufe0f Session timer expiry<\/td><td>SIP session timer expires without successful re-INVITE refresh<\/td><td>200 (normal) or 408<\/td><td>Call duration capped by timer<\/td><\/tr><tr><td>\ud83d\udd27 Administrative disconnect<\/td><td>Operator manually disconnects the call via VOS3000 client<\/td><td>200<\/td><td>Immediate call termination<\/td><\/tr><tr><td>\ud83d\udce1 No-media timeout<\/td><td>RTP media stream stops flowing for the configured timeout period<\/td><td>Various<\/td><td>Detects dead calls consuming resources<\/td><\/tr><tr><td>\ud83d\udee1\ufe0f Maximum duration limit<\/td><td>Call exceeds the configured maximum call duration<\/td><td>200<\/td><td>Policy-based call length cap<\/td><\/tr><tr><td>\ud83d\udd04 Gateway failover cleanup<\/td><td>Server terminates call during gateway switching or failover process<\/td><td>503 or other error<\/td><td>Call may be re-routed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>\ud83d\udca1 <strong>Recording server hangups:<\/strong> Whether CDRs for server-initiated hangups are recorded depends on the <strong>SERVER_BILLING_RECORD_SERVER_HANG_UP<\/strong> parameter. When this parameter is On, VOS3000 generates CDR records even when the server initiates the hangup, providing a complete audit trail of all call terminations. When Off, server-initiated hangups may not generate CDR records, creating gaps in your billing and operational data. For detailed configuration guidance, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-server-hangup-cdr\/\" target=\"_blank\" rel=\"noopener\">server hangup CDR recording guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udccb-end-direction-and-billing-dispute-resolution\">\ud83d\udccb End Direction and Billing Dispute Resolution<\/h2>\n\n\n\n<p>\ud83d\udcb0 The VOS3000 CDR end direction field is one of the most powerful tools for resolving billing disputes. When a customer challenges a charge, the endDirection code provides objective evidence of what happened during the call:<\/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\">Dispute Claim<\/th><th class=\"has-text-align-left\" data-align=\"left\">End Direction<\/th><th class=\"has-text-align-left\" data-align=\"left\">Resolution<\/th><\/tr><tr><td>&#8220;The call dropped after a few seconds&#8221;<\/td><td>0 (caller hangup)<\/td><td>\u2705 The caller (customer) hung up normally \u2014 not a dropped call<\/td><\/tr><tr><td>&#8220;I was disconnected unexpectedly&#8221;<\/td><td>2 (server hangup)<\/td><td>\u26a0\ufe0f Server terminated \u2014 investigate balance exhaustion or session timeout<\/td><\/tr><tr><td>&#8220;The call was much shorter than billed&#8221;<\/td><td>1 (callee hangup)<\/td><td>\u2705 The called party hung up \u2014 duration matches CDR holdTime<\/td><\/tr><tr><td>&#8220;I never made this call&#8221;<\/td><td>0 (caller hangup) with specific callerIp<\/td><td>\ud83d\udd0d Verify the callerIp matches the customer&#8217;s registered device<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>\ud83d\udcca <strong>Evidence chain:<\/strong> For maximum dispute resolution effectiveness, combine the endDirection field with other CDR fields. The endReason code tells you <em>why<\/em> the call ended, the holdTime tells you <em>how long<\/em> the conversation lasted, the callerIp confirms <em>where<\/em> the call originated, and the endDirection tells you <em>who<\/em> terminated the call. Together, these four fields create an unambiguous evidence chain that resolves most billing disputes. For detailed CDR analysis methodology, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-cdr-billing-discrepancy\/\" target=\"_blank\" rel=\"noopener\">CDR billing discrepancy guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-end-direction-and-call-quality-analysis\">\ud83d\udcca End Direction and Call Quality Analysis<\/h2>\n\n\n\n<p>\ud83d\udcc8 Analyzing end direction patterns across your traffic reveals important quality trends that are not visible from ASR and ACD metrics alone. Here are the key analysis patterns to monitor:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-end-direction-distribution-analysis\">\ud83d\udccb End Direction Distribution Analysis<\/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\">Pattern<\/th><th class=\"has-text-align-left\" data-align=\"left\">End Direction Mix<\/th><th class=\"has-text-align-left\" data-align=\"left\">Indicates<\/th><th class=\"has-text-align-left\" data-align=\"left\">Action<\/th><\/tr><tr><td>\u2705 Normal distribution<\/td><td>60% caller, 30% callee, 10% server<\/td><td>Healthy traffic with normal call patterns<\/td><td>No action needed \u2014 continue monitoring<\/td><\/tr><tr><td>\u26a0\ufe0f High server hangup<\/td><td>Server hangup over 25%<\/td><td>Session timeouts, balance exhaustion, or system issues<\/td><td>Check session timer and prepaid balance settings<\/td><\/tr><tr><td>\ud83d\udd0d Short callee hangup<\/td><td>Callee hangup with holdTime under 5s<\/td><td>Called parties rejecting calls \u2014 possible CLI or spam issue<\/td><td>Review caller ID presentation and traffic source<\/td><\/tr><tr><td>\ud83d\udea8 Short caller hangup<\/td><td>Caller hangup with holdTime under 3s<\/td><td>One-way audio or wrong number \u2014 callers hanging up immediately<\/td><td>Check <a href=\"https:\/\/multahost.com\/blog\/vos3000-dialer-call-test-no-voice-one-way-audio-vos3000-pin-call-no-audio\/\" target=\"_blank\" rel=\"noopener\">audio quality<\/a> on affected routes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-end-direction-by-gateway-analysis\">\ud83d\udccb End Direction by Gateway Analysis<\/h3>\n\n\n\n<p>\ud83d\udce1 Segmenting end direction data by gateway (using the callerGatewayId and calleeGatewayId fields) reveals gateway-specific quality issues. A gateway that shows an unusually high percentage of server-initiated hangups (endDirection = 2) may have connectivity problems causing session timer expirations. A gateway with a high proportion of short-duration callee hangups may be routing traffic to low-quality destinations where end users reject the calls. This gateway-level analysis supports data-driven routing decisions and helps you identify which carriers deliver the best call completion quality. For gateway performance monitoring techniques, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-gateway-analysis-reports\/\" target=\"_blank\" rel=\"noopener\">gateway analysis reports guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udccb-end-direction-and-session-timer-interaction\">\ud83d\udccb End Direction and Session Timer Interaction<\/h2>\n\n\n\n<p>\u23f1\ufe0f One of the most important operational interactions is between the VOS3000 CDR end direction and the SIP session timer system. When session timers are enabled, VOS3000 periodically sends re-INVITE messages to refresh the session. If the re-INVITE fails (the endpoint does not respond), VOS3000 terminates the call \u2014 and the endDirection will be 2 (server). This is a common scenario for calls that &#8220;mysteriously drop&#8221; after a fixed interval.<\/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\">Session Timer Scenario<\/th><th class=\"has-text-align-left\" data-align=\"left\">End Direction<\/th><th class=\"has-text-align-left\" data-align=\"left\">End Reason<\/th><th class=\"has-text-align-left\" data-align=\"left\">Resolution<\/th><\/tr><tr><td>\u2705 Re-INVITE succeeds<\/td><td>0 or 1 (normal)<\/td><td>200 OK<\/td><td>Call continues until party hangs up<\/td><\/tr><tr><td>\u26a0\ufe0f Re-INVITE fails (NAT issue)<\/td><td>2 (server)<\/td><td>408 or timeout<\/td><td>Check NAT keepalive settings<\/td><\/tr><tr><td>\ud83d\udd27 No session timer support<\/td><td>2 (server)<\/td><td>Session expiry<\/td><td>Configure <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-no-timer-call-duration\/\" target=\"_blank\" rel=\"noopener\">SS_SIP_NO_TIMER_REINVITE_INTERVAL<\/a><\/td><\/tr><tr><td>\ud83d\udcb0 Prepaid balance depleted<\/td><td>2 (server)<\/td><td>200 OK (normal clear)<\/td><td>Expected behavior for prepaid accounts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>\ud83d\udca1 <strong>Investigating mysterious drops:<\/strong> If customers report calls dropping at consistent intervals (e.g., always at 30 minutes or 2 hours), check the <a href=\"https:\/\/multahost.com\/blog\/vos3000-session-timer\/\" target=\"_blank\" rel=\"noopener\">SIP session timer<\/a> configuration. The session timer interval, combined with the SS_SIP_SESSION_UPDATE_SEGMENT parameter, determines when VOS3000 sends re-INVITE refreshes. If the endpoint does not support session timers and SS_SIP_NO_TIMER_REINVITE_INTERVAL is not configured, VOS3000 may terminate the call after the session timer expires \u2014 resulting in endDirection = 2.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udee1\ufe0f-common-end-direction-analysis-problems-and-solutions\">\ud83d\udee1\ufe0f Common End Direction Analysis Problems and Solutions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-1-excessive-server-hangups-end-direction-2\">\u274c Problem 1: Excessive Server Hangups (endDirection = 2)<\/h3>\n\n\n\n<p>\ud83d\udd0d <strong>Symptom:<\/strong> A high percentage of CDRs show endDirection = 2, indicating the server is terminating many calls.<\/p>\n\n\n\n<p>\ud83d\udca1 <strong>Cause:<\/strong> Multiple factors can cause excessive server hangups: session timer misconfiguration, NAT traversal failures causing re-INVITE timeouts, prepaid accounts frequently running out of balance, or RTP timeout detecting dead media streams.<\/p>\n\n\n\n<p>\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u23f1\ufe0f Review SIP session timer settings \u2014 ensure SS_SIP_NO_TIMER_REINVITE_INTERVAL provides a safety net for non-timer endpoints<\/li>\n\n\n\n<li>\ud83c\udf10 Check NAT keepalive settings \u2014 failed re-INVITEs through NAT firewalls are a leading cause of server-initiated hangups<\/li>\n\n\n\n<li>\ud83d\udcb0 Verify prepaid balance thresholds \u2014 the <a href=\"https:\/\/multahost.com\/blog\/vos3000-midcall-balance-warning\/\" target=\"_blank\" rel=\"noopener\">mid-call balance warning<\/a> should alert users before their balance is depleted<\/li>\n\n\n\n<li>\ud83d\udce1 Monitor RTP timeout settings that may be too aggressive for legitimate silent periods in calls<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-2-billing-disputes-where-customer-claims-call-dropped\">\u274c Problem 2: Billing Disputes Where Customer Claims Call Dropped<\/h3>\n\n\n\n<p>\ud83d\udd0d <strong>Symptom:<\/strong> Customer disputes a charge, claiming the call dropped unexpectedly, but the CDR shows endDirection = 0 (caller hangup) with a substantial holdTime.<\/p>\n\n\n\n<p>\ud83d\udca1 <strong>Cause:<\/strong> The customer may have accidentally ended the call, or their SIP device may have sent a BYE due to a local issue (not a server-side drop). The CDR end direction provides the objective evidence.<\/p>\n\n\n\n<p>\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udccb Present the endDirection = 0 record to the customer as evidence that their device initiated the hangup<\/li>\n\n\n\n<li>\ud83d\udd0d Cross-reference with callerIp to confirm the call originated from the customer&#8217;s registered device<\/li>\n\n\n\n<li>\ud83d\udcca Compare the holdTime with the customer&#8217;s claim about call duration<\/li>\n\n\n\n<li>\ud83d\udcde For endDirection = 2 cases, explain the server termination reason (balance exhaustion, session timeout, etc.)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-3-short-callee-hangups-indicating-traffic-quality-issues\">\u274c Problem 3: Short Callee Hangups Indicating Traffic Quality Issues<\/h3>\n\n\n\n<p>\ud83d\udd0d <strong>Symptom:<\/strong> High volume of endDirection = 1 records with very short holdTime values on a specific route or gateway.<\/p>\n\n\n\n<p>\ud83d\udca1 <strong>Cause:<\/strong> The called parties are answering and immediately hanging up. This can indicate wrong-number calls, CLI (Caller Line Identification) not being presented correctly, or the traffic being perceived as spam by the called parties.<\/p>\n\n\n\n<p>\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udcde Verify that the caller ID being presented to the called party is correct and recognizable<\/li>\n\n\n\n<li>\ud83d\udd27 Check the <a href=\"https:\/\/multahost.com\/blog\/vos3000-caller-id-management-complete\/\" target=\"_blank\" rel=\"noopener\">caller ID management<\/a> configuration for the affected mapping gateway<\/li>\n\n\n\n<li>\ud83d\udcca Analyze the geographic distribution of short callee hangups to identify specific regions or carriers with quality issues<\/li>\n\n\n\n<li>\ud83d\udd04 Consider routing adjustments to avoid low-quality termination carriers<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udca1-end-direction-best-practices\">\ud83d\udca1 End Direction Best Practices<\/h2>\n\n\n\n<p>\ud83c\udfaf Follow these best practices to maximize the value of VOS3000 CDR end direction data in your operations:<\/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\">Best Practice<\/th><th class=\"has-text-align-left\" data-align=\"left\">Recommendation<\/th><th class=\"has-text-align-left\" data-align=\"left\">Reason<\/th><\/tr><tr><td>\ud83d\udccb Always enable server hangup CDR recording<\/td><td>Set SERVER_BILLING_RECORD_SERVER_HANG_UP = On<\/td><td>\ud83d\udd0d Complete audit trail of all call terminations<\/td><\/tr><tr><td>\ud83d\udcca Monitor end direction distribution weekly<\/td><td>Track % of codes 0, 1, 2 across all traffic<\/td><td>\ud83d\udcc8 Early detection of quality and configuration issues<\/td><\/tr><tr><td>\ud83d\udcb0 Use end direction in billing dispute workflows<\/td><td>Include endDirection in dispute resolution SOP<\/td><td>\ud83d\udee1\ufe0f Objective evidence resolves disputes faster<\/td><\/tr><tr><td>\ud83d\udce1 Segment by gateway for quality analysis<\/td><td>Analyze end direction per routing gateway<\/td><td>\ud83d\udd27 Data-driven carrier selection and route optimization<\/td><\/tr><tr><td>\u23f1\ufe0f Correlate endDirection = 2 with session timer<\/td><td>Match server hangups to timer expiry patterns<\/td><td>\ud83d\udd27 Identifies NAT and timer configuration problems<\/td><\/tr><\/tbody><\/table><\/figure>\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-does-vos-3000-cdr-end-direction-2-mean\">\u2753 What does VOS3000 CDR end direction 2 mean?<\/h3>\n\n\n\n<p>\ud83d\udda5\ufe0f A VOS3000 CDR end direction of <strong>2<\/strong> means the <strong>VOS3000 server<\/strong> initiated the call termination. This occurs when the softswitch actively ends the call, rather than either endpoint (caller or callee) hanging up. Common reasons include: prepaid account balance exhaustion (the server terminates the call when funds run out), SIP session timer expiry (the server did not receive a successful re-INVITE refresh), administrative disconnect by the operator, maximum call duration limit reached, or RTP media timeout detecting a dead media stream. The endDirection = 2 code is documented in the VOS3000 manual \u00a74.4 (page 242) as &#8220;server&#8221; hangup side.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-how-do-i-determine-why-a-server-hangup-occurred\">\u2753 How do I determine why a server hangup occurred?<\/h3>\n\n\n\n<p>\ud83d\udd0d To determine the specific reason for a server-initiated hangup (endDirection = 2), cross-reference the endDirection field with the <strong>endReason<\/strong> field (Field 6) in the same CDR record. The endReason provides the SIP response code or cause code that explains why the call was terminated. For example, endDirection = 2 with endReason = 200 typically indicates a normal server-initiated clear (such as balance exhaustion or maximum duration). EndDirection = 2 with endReason = 408 indicates a timeout. Combining these two fields gives you the complete picture of who ended the call and why.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-does-end-direction-affect-billing-calculations\">\u2753 Does endDirection affect billing calculations?<\/h3>\n\n\n\n<p>\ud83d\udcb0 The endDirection field itself does not directly change billing calculations \u2014 the holdTime field determines the billable duration regardless of who hung up. However, endDirection has indirect billing implications. When endDirection = 2 (server hangup), the call may have been terminated before the natural conversation end, which can lead to customer disputes. When analyzing <a href=\"https:\/\/multahost.com\/blog\/vos3000-billing-system\/\" target=\"_blank\" rel=\"noopener\">billing data<\/a>, filtering by endDirection helps you understand the nature of your call completions and identify patterns that affect revenue, such as premature server terminations due to balance exhaustion on prepaid accounts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-can-the-end-direction-value-be-incorrect\">\u2753 Can the endDirection value be incorrect?<\/h3>\n\n\n\n<p>\ud83d\udd27 In rare cases, the endDirection may not accurately reflect the true termination party. This can happen when a SIP ALG (Application Layer Gateway) or intermediate proxy modifies the BYE message direction, or when a gateway sends a BYE on behalf of an endpoint (making it appear as a callee hangup when the caller actually hung up). If you suspect endDirection inaccuracy, enable SIP debug tracing to capture the actual BYE message flow and verify which IP address sent the termination signal. Check our <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-debug-guide\/\" target=\"_blank\" rel=\"noopener\">SIP debug guide<\/a> for instructions on capturing and analyzing SIP message traces.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-how-is-end-direction-different-from-end-reason-in-vos-3000-cdr\">\u2753 How is endDirection different from endReason in VOS3000 CDR?<\/h3>\n\n\n\n<p>\ud83d\udccb The <strong>endDirection<\/strong> field (Field 7) tells you <em>who<\/em> terminated the call \u2014 caller (0), callee (1), or server (2). The <strong>endReason<\/strong> field (Field 6) tells you <em>why<\/em> the call was terminated \u2014 using SIP response codes (200, 486, 503, etc.) or Q.850 cause codes. These two fields answer different questions and must be analyzed together for the complete picture. For example, endDirection = 0 with endReason = 200 means the caller hung up normally. EndDirection = 2 with endReason = 200 means the server terminated the call normally (likely due to balance exhaustion or duration limit). EndDirection = 1 with endReason = 486 means the callee rejected the call with a busy signal.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-should-i-always-record-cd-rs-for-server-initiated-hangups\">\u2753 Should I always record CDRs for server-initiated hangups?<\/h3>\n\n\n\n<p>\ud83d\udcdd Yes, it is strongly recommended to record CDRs for server-initiated hangups by setting <strong>SERVER_BILLING_RECORD_SERVER_HANG_UP = On<\/strong>. Without these records, your CDR data has gaps \u2014 you lose visibility into calls that the server terminated, which are often the most operationally significant calls (balance exhaustion, session timeouts, administrative actions). These records are essential for billing dispute resolution, quality analysis, and system health monitoring. The <a href=\"https:\/\/multahost.com\/blog\/vos3000-zero-duration-cdr\/\" target=\"_blank\" rel=\"noopener\">zero-duration CDR control<\/a> parameter (SERVER_BILLING_RECORD_ZERO_HOLD_TIME) serves a different purpose \u2014 it controls whether failed call attempts are recorded, while SERVER_BILLING_RECORD_SERVER_HANG_UP specifically addresses server-initiated terminations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcde-need-expert-help-with-vos-3000-cdr-end-direction\">\ud83d\udcde Need Expert Help with VOS3000 CDR End Direction?<\/h2>\n\n\n\n<p>\ud83d\udd27 Understanding and analyzing VOS3000 CDR end direction data is essential for billing accuracy, quality monitoring, and operational intelligence. Whether you are investigating server-initiated hangups, resolving billing disputes, or building a call quality dashboard, expert guidance ensures your analysis is accurate and actionable. \ud83d\udcca<\/p>\n\n\n\n<p>\ud83d\udcac <strong>WhatsApp:<\/strong> <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noopener\">+8801911119966<\/a> \u2014 Get immediate assistance with VOS3000 CDR end direction analysis, billing dispute resolution, and call quality monitoring. Our team specializes in VOS3000 CDR analytics, billing system optimization, and VoIP quality assurance. \ud83d\udd27<\/p>\n\n\n\n<p>\ud83d\udd17 Explore related VOS3000 CDR and call quality guides:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-call-termination-reasons\/\" target=\"_blank\" rel=\"noopener\">VOS3000 Call Termination Reasons<\/a> \u2014 Complete reference for endReason codes that complement endDirection analysis<\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-server-hangup-cdr\/\" target=\"_blank\" rel=\"noopener\">VOS3000 Server Hangup CDR<\/a> \u2014 Configuring SERVER_BILLING_RECORD_SERVER_HANG_UP for complete audit trails<\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-cdr-analysis-billing\/\" target=\"_blank\" rel=\"noopener\">VOS3000 CDR Analysis and Billing<\/a> \u2014 Comprehensive CDR analysis methodology for revenue optimization<\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-zero-duration-cdr\/\" target=\"_blank\" rel=\"noopener\">VOS3000 Zero Duration CDR<\/a> \u2014 Managing zero-duration call records during attacks and normal operations<\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-session-timer\/\" target=\"_blank\" rel=\"noopener\">VOS3000 Session Timer<\/a> \u2014 SIP session timer configuration that affects server-initiated hangups<\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-asr-acd-analysis\/\" target=\"_blank\" rel=\"noopener\">VOS3000 ASR ACD Analysis<\/a> \u2014 Using ASR and ACD metrics alongside end direction for quality assessment<\/li>\n<\/ul>\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-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-1024x683.png\" alt=\"VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-1024x683.png\" alt=\"VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-1024x683.png\" alt=\"VOS3000 CDR File Rotation, VOS3000 Real-Time CDR Forwarding, VOS3000 CDR Query Blackout, VOS3000 CDR Query Date Range, VOS3000 CDR Text File Export, VOS3000 CDR Pipe Format, VOS3000 CDR Billing Mode Codes, VOS3000 CDR End Direction Critical\"><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Master VOS3000 CDR end direction codes 0, 1, and 2. Learn who hung up each call \u2014 caller, callee, or server \u2014 and why this matters for billing disputes, quality analysis, and fraud detection.<\/p>\n","protected":false},"author":1,"featured_media":1373,"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":[8305,8301,8324,8312,8299,8315,8296,8323,8297,8307,8289,8319,8310,8304,8321,8313,8322,8320,8291,8293,8309,8302,6843,8318,2594,8272,6641,8317,8308,1228,8294,8300,8073,7562,8075,8288,8292,8314,8290,6992,8298,8303,8306,8311,3735,8316,8295],"class_list":["post-1390","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vos3000","tag-call-quality-analysis-end-direction","tag-call-termination-detection","tag-call-termination-detection-voip","tag-call-termination-reason","tag-callee-hangup-detection","tag-cdr-analysis-end-direction","tag-cdr-call-termination-direction","tag-cdr-data-analysis","tag-cdr-end-direction-analysis","tag-cdr-end-direction-filter","tag-cdr-enddirection-field","tag-cdr-enddirection-troubleshooting","tag-cdr-hangup-initiator","tag-cdr-termination-party-analysis","tag-cdr-termination-party-reference","tag-end-direction-billing-impact","tag-end-direction-field-codes","tag-end-direction-statistics","tag-enddirection-0-caller","tag-enddirection-2-server","tag-enddirection-field-meaning","tag-hangup-side-cdr","tag-server-hangup-cdr-recording","tag-vos3000-asr-acd-correlation","tag-vos3000-billing-disputes","tag-vos3000-billing-record","tag-vos3000-call-accounting","tag-vos3000-call-completion-analysis","tag-vos3000-call-duration-analysis","tag-vos3000-call-monitoring","tag-vos3000-call-termination-party","tag-vos3000-caller-hangup","tag-vos3000-cdr-end-direction","tag-vos3000-cdr-field-reference","tag-vos3000-cdr-pipe-format","tag-vos3000-end-direction","tag-vos3000-enddirection-1-callee","tag-vos3000-fraud-detection-hangup","tag-vos3000-hangup-side","tag-vos3000-operation-management","tag-vos3000-server-hangup","tag-vos3000-server-initiated-hangup","tag-vos3000-session-timeout-hangup","tag-vos3000-sip-bye-direction","tag-vos3000-softswitch-parameters","tag-vos3000-voip-call-termination","tag-vos3000-who-hung-up"],"acf":[],"jetpack_featured_media_url":"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export.png","blog_post_layout_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-150x150.png",150,150,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export.png",1536,1024,false]},"categories_names":{"2":{"name":"VOS3000`","link":"https:\/\/www.vos3000.com\/blog\/category\/vos3000\/"}},"tags_names":{"8305":{"name":"call quality analysis end direction","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-quality-analysis-end-direction\/"},"8301":{"name":"call termination detection","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-termination-detection\/"},"8324":{"name":"call termination detection VoIP","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-termination-detection-voip\/"},"8312":{"name":"call termination reason","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-termination-reason\/"},"8299":{"name":"callee hangup detection","link":"https:\/\/www.vos3000.com\/blog\/tag\/callee-hangup-detection\/"},"8315":{"name":"CDR analysis end direction","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-analysis-end-direction\/"},"8296":{"name":"CDR call termination direction","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-call-termination-direction\/"},"8323":{"name":"CDR data analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-data-analysis\/"},"8297":{"name":"CDR end direction analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-end-direction-analysis\/"},"8307":{"name":"CDR end direction filter","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-end-direction-filter\/"},"8289":{"name":"CDR endDirection field","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-enddirection-field\/"},"8319":{"name":"CDR endDirection troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-enddirection-troubleshooting\/"},"8310":{"name":"CDR hangup initiator","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-hangup-initiator\/"},"8304":{"name":"CDR termination party analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-termination-party-analysis\/"},"8321":{"name":"CDR termination party reference","link":"https:\/\/www.vos3000.com\/blog\/tag\/cdr-termination-party-reference\/"},"8313":{"name":"end direction billing impact","link":"https:\/\/www.vos3000.com\/blog\/tag\/end-direction-billing-impact\/"},"8322":{"name":"end direction field codes","link":"https:\/\/www.vos3000.com\/blog\/tag\/end-direction-field-codes\/"},"8320":{"name":"end direction statistics","link":"https:\/\/www.vos3000.com\/blog\/tag\/end-direction-statistics\/"},"8291":{"name":"endDirection 0 caller","link":"https:\/\/www.vos3000.com\/blog\/tag\/enddirection-0-caller\/"},"8293":{"name":"endDirection 2 server","link":"https:\/\/www.vos3000.com\/blog\/tag\/enddirection-2-server\/"},"8309":{"name":"endDirection field meaning","link":"https:\/\/www.vos3000.com\/blog\/tag\/enddirection-field-meaning\/"},"8302":{"name":"hangup side CDR","link":"https:\/\/www.vos3000.com\/blog\/tag\/hangup-side-cdr\/"},"6843":{"name":"server hangup CDR recording","link":"https:\/\/www.vos3000.com\/blog\/tag\/server-hangup-cdr-recording\/"},"8318":{"name":"VOS3000 ASR ACD correlation","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-asr-acd-correlation\/"},"2594":{"name":"VOS3000 billing disputes","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-billing-disputes\/"},"8272":{"name":"VOS3000 billing record","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-billing-record\/"},"6641":{"name":"VOS3000 call accounting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-call-accounting\/"},"8317":{"name":"VOS3000 call completion analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-call-completion-analysis\/"},"8308":{"name":"VOS3000 call duration analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-call-duration-analysis\/"},"1228":{"name":"VOS3000 call monitoring","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-call-monitoring\/"},"8294":{"name":"VOS3000 call termination party","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-call-termination-party\/"},"8300":{"name":"VOS3000 caller hangup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-caller-hangup\/"},"8073":{"name":"VOS3000 CDR end direction","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-cdr-end-direction\/"},"7562":{"name":"VOS3000 CDR field reference","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-cdr-field-reference\/"},"8075":{"name":"VOS3000 CDR pipe format","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-cdr-pipe-format\/"},"8288":{"name":"VOS3000 end direction","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-end-direction\/"},"8292":{"name":"VOS3000 endDirection 1 callee","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-enddirection-1-callee\/"},"8314":{"name":"VOS3000 fraud detection hangup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-fraud-detection-hangup\/"},"8290":{"name":"VOS3000 hangup side","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-hangup-side\/"},"6992":{"name":"VOS3000 operation management","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-operation-management\/"},"8298":{"name":"VOS3000 server hangup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-server-hangup\/"},"8303":{"name":"VOS3000 server-initiated hangup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-server-initiated-hangup\/"},"8306":{"name":"VOS3000 session timeout hangup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-session-timeout-hangup\/"},"8311":{"name":"VOS3000 SIP BYE direction","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-sip-bye-direction\/"},"3735":{"name":"VOS3000 softswitch parameters","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-softswitch-parameters\/"},"8316":{"name":"VOS3000 VoIP call termination","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-voip-call-termination\/"},"8295":{"name":"VOS3000 who hung up","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-who-hung-up\/"}},"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-150x150.png",150,150,true],"cvmm-medium":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-300x300.png",300,300,true],"cvmm-medium-plus":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-305x207.png",305,207,true],"cvmm-portrait":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-400x600.png",400,600,true],"cvmm-medium-square":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-600x600.png",600,600,true],"cvmm-large":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-1024x1024.png",1024,1024,true],"cvmm-small":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export-130x95.png",130,95,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-CDR-File-Rotation-VOS3000-Real-Time-CDR-Forwarding-VOS3000-CDR-Query-Blackout-VOS3000-CDR-Query-Date-Range-VOS3000-CDR-Text-File-Export.png",1536,1024,false]},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1390","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=1390"}],"version-history":[{"count":1,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1390\/revisions"}],"predecessor-version":[{"id":1394,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1390\/revisions\/1394"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media\/1373"}],"wp:attachment":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media?parent=1390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/categories?post=1390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/tags?post=1390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}