Usando regras de tradução IOS - Criando planos de discagem escaláveis para redes VoIP

Opções de download

PDF (405.0 KB)
Ver no Adobe Reader em vários dispositivos
ePub (107.3 KB)
Ver em vários aplicativos no iPhone, iPad, Android, Sony Reader ou Windows Phone
Mobi (Kindle) (161.8 KB)
Ver no dispositivo Kindle ou no aplicativo Kindle em vários dispositivos

Atualizado:2 de fevereiro de 2006

ID do documento:20595

Linguagem imparcial

O conjunto de documentação deste produto faz o possível para usar uma linguagem imparcial. Para os fins deste conjunto de documentação, a imparcialidade é definida como uma linguagem que não implica em discriminação baseada em idade, deficiência, gênero, identidade racial, identidade étnica, orientação sexual, status socioeconômico e interseccionalidade. Pode haver exceções na documentação devido à linguagem codificada nas interfaces de usuário do software do produto, linguagem usada com base na documentação de RFP ou linguagem usada por um produto de terceiros referenciado. Saiba mais sobre como a Cisco está usando a linguagem inclusiva.

Sobre esta tradução

A Cisco traduziu este documento com a ajuda de tecnologias de tradução automática e humana para oferecer conteúdo de suporte aos seus usuários no seu próprio idioma, independentemente da localização. Observe que mesmo a melhor tradução automática não será tão precisa quanto as realizadas por um tradutor profissional. A Cisco Systems, Inc. não se responsabiliza pela precisão destas traduções e recomenda que o documento original em inglês (link fornecido) seja sempre consultado.

Introduction

Prerequisites

Requirements

Componentes Utilizados

Conventions

Informações de Apoio

Configurar

Diagrama de Rede

Configurações

Verificar

Troubleshoot

Informações Relacionadas

Introduction

Este documento fornece uma configuração de exemplo para criar planos de discagem escaláveis para uma rede VoIP usando regras de tradução IOS. Quando você instala redes de voz e dados integradas, uma dúvida frequente é como gerenciar os planos de numeração das escalas de DDR (Discagem Direta a Ramal) em lugar diferentes. Dependendo do tipo de central telefônica, dos padrões de protocolo de sinalização e até mesmo do local, o provedor de serviços pode passar faixas de números semelhantes para o equipamento do assinante em cada local remoto. Se essas chamadas estão sendo encaminhadas de volta para uma instalação central, pode haver uma sobreposição nos números chamados originários de cada um dos locais remotos. Uma vez que o PBX toma a decisão de roteamento com base em números chamados exclusivos, isso poderia causar problemas com as filas de distribuição automática de chamadas (ACD) em sistemas de central telefônica privada (PBX). Por exemplo, as chamadas de cada local devem ser direcionadas a determinados operadores que falam o idioma do local de origem da chamada. Se os números chamados de cada local se sobrepõem, não há nenhuma maneira de identificar a origem de uma chamada e, consequentemente, o PBX não pode encaminhar a chamada à fila de ACD correta.

Alguns locais remotos podem ter um intervalo de números índios de 2 dígitos, enquanto outros podem ter intervalos de 3 ou 4 dígitos, de modo que os números chamados podem ser de [00 - 99] a [0000 - 999]. Com esses intervalos de números, o roteador do local principal precisaria de configurações para lidar com planos de numeração de 2, 3 e 4 dígitos. Isso pode aumentar a complexidade geral da configuração do roteador.

A solução para esses problemas é usar regras de conversão de dígitos do IOS em cada local remoto para prefixar dígitos à faixa de números que vem da rede telefônica. Isso cria um plano de numeração padrão na rede do cliente e permite que novos locais sejam gradualmente adicionados sem grandes alterações no resto da rede.

Observação: as regras de conversão de dígitos do Cisco IOS permitem que os usuários manipulem os dígitos de identificação automática de números (ANI) de uma chamada que é o número de chamada ou os dígitos do Serviço de identificação de número discado (DNIS) de uma chamada que é o número chamado. Opcionalmente, os tipos de numeração desses campos também podem ser modificados usando as regras de conversão.

No estudo de caso apresentado neste documento, o objetivo é padronizar o plano de numeração. As sugestões incluem:

Use um código de acesso de tronco.
Usar um código de site (área). Essa é uma maneira fácil de criar um código de local exclusivo para usar o código de área da rede telefônica pública comutada (PSTN - Public Switched Telephone Network) local do local remoto.
Expanda (separe) o número chamado original com zeros à esquerda para produzir um número de ramal de 4 dígitos.

Prerequisites

Requirements

Os leitores devem ter conhecimento de:

Configuração de peer de discagem de voz e pots

Componentes Utilizados

As informações neste documento são baseadas nestas versões de software e hardware:

Roteadores Cisco 3660 e 7206VXR executando IOS versão 12.3(4)
As regras de conversão do IOS foram introduzidas no IOS versão 12.07XK1 e estão disponíveis em todas as plataformas Cisco que suportam portas de voz.

As informações neste documento foram criadas a partir de dispositivos em um ambiente de laboratório específico. All of the devices used in this document started with a cleared (default) configuration. Se você estiver trabalhando em uma rede ativa, certifique-se de que entende o impacto potencial de qualquer comando antes de utilizá-lo.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Informações de Apoio

Esta seção usa o estudo de caso: Exemplo de "Calcutá (local remoto)" para explicar a implementação das regras de tradução. Consulte o Diagrama de Rede para obter mais informações.

Em nosso exemplo, o local remoto (Calcutá) tem um tronco E1 que passa uma sequência de discagem de 3 dígitos no intervalo de 000 a 999. O roteador do local principal aceita chamadas de vários locais remotos que também podem cobrir o intervalo de 000 a 999.

As regras de tradução são usadas no roteador Calcutá para prefixar um código de site que identifica exclusivamente chamadas de Calcutá (com base no número chamado) para o PBX do local principal. Por exemplo, a string de discagem de código de área "033" é usada como um código de site. Além disso, um dígito de código de acesso de tronco é adicionado para permitir a seleção de troncos específicos no roteador de local principal de destino. Essas instruções ilustram o procedimento de conversão no roteador Calcutá:

Número chamado original (qualquer 3 dígitos no intervalo de 000 a 999)—" ... "
Número chamado traduzido—"1033... "dígito "1": código de acesso de tronco, dígitos "033": código do site

Quando uma chamada é feita do site Calcutá, o roteador Calcutá aplica a regra de conversão aplicada em sua porta de voz POTS . Você pode verificar isso na configuração da porta de voz 1/0:1 do roteador Calcutá.

A regra de conversão é aplicada à porta de voz onde a chamada entra no roteador. Quando uma chamada é recebida da rede telefônica em direção ao roteador, o número chamado é convertido antes de ser combinado em qualquer ponto de discagem.

A regra de tradução é aplicada da seguinte forma para o site Calcutá para o número discado - 987 para o site principal.
- No chamado número de 3 dígitos - 987, o primeiro dígito - 9 do LHS (lado esquerdo) é tomado e comparado na regra de tradução para substituir os dígitos.
- O número de substituição de 9 na regra de tradução é - 103309, esse número é substituído para o primeiro dígito 9.
- Após substituir o primeiro dígito 9 por 103309, os 2 dígitos restantes - 87 são precedidos do dígito substituído 103309, que se torna 10330987 e a chamada é roteada para o peer de discagem voip como o padrão de destino - 10330.... fósforos.

Mais dois locais remotos precisam ser integrados à rede. O site de Nova Delhi usa um intervalo de dois dígitos, enquanto o site de Chennai usa um intervalo de quatro dígitos. Ao antecipar um código de acesso de tronco e um código de site para o número chamado, você agora tem um plano de discagem da seguinte maneira:

Este código de site/acesso de tronco...	...representa este plano de discagem
"1011... "	índio de 2 dígitos com código de área 011
"1033... "	índio de 3 dígitos com código de área 033
"1044.... "	índio de 4 dígitos com um código de área 044

Este plano de discagem consiste em números de 6, 7 e 8 dígitos, de modo que eles possam ser padronizados com o preenchimento dos números chamados originais com zeros à esquerda para fornecer um código de acesso de 1 dígito, código de site de 3 dígitos e ramal de 4 dígitos:

Este código de site/ acesso de tronco...	...é traduzido para
"1011... "	"101100... "
"1033... "	"10330... "
"1044.... "	"1044...."

O plano numérico no roteador/gateway do local principal agora é consistente com 8 dígitos: (código de acesso de tronco de 1 dígito, código de site de 3 dígitos e número chamado de 4 dígitos com zeros à esquerda). Quando a chamada chega ao gateway/roteador do local principal, o código de acesso é removido e os sete dígitos subsequentes são enviados ao PBX.

Configurar

Neste estudo de caso, há três locais remotos (Nova Deli, Calcutá e Chennai) que estão direcionando chamadas VoIP para o Centro de atendimento ao local principal. O requisito do cliente é para um sistema que direciona chamadas de locais remotos para o local principal. Não há provisão para chamadas de retorno do local principal de volta para os locais remotos. O roteador/gateway do local principal tem 4 troncos que se conectam ao PBX do call center.

Observação: para encontrar informações adicionais sobre os comandos usados neste documento, use a ferramenta Command Lookup Tool (somente clientes registrados).

Diagrama de Rede

Este documento usa a configuração de rede mostrada no diagrama aqui:

Configurações

Este documento utiliza as configurações mostradas aqui:

Nova Delhi (intervalo de dois dígitos)
*!--- Only relevant "IOS translation rule" output is presented* ! translation-rule 1 !-- The "1" above is the tag for the set. rule 0 ^0. 1011000 rule 1 ^1. 1011001 rule 2 ^2. 1011002 rule 3 ^3. 1011003 rule 4 ^4. 1011004 rule 5 ^5. 1011005 rule 6 ^6. 1011006 rule 7 ^7. 1011007 rule 8 ^8. 1011008 rule 9 ^9. 1011009 ! !-- These rules replace the first digit of a 2-digit number with the corresponding !-- translation. The router looks for a 2-digit number starting with a leading [0-9]. !-- The caret, "^" ensures the match only happens at the start of the digit string !-- rather than any occurrence in a digit string. This ensures the router makes the !-- translation only for the leading digits. By default, if an explicit match is made !-- on a digit (in this case the first digit) the router replaces it with the new !-- digits. Therefore, to keep the original numbering, the matched digit needs to be !-- replaced with the same digit at the end of the modified string. Once the call !-- comes in, the called number prepended with 101100 followed by the !-- original 2 digits. ! voice-port 1/0:1 translate called 1 cptone IN compand-type a-law ! !-- The translation rule is applied to the voice port where the !-- call comes in to the router. When a call comes in from the !-- telephone network towards the router, the called number !-- is translated before it is matched on any dial peers. ! dial-peer voice 100 voip destination-pattern 101100.. session target ipv4:main site IP address ip precedence 5 dtmf-relay h245-alphanumeric ! !-- The VoIP dial peer needs to be configured to match on the new numbering plan

Nova Delhi (intervalo de dois dígitos)

!--- Only relevant "IOS translation rule" output is presented
!
translation-rule 1

!-- The "1" above is the tag for the set.

rule 0 ^0. 1011000
rule 1 ^1. 1011001
rule 2 ^2. 1011002
rule 3 ^3. 1011003
rule 4 ^4. 1011004
rule 5 ^5. 1011005
rule 6 ^6. 1011006
rule 7 ^7. 1011007
rule 8 ^8. 1011008
rule 9 ^9. 1011009
!

