Tag: VOS3000 CDR fields

Como Configurar Tarifas VOS3000, Como Agregar Pasarela VOS3000, Como Crear Cuentas VOS3000, Como Leer Registros CDR VOS3000, Como Asegurar Servidor VOS3000, Como Migrar VOS3000 Servidor, Como Actualizar VOS3000 Version, Como Configurar Plan Marcacion VOS3000, Como Exportar CDR VOS3000, Como Bloquear Llamadas Fraudulentas VOS3000

Como Exportar CDR VOS3000 True Essential: Sistema Externo

king

Como Exportar CDR VOS3000 Essential: Sistema Externo 📤

Aprender como exportar CDR VOS3000 a un sistema externo es fundamental para los operadores VoIP que necesitan integrar los registros de llamadas con sistemas de facturacion, conciliacion, analisis o business intelligence. 📊 Los CDR (Call Detail Records) contienen informacion detallada de cada llamada procesada por VOS3000, y exportarlos correctamente permite automatizar procesos financieros y operativos que serian imposibles de realizar manualmente. 🚀

En esta guia completa sobre como exportar CDR VOS3000, cubriremos los diferentes metodos de exportacion disponibles, los formatos de archivo soportados, la integracion con sistemas externos via API, y las mejores practicas para la conciliacion de datos. Cada seccion incluye tablas de referencia y ejemplos practicos. 💰

Que son los Registros CDR en VOS3000 📋

Antes de aprender como exportar CDR VOS3000, es importante comprender que informacion contienen los registros CDR. Cada CDR es una linea de datos que representa una llamada completa, incluyendo informacion de los numeros de origen y destino, la duracion, la tarifa aplicada, el codigo de finalizacion, la pasarela utilizada y muchos otros campos. 📋

Los CDR se generan automaticamente por VOS3000 al finalizar cada llamada y se almacenan en la base de datos del sistema. Desde alli, pueden ser consultados, descargados y exportados en diferentes formatos. Para informacion detallada sobre CDR, consulte nuestra guia de registros CDR avanzados del sistema VOS3000. 📊

📋 Campo CDRDescripcionEjemplo
📞 Caller NumberNumero de origen+12055551234
📱 Called NumberNumero destino+44207123456
⏱️ DurationDuracion en segundos185
💲 Fee AmountTarifa cobrada0.0925
🔄 Release CauseCodigo finalizacion16 (normal)
📅 Call TimeFecha y hora2026-05-19 14:30:22
🔌 GatewayPasarela utilizadaVendor_Alpha
👤 AccountCuenta asociadaClient_001
🎵 CodecCodec utilizadoG729
📊 DirectionDireccion de llamadaOutbound

Metodos de Exportacion de CDR 📤

VOS3000 ofrece multiples metodos para exportar CDR, cada uno con diferentes caracteristicas y casos de uso. Al aprender como exportar CDR VOS3000, es importante elegir el metodo adecuado segun sus necesidades. 📤

📤 MetodoDescripcionMejor Para
📋 Panel WebDescarga desde interfaz graficaExportacion manual puntual
📄 Archivo TextoCDR automaticos en archivo textoIntegracion automatica
🔗 Web APIConsulta via HTTP+JSONIntegracion en tiempo real
🗄️ Base de DatosConsulta directa MySQLAnalisis avanzado
🔄 CDR ForwardingEnvio en tiempo realSistemas de monitoreo

Exportar CDR desde el Panel Web 🖥️

El metodo mas sencillo de como exportar CDR VOS3000 es a traves del panel web. Acceda a la seccion CDR Query en el panel de VOS3000, seleccione el rango de fechas y los filtros deseados, y haga clic en Export para descargar los registros en formato CSV. Este metodo es ideal para exportaciones puntuales o para verificar datos especificos. 🖥️

La exportacion desde el panel web permite filtrar por fecha, cuenta, pasarela, numero de origen o destino, y codigo de finalizacion. Puede exportar todos los campos o seleccionar solo los que necesita. Para informacion sobre consulta de CDR, consulte nuestra guia de gestion CDR del sistema VOS3000. 📋

Exportar CDR en Formato Archivo Texto 📄

VOS3000 puede generar automaticamente archivos de texto con los registros CDR a medida que se completan las llamadas. Este metodo de como exportar CDR VOS3000 es ideal para la integracion automatica con sistemas de facturacion externos, ya que no requiere intervencion manual y los archivos se generan en tiempo real. 📄

Segun la seccion §2.7 del manual oficial, VOS3000 soporta dos formatos de archivo texto: formato pipe (delimitado por el caracter |) y formato CSV (delimitado por comas). El formato pipe es el mas utilizado en integraciones con sistemas de facturacion. Para informacion sobre formato pipe, consulte nuestra guia de formato pipe CDR en VOS3000. 📊

📄 INFOGRAFIA: Formato Pipe CDR VOS3000
================================================
Ejemplo de linea CDR en formato pipe:

2026-05-19|14:30:22|Client_001|+12055551234|
+44207123456|185|0.0925|16|Vendor_Alpha|
G729|Outbound|1/1|0.0005|...

Campos principales:
├── Fecha: 2026-05-19
├── Hora: 14:30:22
├── Cuenta: Client_001
├── Origen: +12055551234
├── Destino: +44207123456
├── Duracion: 185 segundos
├── Tarifa: 0.0925 USD
├── Codigo fin: 16 (normal)
├── Pasarela: Vendor_Alpha
└── Codec: G729
================================================

Exportar CDR via Web API 🔗

La Web API de VOS3000 es el metodo mas potente de como exportar CDR VOS3000 para integraciones en tiempo real. A traves de la API, puede consultar registros CDR utilizando peticiones HTTP con respuestas en formato JSON, lo que permite integrar VOS3000 con cualquier sistema externo. 🔗

Para consultar CDR via API, envie una peticion GET al endpoint de CDR con los parametros de filtro (fecha, cuenta, destino, etc.). La API devuelve los resultados en formato JSON con todos los campos del CDR. Para informacion sobre la API, consulte nuestra guia de API web e integraciones del sistema VOS3000. 💻

