RedMax EXtreme EX-LRT Guia de Resolução de Problemas descarregar pdf (Página 83)

Oracle SBC Security Guide

media-profiles

lookup single

next-key

eloc-str-lkup disabled

eloc-str-match

Create the LRT configuration referenced above. Note that the “best” match mode matches from most

specific to least specific in the LRT table (greatest number of digits matched to fewest).

local-routing-config

name blacklist

file-name blacklist.xml.gz

prefix-length 15

string-lookup disabled

retarget-requests enabled

match-mode best

last-modified-by [email protected]

last-modified-date 2012-10-26 15:40:48

Sample Entries from the LRT are seen below. In this case I’ve opted to forward the blacklist call onto a

“dummy” session agent. You may opt to forward the call onto a recording, or session agent that handles

fraud calls.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<localRoutes xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<route>

<user type="E164">3712900</user>

<next type="regex">!(^.*$)!sip:\110.11.12.13!</next>

</route>

<route>

<user type="E164">88183521</user>

<next type="regex">!(^.*$)!sip:\[email protected]!</next>

</route>

<route>

<user type="E164">2637749</user>

<next type="regex">!(^.*$)!sip:\[email protected]!</next>

</route>

<route>

<user type="E164">3718104</user>

<next type="regex">!(^.*$)!sip:\[email protected]!</next>

</route>

<route>

<user type="E164">3718103</user>

<next type="regex">!(^.*$)!sip:\[email protected]!</next>

</route>

<route>

<user type="E164">3716852</user>

<next type="regex">!(^.*$)!sip:\[email protected]!</next>

</route>

<route>

<user type="E164">447924</user>

<next type="regex">!(^.*$)!sip:\[email protected]!</next>

</route>

<route>

<user type="E164">3712769</user>

1 2 ... 78 79 80 81 82 83 84 85 86 87 88 ... 141 142

Comentários a estes Manuais

Sem comentários