!-- These rules replace the first digit of a 2-digit number with the corresponding !-- translation. The router looks for a 2-digit number starting with a leading [0-9]. !-- The caret, "^" ensures the match only happens at the start of the digit string !-- rather than any occurrence in a digit string. This ensures the router makes the !-- translation only for the leading digits. By default, if an explicit match is made !-- on a digit (in this case the first digit) the router replaces it with the new !-- digits. Therefore, to keep the original numbering, the matched digit needs to be !-- replaced with the same digit at the end of the modified string. Once the call !-- comes in, the called number prepended with 101100 followed by the !-- original 2 digits.
!
voice-port 1/0:1
translate called 1
cptone IN
compand-type a-law
!
!-- The translation rule is applied to the voice port where the !-- call comes in to the router. When a call comes in from the !-- telephone network towards the router, the called number !-- is translated before it is matched on any dial peers.
!
dial-peer voice 100 voip
destination-pattern 101100..
session target ipv4:main site IP address
ip precedence 5
dtmf-relay h245-alphanumeric
!

!-- The VoIP dial peer needs to be configured to match on the new numbering plan

Calcutá (intervalo de 3 dígitos índio)
!--- Only relevant output is presented ! translation-rule 1 rule 0 ^0.. 103300 rule 1 ^1.. 103301 rule 2 ^2.. 103302 rule 3 ^3.. 103303 rule 4 ^4.. 103304 rule 5 ^5.. 103305 rule 6 ^6.. 103306 rule 7 ^7.. 103307 rule 8 ^8.. 103308 rule 9 ^9.. 103309 ! !-- The router looks for a 3-digit called number in the range 000 - 999. It !-- then prepends 10330 to this number before making a match on any other dial peers. !-- Note: rules are executed before incoming POTS dial peer matching takes place. ! voice-port 1/0:1 translate called 1 !-- The translation rule is applied to the voice port: cptone IN compand-type a-law ! dial-peer voice 100 voip destination-pattern 10330... session target ipv4:main site IP address ip precedence 5 dtmf-relay h245-alphanumeric ! !-- The VoIP dial peer needs to be configured to match on the new numbering plan.

Calcutá (intervalo de 3 dígitos índio)


 !--- Only relevant output is presented 
!
translation-rule 1
 rule 0 ^0.. 103300
 rule 1 ^1.. 103301
 rule 2 ^2.. 103302
 rule 3 ^3.. 103303
 rule 4 ^4.. 103304
 rule 5 ^5.. 103305
 rule 6 ^6.. 103306
 rule 7 ^7.. 103307
 rule 8 ^8.. 103308
 rule 9 ^9.. 103309
!

!-- The router looks for a 3-digit called number in the range 000 - 999. It !-- then prepends 10330 to this number before making a match on any other dial peers. !-- Note: rules are executed before incoming POTS dial peer matching takes place. 
!
voice-port 1/0:1
 translate called 1

!-- The translation rule is applied to the voice port: 

 cptone IN
 compand-type a-law
!
dial-peer voice 100 voip 
 destination-pattern 10330...
 session target ipv4:main site IP address
 ip precedence 5 
 dtmf-relay h245-alphanumeric 
!

!-- The VoIP dial peer needs to be configured to match on the new numbering plan.

Chennai (intervalo de 4 dígitos)
! translation-rule 11 rule 0 ^0... 10440 rule 1 ^1... 10441 rule 2 ^2... 10442 rule 3 ^3... 10443 rule 4 ^4... 10444 rule 5 ^5... 10445 rule 6 ^6... 10446 rule 7 ^7... 10447 rule 8 ^8... 10448 rule 9 ^9... 10449 ! !-- The router looks for a 4-digit called !-- number in the range 0000 - 9999. !-- It then prepends 1044 to this number !-- before making a match on any other dial peers. ! voice-port 1/0:1 translate called 1 cptone IN compand-type a-law ! !-- The translation rule is applied to the voice port: dial-peer voice 100 voip destination-pattern 1044…. session target ipv4:main site IP address ip precedence 5 dtmf-relay h245-alphanumeric ! !-- The VoIP dial peer needs to be configured to match on the new numbering plan

Chennai (intervalo de 4 dígitos)

!
translation-rule 11
 rule 0 ^0... 10440
 rule 1 ^1... 10441
 rule 2 ^2... 10442
 rule 3 ^3... 10443
 rule 4 ^4... 10444
 rule 5 ^5... 10445
 rule 6 ^6... 10446
 rule 7 ^7... 10447
 rule 8 ^8... 10448
 rule 9 ^9... 10449
!

!-- The router looks for a 4-digit called !-- number in the range 0000 - 9999. !-- It then prepends 1044 to this number !-- before making a match on any other dial peers. 
!
voice-port 1/0:1
 translate called 1 
 cptone IN
 compand-type a-law 
!
!-- The translation rule is applied to the voice port: 
dial-peer voice 100 voip 
 destination-pattern 1044….
 session target ipv4:main site IP address
 ip precedence 5 
 dtmf-relay h245-alphanumeric 
!

!-- The VoIP dial peer needs to be configured to match on the new numbering plan

Local principal
!-- By default, in POTS dial peers, matched digits get stripped off after a dial !-- peer is matched. Then, the remaining digits are outputed to the PSTN/PBX. dial-peer voice 20 pots description - Call Center voice port 2/0 destination-pattern 1....... port 2/0:1 ! dial-peer voice 21 pots description - Call Center voice port 2/1 destination-pattern 1....... port 2/1:1 ! dial-peer voice 30 pots description - Call Center voice port 3/0 destination-pattern 1....... port 3/0:1 ! dial-peer voice 31 pots description - Call Center voice port 3/1 destination-pattern 1....... port 3/1:1 ! !-- The trunk access code (leading 1) can be used to route the call out the Main Site !-- router towards the Call-Center PBX. This digit is stripped off and the following !-- 7 digits are sent to the external PBX. A single dial peer for each active voice !-- port on the main site gateway router directs calls from the remote sites to !-- the PBX.

Local principal


!-- By default, in POTS dial peers, matched digits get stripped off after a dial !-- peer is matched. Then, the remaining digits are outputed to the PSTN/PBX. 
dial-peer voice 20 pots
 description - Call Center voice port 2/0
 destination-pattern 1.......
 port 2/0:1