🔗 Endpoint APIMetodoParametros
/api/cdr/queryGETstart_date, end_date, account
/api/cdr/detailGETcall_id
/api/cdr/exportGETstart_date, end_date, format

CDR Forwarding en Tiempo Real 🔄

El CDR forwarding es un metodo avanzado de como exportar CDR VOS3000 que envia registros CDR a un sistema externo en tiempo real, inmediatamente despues de que se completa cada llamada. Este metodo es ideal para sistemas de monitoreo, dashboards en tiempo real y alertas automatizadas. 🔄

Segun la seccion §2.7 del manual, VOS3000 puede enviar CDR automaticamente a una direccion IP y puerto configurados, utilizando el formato pipe o CSV. Configure el CDR forwarding en los parametros del sistema con la IP del servidor destino y el puerto. Para informacion sobre forwarding, consulte nuestra guia de forwarding CDR en tiempo real en VOS3000. 📡

Integracion con Sistemas de Facturacion Externa 💰

Una de las razones mas comunes para aprender como exportar CDR VOS3000 es la integracion con sistemas de facturacion externos. Los CDR contienen todos los datos necesarios para generar facturas precisas: duracion, tarifa, cuenta, destino y monto. 📊

El proceso tipico de integracion incluye: exportar los CDR diariamente, procesarlos en el sistema de facturacion externo para calcular totales por cliente, generar las facturas con los detalles de llamadas, y realizar la conciliacion entre los datos de VOS3000 y los del sistema de facturacion. Para informacion sobre facturacion, consulte nuestra guia de facturacion esencial del sistema VOS3000. 💵

Conciliacion de CDR entre Sistemas 📊

La conciliacion de CDR es un proceso critico cuando se aprende como exportar CDR VOS3000. La conciliacion compara los registros de VOS3000 con los registros de los proveedores y los sistemas de facturacion para identificar discrepancias. Las diferencias pueden surgir por duraciones de llamada, codigos de finalizacion o llamadas faltantes. 📋

Para realizar la conciliacion, exporte los CDR de VOS3000 y los CDR del proveedor para el mismo periodo. Compare las llamadas por numero de origen, destino, fecha y hora. Identifique las llamadas que existen en un sistema pero no en el otro, y las llamadas con duraciones o montos diferentes. Para informacion sobre conciliacion, consulte nuestra guia de reportes del sistema VOS3000. 🔍

Preguntas Frecuentes sobre Como Exportar CDR VOS3000 ❓

❓ Como exporto CDR desde el panel de VOS3000?

Para exportar CDR desde el panel como parte de como exportar CDR VOS3000, acceda a la seccion CDR Query en el panel de VOS3000. Seleccione el rango de fechas deseado, aplique los filtros que necesite (cuenta, pasarela, destino) y haga clic en Export. Los datos se descargaran en formato CSV que puede abrir con Excel o cualquier herramienta de analisis. Este metodo es ideal para exportaciones puntuales o verificacion de datos. 🖥️

❓ En que formatos puedo exportar los CDR?

Al aprender como exportar CDR VOS3000, tiene varios formatos disponibles: CSV (comma separated values) desde el panel web, formato pipe (delimitado por |) en los archivos texto automaticos, formato JSON a traves de la Web API, y acceso directo a la base de datos MySQL. El formato pipe es el mas utilizado en integraciones automaticas con sistemas de facturacion, mientras que JSON es el preferido para integraciones web modernas. 📄

❓ Puedo enviar CDR automaticamente a un sistema externo?

Si, VOS3000 puede enviar CDR automaticamente a un sistema externo mediante la funcion de CDR forwarding. Configure la IP y el puerto del servidor destino en los parametros del sistema, y VOS3000 enviara cada registro CDR inmediatamente despues de que se complete la llamada. Este metodo de como exportar CDR VOS3000 es ideal para integraciones en tiempo real con sistemas de monitoreo o facturacion. 🔄

❓ Como integro CDR con mi sistema de facturacion?

Para integrar CDR con su sistema de facturacion mediante como exportar CDR VOS3000, tiene dos opciones principales: exportar archivos texto CDR diariamente y procesarlos en su sistema de facturacion, o utilizar la Web API para consultar los CDR en tiempo real. La primera opcion es mas simple y adecuada para facturacion mensual. La segunda es ideal para facturacion en tiempo real o portales de cliente. Para informacion sobre la API, consulte nuestra documentacion de integraciones web. 💰

❓ Que campos contiene un registro CDR de VOS3000?

Al aprender como exportar CDR VOS3000, encontrara que cada registro contiene: fecha y hora de la llamada, numero de origen (caller), numero destino (called), duracion en segundos, tarifa cobrada (fee amount), codigo de finalizacion (release cause), pasarela utilizada (gateway), cuenta asociada (account), codec utilizado, direccion de la llamada, incremento de facturacion y tarifa por minuto. Para informacion sobre campos CDR, consulte nuestra guia de registros CDR avanzados. 📋

❓ Con que frecuencia debo exportar los CDR?

La frecuencia de exportacion al aprender como exportar CDR VOS3000 depende de sus necesidades. Para conciliacion con proveedores, una exportacion diaria es suficiente. Para facturacion en tiempo real o portales de cliente, utilice la Web API o CDR forwarding para acceso inmediato. Para analisis historico, exportaciones semanales o mensuales pueden ser adecuadas. Configure la rotacion de archivos CDR en VOS3000 para evitar que los archivos crezcan demasiado. 📅

Conclusion 🏆

Aprender como exportar CDR VOS3000 es esencial para cualquier operador que necesite integrar los registros de llamadas con sistemas externos de facturacion, conciliacion o analisis. Con los multiples metodos disponibles (panel web, archivos texto, Web API, CDR forwarding), puede elegir la opcion que mejor se adapte a sus necesidades y automatizar los procesos financieros de su operacion VoIP. 🚀

Para soporte profesional en la exportacion e integracion de CDR, contactenos por WhatsApp al +8801911119966. Tambien puede descargar la ultima version desde vos3000.com/downloads. Para continuar aprendiendo, explore nuestros articulos sobre registros CDR avanzados y facturacion esencial del sistema VOS3000. 🤝

