Session Router Configuration
207
Figure 22-1: Direct Call Routing vs. Advanced Session Routing
Due to the tree search algorithm implemented in the Session Router very large routing tables can be
scanned very quickly with minimal impact on the call setup delay. The SmartWare Session Router
supports the following routing criteria:
•
Calling Party Number (CnPN); also called Source-Nr, A-Nr, MSN, DDI or CLIP
•
Called Party Number (CdPN); also called Destination-Nr or B-Nr
•
ISDN Bearer Capability; also called ISDN Service or information transfer capability (ITC)
•
Day of Week; Mon - Sun
•
Time of Day; hour:minute
•
Date; year/month/day
22.1.1 Routing Table Structure
Every routing table has the same general format:
type <name> {<key>|default} {dest-table <dst-name> | dest-interface <dst-name> | none} [<function>]
type Identifies
the
type
of the table according to the routing criteria
<name>
Is a unique name identifying the table. Use “speaking” names
<key>
Is the matching
key
, according to the routing criteria. The Session Router reads
through the table to find the best matching key. Having found one, it examines the
other elements in that row. The default matching key is followed if no other row
matches. If no default entry is configured and no other entry matches, the call is
routed to the fallback destination configured on the interface.
dest-table
Specifies the routing table (name) to be used as the next step in the decision tree. The
call setup is forwarded to the table and matched against the keys.
Software Configuration Guide, Revision 1.03
Summary of Contents for SmartWare R2.00
Page 2: ......