!
dial-peer voice 21 pots
 description - Call Center voice port 2/1
 destination-pattern 1.......
 port 2/1:1
!
dial-peer voice 30 pots
 description - Call Center voice port 3/0
 destination-pattern 1.......
 port 3/0:1
!
dial-peer voice 31 pots
 description - Call Center voice port 3/1
 destination-pattern 1.......
 port 3/1:1
!

!-- The trunk access code (leading 1) can be used to route the call out the Main Site !-- router towards the Call-Center PBX. This digit is stripped off and the following !-- 7 digits are sent to the external PBX. A single dial peer for each active voice !-- port on the main site gateway router directs calls from the remote sites to !-- the PBX.

Observação: como o PBX do local principal não exige o código de acesso de tronco, o roteador do local principal o removeria. Portanto, a chamada é identificada para o PBX do site principal por um código de três dígitos e pelo ramal de quatro dígitos. O PBX precisaria de algumas alterações de configuração para corresponder a esse plano de numeração, mas a vantagem é que ele pode reconhecer o código do site do número chamado e rotear a chamada para uma fila do ACD específica configurada para cada local. Quando uma chamada vem de uma região nacional específica, ela é direcionada para agentes que falam o idioma local.

Observação: para obter mais informações sobre comandos, consulte a Command Lookup Tool (somente clientes registrados) .

Verificar

Esta seção fornece informações que você pode usar para confirmar se sua configuração está funcionando adequadamente.

A Output Interpreter Tool (somente clientes registrados) oferece suporte a determinados comandos show, o que permite exibir uma análise da saída do comando show.

test translation-rule name-tag input-number —Usado para testar a execução das regras de conversão em uma marca de nome específica. A sintaxe desse comando está descrita nesta tabela:

Sintaxe	Descrição
name-tag	O número da marca pelo qual o conjunto de regras é referenciado.
input-number	A cadeia de entrada de dígitos para a qual é executada uma correspondência de padrões.

show translation-rule [name-tag] — Usado para exibir o conteúdo das regras que foram configuradas para um nome de tradução específico. A sintaxe desse comando é descrita nesta tabela:

Sintaxe	Descrição
name-tag	(Opcional) O número da etiqueta pela qual o conjunto de regras é referenciado

Esta saída foi capturada do roteador NewDelhi, que mostra as regras de conversão aplicadas durante a discagem do site NewDelhi.

NovaDeli - Saída
!-- It is possible to confirm the translation rules are working: ! ! NewDelhi# test translation-rule 1 99 !-- Original called number is "99" The replaced number: 10110099 !-- Translated to 8 digits NewDelhi# show translation-rule 1 Translation rule address: 0x64ADC2A8 Tag name: 1 Translation rule in_used 1 ** Xrule rule table *** Rule : 0 in_used state: 1 Match pattern: ^0. Sub pattern: 1011000 Xrule rule table *** Rule : 1 in_used state: 1 Match pattern: ^1. Sub pattern: 1011001 Xrule rule table *** Rule : 2 in_used state: 1 Match pattern: ^2. Sub pattern: 1011002 Xrule rule table *** Rule : 3 in_used state: 1 Match pattern: ^3. Sub pattern: 1011003 Xrule rule table *** Rule : 4 in_used state: 1 Match pattern: ^4. Sub pattern: 1011004 Xrule rule table *** Rule : 5 in_used state: 1 Match pattern: ^5. Sub pattern: 1011005 Xrule rule table *** Rule : 6 in_used state: 1 Match pattern: ^6. Sub pattern: 1011006 Xrule rule table *** Rule : 7 in_used state: 1 Match pattern: ^7. Sub pattern: 1011007 Xrule rule table *** Rule : 8 in_used state: 1 Match pattern: ^8. Sub pattern: 1011008 Xrule rule table ***** Rule : 9 in_used state: 1 Match pattern: ^9. Sub pattern: 1011009 NewDelhi#

NovaDeli - Saída


!-- It is possible to confirm the translation rules are working:
!
!
NewDelhi#
test translation-rule 1 99


!-- Original called number is "99" 
The replaced number: 10110099
 !-- Translated to 8 digits 


NewDelhi#
show translation-rule 1

Translation rule address: 0x64ADC2A8
Tag name: 1
Translation rule in_used 1
**** Xrule rule table *******
        Rule : 0
        in_used state: 1
        Match pattern: ^0.
        Sub  pattern: 1011000
**** Xrule rule table *******
        Rule : 1
        in_used state: 1
        Match pattern: ^1.
        Sub  pattern: 1011001
**** Xrule rule table *******
        Rule : 2
        in_used state: 1
        Match pattern: ^2.
        Sub  pattern: 1011002
**** Xrule rule table *******
        Rule : 3
        in_used state: 1
        Match pattern: ^3.
        Sub  pattern: 1011003
**** Xrule rule table *******
        Rule : 4
        in_used state: 1
        Match pattern: ^4.
        Sub  pattern: 1011004
**** Xrule rule table *******
        Rule : 5
        in_used state: 1
        Match pattern: ^5.
        Sub  pattern: 1011005
**** Xrule rule table *******
        Rule : 6
        in_used state: 1
        Match pattern: ^6.
        Sub  pattern: 1011006
**** Xrule rule table *******
        Rule : 7
        in_used state: 1
        Match pattern: ^7.
        Sub  pattern: 1011007
**** Xrule rule table *******
        Rule : 8
        in_used state: 1
        Match pattern: ^8.
        Sub  pattern: 1011008
**** Xrule rule table *******
        Rule : 9
        in_used state: 1
        Match pattern: ^9.
        Sub  pattern: 1011009
NewDelhi#

Troubleshoot

Esta seção fornece informações que podem ser usadas para o troubleshooting da sua configuração.

Observação: antes de inserir o comando debug, consulte Informações importantes sobre os comandos debug.

