Epygi QX series, Administrator'S Manual

Page: 60 / 151

QX5
QXFXO4/QXISDN4/QXE1T1/QXFXS24; (SW Version 6.0.x) 60
QXFXO4/QXISDN4/QXE1T1/QXFXS24 Manual II: Administrator’s Guide
The
Call Routing Wizard – Tracing/Debug Options
page appears if the
Set Tracing / Debug Options on This Rule
checkbox was previously
enabled on Page 1 of the
Local Call Routing Wizard
. It will require
information about the tracing/debug options.
This page offers result options of the corresponding routing rule
execution when the notification event will be printed in the System
Events page.
• In Case of Successful Call
– a notification event is printed
when the successful call was established with the routing
rule.
• In Case of Failover
– a notification event is printed when
the call ends up on one of the failover reasons selected on
the Page 2 of the
Local Call Routing Wizard.
• In Case if Call Failed to Establish
– a notification event is
printed when the call executed with the routing rule failed.
Fig.II- 72: Call Routing Wizard – Tracing/ Debug Options page
Call Routing
The
Call Routing
page offers the following components:
•
When the
Route all incoming SIP calls to Call Routing
checkbox is
disabled, for all incoming SIP calls QX will first search the incoming
SIP address in the Extensions Management table. If found, the
incoming SIP call will ring on the corresponding extension. If not
found, QX will look for a matching routing rule in Call Routing Table .
When the
Route all incoming SIP calls to Call Routing
checkbox is
enabled, for all incoming SIP calls QX will directly look for a
matching routing rule in Call Routing Table and will ignore the
possible matches in the Extensions Management table.
Fig.II- 73: Call Routing page
Attention:
Regardless of whether the
Route all incoming SIP calls to Call Routing
checkbox is selected or not, SIP calls from external callers will or
may go to the Call Routing table, so any unprotected routing rule can be misused. That is why it is strongly recommended to secure the rules in the
Call Routing table by setting the filtering or authentication options.
Local AAA Table
The
Local AAA Table
page allows you to manage local authentication and the authorization database. Callers dialing the routes which have an AAA
(Authentication, Authorization, and Accounting) option enabled, will pass the authorization on the
Local AAA Table
by using a phone number or
username/password, depending on the corresponding entry configuration on this page.
The caller passes authorization automatically if the detected phone
number of the caller dialing a route has the AAA option enabled and is
registered in the
Local AAA Table
. If the caller ID service is disabled or
the caller’s phone number is not registered, the caller is asked to enter a
registration user name and password.
The
Add
functional button opens the
Call Routing – Local AAA Table -
Add Entry
page where a new local AAA record can be created.
The
Call Routing – Local AAA Table - Add Entry
page offers a group of
manipulation radio buttons to select the type of authorization and the
following other parameters:
Fig.II- 74: Call Routing - Local AAA Table page