Para consultas sobre servidores, licencias y servicios profesionales, contactenos por WhatsApp al +8801911119966. 📱

📞 Need Professional VOS3000 Setup Support?

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

📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com

Como Configurar Tarifas VOS3000, Como Agregar Pasarela VOS3000, Como Crear Cuentas VOS3000, Como Leer Registros CDR VOS3000, Como Asegurar Servidor VOS3000, Como Migrar VOS3000 Servidor, Como Actualizar VOS3000 Version, Como Configurar Plan Marcacion VOS3000, Como Exportar CDR VOS3000, Como Bloquear Llamadas Fraudulentas VOS3000Como Configurar Tarifas VOS3000, Como Agregar Pasarela VOS3000, Como Crear Cuentas VOS3000, Como Leer Registros CDR VOS3000, Como Asegurar Servidor VOS3000, Como Migrar VOS3000 Servidor, Como Actualizar VOS3000 Version, Como Configurar Plan Marcacion VOS3000, Como Exportar CDR VOS3000, Como Bloquear Llamadas Fraudulentas VOS3000Como Configurar Tarifas VOS3000, Como Agregar Pasarela VOS3000, Como Crear Cuentas VOS3000, Como Leer Registros CDR VOS3000, Como Asegurar Servidor VOS3000, Como Migrar VOS3000 Servidor, Como Actualizar VOS3000 Version, Como Configurar Plan Marcacion VOS3000, Como Exportar CDR VOS3000, Como Bloquear Llamadas Fraudulentas VOS3000
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

VOS3000 CDR Pipe Format Definitive 18-Field Important Reference Guide

king

VOS3000 CDR Pipe Format Definitive 18-Field Reference Guide

📊 Every VOS3000 operator who exports call detail records must understand the VOS3000 CDR pipe format down to the individual field level. The pipe-delimited text file is the universal interface between your softswitch and every external system that consumes call data — billing platforms, fraud detection engines, analytics dashboards, and regulatory compliance archives. A single misinterpreted field can cascade into billing errors, incorrect traffic reports, or failed audits. Yet the official manual provides only a brief field listing, leaving operators to figure out data types, edge cases, and integration mappings on their own. 🔍

⚙️ This guide provides a definitive, field-by-field reference of every column in the VOS3000 CDR pipe format. Each field is documented with its position in the pipe-delimited line, data type, example value, special considerations, and how it maps to external billing and analytics systems. All field definitions are sourced from the official VOS3000 2.1.8.0/2.1.9.07 English manual §4.4 (pages 241–243), with additional practical guidance based on real-world parsing and integration experience. 📘

🎯 Whether you are building a Python CDR parser, configuring a MySQL import pipeline, or integrating VOS3000 with a third-party billing system, this reference eliminates the guesswork from field mapping and data interpretation. Let us walk through every field in the exact order it appears in each CDR line. 🔧

🔐 VOS3000 CDR Pipe Format Overview

📁 When SS_CDR_RECORD_TO_FILE is enabled in VOS3000, the softswitch generates hourly text files in the cdr/ directory. Each file follows the naming convention YYYYMMDDHH.txt, and each line within the file represents one call detail record with fields separated by the pipe character (|, ASCII 124). The format specification is documented in the official VOS3000 manual §4.4.

📋 CDR Line Format Structure – VOS3000 CDR Pipe

callerE164|calleeE164|startTime|stopTime|holdTime|endReason|
endDirection|callerGatewayId|calleeGatewayId|callerIp|calleeIp|
callerAccessE164|calleeAccessE164|callerToGatewayE164|
calleeToGatewayE164|calleeBilling|billingMode|callerPdd|calleePdd

📝 Field count note: The VOS3000 manual §4.4 documents the header line with 18 pipe separators producing 19 columns. The first 17 fields (through billingMode) are the core billing-critical fields present in all CDR records. Fields 18 and 19 (callerPdd and calleePdd) provide Post-Dial Delay metrics that measure call setup timing. Your parsing logic should handle both 17-field and 19-field records for maximum compatibility across VOS3000 versions.

📊 Complete Field-by-Field Reference – VOS3000 CDR Pipe

📋 Below is the definitive reference for every field in the VOS3000 CDR pipe format, in the exact order they appear in each line:

Field 1: callerE164 — The Caller ID 🔔

AttributeValue
📌 Field Position1 (first field)
📐 Data TypeString (numeric E.164 format)
📝 DescriptionThe caller ID — the originating party’s phone number
🔢 Example12125551234
⚠️ NotesMay differ from callerAccessE164 after prefix transformations

💡 Practical note: The callerE164 field reflects the caller ID after VOS3000 has applied any configured prefix transformations. This is the number as seen by the billing engine, not necessarily the original incoming number. For the original incoming caller ID before any transformations, refer to Field 12 (callerAccessE164). Understanding this distinction is essential when troubleshooting billing discrepancies.

Field 2: calleeE164 — The Callee ID 📞

AttributeValue
📌 Field Position2
📐 Data TypeString (numeric E.164 format)
📝 DescriptionThe callee ID — the destination phone number
🔢 Example18005559876
⚠️ NotesThis is the billed destination number after prefix processing

🔑 Billing relevance: The calleeE164 is the number used by the VOS3000 billing engine to match the call against rate tables. If your prefix settings strip or add digits, the calleeE164 reflects the number after those transformations. This is critical for rate table matching — a calleeE164 of 18005559876 matches a different rate entry than 01118005559876.

Field 3: startTime — Call Begin Time ⏰

AttributeValue
📌 Field Position3
📐 Data TypeDatetime string
📝 DescriptionBegin time of the call
🔢 Example2018-12-20 11:20:18
⚠️ NotesFormat is YYYY-MM-DD HH:MM:SS; timezone is server local time

⏱️ Time zone awareness: The startTime is recorded in the VOS3000 server’s local timezone. If your server is configured in UTC+6 (Bangladesh Standard Time), all timestamps reflect that timezone. When integrating CDR data with systems in different timezones, always account for the offset. The startTime represents when the call was initially received by VOS3000, not when it was answered.

Field 4: stopTime — Call End Time 🛑

