{"id":928,"date":"2026-04-03T00:43:44","date_gmt":"2026-04-03T00:43:44","guid":{"rendered":"https:\/\/www.vos3000.com\/blog\/?p=928"},"modified":"2026-04-03T00:43:52","modified_gmt":"2026-04-03T00:43:52","slug":"vos3000-debug-trace","status":"publish","type":"post","link":"https:\/\/www.vos3000.com\/blog\/vos3000-debug-trace\/","title":{"rendered":"VOS3000 Debug Trace: Complete Call Signaling Analysis &amp; Troubleshooting Easy Guide"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\" id=\"vos-3000-debug-trace-complete-call-signaling-analysis-troubleshooting-guide\">VOS3000 Debug Trace: Complete Call Signaling Analysis &amp; Troubleshooting Guide<\/h1>\n\n\n\n<p><strong>VOS3000 debug trace is an essential tool for diagnosing and resolving VoIP signaling issues.<\/strong> When calls fail, registrations don&#8217;t complete, or audio problems occur, the debug trace function provides detailed visibility into SIP and H.323 message flows, enabling administrators to pinpoint root causes quickly. This comprehensive guide covers all debug trace features based on official VOS3000 2.1.9.07 documentation.<\/p>\n\n\n\n<p>\ud83d\udcde <strong>Need help with VOS3000 troubleshooting?<\/strong> WhatsApp: <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noreferrer noopener\">+8801911119966<\/a><\/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-debug-trace-complete-call-signaling-analysis-troubleshooting-guide\">VOS3000 Debug Trace: Complete Call Signaling Analysis &amp; Troubleshooting Guide<\/a><ul><li><a href=\"#\ud83d\udd0d-understanding-vos-3000-debug-trace\">\ud83d\udd0d Understanding VOS3000 Debug Trace<\/a><ul><li><a href=\"#\ud83d\udcca-what-debug-trace-captures-vos-3000-debug-trace\">\ud83d\udcca What Debug Trace Captures (VOS3000 Debug Trace)<\/a><\/li><\/ul><\/li><li><a href=\"#\u2699\ufe0f-enabling-debug-trace\">\u2699\ufe0f Enabling Debug Trace<\/a><ul><li><a href=\"#\ud83d\udccd-access-location\">\ud83d\udccd Access Location<\/a><\/li><li><a href=\"#\ud83d\udd27-debug-trace-configuration-options\">\ud83d\udd27 Debug Trace Configuration Options<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcc1-trace-file-management-vos-3000-debug-trace\">\ud83d\udcc1 Trace File Management (VOS3000 Debug Trace)<\/a><ul><li><a href=\"#\u2699\ufe0f-trace-file-parameters\">\u2699\ufe0f Trace File Parameters<\/a><\/li><li><a href=\"#\ud83d\udcc1-two-file-rotation-system\">\ud83d\udcc1 Two-File Rotation System<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-using-trace-for-troubleshooting\">\ud83d\udcca Using Trace for Troubleshooting<\/a><ul><li><a href=\"#\ud83d\udccd-accessing-trace-results-vos-3000-debug-trace\">\ud83d\udccd Accessing Trace Results (VOS3000 Debug Trace)<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udd27-interpreting-trace-output-vos-3000-debug-trace\">\ud83d\udd27 Interpreting Trace Output (VOS3000 Debug Trace)<\/a><ul><li><a href=\"#\ud83d\udcca-sip-message-format\">\ud83d\udcca SIP Message Format<\/a><\/li><li><a href=\"#\ud83d\udcca-h-323-message-format-vos-3000-debug-trace\">\ud83d\udcca H.323 Message Format (VOS3000 Debug Trace)<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udea8-common-debugging-scenarios-vos-3000-debug-trace\">\ud83d\udea8 Common Debugging Scenarios (VOS3000 Debug Trace)<\/a><ul><li><a href=\"#\ud83d\udcca-one-way-audio-diagnosis\">\ud83d\udcca One-Way Audio Diagnosis<\/a><\/li><li><a href=\"#\ud83d\udcca-registration-failure-analysis-vos-3000-debug-trace\">\ud83d\udcca Registration Failure Analysis (VOS3000 Debug Trace)<\/a><\/li><li><a href=\"#\ud83d\udcca-call-drop-investigation-vos-3000-debug-trace\">\ud83d\udcca Call Drop Investigation (VOS3000 Debug Trace)<\/a><\/li><\/ul><\/li><li><a href=\"#\u2699\ufe0f-advanced-trace-configuration\">\u2699\ufe0f Advanced Trace Configuration<\/a><ul><li><a href=\"#\ud83d\udcca-trace-mask-settings\">\ud83d\udcca Trace Mask Settings<\/a><\/li><li><a href=\"#\u2699\ufe0f-performance-impact-vos-3000-debug-trace\">\u2699\ufe0f Performance Impact (VOS3000 Debug Trace)<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-cdr-end-reason-reference-vos-3000-debug-trace\">\ud83d\udcca CDR End Reason Reference (VOS3000 Debug Trace)<\/a><ul><li><a href=\"#\ud83d\udccb-server-side-end-reasons-vos-3000-debug-trace\">\ud83d\udccb Server-Side End Reasons (VOS3000 Debug Trace)<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udd17-related-resources-vos-3000-debug-trace\">\ud83d\udd17 Related Resources (VOS3000 Debug Trace)<\/a><\/li><li><a href=\"#\u2753-frequently-asked-questions\">\u2753 Frequently Asked Questions<\/a><ul><li><a href=\"#where-are-trace-files-stored\">Where are trace files stored?<\/a><\/li><li><a href=\"#how-long-should-i-keep-debug-trace-enabled\">How long should I keep debug trace enabled?<\/a><\/li><li><a href=\"#can-i-export-trace-data-for-analysis\">Can I export trace data for analysis?<\/a><\/li><li><a href=\"#why-cant-i-see-trace-for-old-calls\">Why can&#8217;t I see trace for old calls?<\/a><\/li><li><a href=\"#does-trace-capture-rtp-media-content\">Does trace capture RTP media content?<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcde-get-expert-help-with-vos-3000-debugging\">\ud83d\udcde Get Expert Help with VOS3000 Debugging<\/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\udd0d-understanding-vos-3000-debug-trace\">\ud83d\udd0d Understanding VOS3000 Debug Trace<\/h2>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)<\/p>\n\n\n\n<p>The debug trace function in VOS3000 captures all signaling messages processed by the softswitch, including SIP INVITE, REGISTER, BYE messages and H.323 signaling. This provides a complete record of call flows for troubleshooting and analysis.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-what-debug-trace-captures-vos-3000-debug-trace\">\ud83d\udcca What Debug Trace Captures (VOS3000 Debug Trace)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Protocol<\/th><th class=\"has-text-align-left\" data-align=\"left\">Messages Captured<\/th><th class=\"has-text-align-left\" data-align=\"left\">Use Cases<\/th><\/tr><\/thead><tbody><tr><td><strong>SIP<\/strong><\/td><td>INVITE, REGISTER, BYE, CANCEL, OPTIONS, 1xx\/2xx\/3xx\/4xx\/5xx\/6xx responses<\/td><td>Call setup failures, registration issues, NAT problems<\/td><\/tr><tr><td><strong>H.323<\/strong><\/td><td>Setup, CallProceeding, Alerting, Connect, ReleaseComplete, H.245 messages<\/td><td>Gateway interconnection, codec negotiation<\/td><\/tr><tr><td><strong>RTP<\/strong><\/td><td>Media stream information (limited)<\/td><td>Audio path verification, codec confirmation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\u2699\ufe0f-enabling-debug-trace\">\u2699\ufe0f Enabling Debug Trace<\/h2>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccd-access-location\">\ud83d\udccd Access Location<\/h3>\n\n\n\n<p>Navigate to: <strong>System &gt; Debug trace<\/strong> in the VOS3000 client menu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udd27-debug-trace-configuration-options\">\ud83d\udd27 Debug Trace Configuration Options<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><th class=\"has-text-align-left\" data-align=\"left\">Recommendation<\/th><\/tr><\/thead><tbody><tr><td><strong>On\/Off<\/strong><\/td><td>Enable or disable trace capture<\/td><td>Enable only when troubleshooting<\/td><\/tr><tr><td><strong>Trace Length<\/strong><\/td><td>Duration to capture (in minutes)<\/td><td>Set specific duration or uncheck for continuous<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<pre class=\"wp-block-preformatted\">Step-by-Step Debug Trace Activation:\n====================================\n\n1. Open VOS3000 Client\n\n2. Navigate to:\n   Menu bar &gt; System &gt; Debug trace\n\n3. Configure Settings:\n   \u2611 Check \"On\" to enable trace\n   \u2610 Uncheck \"Trace length\" for continuous capture\n   OR set specific duration (e.g., 30 minutes)\n\n4. Click OK to start capture\n\n5. Reproduce the problem:\n   - Make test call\n   - Attempt registration\n   - Generate the issue you're investigating\n\n6. View Trace Results:\n   - Current Call: Right-click &gt; Trace\n   - CDR: Right-click &gt; Call analysis\n\nImportant Notes:\n================\n- Trace impacts performance slightly when enabled\n- Disable trace when not actively troubleshooting\n- Trace files rotate automatically when size limit reached\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcc1-trace-file-management-vos-3000-debug-trace\">\ud83d\udcc1 Trace File Management (VOS3000 Debug Trace)<\/h2>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205) and Section 4.3.5.2 (Page 237-238)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2699\ufe0f-trace-file-parameters\">\u2699\ufe0f Trace File Parameters<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><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\">Range<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><\/tr><\/thead><tbody><tr><td><strong>SS_TRACE_FILE_LENGTH<\/strong><\/td><td>40960<\/td><td>KB<\/td><td>Size of softswitch debug file (KB)<\/td><\/tr><tr><td><strong>SS_TRACE_CALL_FILE_SIZE<\/strong><\/td><td>16<\/td><td>16-2048 MB<\/td><td>Call signaling trace file size limit (MB)<\/td><\/tr><tr><td><strong>SS_TRACE_REGISTER_FILE_SIZE<\/strong><\/td><td>16<\/td><td>16-2048 MB<\/td><td>Registration signaling trace file size limit (MB)<\/td><\/tr><tr><td><strong>SS_TRACE_MASK<\/strong><\/td><td>ERROR<\/td><td>ERROR\/DEBUG<\/td><td>Level of debug information to display<\/td><\/tr><tr><td><strong>SS_TRACETOFILE<\/strong><\/td><td>On<\/td><td>On\/Off<\/td><td>Output debug information into file<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcc1-two-file-rotation-system\">\ud83d\udcc1 Two-File Rotation System<\/h3>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">VOS3000 Trace File Rotation:\n=============================\n\nVOS3000 uses 2 files to record trace signaling:\n\nFile 1: trace1.log (or similar)\nFile 2: trace2.log (or similar)\n\nHow It Works:\n=============\n1. System writes to File 1\n2. When File 1 reaches size limit (SS_TRACE_FILE_LENGTH)\n3. System switches to File 2\n4. When File 2 reaches size limit\n5. System overwrites File 1 (oldest data lost)\n6. Cycle continues...\n\nAdvantages:\n===========\n- Actual storage is double the file size limit\n- Continuous capture without manual intervention\n- Recent history always available\n- Automatic cleanup of old data\n\nImportant:\n==========\nAll trace signaling is saved unless file has been covered.\nIf you need to preserve trace data, copy files before rotation.\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-using-trace-for-troubleshooting\">\ud83d\udcca Using Trace for Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccd-accessing-trace-results-vos-3000-debug-trace\">\ud83d\udccd Accessing Trace Results (VOS3000 Debug Trace)<\/h3>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 2.17.1 (Page 205)<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Access Method<\/th><th class=\"has-text-align-left\" data-align=\"left\">Location<\/th><th class=\"has-text-align-left\" data-align=\"left\">Information Shown<\/th><\/tr><\/thead><tbody><tr><td><strong>Current Call Trace<\/strong><\/td><td>Current Call &gt; Right-click &gt; Trace<\/td><td>Real-time call signaling for active calls<\/td><\/tr><tr><td><strong>CDR Call Analysis<\/strong><\/td><td>CDR &gt; Right-click &gt; Call analysis<\/td><td>Complete signaling flow for completed call<\/td><\/tr><tr><td><strong>Registration Analysis<\/strong><\/td><td>Registration Management &gt; Right-click<\/td><td>Registration message flow and status<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd27-interpreting-trace-output-vos-3000-debug-trace\">\ud83d\udd27 Interpreting Trace Output (VOS3000 Debug Trace)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-sip-message-format\">\ud83d\udcca SIP Message Format<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Sample SIP INVITE Trace Output:\n===============================\n\n---------- 2026-04-03 10:25:32.123 ----------\nINVITE sip:1234567890@192.168.1.100 SIP\/2.0\nVia: SIP\/2.0\/UDP 192.168.1.50:5060;branch=z9hG4bK123456\nFrom: ;tag=12345\nTo: \nCall-ID: abc123def456@192.168.1.50\nCSeq: 1 INVITE\nContact: \nContent-Type: application\/sdp\nContent-Length: 200\n\nv=0\no=user 123 456 IN IP4 192.168.1.50\ns=Session\nc=IN IP4 192.168.1.50\nt=0 0\nm=audio 10000 RTP\/AVP 0 8 18\na=rtpmap:0 PCMU\/8000\na=rtpmap:8 PCMA\/8000\na=rtpmap:18 G729\/8000\n\nKey Headers to Analyze:\n=======================\n- Via: Message path and NAT information\n- From\/To: Caller and callee identities\n- Call-ID: Unique call identifier\n- Contact: Where to send responses\n- SDP (body): Media negotiation details\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-h-323-message-format-vos-3000-debug-trace\">\ud83d\udcca H.323 Message Format (VOS3000 Debug Trace)<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Sample H.323 Setup Trace Output:\n================================\n\n---------- 2026-04-03 10:26:15.456 ----------\nH.225 Setup Message:\n  Protocol Identifier: 0.0.8.2250.0.4\n  Source Address:\n    IP: 192.168.1.50\n    Port: 1720\n  Destination Address:\n    IP: 192.168.1.100\n    Port: 1720\n  Source Info:\n    E164: 0987654321\n  Destination Info:\n    E164: 1234567890\n  Active MC: FALSE\n  Conference ID: 0x12345678...\n\nKey Elements to Analyze:\n========================\n- Protocol Identifier: H.323 version\n- Source\/Destination: Endpoint addresses\n- E164 numbers: Calling\/called numbers\n- Conference ID: Call identifier\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udea8-common-debugging-scenarios-vos-3000-debug-trace\">\ud83d\udea8 Common Debugging Scenarios (VOS3000 Debug Trace)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-one-way-audio-diagnosis\">\ud83d\udcca One-Way Audio Diagnosis<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Trace Finding<\/th><th class=\"has-text-align-left\" data-align=\"left\">Meaning<\/th><th class=\"has-text-align-left\" data-align=\"left\">Solution<\/th><\/tr><\/thead><tbody><tr><td>SDP shows private IP in c= line<\/td><td>NAT issue &#8211; endpoint behind NAT<\/td><td>Enable media proxy, check NAT settings<\/td><\/tr><tr><td>RTP port mismatch between INVITE and 200 OK<\/td><td>SDP negotiation problem<\/td><td>Check codec compatibility, port ranges<\/td><\/tr><tr><td>Contact header has wrong IP<\/td><td>SIP ALG interference<\/td><td>Disable SIP ALG on router<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-registration-failure-analysis-vos-3000-debug-trace\">\ud83d\udcca Registration Failure Analysis (VOS3000 Debug Trace)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Trace Finding<\/th><th class=\"has-text-align-left\" data-align=\"left\">Meaning<\/th><th class=\"has-text-align-left\" data-align=\"left\">Solution<\/th><\/tr><\/thead><tbody><tr><td>401 Unauthorized response<\/td><td>Authentication credentials required<\/td><td>Configure correct username\/password<\/td><\/tr><tr><td>403 Forbidden response<\/td><td>Account locked or IP not allowed<\/td><td>Check account status, IP whitelist<\/td><\/tr><tr><td>No response to REGISTER<\/td><td>Network or firewall issue<\/td><td>Check SIP port 5060, firewall rules<\/td><\/tr><tr><td>Authentication retry exceeded<\/td><td>Wrong credentials repeatedly<\/td><td>Verify credentials, check for typos<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-call-drop-investigation-vos-3000-debug-trace\">\ud83d\udcca Call Drop Investigation (VOS3000 Debug Trace)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Trace Finding<\/th><th class=\"has-text-align-left\" data-align=\"left\">Meaning<\/th><th class=\"has-text-align-left\" data-align=\"left\">Solution<\/th><\/tr><\/thead><tbody><tr><td>BYE at 30-second interval<\/td><td>NAT binding timeout<\/td><td>Increase NAT keepalive, disable SIP ALG<\/td><\/tr><tr><td>Session timer expiry<\/td><td>Session timer not refreshed<\/td><td>Check SS_SIP_SESSION_TTL setting<\/td><\/tr><tr><td>RTP timeout in trace<\/td><td>No media received for configured time<\/td><td>Check media path, SS_MEDIA_CHECK_TIMEOUT<\/td><\/tr><tr><td>503 Service Unavailable<\/td><td>Gateway overloaded or down<\/td><td>Check gateway status, line limits<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\u2699\ufe0f-advanced-trace-configuration\">\u2699\ufe0f Advanced Trace Configuration<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcca-trace-mask-settings\">\ud83d\udcca Trace Mask Settings<\/h3>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 4.3.5.2 (Page 238)<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">Information Level<\/th><th class=\"has-text-align-left\" data-align=\"left\">When to Use<\/th><\/tr><\/thead><tbody><tr><td><strong>ERROR<\/strong><\/td><td>Errors and warnings only<\/td><td>Normal troubleshooting, production systems<\/td><\/tr><tr><td><strong>DEBUG<\/strong><\/td><td>Detailed debug information<\/td><td>Complex issues, development testing<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2699\ufe0f-performance-impact-vos-3000-debug-trace\">\u2699\ufe0f Performance Impact (VOS3000 Debug Trace)<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Performance Considerations:\n==========================\n\nSS_TRACE_MASK = ERROR (Default):\n- Minimal performance impact\n- Captures only error conditions\n- Suitable for production systems\n- Adequate for most troubleshooting\n\nSS_TRACE_MASK = DEBUG:\n- Higher performance impact\n- Captures all message details\n- More disk space usage\n- Use for complex debugging only\n\nRecommendations:\n================\n1. Use ERROR level for normal operations\n2. Switch to DEBUG only when needed\n3. Disable trace when not troubleshooting\n4. Monitor disk space on busy systems\n5. Set appropriate file size limits\n\nProduction Guidelines:\n======================\n- Keep SS_TRACETOFILE = On (writes to file, not memory)\n- Set SS_TRACE_FILE_LENGTH appropriately (40MB default)\n- Use SS_TRACE_MASK = ERROR\n- Disable during high-traffic periods if possible\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-cdr-end-reason-reference-vos-3000-debug-trace\">\ud83d\udcca CDR End Reason Reference (VOS3000 Debug Trace)<\/h2>\n\n\n\n<p>Reference: VOS3000 2.1.9.07 Manual, Section 4.5 (Page 243-248)<\/p>\n\n\n\n<p>When analyzing call failures, the end reason in CDR combined with trace provides complete information:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udccb-server-side-end-reasons-vos-3000-debug-trace\">\ud83d\udccb Server-Side End Reasons (VOS3000 Debug Trace)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th class=\"has-text-align-left\" data-align=\"left\">End Reason<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><th class=\"has-text-align-left\" data-align=\"left\">Trace Analysis<\/th><\/tr><\/thead><tbody><tr><td>Response timeout<\/td><td>No answer before timeout<\/td><td>Check INVITE sent, no 180\/183\/200 received<\/td><\/tr><tr><td>Connection timeout<\/td><td>No SIP response after retries<\/td><td>Check INVITE sent, check network path<\/td><\/tr><tr><td>Account locked<\/td><td>Account disabled<\/td><td>403 Forbidden in trace<\/td><\/tr><tr><td>Session timeout<\/td><td>Session timer expired<\/td><td>Check UPDATE\/re-INVITE messages<\/td><\/tr><tr><td>No matching rate<\/td><td>No rate for destination<\/td><td>Call rejected before INVITE sent<\/td><\/tr><tr><td>Insufficient balance<\/td><td>Account out of funds<\/td><td>403 Forbidden after billing check<\/td><\/tr><tr><td>The called not online<\/td><td>No route available<\/td><td>No matching routing gateway<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd17-related-resources-vos-3000-debug-trace\">\ud83d\udd17 Related Resources (VOS3000 Debug Trace)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/faster-support-for-vos3000-easy-troubleshoot-for-problems\/\" target=\"_blank\" rel=\"noreferrer noopener\">Faster Support for VOS3000 Troubleshooting<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/vos3000-softswitch-faq-based-on-official-manual\/\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 Softswitch FAQ<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/noavailablerouter-error-in-vos3000-2-1-4-0-or-vos3000-2-1-6-0-in-termination-reason\/\" target=\"_blank\" rel=\"noreferrer noopener\">NoAvailableRouter Error Troubleshooting<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/multahost.com\/blog\/sip-alg-problems-voip-nat-troubleshooting-guide\/\" target=\"_blank\" rel=\"noreferrer noopener\">SIP ALG Problems Troubleshooting Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udcd6 <a href=\"https:\/\/vos3000.com\/downloads.php\" target=\"_blank\" rel=\"noreferrer noopener\">VOS3000 Downloads<\/a><\/li>\n<\/ul>\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=\"where-are-trace-files-stored\">Where are trace files stored?<\/h3>\n\n\n\n<p>Trace files are stored in the VOS3000 installation directory, typically under a &#8220;trace&#8221; or &#8220;log&#8221; subdirectory. The exact location depends on your installation path. The files are managed automatically by VOS3000&#8217;s two-file rotation system.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"how-long-should-i-keep-debug-trace-enabled\">How long should I keep debug trace enabled?<\/h3>\n\n\n\n<p>Enable debug trace only when actively troubleshooting issues. For production systems, keep trace disabled or set to ERROR level to minimize performance impact. Enable DEBUG level only when investigating complex issues, then disable after resolution.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"can-i-export-trace-data-for-analysis\">Can I export trace data for analysis?<\/h3>\n\n\n\n<p>Yes, you can use the call analysis feature in CDR to view detailed trace for specific calls. For bulk analysis, trace files can be copied from the server and analyzed with text editors or tools like Wireshark (for SIP traces saved in pcap format).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"why-cant-i-see-trace-for-old-calls\">Why can&#8217;t I see trace for old calls?<\/h3>\n\n\n\n<p>Trace files have size limits and use rotation. When files exceed SS_TRACE_FILE_LENGTH or SS_TRACE_CALL_FILE_SIZE, older data is overwritten. If you need to preserve trace data for compliance or analysis, copy trace files before rotation occurs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"does-trace-capture-rtp-media-content\">Does trace capture RTP media content?<\/h3>\n\n\n\n<p>No, VOS3000 debug trace captures signaling only (SIP and H.323). It does not capture the actual RTP media content (voice\/audio). For media analysis, you would need separate packet capture tools like tcpdump or Wireshark on the server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcde-get-expert-help-with-vos-3000-debugging\">\ud83d\udcde Get Expert Help with VOS3000 Debugging<\/h2>\n\n\n\n<p>Need assistance analyzing trace output or resolving complex VoIP issues? Our VOS3000 experts provide remote debugging support, signaling analysis, and troubleshooting services.<\/p>\n\n\n\n<p><strong>\ud83d\udcf1 WhatsApp: <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noreferrer noopener\">+8801911119966<\/a><\/strong><\/p>\n\n\n\n<p>Contact us for VOS3000 installation, troubleshooting support, configuration optimization, and professional VoIP services!<\/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\" style=\"\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/03\/VOS3000-API-problemas-VOS3000-LCR-Least-Cost-Routing-VOS3000-Backup-MySQL-Spanish-Banner-4-1024x683.png\" alt=\"VOS3000 API problemas, VOS3000 LCR Least Cost Routing, VOS3000 Backup MySQL, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP\u6279\u53d1\u4e1a\u52a1, \u8f6f\u4ea4\u6362\u6bd4\u8f83, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Gu\u00eda Completa VOS3000 2026, VOS3000 \u6307\u5357 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization\"><\/td><td><img decoding=\"async\" style=\"\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/03\/VOS3000-API-problemas-VOS3000-LCR-Least-Cost-Routing-VOS3000-Backup-MySQL-Spanish-Banner-4-1024x683.png\" alt=\"VOS3000 API problemas, VOS3000 LCR Least Cost Routing, VOS3000 Backup MySQL, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP\u6279\u53d1\u4e1a\u52a1, \u8f6f\u4ea4\u6362\u6bd4\u8f83, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Gu\u00eda Completa VOS3000 2026, VOS3000 \u6307\u5357 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization\"><\/td><td><img decoding=\"async\" style=\"\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/03\/VOS3000-API-problemas-VOS3000-LCR-Least-Cost-Routing-VOS3000-Backup-MySQL-Spanish-Banner-4-1024x683.png\" alt=\"VOS3000 API problemas, VOS3000 LCR Least Cost Routing, VOS3000 Backup MySQL, Negocio VoIP Mayorista, VICIDIAL Servidor, Softswitch Barato, VoIP\u6279\u53d1\u4e1a\u52a1, \u8f6f\u4ea4\u6362\u6bd4\u8f83, Advance Routing, VOS3000 Troubleshooting Guide, VOS3000 CDR Analysis, Gu\u00eda Completa VOS3000 2026, VOS3000 \u6307\u5357 2026, SIP ALG Problems, VOS3000 gateway configuration, VoIP Fraud Prevention, VOS3000 Media Proxy, VOS3000 Call Termination Reasons, SIP 403 forbidden, VOS3000 QoS configuration, VOS3000 debug trace, VOS3000 SIP session timer, VOS3000 dial plan, VOS3000 routing optimization\"><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Master VOS3000 debug trace for VoIP troubleshooting. Complete guide to call signaling analysis, SIP\/H.323 trace, and debugging configuration for faster support.<\/p>\n","protected":false},"author":1,"featured_media":916,"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":[3911,3923,3932,3939,3943,3924,3906,3917,3940,3919,3931,3926,3927,3907,3936,3929,3928,3933,3912,3937,3938,3908,3944,3921,3935,3925,3915,3909,3913,3941,3945,3930,3922,3942,3914,3910,3869,3918,3920,498,3465,3870,3916,328,482,244,3934],"class_list":["post-928","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vos3000","tag-call-analysis","tag-call-drop-analysis","tag-call-flow","tag-call-investigation","tag-call-setup-analysis","tag-call-signaling","tag-call-trace","tag-debug-configuration","tag-debug-file","tag-debug-log","tag-debug-tools","tag-h-323-error","tag-h-323-message","tag-h-323-trace","tag-media-analysis","tag-one-way-audio-diagnosis","tag-registration-analysis","tag-registration-failure","tag-registration-trace","tag-routing-problem","tag-rtp-trace","tag-signaling-analysis","tag-signaling-problem","tag-signaling-trace","tag-sip-debugging","tag-sip-error","tag-sip-message","tag-sip-signaling","tag-sip-trace","tag-technical-troubleshooting","tag-telecom-debugging","tag-trace-analysis","tag-trace-file","tag-trace-parameters","tag-troubleshooting","tag-voip-debugging","tag-voip-support","tag-voip-trace","tag-voip-troubleshooting-tools","tag-vos3000-configuration","tag-vos3000-debug-trace","tag-vos3000-expert","tag-vos3000-log-analysis","tag-vos3000-manual","tag-vos3000-support","tag-vos3000-troubleshooting","tag-wireshark-voip"],"acf":[],"jetpack_featured_media_url":"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6.png","blog_post_layout_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-150x150.png",150,150,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6.png",1733,907,false]},"categories_names":{"2":{"name":"VOS3000`","link":"https:\/\/www.vos3000.com\/blog\/category\/vos3000\/"}},"tags_names":{"3911":{"name":"call analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-analysis\/"},"3923":{"name":"call drop analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-drop-analysis\/"},"3932":{"name":"call flow","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-flow\/"},"3939":{"name":"call investigation","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-investigation\/"},"3943":{"name":"call setup analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-setup-analysis\/"},"3924":{"name":"call signaling","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-signaling\/"},"3906":{"name":"call trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/call-trace\/"},"3917":{"name":"debug configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/debug-configuration\/"},"3940":{"name":"debug file","link":"https:\/\/www.vos3000.com\/blog\/tag\/debug-file\/"},"3919":{"name":"debug log","link":"https:\/\/www.vos3000.com\/blog\/tag\/debug-log\/"},"3931":{"name":"debug tools","link":"https:\/\/www.vos3000.com\/blog\/tag\/debug-tools\/"},"3926":{"name":"H.323 error","link":"https:\/\/www.vos3000.com\/blog\/tag\/h-323-error\/"},"3927":{"name":"H.323 message","link":"https:\/\/www.vos3000.com\/blog\/tag\/h-323-message\/"},"3907":{"name":"H.323 trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/h-323-trace\/"},"3936":{"name":"media analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/media-analysis\/"},"3929":{"name":"one-way audio diagnosis","link":"https:\/\/www.vos3000.com\/blog\/tag\/one-way-audio-diagnosis\/"},"3928":{"name":"registration analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/registration-analysis\/"},"3933":{"name":"registration failure","link":"https:\/\/www.vos3000.com\/blog\/tag\/registration-failure\/"},"3912":{"name":"registration trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/registration-trace\/"},"3937":{"name":"routing problem","link":"https:\/\/www.vos3000.com\/blog\/tag\/routing-problem\/"},"3938":{"name":"RTP trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/rtp-trace\/"},"3908":{"name":"signaling analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/signaling-analysis\/"},"3944":{"name":"signaling problem","link":"https:\/\/www.vos3000.com\/blog\/tag\/signaling-problem\/"},"3921":{"name":"signaling trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/signaling-trace\/"},"3935":{"name":"SIP debugging","link":"https:\/\/www.vos3000.com\/blog\/tag\/sip-debugging\/"},"3925":{"name":"SIP error","link":"https:\/\/www.vos3000.com\/blog\/tag\/sip-error\/"},"3915":{"name":"SIP message","link":"https:\/\/www.vos3000.com\/blog\/tag\/sip-message\/"},"3909":{"name":"SIP signaling","link":"https:\/\/www.vos3000.com\/blog\/tag\/sip-signaling\/"},"3913":{"name":"SIP trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/sip-trace\/"},"3941":{"name":"technical troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/technical-troubleshooting\/"},"3945":{"name":"telecom debugging","link":"https:\/\/www.vos3000.com\/blog\/tag\/telecom-debugging\/"},"3930":{"name":"trace analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/trace-analysis\/"},"3922":{"name":"trace file","link":"https:\/\/www.vos3000.com\/blog\/tag\/trace-file\/"},"3942":{"name":"trace parameters","link":"https:\/\/www.vos3000.com\/blog\/tag\/trace-parameters\/"},"3914":{"name":"troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/troubleshooting\/"},"3910":{"name":"VoIP debugging","link":"https:\/\/www.vos3000.com\/blog\/tag\/voip-debugging\/"},"3869":{"name":"VoIP support","link":"https:\/\/www.vos3000.com\/blog\/tag\/voip-support\/"},"3918":{"name":"VoIP trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/voip-trace\/"},"3920":{"name":"VoIP troubleshooting tools","link":"https:\/\/www.vos3000.com\/blog\/tag\/voip-troubleshooting-tools\/"},"498":{"name":"VOS3000 configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-configuration\/"},"3465":{"name":"vos3000 debug trace","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-debug-trace\/"},"3870":{"name":"VOS3000 expert","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-expert\/"},"3916":{"name":"VOS3000 log analysis","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-log-analysis\/"},"328":{"name":"VOS3000 Manual","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-manual\/"},"482":{"name":"VOS3000 Support","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-support\/"},"244":{"name":"VOS3000 troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-troubleshooting\/"},"3934":{"name":"Wireshark VoIP","link":"https:\/\/www.vos3000.com\/blog\/tag\/wireshark-voip\/"}},"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-150x150.png",150,150,true],"cvmm-medium":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-300x300.png",300,300,true],"cvmm-medium-plus":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-305x207.png",305,207,true],"cvmm-portrait":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-400x600.png",400,600,true],"cvmm-medium-square":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-600x600.png",600,600,true],"cvmm-large":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-1024x907.png",1024,907,true],"cvmm-small":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6-130x95.png",130,95,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/SIP-403-forbidden-VOS3000-QoS-configuration-VOS3000-debug-trace-VOS3000-SIP-session-timer-VOS3000-dial-plan-VOS3000-routing-optimization-6.png",1733,907,false]},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/928","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=928"}],"version-history":[{"count":1,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/928\/revisions"}],"predecessor-version":[{"id":931,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/928\/revisions\/931"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media\/916"}],"wp:attachment":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media?parent=928"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/categories?post=928"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/tags?post=928"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}