Solución de problemas de configuración de llamadas con VTR y VTRI

Actualizado:31 de enero de 2023

ID del documento:220179

Lenguaje no discriminatorio

El conjunto de documentos para este producto aspira al uso de un lenguaje no discriminatorio. A los fines de esta documentación, "no discriminatorio" se refiere al lenguaje que no implica discriminación por motivos de edad, discapacidad, género, identidad de raza, identidad étnica, orientación sexual, nivel socioeconómico e interseccionalidad. Puede haber excepciones en la documentación debido al lenguaje que se encuentra ya en las interfaces de usuario del software del producto, el lenguaje utilizado en función de la documentación de la RFP o el lenguaje utilizado por un producto de terceros al que se hace referencia. Obtenga más información sobre cómo Cisco utiliza el lenguaje inclusivo.

Acerca de esta traducción

Cisco ha traducido este documento combinando la traducción automática y los recursos humanos a fin de ofrecer a nuestros usuarios en todo el mundo contenido en su propio idioma. Tenga en cuenta que incluso la mejor traducción automática podría no ser tan precisa como la proporcionada por un traductor profesional. Cisco Systems, Inc. no asume ninguna responsabilidad por la precisión de estas traducciones y recomienda remitirse siempre al documento original escrito en inglés (insertar vínculo URL).

Contenido

Introducción

Antecedentes

Prerequisites

Requirements

Componentes Utilizados

Uso de la herramienta VTR(I)

Ejecute la herramienta VTR(I) Tool desde la CLI

Ejecución de la herramienta VTR(I) desde la interfaz gráfica de usuario web

Desglose de las salidas del VTR(I)

Parámetros de SIP Invite

Información del autor

Información de llamada de origen

Resultado de traducción de origen

Información de finalización de llamada

Información del tratamiento

Marcas de tiempo

Resultado

Topología de red y flujo de llamadas

Escenarios de llamada

Situación 1: llamada correcta

Situación 2: llamada rechazada por el servicio de aceptación selectiva de llamadas

Situación 3: llamada a un número no asignado

Introducción

En este documento se describe cómo utilizar la herramienta Verificar traducción y routing (VTR) en el servidor de aplicaciones (AS) para solucionar problemas comunes de configuración de llamadas.

Antecedentes

BroadWorks Application Server tiene dos herramientas integradas que se pueden utilizar para solucionar problemas de configuración de llamadas: VTR y Verify Translation and Routing INVITE (VTRI). El propósito de estas dos herramientas es el mismo, la diferencia está en la entrada de comandos:

El VTR toma los datos de la persona que llama (como la ID de usuario o el número de teléfono), así como el número de destino como entrada,
VTRI acepta el mensaje SIP INVITE como entrada.

Precaución: Los comandos VTR y VTRI también están disponibles en el servidor de red (NS), pero la estructura de salida es diferente de la del AS. Este documento se centra en AS VTR(I) y no puede utilizarse como referencia durante el trabajo con NS VTR(I).

La referencia completa de comandos para el VTR AS está disponible en la Guía de Administración del VTR de Application Server.

Prerequisites

Requirements

Cisco recomienda que tenga conocimiento de lo siguiente:

Señalización del protocolo de inicio de sesión (SIP).
Mecanismo de procesamiento de llamadas del servidor de aplicaciones, junto con los servicios disponibles y su configuración.

Componentes Utilizados

La información de este documento se basa en BroadWorks AS versión R24. Sin embargo, el comportamiento para otras versiones de software es similar.

La información que contiene este documento se creó a partir de los dispositivos en un ambiente de laboratorio específico. Todos los dispositivos que se utilizan en este documento se pusieron en funcionamiento con una configuración verificada (predeterminada). Si tiene una red en vivo, asegúrese de entender el posible impacto de cualquier comando.

Uso de la herramienta VTR(I)

El análisis del magnetoscopio se puede activar tanto desde la interfaz de línea de comandos (CLI) como desde la interfaz web.

Ejecute la herramienta VTR(I) Tool desde la CLI

Para ejecutar el VTR desde la GUI web, siga estos pasos:

Paso 1. Inicie sesión en BroadWorks CLI con sus credenciales bwadmin.

Paso 2. Inicie BroadWorks CLI y navegue hasta AS_CLI/ASDiagnostic/Diag:

AS_CLI> cd ASDiagnostic/Diag

Paso 3. Para utilizar VTRI, ejecute el comando vtri, seguido por SIP INVITE, y el carácter de punto en la nueva línea. Por ejemplo:

AS_CLI/ASDiagnostic/Diag> vtri
Enter a SIP message. When complete, enter a single period (.) on a line to start verifying the translation.
INVITE sip:2012@mleus.lab SIP/2.0
Via: SIP/2.0/UDP 10.61.205.219:58300;rport;branch=z9hG4bKPjgINPvPUvoBT57iTOBPsgCfEqE5GX1aj7
Max-Forwards: 70
From: "Marek Leus" 
     
     
       ;tag=6fU.VlLrWc6WI3JU8jWKS.25yeoWEhpc To: sip:2012@mleus.lab Contact: "Marek Leus" 
      
        Call-ID: dTUVBWON9UjmftpGCOoJzhLfbajBm11C CSeq: 6492 INVITE Route: 
       
         Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, norefersub User-Agent: Telephone 1.6 Content-Type: application/sdp Content-Length: 480 v=0 o=- 3883737105 3883737105 IN IP4 10.61.205.219 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 4012 RTP/AVP 96 9 8 0 101 102 c=IN IP4 10.61.205.219 b=TIAS:96000 a=rtcp:4013 IN IP4 10.61.205.219 a=sendrecv a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=rtpmap:102 telephone-event/8000 a=fmtp:102 0-16 a=ssrc:2039250127 cname:43ec7f3b5b951d53 .

Paso 4. Para utilizar el VTR, ejecute el comando vtr, seguido de los detalles de la persona que llama y el destino. Por ejemplo:

# Command reference:
AS_CLI/ASDiagnostic/Diag> h vtr
This command is used to perform a test call and see the routing results. Please
be careful when performing test calls, it may have an impact on existing real
calls or cause user migration.

Parameters description:
origType   : The type of origination used to trigger the VTR request.
linePort   : The lineport of the originating user.
bwphone    : The originating BroadWorks user phone number.
pstnphone  : The originating PSTN user phone number.
userId     : The originating BroadWorks user Id.
url        : The originating url.
destination: The called user, number or URI.
option     : Additional vtr options.
contact    : The contact URL to use for the test call.
diversion  : The diversion URL to use for the test call.

======================================================================
vtr
    
     
     
       , Choice = {linePort, bwphone, pstnphone, userId, url} 
      
        , String {1 to 80 characters} 
       
         , String {1 to 17 characters} 
        
          , String {1 to 17 characters} 
         
           , String {2 to 161 characters} 
          
            , String {2 to 161 characters} 
           
             , String {1 to 161 characters} [

Ejecución de la herramienta VTR(I) desde la interfaz gráfica de usuario web

Para ejecutar el VTR desde la GUI web, siga estos pasos:

Paso 1. Navegue hasta la página https://<AS_FQDN>/Login e inicie sesión en la interfaz web de AS.

Paso 2. Vaya a System > Utilities > Verify Translation and Routing.

Paso 3. Para utilizar VTRI, haga clic en el botón de opción SIP Message y pegue el mensaje SIP INVITE en el campo de entrada. A continuación, haga clic en el enlace Execute VTR request:

Verify Translation and Routing

Paso 4. Para utilizar el VTR, haga clic en el botón de opción Parameters y rellene todos los campos requeridos. A continuación, haga clic en el enlace Execute VTR request:

Verify Translation and Routing Parameters

Desglose de las salidas del VTR(I)

El formato de los resultados de los magnetoscopios y VTRI es similar. Consta de ocho secciones:

Parámetros o SIP INVITE (sólo presente en el VTR; no es necesario en el VTRI porque funciona en mensajes SIP reales).
Información del autor.
Información de la llamada de origen.
Resultado de traducción de origen.
Finalizando información de llamada.
Información del tratamiento
Grupo fecha/hora.
Resultado.

Nota: Todas las salidas de VTR de este documento se basan en la salida del comando vtr userId <user_id> <destination_number>, a menos que se indique lo contrario.

Parámetros de SIP Invite

La primera parte del resultado del magnetoscopio es SIP INVITE o los parámetros utilizados para simular la llamada. Esta sección no está visible si proporciona SIP INVITE explícitamente (es decir, si utiliza VTRI).

Se genera una SIP INVITE cuando el origen se establece en una URL o en una línea/puerto. Por ejemplo:

AS_CLI/ASDiagnostic/Diag> vtr linePort 5403362011@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following SIP INVITE to run VTRI command with Lineport
 -------------------------------------------------------
INVITE sip:2012@10.48.93.126 SIP/2.0
Via:SIP/2.0/UDP 127.0.0.1:5061;branch=vtr-unique-via-branch-26
From:"VTR Calling Name"
     
     
       ;tag=26 To:"VTR Called Name" 
      
        Call-ID:26 CSeq:26 INVITE Contact: 
       
         Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REGISTER,UPDATE Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv

Los parámetros se muestran si el origen está configurado en User ID (ID de usuario) o Phone (teléfono bwphone y pstnphone). Por ejemplo:

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 16
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint          5403362011@mleus.lab

Información del autor

Esta sección muestra información sobre la parte de origen (llamante). Si la persona que llama es un usuario local de BroadWorks, se muestra información detallada sobre el usuario. Por ejemplo:

=====================================================
===========     ORIGINATOR INFO   ===================
=====================================================
[Orig-Id]	VTR Short form trigger.
[Orig-Id]	No Endpoint.
[Orig-Id]	Originating user type: BroadWorks
[Orig-Id]	User Info
[Orig-Id]	User Id                      = ngnuserB1@mleus.lab
[Orig-Id]	User Uid                     = 110439218
[Orig-Id]	Group Id                     = ngngroupB1
[Orig-Id]	Service Provider Id          = ngnentB1
[Orig-Id]	Reseller Id                  = null
[Orig-Id]	ASCII First Name             = Marek
[Orig-Id]	ASCII Last Name              = Leus
[Orig-Id]	Unicode First Name           = Marek
[Orig-Id]	Unicode Last Name            = Leus
[Orig-Id]	Country Code                 = 1
[Orig-Id]	User Type                    = User
[Orig-Id]	Trunk User Type              = BroadWorks Regular User
[Orig-Id]	(0) Address type             = main
[Orig-Id]	(0) dn                       = +15403362011
[Orig-Id]	(0) extension                = 2011
[Orig-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Orig-Id]	beingRemoved                 = false
[Orig-Id]	configurable CLID            = 5403362010
[Orig-Id]	synchronizationASRSentToNS   = false

Información de llamada de origen

En esta sección, la progresión de los eventos en el lado de la persona que llama de la llamada se muestra en orden. Si la persona que llama es un usuario de Cisco BroadWorks, éste es el lugar donde se ejecutan los servicios asignados. Por ejemplo:

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	Resuming event processing after TranslationServiceOrigInstance
[Orig/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
(...)
# Output omitted for clarity
(...)
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/ReleaseWithCauseHandler]	Post Processing RWC for Call.

Resultado de traducción de origen

En esta sección se proporciona información sobre una traducción solicitada al servidor de red Cisco BroadWorks. Si se requiere una traducción de red, se muestra información sobre la política de plan de marcación utilizada. También muestra los mensajes SIP intercambiados con este fin. Por ejemplo:

=====================================================
===========  ORIGINATING TRANSLATION RESULT =========
=====================================================
[Orig-Xlation/DialPlanPolicy]	--Dial Plan Policy Information--
[Orig-Xlation/DialPlanPolicy]	requiresAccessCodeForPublicCalls = false
[Orig-Xlation/DialPlanPolicy]	allowE164PublicCalls             = false
[Orig-Xlation/DialPlanPolicy]	privateDigitMap                  =
[Orig-Xlation/DialPlanPolicy]	publicDigitMap                   = ([2-9]11|[0-1][2-9]11|0[#T]|00|01[2-9]xx.[#T]|*xx|011x.[#T]|[0-1]xxxxxxx[#T]|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxxxx[#T]|101xxxx.[#T]|11|[2-9][#T])
[Orig-Xlation/DialPlanPolicy]	preferE164FormatForCallbackSvcs  = false

[Orig-Xlation/NetworkUsagePolicy]	Network Usage Policy is - do not force all calls to network -
[Orig-Xlation/NetworkServerINVITE]	Sending INVITE event to network server for Translation Service Originating Side client
[Orig-Xlation/NetworkServerINVITE]	Endpoint Id: callhalf-60487:0
    udp 1128 SIP Bytes OUT to 10.48.93.128:5060
    INVITE sip:2014@10.48.93.128;user=phone;transport=udp SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564-
    From:"Marek Leus"
     
     
       ;tag=1152157837-1674811757564- To: 
      
        Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Contact: 
       
         P-Asserted-Identity:"Marek Leus" 
        
          Privacy:none X-BroadWorks-Correlation-Info:be8fde53-9ba5-4fc4-a788-ee426ed1fe90 Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY Supported: Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [Orig-Xlation/NS-RESPONSE] Got Network Server response for Translation Service Originating Side client udp 394 SIP Bytes IN from 10.48.93.128:49109 SIP/2.0 404 Not found Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564- From:"Marek Leus" 
         
           ;tag=1152157837-1674811757564- To: 
          
            ;tag=1006595920-1674811749882 Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Content-Length:0 [Orig-Xlation/TranslationManager] Translation Client: Translation Service Originating Side call Id is callhalf-60487:0 [Orig-Xlation/TranslationManager] === TranslationResult === [Orig-Xlation/TranslationManager] callType Network [Orig-Xlation/TranslationManager] address 2014 [Orig-Xlation/TranslationManager] addressType main [Orig-Xlation/TranslationManager] isServiceCode false [Orig-Xlation/TranslationManager] sc8Translated false [Orig-Xlation/TranslationManager] sc100Translated false [Orig-Xlation/TranslationManager] oacTranslated false [Orig-Xlation/TranslationManager] carrierPrefixTranslated false [Orig-Xlation/TranslationManager] intraSP false [Orig-Xlation/TranslationManager] alias false [Orig-Xlation/TranslationManager] preExtEmergencyRtgAK null [Orig-Xlation/TranslationManager] === Carrier Info === [Orig-Xlation/TranslationManager] ;csel=noind

Información de finalización de llamada

Si la llamada tiene un destino válido, se muestra información sobre su identidad y los eventos en el bus de servicio de terminación. De forma similar a la sección de información de llamada de origen, se trata de un lugar en el que se ejecutan los servicios asignados del usuario de destino. También muestra la SIP INVITE que se envía al destino. Por ejemplo:

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term/CallManagerServiceBus]	CallManagerId is callhalf-60459
[Term/CallManagerServiceBus]	 === Routing TerminationEvent on the Call Manager bus ===

[Term/Term-Id]	Terminating user type: BroadWorks
[Term/Term-Id]	User Info
[Term/Term-Id]	User Id                      = ngnuserB2@mleus.lab
[Term/Term-Id]	User Uid                     = 156778964
[Term/Term-Id]	Group Id                     = ngngroupB1
[Term/Term-Id]	Service Provider Id          = ngnentB1
[Term/Term-Id]	Reseller Id                  = null
[Term/Term-Id]	ASCII First Name             = John
[Term/Term-Id]	ASCII Last Name              = Doe
[Term/Term-Id]	Unicode First Name           = John
[Term/Term-Id]	Unicode Last Name            = Doe
[Term/Term-Id]	Country Code                 = 1
[Term/Term-Id]	User Type                    = User
[Term/Term-Id]	Trunk User Type              = BroadWorks Regular User
[Term/Term-Id]	(0) Address type             = main
[Term/Term-Id]	(0) dn                       = +15403362012
[Term/Term-Id]	(0) extension                = 2012
[Term/Term-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Term/Term-Id]	beingRemoved                 = false
[Term/Term-Id]	configurable CLID            = 5403362010
[Term/Term-Id]	synchronizationASRSentToNS   = false

[Term/CallServiceBus]	CallId is callhalf-60459:0
[Term/CallServiceBus]	 === Routing InvitationEvent on the Terminating Call bus ===

[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	NumberPortabilityQueryServiceTermInstance has processed the event...continue
(...)
# Output omitted for clarity
(...)
[Term/CallManagerServiceBus]	RingTimeoutServiceInstance has processed the event...continue
[Term/SipINVITE]	 Outgoing resulting INVITE for Endpoint Id: callhalf-60459:0
    udp 1195 SIP Bytes OUT to 10.61.71.93:62388
    INVITE sip:5403362012@10.61.71.93:62388;transport=UDP;rinstance=c71abb15b3ff5d4a SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.61.71.93V62388-0-960978525-1694279432-1674811718841-
    From:"Marek Leus"
     
     
       ;tag=1694279432-1674811718841- To:"John Doe" 
      
        Call-ID:BW102838841270123-1135433227@10.48.93.126 CSeq:960978525 INVITE Contact: 
       
         Supported:100rel Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE Call-Info: 
        
          ;appearance-index=1 Recv-Info:x-broadworks-client-session-info Accept:application/media_control+xml,application/sdp,multipart/mixed Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv

Información del tratamiento

Esta sección solo está presente para las llamadas que no se realizan correctamente. Ofrece una explicación detallada del motivo del fallo de la llamada. También enumera qué anuncio/tono reproduce el servidor de medios si la llamada falla por ese motivo. Por ejemplo:

=====================================================
===========  TREATMENT INFORMATION          =========
=====================================================
[Treatment/TreatmentsService]	Treatment service processing RWC. Release Cause is FORBIDDEN
[Treatment/TreatmentsService]	defaultAnnouncement isTrtCallFailure.wav
[Treatment/TreatmentsService]	defaultTone is reorder-pcmu.wav

[Treatment/TreatmentsService]	Configurable Treatment NOT used but specific audio treatment files have been provided
[Treatment/TreatmentsService]	audioAnnouncement(s):
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/silence10s.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav

Marcas de tiempo

Las marcas de tiempo de las llamadas se pueden utilizar para correlacionar eventos en VTRI con registros XSL.

Resultado

El resultado final de la llamada de prueba. Los valores posibles son:

Permitido: la llamada se puede extender correctamente a la persona remota. El mensaje INVITE saliente se muestra en la sección Terminating Call Info (Información de finalización de llamada).
Bloqueada: la configuración de la llamada se bloqueó debido a alguna directiva o a una condición anormal. El motivo puede estar en el lado del origen o en el lado de la terminación (dependiendo del motivo).
Redirigido: la llamada se redirigió sin condiciones. El destino de redirección se identifica y se muestra en el informe.
Tiempo de espera: algo impidió que la llamada de prueba finalizara correctamente y se alcanzó el límite de tiempo interno de 10 segundos. Se puede utilizar la información disponible, pero no se muestra el resultado final.
Medios: se ha iniciado un componente multimedia de forma interna (normalmente una respuesta de voz interactiva [IVR]) para reproducir un anuncio específico o recopilar dígitos. Las llamadas de prueba se detienen en este caso, pero el informe muestra los eventos hasta este punto.

Topología de red y flujo de llamadas

Para mayor simplicidad, en este documento se utiliza un escenario de llamadas básico:

Las aplicaciones de softphone se registran directamente en AS.
Todos los usuarios están en el mismo grupo.
No se ha utilizado ni el desvío ni la redirección de llamadas.

Escenarios de llamada

Este documento cubre tres escenarios donde un usuario con la extensión 2011 marca en secuencia:

Extensión 2012, asignada a un dispositivo registrado.
Extensión 2012, que está asignada a un dispositivo registrado, pero el servicio de aceptación selectiva de llamadas está configurado para rechazar la llamada desde 2011 como se muestra en esta captura de pantalla:
Extensión 2014, que no está asignada a ningún usuario.

Situación 1: llamada correcta

En esta situación, un usuario local marca a otro usuario local por su extensión. Veamos la salida del magnetoscopio de esta llamada para obtener más información:

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 12
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint          5403362011@mleus.lab

En la primera sección de los resultados del magnetoscopio, puede ver cómo AS asigna los parámetros del comando vtr a las URL de SIP:

Persona que llama: 5403362011@mleus.lab
Destino: 2012@10.48.93.126:5060

=====================================================
===========     ORIGINATOR INFO   ===================
=====================================================
[Orig-Id]	VTR Short form trigger.
[Orig-Id]	No Endpoint.
[Orig-Id]	Originating user type: BroadWorks
[Orig-Id]	User Info
[Orig-Id]	User Id                      = ngnuserB1@mleus.lab
[Orig-Id]	User Uid                     = 110439218
[Orig-Id]	Group Id                     = ngngroupB1
[Orig-Id]	Service Provider Id          = ngnentB1
[Orig-Id]	Reseller Id                  = null
[Orig-Id]	ASCII First Name             = Marek
[Orig-Id]	ASCII Last Name              = Leus
[Orig-Id]	Unicode First Name           = Marek
[Orig-Id]	Unicode Last Name            = Leus
[Orig-Id]	Country Code                 = 1
[Orig-Id]	User Type                    = User
[Orig-Id]	Trunk User Type              = BroadWorks Regular User
[Orig-Id]	(0) Address type             = main
[Orig-Id]	(0) dn                       = +15403362011
[Orig-Id]	(0) extension                = 2011
[Orig-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Orig-Id]	beingRemoved                 = false
[Orig-Id]	configurable CLID            = 5403362010
[Orig-Id]	synchronizationASRSentToNS   = false

A continuación, como la persona que llama es local, se imprimen todos los detalles sobre el usuario. En esta sección, puede saber cuáles son el nombre del usuario (Marek) y el apellido (Leus), cuál es su extensión (2011), así como cuál es el número completo (+15403362011) y a qué empresa/grupo (ngnentB1/ngngroupB1) pertenecen.

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60455:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60455:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	Resuming event processing after TranslationServiceOrigInstance
[Orig/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ReturnCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LNDServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LocationControlServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validating origination. Using call type Group
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validation returned disposition Allow - OCP call type: Group

[Orig/CallServiceBus]	ACRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	NPAnnouncementServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFAlwaysFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCFFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DNDFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CPCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ClassmarkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VAOCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ExecutiveAssistantOrigServiceInstance has processed the event...continue
[Orig/VTR_FINAL]	Triggering report.

Dado que se trata de un usuario sencillo sin servicios habilitados, no hay mucha información en la sección Información de la llamada de origen. El AS comprueba un servicio tras otro y, finalmente, pasa a la siguiente sección del VTR. También define esta llamada como una llamada de grupo. Si desea correlacionar este análisis de VTR con registros XSL, puede extraer el ID de la mitad de la llamada (callhalf-60455) de esta sección y, a continuación, utilizarlo para buscar esta llamada en los archivos de registro. Por ejemplo:

bwadmin@as1.mleus.lab$ less XSLog2023.01.27-00.00.00.txt | grep callhalf-60455
2023.01.27 10:28:38:819 CET | Info       | Sip | BCCT Worker #1 | 3104778 | +15403362011 | callhalf-60455
	$ new CHSS > +15403362011 >  > callhalf-60455
2023.01.27 10:28:38:819 CET | FieldDebug | StateReplication | BCCT Worker #1 | 3104779 | +15403362011 | callhalf-60455
2023.01.27 10:28:38:821 CET | Info       | CallP | Call Half Input Adapter 5 | 3104780 | Call Manager | +15403362011 | ngngroupB1 | callhalf-60455

La siguiente sección es Resultado de la traducción de origen:

=====================================================
===========  ORIGINATING TRANSLATION RESULT =========
=====================================================
[Orig-Xlation/DialPlanPolicy]	--Dial Plan Policy Information--
[Orig-Xlation/DialPlanPolicy]	requiresAccessCodeForPublicCalls = false
[Orig-Xlation/DialPlanPolicy]	allowE164PublicCalls             = false
[Orig-Xlation/DialPlanPolicy]	privateDigitMap                  =
[Orig-Xlation/DialPlanPolicy]	publicDigitMap                   = ([2-9]11|[0-1][2-9]11|0[#T]|00|01[2-9]xx.[#T]|*xx|011x.[#T]|[0-1]xxxxxxx[#T]|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxxxx[#T]|101xxxx.[#T]|11|[2-9][#T])
[Orig-Xlation/DialPlanPolicy]	preferE164FormatForCallbackSvcs  = false

[Orig-Xlation/NetworkUsagePolicy]	Network Usage Policy is - do not force all calls to network -
[Orig-Xlation/TranslationManager]	Translation Client: Translation Service Originating Side call Id is callhalf-60455:0
[Orig-Xlation/TranslationManager]	  === TranslationResult ===
[Orig-Xlation/TranslationManager]	callType             Group
[Orig-Xlation/TranslationManager]	address             2012
[Orig-Xlation/TranslationManager]	destination uid      156778964
[Orig-Xlation/TranslationManager]	destination user Id  ngnuserB2@mleus.lab
[Orig-Xlation/TranslationManager]	addressType          main
[Orig-Xlation/TranslationManager]	originalAddress      2012
[Orig-Xlation/TranslationManager]	dgcAlternateAddress  2012
[Orig-Xlation/TranslationManager]	isServiceCode           false
[Orig-Xlation/TranslationManager]	sc8Translated           false
[Orig-Xlation/TranslationManager]	sc100Translated         false
[Orig-Xlation/TranslationManager]	oacTranslated           false
[Orig-Xlation/TranslationManager]	carrierPrefixTranslated false
[Orig-Xlation/TranslationManager]	intraSP                 false
[Orig-Xlation/TranslationManager]	alias                   false
[Orig-Xlation/TranslationManager]	preExtEmergencyRtgAK null

En esta sección puede obtener información sobre el plan de marcación que se aplica a una llamada determinada. Para esta llamada, el resultado informa que es una llamada dentro del grupo y se dirige al usuario ngnuserB2@mleus.lab. En la siguiente sección se ofrece más información sobre este usuario:

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term/CallManagerServiceBus]	CallManagerId is callhalf-60459
[Term/CallManagerServiceBus]	 === Routing TerminationEvent on the Call Manager bus ===

[Term/Term-Id]	Terminating user type: BroadWorks
[Term/Term-Id]	User Info
[Term/Term-Id]	User Id                      = ngnuserB2@mleus.lab
[Term/Term-Id]	User Uid                     = 156778964
[Term/Term-Id]	Group Id                     = ngngroupB1
[Term/Term-Id]	Service Provider Id          = ngnentB1
[Term/Term-Id]	Reseller Id                  = null
[Term/Term-Id]	ASCII First Name             = John
[Term/Term-Id]	ASCII Last Name              = Doe
[Term/Term-Id]	Unicode First Name           = John
[Term/Term-Id]	Unicode Last Name            = Doe
[Term/Term-Id]	Country Code                 = 1
[Term/Term-Id]	User Type                    = User
[Term/Term-Id]	Trunk User Type              = BroadWorks Regular User
[Term/Term-Id]	(0) Address type             = main
[Term/Term-Id]	(0) dn                       = +15403362012
[Term/Term-Id]	(0) extension                = 2012
[Term/Term-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Term/Term-Id]	beingRemoved                 = false
[Term/Term-Id]	configurable CLID            = 5403362010
[Term/Term-Id]	synchronizationASRSentToNS   = false

En esta parte, aprenderá los mismos detalles sobre el destino de la llamada que anteriormente para la persona que llama: nombre y apellidos (Juan Pérez), extensión (2012) y número completo (+15403362012), así como la empresa/grupo (ngnentB1/ngngroupB1).

[Term/CallServiceBus]	CallId is callhalf-60459:0
[Term/CallServiceBus]	 === Routing InvitationEvent on the Terminating Call bus ===

[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	NumberPortabilityQueryServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	CMServiceInstance has processed the event...continue
[Term/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Term/CallServiceBus]	OCPTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	ICPServiceInstance has processed the event...continue
[Term/CallServiceBus]	ACRServiceInstance has processed the event...continue
[Term/CallServiceBus/SCRServiceInstance]	Criteria Set(s) evaluated but not triggered:
[Term/CallServiceBus/SCRServiceInstance]
[Term/CallServiceBus/SCRServiceInstance]	Criteria Set:
[Term/CallServiceBus/SCRServiceInstance]	description: Reject_all
[Term/CallServiceBus/SCRServiceInstance]	active: false
[Term/CallServiceBus/SCRServiceInstance]	blackListFlag: false
[Term/CallServiceBus/SCRServiceInstance]	ScheduleCriteria
[Term/CallServiceBus/SCRServiceInstance]	- No Schedule associated
[Term/CallServiceBus/SCRServiceInstance]	- inScheduleRightNow: true
[Term/CallServiceBus/SCRServiceInstance]	CallingPartyAddressCriteria
[Term/CallServiceBus/SCRServiceInstance]	Any Address
[Term/CallServiceBus/SCRServiceInstance]	CallToCriteria
[Term/CallServiceBus/SCRServiceInstance]	CallTo matches ANY

[Term/CallServiceBus]	SCRServiceInstance has processed the event...continue
[Term/CallServiceBus]	PTTTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	LNRServiceInstance has processed the event...continue
[Term/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Term/CallServiceBus]	GroupNightForwardingServiceInstance has processed the event...continue
[Term/CallServiceBus]	FaxMessagingServiceInstance has processed the event...continue
[Term/CallServiceBus]	SCFServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFAlwaysTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	DNDServiceInstance has processed the event...continue
[Term/CallServiceBus]	PersonalAssistantServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallWaitingTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	PreAlertingAnnouncementServiceInstance has processed the event...continue
[Term/CallServiceBus]	AnswerTimerServiceInstance has processed the event...continue
[Term/CallServiceBus]	VMServiceInstance has processed the event...continue
[Term/CallServiceBus]	RedirectionServiceInstance has processed the event...continue
[Term/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
[Term/CallServiceBus]	ExecutiveTermServiceInstance has processed the event...continue
[Term/CallServiceBus]	ExecutiveAssistantTermServiceInstance has processed the event...continue

Más adelante en esta sección, se comprueban todos los servicios. Solo hay un servicio asignado a este usuario (Aceptación selectiva de llamadas), pero el único conjunto de criterios (Reject_2011) está inactivo. Por lo tanto, no se activa y el análisis del VTR pasa a la siguiente etapa de la sección Información de finalización de llamada, que muestra el resultado final del análisis.

[Term/CallManagerServiceBus]	CallManagerId is callhalf-60459
[Term/CallManagerServiceBus]	 === Routing InvitationEvent on the Call Manager bus ===

[Term/CallManagerServiceBus]	AccessRoutingServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	VAOServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	TSDServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	SCAPServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	CallCenterAgentServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	FlashServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	RingTimeoutServiceInstance has processed the event...continue
[Term/SipINVITE]	 Outgoing resulting INVITE for Endpoint Id: callhalf-60459:0
    udp 1195 SIP Bytes OUT to 10.61.71.93:62388
    INVITE sip:5403362012@10.61.71.93:62388;transport=UDP;rinstance=c71abb15b3ff5d4a SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.61.71.93V62388-0-960978525-1694279432-1674811718841-
    From:"Marek Leus"
     
     
       ;tag=1694279432-1674811718841- To:"John Doe" 
      
        Call-ID:BW102838841270123-1135433227@10.48.93.126 CSeq:960978525 INVITE Contact: 
       
         Supported:100rel Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE Call-Info: 
        
          ;appearance-index=1 Recv-Info:x-broadworks-client-session-info Accept:application/media_control+xml,application/sdp,multipart/mixed Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv

En esta sección, verá el mensaje INVITE que se extendería al destino final si se tratara de una llamada real. También puede extraer el ID de la mitad de la llamada (callhalf-60459) que se puede utilizar para rastrear esta llamada en los archivos de registro:

bwadmin@as1.mleus.lab$ less XSLog2023.01.27-00.00.00.txt | grep callhalf-60459
2023.01.27 10:28:38:827 CET | Info       | Sip | Call Half Input Adapter 5 | 3104796 | +15403362012 | callhalf-60459 | 5ff0de06-90a9-4bb6-892a-610d7441ed69
	$ new CHSS > +15403362012 > callhalf-60455:0 > callhalf-60459
2023.01.27 10:28:38:827 CET | FieldDebug | StateReplication | Call Half Input Adapter 5 | 3104797 | +15403362012 | callhalf-60459 | 5ff0de06-90a9-4bb6-892a-610d7441ed69
2023.01.27 10:28:38:827 CET | Info       | CallP | Call Half Input Adapter 0 | 3104798 | Call Manager | +15403362012 | ngngroupB1 | callhalf-60459 | 5ff0de06-90a9-4bb6-892a-610d7441ed69

En las dos últimas secciones se muestran el resultado final y las marcas de tiempo de este análisis:

=====================================================
===========           TIMESTAMPS            =========
=====================================================
[Timestamps]	Start time = 2023.01.27 10:28:38:819 CET
[Timestamps]	End time   = 2023.01.27 10:28:38:846 CET

=====================================================
===========   RESULT: ALLOWED         ===============
=====================================================

Situación 2: llamada rechazada por el servicio de aceptación selectiva de llamadas

En esta situación, un usuario local vuelve a marcar otro usuario local por su extensión; sin embargo, esta vez la aceptación selectiva de llamadas se configura para rechazar esta llamada. Veamos la salida del magnetoscopio de esta llamada para obtener más información:

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 16
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint          5403362011@mleus.lab

IEn la primera sección de los resultados del magnetoscopio, puede ver cómo el AS asigna parámetros del comando vtr a las URL de SIP:

Persona que llama: 5403362011@mleus.lab
Destino: 2012@10.48.93.126:5060

Dado que es exactamente el mismo llamador que en el primer escenario, la sección Información del autor para esto es exactamente igual también. Por lo tanto, se omite para mayor claridad y el análisis continúa en la sección Información de llamada de origen:

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	Resuming event processing after TranslationServiceOrigInstance
[Orig/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ReturnCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LNDServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LocationControlServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validating origination. Using call type Group
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validation returned disposition Allow - OCP call type: Group

[Orig/CallServiceBus]	ACRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	NPAnnouncementServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFAlwaysFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCFFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DNDFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CPCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ClassmarkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VAOCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ExecutiveAssistantOrigServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing ReleaseWithCauseEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has processed the event...continue
[Orig/CallServiceBus]	CallTransferRecallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallParkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	Treatments Service would have started the announcement (see Treatment Section for more details).
[Orig/CallServiceBus/TreatmentsServiceInstance]	Letting event continue to release test call resources properly

[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFBusyFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNoAnswerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNotReachableFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DirectedCallPickupServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DPUBIServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	MusicOnHoldServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/ReleaseWithCauseHandler]	Post Processing RWC for Call.

Esta sección muestra que el AS conoce el número de destino y define la llamada como una llamada de grupo. Sin embargo, también puede determinar si algo va mal. En primer lugar, está la instrucción "Routing ReleaseWithCauseEvent en el bus de llamada de origen" y se incluye TreatmentServiceInstance. Del mismo modo, la sección concluye con ReleaseWithCauseHandler.

La siguiente sección es Originating Translation Result (Resultado de traducción de origen), que es idéntico a la sección del escenario 1 porque la llamada se dirige al mismo usuario. Por lo tanto, se omite para mayor claridad. La diferencia aparece en la sección Información de finalización de llamada:

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term/CallManagerServiceBus]	CallManagerId is callhalf-60511
[Term/CallManagerServiceBus]	 === Routing TerminationEvent on the Call Manager bus ===

[Term/Term-Id]	Terminating user type: BroadWorks
[Term/Term-Id]	User Info
[Term/Term-Id]	User Id                      = ngnuserB2@mleus.lab
[Term/Term-Id]	User Uid                     = 156778964
[Term/Term-Id]	Group Id                     = ngngroupB1
[Term/Term-Id]	Service Provider Id          = ngnentB1
[Term/Term-Id]	Reseller Id                  = null
[Term/Term-Id]	ASCII First Name             = John
[Term/Term-Id]	ASCII Last Name              = Doe
[Term/Term-Id]	Unicode First Name           = John
[Term/Term-Id]	Unicode Last Name            = Doe
[Term/Term-Id]	Country Code                 = 1
[Term/Term-Id]	User Type                    = User
[Term/Term-Id]	Trunk User Type              = BroadWorks Regular User
[Term/Term-Id]	(0) Address type             = main
[Term/Term-Id]	(0) dn                       = +15403362012
[Term/Term-Id]	(0) extension                = 2012
[Term/Term-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Term/Term-Id]	beingRemoved                 = false
[Term/Term-Id]	configurable CLID            = 5403362010
[Term/Term-Id]	synchronizationASRSentToNS   = false

[Term/CallServiceBus]	CallId is callhalf-60511:0
[Term/CallServiceBus]	 === Routing InvitationEvent on the Terminating Call bus ===

[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	NumberPortabilityQueryServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	CMServiceInstance has processed the event...continue
[Term/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Term/CallServiceBus]	OCPTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	ICPServiceInstance has processed the event...continue
[Term/CallServiceBus]	ACRServiceInstance has processed the event...continue
[Term/CallServiceBus/SCAServiceInstance]	Criteria Set evaluated and triggered:
[Term/CallServiceBus/SCAServiceInstance]
[Term/CallServiceBus/SCAServiceInstance]	Criteria Set:
[Term/CallServiceBus/SCAServiceInstance]	description: Reject_2011
[Term/CallServiceBus/SCAServiceInstance]	active: true
[Term/CallServiceBus/SCAServiceInstance]	blackListFlag: true
[Term/CallServiceBus/SCAServiceInstance]	ScheduleCriteria
[Term/CallServiceBus/SCAServiceInstance]	- No Schedule associated
[Term/CallServiceBus/SCAServiceInstance]	- inScheduleRightNow: true
[Term/CallServiceBus/SCAServiceInstance]	CallingPartyAddressCriteria
[Term/CallServiceBus/SCAServiceInstance]	+15403362011
[Term/CallServiceBus/SCAServiceInstance]	CallToCriteria
[Term/CallServiceBus/SCAServiceInstance]	CallTo matches ANY

[Term/CallServiceBus]	SCAServiceInstance has CONSUMED the event.
[Term/CallServiceBus]	CallId is callhalf-60511:0
[Term/CallServiceBus]	 === Routing ReleaseWithCauseEvent on the Terminating Call bus ===
[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	CMServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallParkServiceInstance has processed the event...continue
[Term/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Term/CallServiceBus]	OCPTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	PTTTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	LNRServiceInstance has processed the event...continue
[Term/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Term/CallServiceBus]	PersonalAssistantServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallWaitingTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFBusyTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	AnswerTimerServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFNotReachableTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFNoAnswerTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	VMServiceInstance has processed the event...continue
[Term/CallServiceBus]	DirectedCallPickupServiceInstance has processed the event...continue
[Term/CallServiceBus]	DPUBIServiceInstance has processed the event...continue
[Term/CallServiceBus]	RedirectionServiceInstance has processed the event...continue
[Term/CallServiceBus]	MusicOnHoldServiceInstance has processed the event...continue

Puede ver que esta vez el conjunto de criterios Rechazar_2011 está activo. Como resultado, se activa el servicio de aceptación selectiva de llamadas. Como resultado, se provoca ReleaseWithCauseEvent en el bus de finalización de llamada. El AS verifica el resto de los servicios y se traslada a la sección de Información sobre el Tratamiento:

=====================================================
===========  TREATMENT INFORMATION          =========
=====================================================
[Treatment/TreatmentsService]	Treatment service processing RWC. Release Cause is FORBIDDEN
[Treatment/TreatmentsService]	defaultAnnouncement isTrtCallFailure.wav
[Treatment/TreatmentsService]	defaultTone is reorder-pcmu.wav

[Treatment/TreatmentsService]	Configurable Treatment NOT used but specific audio treatment files have been provided
[Treatment/TreatmentsService]	audioAnnouncement(s):
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/silence10s.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav

En esta sección puede conocer el motivo del fallo de la llamada (PROHIBIDO) y si se va a reproducir el anuncio TrtSelectCallReject.wav.

En las dos últimas secciones se muestran el resultado final y las marcas de tiempo de este análisis:

=====================================================
===========           TIMESTAMPS            =========
=====================================================
[Timestamps]	Start time = 2023.01.27 10:31:29:425 CET
[Timestamps]	End time   = 2023.01.27 10:31:29:466 CET

=====================================================
===========   RESULT: BLOCKED         ===============
=====================================================

Situación 3: llamada a un número no asignado

En esta situación, un usuario local marca otra extensión que no está asignada. Veamos la salida del magnetoscopio de esta llamada para obtener más información:

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2014
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 14
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2014@10.48.93.126:5060
dialedDigits (initial) 2014
deviceEnpoint          5403362011@mleus.lab

En la primera sección de los resultados del VTR, puede ver cómo el AS asigna parámetros del comando vtr a las URL de SIP:

Persona que llama: 5403362011@mleus.lab
Destino: 2014@10.48.93.126:5060

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60487:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60487:0
[Orig/CallServiceBus]	 === Routing ReleaseWithCauseEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has processed the event...continue
[Orig/CallServiceBus]	CallTransferRecallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallParkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	Treatments Service would have started the announcement (see Treatment Section for more details).
[Orig/CallServiceBus/TreatmentsServiceInstance]	Letting event continue to release test call resources properly

[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFBusyFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNoAnswerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNotReachableFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DirectedCallPickupServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DPUBIServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	MusicOnHoldServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/ReleaseWithCauseHandler]	Post Processing RWC for Call.

En esta sección, ya puede darse cuenta de que algo está mal. En primer lugar, hay una sentencia "Routing ReleaseWithCauseEvent en el bus de llamada de origen" en lugar de la sentencia "Routing InvitationEvent en el bus de llamada de origen". A continuación, hay una instrucción TreatmentServiceInstance involucrada. Finalmente, la sección termina con la instrucción ReleaseWithCauseHandler.

=====================================================
===========  ORIGINATING TRANSLATION RESULT =========
=====================================================
[Orig-Xlation/DialPlanPolicy]	--Dial Plan Policy Information--
[Orig-Xlation/DialPlanPolicy]	requiresAccessCodeForPublicCalls = false
[Orig-Xlation/DialPlanPolicy]	allowE164PublicCalls             = false
[Orig-Xlation/DialPlanPolicy]	privateDigitMap                  =
[Orig-Xlation/DialPlanPolicy]	publicDigitMap                   = ([2-9]11|[0-1][2-9]11|0[#T]|00|01[2-9]xx.[#T]|*xx|011x.[#T]|[0-1]xxxxxxx[#T]|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxxxx[#T]|101xxxx.[#T]|11|[2-9][#T])
[Orig-Xlation/DialPlanPolicy]	preferE164FormatForCallbackSvcs  = false

[Orig-Xlation/NetworkUsagePolicy]	Network Usage Policy is - do not force all calls to network -
[Orig-Xlation/NetworkServerINVITE]	Sending INVITE event to network server for Translation Service Originating Side client
[Orig-Xlation/NetworkServerINVITE]	Endpoint Id: callhalf-60487:0
    udp 1128 SIP Bytes OUT to 10.48.93.128:5060
    INVITE sip:2014@10.48.93.128;user=phone;transport=udp SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564-
    From:"Marek Leus"
     
     
       ;tag=1152157837-1674811757564- To: 
      
        Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Contact: 
       
         P-Asserted-Identity:"Marek Leus" 
        
          Privacy:none X-BroadWorks-Correlation-Info:be8fde53-9ba5-4fc4-a788-ee426ed1fe90 Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY Supported: Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [Orig-Xlation/NS-RESPONSE] Got Network Server response for Translation Service Originating Side client udp 394 SIP Bytes IN from 10.48.93.128:49109 SIP/2.0 404 Not found Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564- From:"Marek Leus" 
         
           ;tag=1152157837-1674811757564- To: 
          
            ;tag=1006595920-1674811749882 Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Content-Length:0 [Orig-Xlation/TranslationManager] Translation Client: Translation Service Originating Side call Id is callhalf-60487:0 [Orig-Xlation/TranslationManager] === TranslationResult === [Orig-Xlation/TranslationManager] callType Network [Orig-Xlation/TranslationManager] address 2014 [Orig-Xlation/TranslationManager] addressType main [Orig-Xlation/TranslationManager] isServiceCode false [Orig-Xlation/TranslationManager] sc8Translated false [Orig-Xlation/TranslationManager] sc100Translated false [Orig-Xlation/TranslationManager] oacTranslated false [Orig-Xlation/TranslationManager] carrierPrefixTranslated false [Orig-Xlation/TranslationManager] intraSP false [Orig-Xlation/TranslationManager] alias false [Orig-Xlation/TranslationManager] preExtEmergencyRtgAK null [Orig-Xlation/TranslationManager] === Carrier Info === [Orig-Xlation/TranslationManager] ;csel=noind

La sección Resultado de la traducción de origen proporciona información sobre por qué la llamada no se realiza correctamente. De la salida se desprende claramente que el AS intenta resolver el número 2014 con el NS, pero devuelve la respuesta de error 404 Not Found.

Debido a que la llamada no se puede extender a su destino, la sección Información de finalización de llamada es muy breve:

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term]	Terminating call processing information has not been populated

En su lugar, hay una sección de información de tratamiento con información sobre cómo debe manejarse la llamada fallida:

=====================================================
===========  TREATMENT INFORMATION          =========
=====================================================
[Treatment/TreatmentsService]	Treatment service processing RWC. Release Cause is USER_NOT_FOUND
[Treatment/TreatmentsService]	defaultAnnouncement isTrtUnknownUser.wav
[Treatment/TreatmentsService]	defaultTone is reorder-pcmu.wav

[Treatment/TreatmentsService]	Treatment playing default announcement https://10.48.93.126/media/en/TrtUnknownUser.wav

En esta sección se indica el motivo del fallo de la llamada (USER_NOT_FOUND) y se informa de que se va a reproducir el anuncio TrtUnknownUser.wav y/o el tono reorder-pcmu.wav. También señala la ruta que se utilizará en el diálogo con el servidor de medios para indicarle que reproduzca el anuncio adecuado.

En las dos últimas secciones se muestran el resultado final y las marcas de tiempo de este análisis:

=====================================================
===========           TIMESTAMPS            =========
=====================================================
[Timestamps]	Start time = 2023.01.27 10:29:17:525 CET
[Timestamps]	End time   = 2023.01.27 10:29:17:669 CET

=====================================================
===========   RESULT: BLOCKED         ===============
=====================================================

Historial de revisiones

Revisión	Fecha de publicación	Comentarios
1.0	31-Jan-2023	Versión inicial

Con la colaboración de ingenieros de Cisco

Marek Leus
Ingeniero de consultoría técnica

¿Resultó útil este documento?

Comentarios

Contacte a Cisco

Abrir un caso de soporte
(Requiere un Cisco Service Contract)