AttributeValue
📌 Field Position4
📐 Data TypeDatetime string
📝 DescriptionEnd time of the call
🔢 Example2018-12-20 16:34:09

📊 Duration calculation: The actual call duration is stored in Field 5 (holdTime), not calculated from startTime and stopTime. The difference between startTime and stopTime includes call setup time, ringing time, and other pre-connection delays. Only holdTime represents the actual conversation duration. The stopTime determines which hourly CDR file the record is written to.

Field 5: holdTime — Call Duration ⏱️

AttributeValue
📌 Field Position5
📐 Data TypeInteger (milliseconds)
📝 DescriptionCall duration in milliseconds
🔢 Example45000 (equals 45 seconds)
🚨 Critical NoteValue is in MILLISECONDS, not seconds — a common parsing error

⚠️ The #1 parsing mistake: The holdTime field is recorded in milliseconds, not seconds. A value of 45000 means 45 seconds of conversation, not 45000 seconds. This is the single most common error when integrating VOS3000 CDR data with external billing systems. Always divide holdTime by 1000 before applying per-second or per-minute billing rates. The holdTime is also affected by the SERVER_BILLING_HOLD_TIME_PRECISION parameter, which controls millisecond rounding before billing calculation.

Field 6: endReason — End Reason Code 📋

AttributeValue
📌 Field Position6
📐 Data TypeString/Integer
📝 DescriptionEnd reason — SIP response code or Q.850 cause code
🔢 Example200 (normal), 486 (busy), 480 (no answer)

🔍 Interpreting endReason: For SIP calls, the endReason typically contains the SIP response code from the final response message (200 OK, 486 Busy, 480 Temporarily Unavailable, 503 Service Unavailable, etc.). For H.323 calls, it may contain Q.850 cause codes. The endReason field, combined with endDirection, provides the complete picture of why and how a call terminated. For a detailed breakdown of termination codes, see our guide on VOS3000 call termination reasons.

Field 7: endDirection — Hangup Side 🔄

AttributeValue
📌 Field Position7
📐 Data TypeInteger (0, 1, or 2)
📝 DescriptionHangup side: 0 = caller, 1 = callee, 2 = server

🔑 Billing impact: The endDirection tells you who initiated the call termination. A value of 0 means the calling party hung up normally, 1 means the called party hung up, and 2 means the VOS3000 server itself terminated the call (which could indicate a session timeout, account balance exhaustion, or administrative intervention). This field is critical for dispute resolution — see our detailed analysis in the server hangup CDR recording guide.

Fields 8–9: Gateway Identifiers 📡

FieldPositionDescriptionExample
callerGatewayId8Calling gateway ID1001
calleeGatewayId9Called gateway ID2003

📡 Gateway mapping: These fields contain the VOS3000 internal gateway IDs, not the gateway names you see in the client interface. To map these IDs to human-readable gateway names, you need to cross-reference the VOS3000 gateway configuration. The callerGatewayId refers to the mapping gateway (incoming side), while the calleeGatewayId refers to the routing gateway (outgoing side). Understanding this mapping is essential for gateway performance analysis and route optimization.

Fields 10–11: IP Addresses 🌐

FieldPositionDescriptionExample
callerIp10Caller IP address192.168.1.100
calleeIp11Callee IP address10.0.0.50

🔒 Security value: The IP address fields are invaluable for security analysis. By tracking callerIp patterns, you can identify traffic from unexpected source IPs that may indicate unauthorized access or SIP scanning attacks. The VOS3000 anti-hack configuration uses IP-level authentication, and these CDR fields provide the audit trail for verifying that authentication is working correctly.

Fields 12–13: Access (Incoming) E164 Numbers 📥

FieldPositionDescription
callerAccessE16412Incoming caller — the original caller ID as received by VOS3000 before any transformations
calleeAccessE16413Incoming callee — the original destination number as received before transformations

🔄 Why access fields matter: These fields preserve the original phone numbers as they arrived at VOS3000, before any callee rewrite rules, prefix stripping, or number transformations were applied. This is crucial for debugging routing issues — if a call was routed incorrectly because a prefix transformation changed the destination, you can compare calleeAccessE164 (original) with calleeE164 (transformed) to identify exactly where the routing went wrong. For detailed prefix configuration guidance, see our callee rewrite rule guide.

Fields 14–15: Outbound (To Gateway) E164 Numbers 📤

FieldPositionHeader NameDescription
callerToGatewayE16414callerToGatewayE164Outbound caller — the caller ID sent to the outgoing gateway
calleeToGatewayE16415calleeToGatewayE164Outbound callee — the destination number sent to the outgoing gateway

📋 Naming discrepancy note: The VOS3000 manual §4.4 header line labels these fields as callerToGatewayE164 and calleeToGatewayE164, but the field description table in the same section refers to them as “Outbound caller” and “Outbound callee” (callerOutE164 / calleeOutE164). Both names refer to the same data — the phone numbers after all VOS3000 transformations have been applied, as they are sent out to the routing gateway. These outbound fields show the final form of the numbers as seen by the terminating carrier.

Field 16: calleeBilling — Billing Method 💰

AttributeValue
📌 Field Position16
📐 Data TypeInteger (0 or 1)
📝 DescriptionBilling method: 0 = By caller, 1 = By callee

💡 Understanding billing method: This field indicates which party’s account is charged for the call. A value of 0 means the caller’s account is billed (the standard arrangement for most calls). A value of 1 means the callee’s account is billed, which applies to collect calls, toll-free number calls, or special reverse-charging arrangements. This field works in conjunction with billingMode (Field 17) to determine the complete billing attribution for each call.

Field 17: billingMode — Charge Mode 💳

AttributeValue
📌 Field Position17
📐 Data TypeInteger (-1, 0, 1, or 3)
📝 DescriptionCharge mode: -1 = no billing, 0 = phone number, 1 = gateway ID, 3 = phone card

🔑 Billing mode codes explained: This is one of the most important fields for billing analysis. A billingMode of -1 means the call was not billed at all — this applies to illegal calls, free numbers, and calls that bypass the billing engine. A value of 0 means billing is attributed to a phone number account. A value of 1 means billing is attributed to a gateway ID. A value of 3 means billing is attributed to a phone card (calling card). For a comprehensive breakdown of how each code affects billing calculations, refer to our detailed billing mode codes reference.