debug translation {detail | min} —Usado para depurar rastreamentos de tradução de número com as opções descritas nesta tabela:

Opção	Descrição
detail	Habilita um rastreamento de depuração detalhado.
min	Habilita um rastreamento de depuração mínimo.

NovaDeli - Saída
NewDelhi#debug translation detail xrule detail tracing is enabled Apr 4 04:52:57.124: xrule_checking Apr 4 04:52:57.124: xrule_checking calling , called Apr 4 04:52:57.124: xrule_checking peer_tag 0, direction 1, protocol 6 Apr 4 04:52:57.124: xrule_translation Apr 4 04:52:57.124: xrule_translation callednumber , strlen 0 Apr 4 04:52:57.124: xrule_translation callednumber null xruleCalledTag=1 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 0, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^0. Apr 4 04:52:57.124: dpMatchString match_tmp 0, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 0,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 0 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 1, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^1. Apr 4 04:52:57.124: dpMatchString match_tmp 1, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 1,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 1 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 2, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^2. Apr 4 04:52:57.124: dpMatchString match_tmp 2, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 2,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 2 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 3, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^3. Apr 4 04:52:57.124: dpMatchString match_tmp 3, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 3,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 3 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 4, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^4. Apr 4 04:52:57.124: dpMatchString match_tmp 4, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 4,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 4 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 5, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^5. Apr 4 04:52:57.124: dpMatchString match_tmp 5, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 5,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 5 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 6, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^6. Apr 4 04:52:57.124: dpMatchString match_tmp 6, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 6,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 6 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 7, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^7. Apr 4 04:52:57.124: dpMatchString match_tmp 7, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 7,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 7 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 8, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^8. Apr 4 04:52:57.124: dpMatchString match_tmp 8, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 8,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 8 Apr 4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81, match_type 0x0 Apr 4 04:52:57.124: xrule_translation Xrule index 9, Numpertype 0x9 Apr 4 04:52:57.124: dpMatchString, target_number null, match_number ^9. Apr 4 04:52:57.124: dpMatchString match_tmp 9, match_len 1 Apr 4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 9,target null Apr 4 04:52:57.124: dpMatchString: len 4 Apr 4 04:52:57.124: xrule_translation there was no match index 9 Apr 4 04:52:57.124: xrule_translation Return rc = -4 any_match 0 Apr 4 04:52:57.124: xrule_checking Return rc = -4 Apr 4 04:52:59.396: xrule_checking Apr 4 04:52:59.396: xrule_checking calling , called 9 Apr 4 04:52:59.396: xrule_checking peer_tag 0, direction 1, protocol 6 Apr 4 04:52:59.396: xrule_translation Apr 4 04:52:59.396: xrule_translation callednumber 9, strlen 1 Apr 4 04:52:59.396: xrule_translation callednumber 9 xruleCalledTag=1 Apr 4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.396: xrule_translation Xrule index 0, Numpertype 0x9 Apr 4 04:52:59.396: dpMatchString, target_number 9, match_number ^0. Apr 4 04:52:59.396: dpMatchString match_tmp 0, match_len 1 Apr 4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 0,target 9 Apr 4 04:52:59.396: dpMatchString: len 1 Apr 4 04:52:59.396: xrule_translation there was no match index 0 Apr 4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.396: xrule_translation Xrule index 1, Numpertype 0x9 Apr 4 04:52:59.396: dpMatchString, target_number 9, match_number ^1. Apr 4 04:52:59.396: dpMatchString match_tmp 1, match_len 1 Apr 4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 1,target 9 Apr 4 04:52:59.396: dpMatchString: len 1 Apr 4 04:52:59.396: xrule_translation there was no match index 1 Apr 4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.396: xrule_translation Xrule index 2, Numpertype 0x9 Apr 4 04:52:59.396: dpMatchString, target_number 9, match_number ^2. Apr 4 04:52:59.396: dpMatchString match_tmp 2, match_len 1 Apr 4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 2,target 9 Apr 4 04:52:59.396: dpMatchString: len 1 Apr 4 04:52:59.396: xrule_translation there was no match index 2 Apr 4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.396: xrule_translation Xrule index 3, Numpertype 0x9 Apr 4 04:52:59.396: dpMatchString, target_number 9, match_number ^3. Apr 4 04:52:59.396: dpMatchString match_tmp 3, match_len 1 Apr 4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 3,target 9 Apr 4 04:52:59.396: dpMatchString: len 1 Apr 4 04:52:59.396: xrule_translation there was no match index 3 Apr 4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.396: xrule_translation Xrule index 4, Numpertype 0x9 Apr 4 04:52:59.396: dpMatchString, target_number 9, match_number ^4. Apr 4 04:52:59.396: dpMatchString match_tmp 4, match_len 1 Apr 4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 4,target 9 Apr 4 04:52:59.396: dpMatchString: len 1 Apr 4 04:52:59.396: xrule_translation there was no match index 4 Apr 4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.396: xrule_translation Xrule index 5, Numpertype 0x9 Apr 4 04:52:59.396: dpMatchString, target_number 9, match_number ^5. Apr 4 04:52:59.396: dpMatchString match_tmp 5, match_len 1 Apr 4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 5,target 9 Apr 4 04:52:59.396: dpMatchString: len 1 Apr 4 04:52:59.396: xrule_translation there was no match index 5 Apr 4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.400: xrule_translation Xrule index 6, Numpertype 0x9 Apr 4 04:52:59.400: dpMatchString, target_number 9, match_number ^6. Apr 4 04:52:59.400: dpMatchString match_tmp 6, match_len 1 Apr 4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 6,target 9 Apr 4 04:52:59.400: dpMatchString: len 1 Apr 4 04:52:59.400: xrule_translation there was no match index 6 Apr 4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.400: xrule_translation Xrule index 7, Numpertype 0x9 Apr 4 04:52:59.400: dpMatchString, target_number 9, match_number ^7. Apr 4 04:52:59.400: dpMatchString match_tmp 7, match_len 1 Apr 4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 7,target 9 Apr 4 04:52:59.400: dpMatchString: len 1 Apr 4 04:52:59.400: xrule_translation there was no match index 7 Apr 4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.400: xrule_translation Xrule index 8, Numpertype 0x9 Apr 4 04:52:59.400: dpMatchString, target_number 9, match_number ^8. Apr 4 04:52:59.400: dpMatchString match_tmp 8, match_len 1 Apr 4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 8,target 9 Apr 4 04:52:59.400: dpMatchString: len 1 Apr 4 04:52:59.400: xrule_translation there was no match index 8 Apr 4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0, match_type 0x0 Apr 4 04:52:59.400: xrule_translation Xrule index 9, Numpertype 0x9 Apr 4 04:52:59.400: dpMatchString, target_number 9, match_number ^9. Apr 4 04:52:59.400: dpMatchString match_tmp 9, match_len 1 Apr 4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 9,target 9 Apr 4 04:52:59.400: dpMatchString 0. target 9,match_tmp 9,match_len 1 Apr 4 04:52:59.400: replace_string Apr 4 04:52:59.400: replace_string match ^9., replace 1011009 Apr 4 04:52:59.400: translation_format replace_rule ^9., strip_proceeding 0 Apr 4 04:52:59.400: replace_string match_tmp ^9., strip_proceeding 0 Apr 4 04:52:59.400: replace_string match_tmp 9 Apr 4 04:52:59.400: replace_string direction 1, callparty 2 Apr 4 04:52:59.400: replace_string direction 1, callparty 2, target 9 Apr 4 04:52:59.400: replace_string match_tmp 9,replace 1011009 Apr 4 04:52:59.400: replace_string0.replace19,target,current,match_tmp Apr 4 04:52:59.400: replace_string0.1 compare_len 1,match_len 1 Apr 4 04:52:59.400: replace_string 3. replace1 9, compare_len 1 Apr 4 04:52:59.400: replace_string 4. replace1 1,compare_len 0,replace 011009 Apr 4 04:52:59.400: replace_string 4. replace1 10,compare_len -1,replace 11009 Apr 4 04:52:59.400: replace_string 4. replace1 101,compare_len -2,replace 1009 Apr 4 04:52:59.400: replace_string 4. replace1 1011,compare_len -3,replace 009 Apr 4 04:52:59.400: replace_string 4. replace1 10110,compare_len -4,replace 09 Apr 4 04:52:59.400: replace_string 4. replace1 101100,compare_len -5,replace 9 Apr 4 04:52:59.400: replace_string 4. replace1 1011009,compare_len -6,replace Apr 4 04:52:59.400: replace_string 5. replace1 1011009, compare_len -6,match_l en 1 Apr 4 04:52:59.400: replace_string 6. replace1 1011009,compare_len -6,current Apr 4 04:52:59.400: replace_string buffer 1011009 Apr 4 04:52:59.400: xrule_translation index 9,xrule_number 1011009, callparty 2 Apr 4 04:52:59.400: xrule_translation Return rc = 0 any_match 0 Apr 4 04:52:59.400: xrule_checking Return rc = 0 Apr 4 04:53:00.156: xrule_checking Apr 4 04:53:00.156: xrule_checking calling 4444, called 10110099 Apr 4 04:53:00.156: xrule_checking peer_tag 100, direction 2, protocol 0 Apr 4 04:53:00.156: xrule_checking Return rc = -5 NewDelhi#debug translation min* Apr 4 02:37:17.045: xrule_checking Apr 4 02:37:17.045: xrule_translation Apr 4 02:37:17.045: xrule_translation callednumber , strlen 0 Apr 4 02:37:17.045: xrule_translation callednumber null xruleCalledTag=1 Apr 4 02:37:19.457: xrule_checking Apr 4 02:37:19.457: xrule_translation Apr 4 02:37:19.457: xrule_translation callednumber 9, strlen 1 Apr 4 02:37:19.457: xrule_translation callednumber 9 xruleCalledTag=1 Apr 4 02:37:19.457: dpMatchString 0. target 9,match_tmp 9,match_len 1 Apr 4 02:37:19.457: replace_string Apr 4 02:37:19.461: replace_string0.replace19,target,current,match_tmp Apr 4 02:37:19.461: replace_string0.1 compare_len 1,match_len 1 Apr 4 02:37:19.461: replace_string 3. replace1 9, compare_len 1 Apr 4 02:37:19.461: replace_string 4. replace1 1,compare_len 0,replace 011009 Apr 4 02:37:19.461: replace_string 4. replace1 10,compare_len -1,replace 11009 Apr 4 02:37:19.461: replace_string 4. replace1 101,compare_len -2,replace 1009 Apr 4 02:37:19.461: replace_string 4. replace1 1011,compare_len -3,replace 009 Apr 4 02:37:19.461: replace_string 4. replace1 10110,compare_len -4,replace 09 Apr 4 02:37:19.461: replace_string 4. replace1 101100,compare_len -5,replace 9 Apr 4 02:37:19.461: replace_string 4. replace1 1011009,compare_len -6,replace Apr 4 02:37:19.461: replace_string 5. replace1 1011009, compare_len -6,match_l en 1 Apr 4 02:37:19.461: replace_string 6. replace1 1011009,compare_len -6,current Apr 4 02:37:19.461: replace_string buffer 1011009 Apr 4 02:37:19.461: xrule_translation index 9,xrule_number 1011009, callparty 2 *Apr 4 02:37:19.841: xrule_checking