Fields 18–19: Post-Dial Delay Metrics ⏱️

FieldPositionDescription
callerPdd18Time elapsed from call received to call connected (incoming PDD)
calleePdd19Time elapsed from call sent to routing response (outgoing PDD)

📊 PDD analysis value: Post-Dial Delay is a critical quality-of-service metric. High callerPdd values indicate that calls take too long to connect on the incoming side, which frustrates callers. High calleePdd values indicate slow response from routing gateways, which may point to gateway overload, network latency, or incorrect INVITE timeout configuration. Monitoring PDD trends helps you identify degrading gateway performance before it impacts your ASR.

📋 Complete VOS3000 CDR Pipe Format Quick Reference Table

#Field NameTypeDescriptionExample
1callerE164StringThe caller ID12125551234
2calleeE164StringThe callee ID18005559876
3startTimeDatetimeCall begin time2018-12-20 11:20:18
4stopTimeDatetimeCall end time2018-12-20 16:34:09
5holdTimeInteger (ms)Call duration in milliseconds45000
6endReasonString/IntEnd reason code200
7endDirectionIntegerHangup side (0/1/2)0
8callerGatewayIdIntegerCalling gateway1001
9calleeGatewayIdIntegerCalled gateway2003
10callerIpStringCaller IP address192.168.1.100
11calleeIpStringCallee IP address10.0.0.50
12callerAccessE164StringIncoming caller12125551234
13calleeAccessE164StringIncoming callee01118005559876
14callerToGatewayE164StringOutbound caller12125551234
15calleeToGatewayE164StringOutbound callee18005559876
16calleeBillingIntegerBilling method (0/1)0
17billingModeIntegerCharge mode (-1/0/1/3)0
18callerPddIntegerIncoming PDD (ms)3200
19calleePddIntegerOutgoing PDD (ms)1500

📊 External System Mapping Guide – VOS3000 CDR Pipe

🔗 When integrating VOS3000 CDR data with external billing and analytics systems, field names and data types often need to be mapped to the target system’s schema. Here is a reference mapping for common integration targets:

VOS3000 FieldMySQL ColumnCommon Billing LabelTransform Needed
callerE164VARCHAR(32)ANI / Calling NumberNone
calleeE164VARCHAR(32)DNIS / Called NumberNone
startTimeDATETIMECall Start / Setup TimeParse datetime string
holdTimeINTDuration (seconds)⚠️ Divide by 1000
endReasonVARCHAR(16)Release CauseMap to cause code table
endDirectionTINYINTRelease SourceMap 0/1/2 to labels
billingModeTINYINTBilling TypeMap -1/0/1/3 to labels

❓ Frequently Asked Questions

❓ How many fields are in the VOS3000 CDR pipe format?

📋 The VOS3000 CDR pipe format contains 17 core billing-critical fields (through the billingMode field at position 17) plus 2 Post-Dial Delay fields (callerPdd at position 18 and calleePdd at position 19), for a total of up to 19 fields. The pipe delimiter creates 18 separators for the full 19-column format. Older VOS3000 versions may produce records with only 17 fields (without PDD data). Your parsing code should handle variable field counts gracefully by checking the number of pipe-delimited columns in each line before processing.

❓ Why is holdTime in milliseconds instead of seconds?

⏱️ VOS3000 records holdTime in milliseconds to support high-precision billing configurations. The SERVER_BILLING_FEE_PRECISTION and SERVER_BILLING_HOLD_TIME_PRECISION parameters allow billing calculations down to millisecond granularity. While most operators bill in whole seconds or minutes, the millisecond precision in the CDR ensures that no rounding is applied before the data is exported — any rounding happens in the billing engine according to the configured precision parameters. When parsing CDR data, always divide holdTime by 1000 to convert to seconds.

❓ What is the difference between callerE164 and callerAccessE164?

🔄 callerE164 (Field 1) is the caller ID after VOS3000 has applied all prefix transformations and number manipulations. callerAccessE164 (Field 12) is the original incoming caller ID as it was received by VOS3000 before any transformations. The two values differ when VOS3000’s callee rewrite rules, prefix stripping, or caller ID manipulation features modify the number. Similarly, calleeE164 (Field 2) may differ from calleeAccessE164 (Field 13) when the destination number is transformed before routing.

❓ What does a billingMode of -1 mean in the CDR?

💳 A billingMode of -1 means the call was not billed. This applies to calls that bypass the billing engine entirely, including illegal calls from unauthorized IP addresses, calls to toll-free numbers configured under SERVER_BILLING_FREE_E164S, and calls where the billing system could not determine an account to charge. These records still appear in the CDR export (when SS_CDR_RECORD_ILLEGAL is On) for security auditing purposes, but they carry no billing charge.

❓ How do I parse VOS3000 CDR files with different field counts?

🔧 The safest approach is to split each CDR line on the pipe character and check the resulting field count before processing. Lines with 17 fields contain core billing data without PDD metrics. Lines with 19 fields include the PDD columns. Always map fields by position (index), not by counting from the end, since new fields are added at the end of the line. Use the field position reference table in this guide to ensure correct mapping regardless of the field count in your specific VOS3000 version.

❓ Are VOS3000 CDR timestamps in UTC or local time?

⏰ VOS3000 CDR timestamps (startTime and stopTime) are recorded in the server’s local timezone, not UTC. If your server is configured with timezone Asia/Dhaka (UTC+6), all timestamps will be in BST. When integrating CDR data with systems that expect UTC, you must apply the appropriate timezone offset during parsing. Always verify your server’s timezone setting with the date command in SSH before assuming the timezone in your CDR processing logic.

📞 Need Expert Help with VOS3000 CDR Pipe Format?

🔧 Accurate VOS3000 CDR pipe format parsing is the foundation of every billing integration, analytics pipeline, and compliance archive. A single misinterpreted field — especially the millisecond holdTime or the billing mode codes — can cascade into revenue-impacting billing errors. Whether you are building a CDR parser from scratch, troubleshooting field mapping issues, or integrating VOS3000 with an external billing platform, expert guidance ensures your data pipeline is accurate from day one. 📊