NovaDeli - Saída

	
NewDelhi#debug translation detail
xrule detail tracing is enabled
*Apr  4 04:52:57.124: xrule_checking
*Apr  4 04:52:57.124: xrule_checking calling , called
*Apr  4 04:52:57.124: xrule_checking peer_tag 0, direction 1, protocol 6
*Apr  4 04:52:57.124: xrule_translation
*Apr  4 04:52:57.124: xrule_translation callednumber , strlen 0
*Apr  4 04:52:57.124: xrule_translation callednumber null xruleCalledTag=1
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 0, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^0.
*Apr  4 04:52:57.124: dpMatchString match_tmp 0, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 0,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 0
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 1, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^1.
*Apr  4 04:52:57.124: dpMatchString match_tmp 1, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 1,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 1
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 2, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^2.
*Apr  4 04:52:57.124: dpMatchString match_tmp 2, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 2,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 2
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 3, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^3.
*Apr  4 04:52:57.124: dpMatchString match_tmp 3, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 3,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 3
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 4, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^4.
*Apr  4 04:52:57.124: dpMatchString match_tmp 4, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 4,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 4
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 5, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^5.
*Apr  4 04:52:57.124: dpMatchString match_tmp 5, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 5,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 5
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 6, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^6.
*Apr  4 04:52:57.124: dpMatchString match_tmp 6, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 6,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 6
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 7, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^7.
*Apr  4 04:52:57.124: dpMatchString match_tmp 7, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 7,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 7
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 8, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^8.
*Apr  4 04:52:57.124: dpMatchString match_tmp 8, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 8,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 8
*Apr  4 04:52:57.124: xrule_translation called Callparms Numpertype 0x81,
                               match_type 0x0