💬 WhatsApp: +8801911119966 — Get immediate assistance with VOS3000 CDR pipe format parsing, field mapping, and external system integration. Our team specializes in VOS3000 CDR data extraction, billing system integration, and custom analytics development. 🔧

🔗 Explore related VOS3000 CDR and configuration guides:

📞 Need Professional VOS3000 Setup Support?

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

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

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 CriticalVOS3000 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 CriticalVOS3000 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
VOS3000 2.1.9.07 Release Notes

VOS3000 2.1.9.07 Release Notes – Complete Important Features Upgrade from 2.1.8.05/2.1.8.0

king

VOS3000 2.1.9.07 Release Notes – Complete Important Features Upgrade from 2.1.8.05/2.1.8.0

VOS3000 2.1.8.05 and 2.1.9.07 Version Differences, What is New at VOS3000 2.1.9.07 Version, New Updates of VOS3000 2.1.9.07 version – all contains in this VOS3000 2.1.9.07 Release Notes

This document contains the complete and verified VOS3000 2.1.9.07 Release Notes prepared after a detailed comparison between version 2.1.8.05 and 2.1.9.07 manuals. Every new module, routing logic, billing upgrade, SIP enhancement, security feature and backend architectural improvement has been documented.

For more deep technical tutorials visit: VOS3000 Technical Blog

🆕 1. New Major Sections & Functional Modules

🧾 1.1 Modify CDR (Account Management – 2.4.7)

  • Post-billing correction of charged amount
  • Manual modification of historical CDR charge
  • Administrative billing adjustment control
  • Permission-based modification access

Purpose: Billing correction without database-level manipulation.

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

🌍 1.2 Geofencing (Operation Management – 2.5.7)

Replaces older “Prohibited Media IP” module.

New Capabilities:

  • IP range definition (start IP + count)
  • Signaling IP checking
  • SDP media IP checking
  • RTP actual IP checking

Mode Selection:

  • Ignore
  • Forbidden
  • Allow

Applied At:

  • Global level
  • Routing gateway
  • Mapping gateway
  • Phone management

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

📘 1.3 Functional Scenarios (New Chapter 3)

🔹 3.1 First Usage

Updated wholesale deployment quick-start scenario.

🔹 3.2 Pickup Call Transfer

  • Access code configuration
  • Position definition
  • Association settings
  • Functional logic explanation

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

🧠 1.4 Function Explanation (New Chapter 4.1)

⏱ Network Routing Quality Reserve Time

  • SS_GATEWAY_QUALITY_RESERVE_SEPARATE
  • SS_GATEWAY_QUALITY_RESERVE_TIME

Enables ASR/ACD time-sliced calculation.

🔄 NAT Keep

UDP keep-alive logic to maintain NAT bindings.

⏳ SIP Timer Protocol

Session timer support and related parameters.

📡 Signaling QoS

  • SS_QOS_SIGNAL
  • SS_QOS_RTP

DSCP control for SIP and RTP packets.

🔁 Enable Bilateral Reconciliation

Real-time reconciliation between two VOS platforms with deviation alarm. VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

🛡 2. Security & Anti-Fraud Enhancements

🚫 2.1 Dynamic Malicious Call Blacklist Engine

  • Concurrent caller limit detection
  • Malicious frequency limit detection
  • No-answer attack detection
  • Time-window based analysis
  • Auto blacklist expiration
  • Dynamic blocking logic
  • Concurrency limit parameters
  • Malicious call check interval
  • Blacklist expiration timer

🔐 2.2 Authentication Security Controls

  • Max authentication retry limit
  • Auto suspend after failure
  • Brute-force mitigation logic

📡 3. Real-Time Integration & External Control

🌐 3.1 Call State HTTP Reporting

  • HTTP call state reporting
  • Configurable report IP
  • Configurable report port
  • Retry mechanism
  • Retry interval control

🔀 3.2 External SIP Redirect Server (3xx Support)

  • External routing decision server
  • SIP 3xx redirect integration
  • Selective phone availability

📱 3.3 Phone Service Layer

  • Phone online/offline reporting
  • Dedicated phone service IP & port
  • Offline phone redirect to gateway
  • Phone state monitoring

🔄 4. Call Handling & Transfer Enhancements

☎ 4.1 Advanced Transfer Controls

  • Blind transfer key
  • Attended transfer key
  • Wait-access timeout
  • Remote ring passthrough
  • Transfer cancel key
  • Transfer end key
  • Transfer display customization

🎵 4.2 Auxiliary Ring Tone

  • Local ringback tone playback
  • SS_AUXILIARY_RING_TONE_ACTIVATION_DELAY

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

📊 5. Routing & Gateway Enhancements

🛣 5.1 Real-Time Routing Quality Calculation

  • SS_GATEWAY_QUALITY_CALCULATE

📈 5.2 Routing Strategy

  • Sort by ASR
  • Sort by lowest rate per second

🔁 5.3 Bilateral Reconciliation Controls

  • SERVER_GATEWAY_ROUTE_BILATERAL_RECONCILIATION_LINE
  • SERVER_GATEWAY_BILATERAL_RECONCILIATION_PERIOD

📞 5.4 Caller Number Pool

  • Enable caller number pool
  • Concurrency per number
  • Forwarding caller pool
  • Multiplex control

🚦 5.5 Rate Limiting

New signaling rate control per gateway.

🧾 5.6 SIP Enhancements

  • Stop switching response code
  • Reply address mode selection
  • Request address selection
  • G729 annexb control
  • G723 annexa control
  • Enable timer protocol
  • Enable 100rel
  • Retry-After header support
  • Reason header injection
  • user=phone support
  • Allow Publish
  • Enable local domain name
  • Enable call forward signal
  • SIP OPTIONS online check
  • Ptime adaptive
  • NAT media SDP IP first
  • Invite custom header fields
  • Allow all extra header fields
  • Allow specified extra header fields
  • Support Privacy
  • Recognize call forward signal
  • Replace failed reason mapping
  • Remote ringback mode

🔢 5.7 LRN Handling

  • Eat prefix length
  • Failure action
  • Routing using number
  • Interstate billing prefix
  • Undetermined billing prefix

🎙 5.8 H.323 Enhancements

  • Q.931 ProgressIndicator
  • Caller field selection
  • Callee field selection
  • Send CallProceeding immediately
  • Convert Trying to CallProceeding
  • Convert 183(SDP) to Alerting

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

📂 6. CDR & Reporting Improvements

🧾 6.1 Enhanced CDR Fields

  • Incoming caller
  • Outgoing caller
  • Connect delay (PDD)
  • Continue duration
  • Billing method
  • Package usage duration
  • Package charges
  • Transparent hangup reason

📊 6.2 Reorganized CDR Analysis

  • Mapping Gateway Analysis
  • Routing Gateway Analysis
  • Performance analysis
  • Call analysis
  • Fail analysis
  • Daily call analysis
  • Area analysis
  • Gateway area cross analysis
  • Overall Area analysis

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

💰 7. Billing & Financial Enhancements

💳 7.1 Customer Package (Suite Order System)

  • Subscription packages
  • Effective & expiration control
  • Priority control
  • Free minutes
  • Free amount
  • Minimum consumption
  • Percentage rent
  • Renewal handling rules
  • Failed processing mode selection

📐 7.2 Billing Precision Controls

  • Billing fee precision
  • Billing unit precision
  • Hold-time precision
  • Overdraft prevention advance time
  • Profit formula logic
  • Gateway route prefix billing
  • Forward prefix billing logic

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

🔔 8. Alarm & Monitoring

  • Voice-based notification
  • Passthrough RTP loss rate

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

🖥 9. Major Backend Upgrade – 64 Bit Linux Architecture

Up to version 2.1.8.05 all backend components were based on 32-bit architecture.

Limitations of 32-bit:

  • ~4GB memory ceiling
  • Limited process scalability
  • Lower high-concurrency stability

2.1.9.07 Backend Improvements:

  • Full 64-bit Linux architecture
  • High RAM utilization (32GB / 64GB / 128GB+)
  • Better multi-core CPU usage
  • Improved database caching
  • Higher CPS handling capability
  • Better memory allocation efficiency
  • Improved stability under heavy wholesale traffic
VOS3000 2.1.9.07 sample RPM Installation Files

VOS3000 2.1.9.07 Release Notes is created by AI software from 2 versions user manuals

📊 Complete Comparison Table – VOS3000 2.1.8.05 vs 2.1.9.07

Module / FeatureVOS3000 2.1.8.05VOS3000 2.1.9.07
Backend Architecture32-bit Linux64-bit Linux (High RAM Support)
Modify CDR (Post Billing Correction)Not AvailableAvailable
Geofencing (Advanced IP Control)Basic Prohibited Media IPFull Geofencing (Signaling + SDP + RTP)
Dynamic Malicious Call BlacklistNot AvailableAvailable (Auto Detection Engine)
Concurrent Caller DetectionNoYes
No-Answer Attack DetectionNoYes
Authentication Retry ProtectionBasicAdvanced with Auto Suspend
HTTP Call State ReportingNoYes (Real-Time Push API)
External SIP Redirect Server (3xx)NoYes
Phone Service LayerNoYes (Online/Offline Monitoring)
Real-Time Routing Quality CalculationStatic RoutingASR/ACD Real-Time Calculation
Bilateral ReconciliationNoYes
Caller Number PoolNoYes
Signaling Rate LimitingNoYes
SIP Timer ProtocolLimitedEnhanced
SIP 100rel SupportNoYes
Retry-After HeaderNoYes
Reason Header InjectionNoYes
Privacy Header SupportBasicEnhanced
LRN Advanced HandlingLimitedPrefix + Routing Enhancements
H.323 ProgressIndicatorNoYes
Advanced Transfer ControlsBasicBlind + Attended + Cancel + Display
Auxiliary Ring ToneNoYes
Enhanced CDR Fields (PDD, Package Usage)LimitedExpanded Fields
Structured CDR AnalysisBasicAdvanced Gateway & Area Analytics
Customer Package (Suite Order System)NoYes
Billing Precision ControlLimitedAdvanced Precision Parameters
Profit Formula LogicBasicEnhanced
Voice Alarm SupportNoYes
Passthrough RTP Loss StatisticsNoYes
High RAM SupportLimited (~4GB)32GB / 64GB / 128GB+
High CPS StabilityModerateHigh Performance

❓ FAQ – VOS3000 2.1.9.07 Release Notes

1. What is the biggest upgrade in VOS3000 2.1.9.07?

The most significant upgrade is the migration to a 64-bit Linux backend architecture, enabling high RAM utilization, improved concurrency handling, and enhanced system stability for wholesale VoIP deployments.

2. Does VOS3000 2.1.9.07 support real-time routing optimization?

Yes. The new real-time routing quality calculation (ASR/ACD based) dynamically sorts gateways based on performance metrics.

3. What is the purpose of the Modify CDR feature?

Modify CDR allows administrators to adjust historical billing charges without directly manipulating the database, improving operational safety and billing correction flexibility.

4. How does the new Geofencing system improve security?

Geofencing validates signaling IP, SDP IP, and actual RTP IP. It can Allow, Ignore, or Block calls based on defined IP ranges, significantly improving fraud prevention.

5. Does this version include anti-fraud protection?

Yes. It introduces a dynamic malicious call blacklist engine with concurrent call detection, frequency monitoring, no-answer attack detection, and automatic blacklist expiration.

6. Can VOS3000 2.1.9.07 integrate with CRM or external billing systems?

Yes. Through HTTP Call State Reporting and External SIP Redirect Server support, real-time integration with CRM, monitoring, and billing platforms is possible.

7. Is bilateral reconciliation supported?

Yes. Two VOS platforms can now perform real-time reconciliation with deviation alarms to prevent financial mismatches.

8. Does 2.1.9.07 improve SIP interoperability?

Yes. It adds support for 100rel, Retry-After, Reason header injection, Privacy handling, advanced NAT processing, and SIP timer protocol enhancements.