*Apr  4 04:52:57.124: xrule_translation Xrule index 9, Numpertype 0x9
*Apr  4 04:52:57.124: dpMatchString, target_number null, match_number ^9.
*Apr  4 04:52:57.124: dpMatchString match_tmp 9, match_len 1
*Apr  4 04:52:57.124: dpMatchString beginning_replace 1, match_tmp 9,target null
*Apr  4 04:52:57.124: dpMatchString: len 4
*Apr  4 04:52:57.124: xrule_translation there was no match index 9
*Apr  4 04:52:57.124: xrule_translation Return rc = -4 any_match 0
*Apr  4 04:52:57.124: xrule_checking Return rc = -4
*Apr  4 04:52:59.396: xrule_checking
*Apr  4 04:52:59.396: xrule_checking calling , called 9
*Apr  4 04:52:59.396: xrule_checking peer_tag 0, direction 1, protocol 6
*Apr  4 04:52:59.396: xrule_translation
*Apr  4 04:52:59.396: xrule_translation callednumber 9, strlen 1
*Apr  4 04:52:59.396: xrule_translation callednumber 9 xruleCalledTag=1
*Apr  4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.396: xrule_translation Xrule index 0, Numpertype 0x9
*Apr  4 04:52:59.396: dpMatchString, target_number 9, match_number ^0.
*Apr  4 04:52:59.396: dpMatchString match_tmp 0, match_len 1
*Apr  4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 0,target 9
*Apr  4 04:52:59.396: dpMatchString: len 1
*Apr  4 04:52:59.396: xrule_translation there was no match index 0
*Apr  4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.396: xrule_translation Xrule index 1, Numpertype 0x9
*Apr  4 04:52:59.396: dpMatchString, target_number 9, match_number ^1.
*Apr  4 04:52:59.396: dpMatchString match_tmp 1, match_len 1
*Apr  4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 1,target 9
*Apr  4 04:52:59.396: dpMatchString: len 1
*Apr  4 04:52:59.396: xrule_translation there was no match index 1
*Apr  4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.396: xrule_translation Xrule index 2, Numpertype 0x9
*Apr  4 04:52:59.396: dpMatchString, target_number 9, match_number ^2.
*Apr  4 04:52:59.396: dpMatchString match_tmp 2, match_len 1
*Apr  4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 2,target 9
*Apr  4 04:52:59.396: dpMatchString: len 1
*Apr  4 04:52:59.396: xrule_translation there was no match index 2
*Apr  4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.396: xrule_translation Xrule index 3, Numpertype 0x9
*Apr  4 04:52:59.396: dpMatchString, target_number 9, match_number ^3.
*Apr  4 04:52:59.396: dpMatchString match_tmp 3, match_len 1
*Apr  4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 3,target 9
*Apr  4 04:52:59.396: dpMatchString: len 1
*Apr  4 04:52:59.396: xrule_translation there was no match index 3
*Apr  4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.396: xrule_translation Xrule index 4, Numpertype 0x9
*Apr  4 04:52:59.396: dpMatchString, target_number 9, match_number ^4.
*Apr  4 04:52:59.396: dpMatchString match_tmp 4, match_len 1
*Apr  4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 4,target 9
*Apr  4 04:52:59.396: dpMatchString: len 1
*Apr  4 04:52:59.396: xrule_translation there was no match index 4
*Apr  4 04:52:59.396: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.396: xrule_translation Xrule index 5, Numpertype 0x9
*Apr  4 04:52:59.396: dpMatchString, target_number 9, match_number ^5.
*Apr  4 04:52:59.396: dpMatchString match_tmp 5, match_len 1
*Apr  4 04:52:59.396: dpMatchString beginning_replace 1, match_tmp 5,target 9
*Apr  4 04:52:59.396: dpMatchString: len 1
*Apr  4 04:52:59.396: xrule_translation there was no match index 5
*Apr  4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.400: xrule_translation Xrule index 6, Numpertype 0x9
*Apr  4 04:52:59.400: dpMatchString, target_number 9, match_number ^6.
*Apr  4 04:52:59.400: dpMatchString match_tmp 6, match_len 1
*Apr  4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 6,target 9
*Apr  4 04:52:59.400: dpMatchString: len 1
*Apr  4 04:52:59.400: xrule_translation there was no match index 6
*Apr  4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.400: xrule_translation Xrule index 7, Numpertype 0x9
*Apr  4 04:52:59.400: dpMatchString, target_number 9, match_number ^7.
*Apr  4 04:52:59.400: dpMatchString match_tmp 7, match_len 1
*Apr  4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 7,target 9
*Apr  4 04:52:59.400: dpMatchString: len 1
*Apr  4 04:52:59.400: xrule_translation there was no match index 7
*Apr  4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.400: xrule_translation Xrule index 8, Numpertype 0x9
*Apr  4 04:52:59.400: dpMatchString, target_number 9, match_number ^8.
*Apr  4 04:52:59.400: dpMatchString match_tmp 8, match_len 1
*Apr  4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 8,target 9
*Apr  4 04:52:59.400: dpMatchString: len 1
*Apr  4 04:52:59.400: xrule_translation there was no match index 8
*Apr  4 04:52:59.400: xrule_translation called Callparms Numpertype 0x0,
                               match_type 0x0
*Apr  4 04:52:59.400: xrule_translation Xrule index 9, Numpertype 0x9
*Apr  4 04:52:59.400: dpMatchString, target_number 9, match_number ^9.
*Apr  4 04:52:59.400: dpMatchString match_tmp 9, match_len 1
*Apr  4 04:52:59.400: dpMatchString beginning_replace 1, match_tmp 9,target 9
*Apr  4 04:52:59.400: dpMatchString 0. target 9,match_tmp 9,match_len 1
*Apr  4 04:52:59.400: replace_string
*Apr  4 04:52:59.400: replace_string match ^9., replace 1011009
*Apr  4 04:52:59.400: translation_format replace_rule ^9., strip_proceeding 0
*Apr  4 04:52:59.400: replace_string match_tmp ^9., strip_proceeding 0
*Apr  4 04:52:59.400: replace_string match_tmp 9
*Apr  4 04:52:59.400: replace_string direction 1, callparty  2
*Apr  4 04:52:59.400: replace_string direction 1, callparty 2, target 9
*Apr  4 04:52:59.400: replace_string match_tmp 9,replace 1011009
*Apr  4 04:52:59.400: replace_string0.replace19,target,current,match_tmp
*Apr  4 04:52:59.400: replace_string0.1 compare_len 1,match_len 1
*Apr  4 04:52:59.400: replace_string 3. replace1 9, compare_len 1
*Apr  4 04:52:59.400: replace_string 4. replace1 1,compare_len 0,replace 011009
*Apr  4 04:52:59.400: replace_string 4. replace1 10,compare_len -1,replace 11009
*Apr  4 04:52:59.400: replace_string 4. replace1 101,compare_len -2,replace 1009
*Apr  4 04:52:59.400: replace_string 4. replace1 1011,compare_len -3,replace 009
*Apr  4 04:52:59.400: replace_string 4. replace1 10110,compare_len -4,replace 09
*Apr  4 04:52:59.400: replace_string 4. replace1 101100,compare_len -5,replace 9
*Apr  4 04:52:59.400: replace_string 4. replace1 1011009,compare_len -6,replace
*Apr  4 04:52:59.400: replace_string 5. replace1 1011009, compare_len -6,match_l
en 1
*Apr  4 04:52:59.400: replace_string 6. replace1 1011009,compare_len -6,current
*Apr  4 04:52:59.400: replace_string buffer 1011009
*Apr  4 04:52:59.400: xrule_translation index 9,xrule_number 1011009, callparty
2
*Apr  4 04:52:59.400: xrule_translation Return rc = 0 any_match 0
*Apr  4 04:52:59.400: xrule_checking Return rc = 0
*Apr  4 04:53:00.156: xrule_checking
*Apr  4 04:53:00.156: xrule_checking calling 4444, called 10110099
*Apr  4 04:53:00.156: xrule_checking peer_tag 100, direction 2, protocol 0
*Apr  4 04:53:00.156: xrule_checking Return rc = -5


NewDelhi#debug translation min
*Apr  4 02:37:17.045: xrule_checking
*Apr  4 02:37:17.045: xrule_translation
*Apr  4 02:37:17.045: xrule_translation callednumber , strlen 0
*Apr  4 02:37:17.045: xrule_translation callednumber null xruleCalledTag=1
*Apr  4 02:37:19.457: xrule_checking
*Apr  4 02:37:19.457: xrule_translation
*Apr  4 02:37:19.457: xrule_translation callednumber 9, strlen 1
*Apr  4 02:37:19.457: xrule_translation callednumber 9 xruleCalledTag=1
*Apr  4 02:37:19.457: dpMatchString 0. target 9,match_tmp 9,match_len 1
*Apr  4 02:37:19.457: replace_string
*Apr  4 02:37:19.461: replace_string0.replace19,target,current,match_tmp
*Apr  4 02:37:19.461: replace_string0.1 compare_len 1,match_len 1
*Apr  4 02:37:19.461: replace_string 3. replace1 9, compare_len 1
*Apr  4 02:37:19.461: replace_string 4. replace1 1,compare_len 0,replace 011009
*Apr  4 02:37:19.461: replace_string 4. replace1 10,compare_len -1,replace 11009
*Apr  4 02:37:19.461: replace_string 4. replace1 101,compare_len -2,replace 1009
*Apr  4 02:37:19.461: replace_string 4. replace1 1011,compare_len -3,replace 009
*Apr  4 02:37:19.461: replace_string 4. replace1 10110,compare_len -4,replace 09
*Apr  4 02:37:19.461: replace_string 4. replace1 101100,compare_len -5,replace 9
*Apr  4 02:37:19.461: replace_string 4. replace1 1011009,compare_len -6,replace
*Apr  4 02:37:19.461: replace_string 5. replace1 1011009, compare_len -6,match_l
en 1
*Apr  4 02:37:19.461: replace_string 6. replace1 1011009,compare_len -6,current
*Apr  4 02:37:19.461: replace_string buffer 1011009
*Apr  4 02:37:19.461: xrule_translation index 9,xrule_number 1011009, callparty
2
*Apr  4 02:37:19.841: xrule_checking

Informações Relacionadas

Colaboração de

dharper
dfuss

Usando regras de tradução IOS - Criando planos de discagem escaláveis para redes VoIP

Opções de download

Linguagem imparcial

Sobre esta tradução

Contents

Colaboração de

Este documento lhe foi útil?

Contate a Cisco

Este documento se refere a estes produtos