9. What billing improvements are included?

The Suite Order System introduces subscription packages, free minutes, minimum consumption, percentage rent billing, and advanced precision control for billing fees and units.

10. Is VOS3000 2.1.9.07 suitable for high-volume wholesale VoIP traffic?

Yes. With 64-bit architecture, improved routing intelligence, anti-fraud engine, and high RAM utilization, it is significantly more stable under heavy traffic compared to 2.1.8.x.

📥 Official Resources

VOS3000 Technical Blog: https://www.vos3000.com/blog/vos3000
Official Blog: https://www.vos3000.com/blog/
Downloads & Manuals: https://www.vos3000.com/downloads.php
Advanced Security Guides: https://multahost.com/blog/

📞 Contact for VOS3000 Hosting

VOS3000 2.1.9.07 One Time Installation / Hosted (Dedicated Server Only) Available!

📲 WhatsApp: +8801911119966

Direct Link: wa.me/+8801911119966

🌍 China | Hong Kong | Vietnam | Thailand Servers Available

More technical articles:
👉 VOS3000 Technical Blog

VOS3000 Installation, VOS3000 Server, VOS3000 SoftSwitch, VOS3000 Switch, VOS3000, VOS3000 Pricem VOS3000 Web, VOS3000 API, VOS3000 Rent, VOS3000 Manual, VOS3000 Downloads, VOS3000 VoIP, VOS3000 Carrier Switch, VOS3000, VOS3000 Login, VOS3000 Monitoring, VOS3000 Performance Metrics, VOS3000 Call Routing, VOS3000 Security, VOS3000 Web Manager, VOS3000 Versions, VOS3000 BillingVOS3000 Monitoring,VOS3000 Capacity, VOS3000 Billing System, VOS3000 License,VOS3000 Installation, VOS3000 Server, VOS3000 SoftSwitch, VOS3000 Switch, VOS3000, VOS3000 Pricem VOS3000 Web, VOS3000 API, VOS3000 Rent, VOS3000 Manual, VOS3000 Downloads, VOS3000 VoIP, VOS3000 Carrier Switch, VOS3000, VOS3000 Login, VOS3000 Monitoring, VOS3000 Performance Metrics, VOS3000 Call Routing, VOS3000 Security, VOS3000 Web Manager, VOS3000 Versions, VOS3000 BillingVOS3000 Monitoring,VOS3000 Capacity, VOS3000 Billing System, VOS3000 License, Mobile Apps for VOS3000, VOS3000 Mobile Apps, Mobile Apps, VOS3000 Apps, Android VOS3000, VOS3000 in IOS, Manual for VOS3000, VOS3000 Manual, Manual VOS3000, Reference Manual VOS3000, User Manual VOS3000, VOS安装, VOS3000 Security, VOS3000 托管VOS3000 Installation, VOS3000 Server, VOS3000 SoftSwitch, VOS3000 Switch, VOS3000, VOS3000 Pricem VOS3000 Web, VOS3000 API, VOS3000 Rent, VOS3000 Manual, VOS3000 Downloads, VOS3000 VoIP, VOS3000 Carrier Switch, VOS3000, VOS3000 Login, VOS3000 Monitoring, VOS3000 Performance Metrics, VOS3000 Call Routing, VOS3000 Security, VOS3000 Web Manager, VOS3000 Versions, VOS3000 BillingVOS3000 Monitoring,VOS3000 Capacity, VOS3000 Billing System, VOS3000 License,VOS3000 Installation, VOS3000 Server, VOS3000 SoftSwitch, VOS3000 Switch, VOS3000, VOS3000 Pricem VOS3000 Web, VOS3000 API, VOS3000 Rent, VOS3000 Manual, VOS3000 Downloads, VOS3000 VoIP, VOS3000 Carrier Switch, VOS3000, VOS3000 Login, VOS3000 Monitoring, VOS3000 Performance Metrics, VOS3000 Call Routing, VOS3000 Security, VOS3000 Web Manager, VOS3000 Versions, VOS3000 BillingVOS3000 Monitoring,VOS3000 Capacity, VOS3000 Billing System, VOS3000 License, Mobile Apps for VOS3000, VOS3000 Mobile Apps, Mobile Apps, VOS3000 Apps, Android VOS3000, VOS3000 in IOS, Manual for VOS3000, VOS3000 Manual, Manual VOS3000, Reference Manual VOS3000, User Manual VOS3000, VOS安装, VOS3000 Security, VOS3000 托管VOS3000 Installation, VOS3000 Server, VOS3000 SoftSwitch, VOS3000 Switch, VOS3000, VOS3000 Pricem VOS3000 Web, VOS3000 API, VOS3000 Rent, VOS3000 Manual, VOS3000 Downloads, VOS3000 VoIP, VOS3000 Carrier Switch, VOS3000, VOS3000 Login, VOS3000 Monitoring, VOS3000 Performance Metrics, VOS3000 Call Routing, VOS3000 Security, VOS3000 Web Manager, VOS3000 Versions, VOS3000 BillingVOS3000 Monitoring,VOS3000 Capacity, VOS3000 Billing System, VOS3000 License,VOS3000 Installation, VOS3000 Server, VOS3000 SoftSwitch, VOS3000 Switch, VOS3000, VOS3000 Pricem VOS3000 Web, VOS3000 API, VOS3000 Rent, VOS3000 Manual, VOS3000 Downloads, VOS3000 VoIP, VOS3000 Carrier Switch, VOS3000, VOS3000 Login, VOS3000 Monitoring, VOS3000 Performance Metrics, VOS3000 Call Routing, VOS3000 Security, VOS3000 Web Manager, VOS3000 Versions, VOS3000 BillingVOS3000 Monitoring,VOS3000 Capacity, VOS3000 Billing System, VOS3000 License, Mobile Apps for VOS3000, VOS3000 Mobile Apps, Mobile Apps, VOS3000 Apps, Android VOS3000, VOS3000 in IOS, Manual for VOS3000, VOS3000 Manual, Manual VOS3000, Reference Manual VOS3000, User Manual VOS3000, VOS安装, VOS3000 Security, VOS3000 托管