User's Manual
19-2 Preliminary May 9, 2000  APX 8000/MAX TNT/DSLTNT Physical Interface Configuration Guide
Configuring Call Routing
Understanding the call-routing database
Some slot cards act in a dual capacity, performing both network and host functions. Some 
dual-purpose cards provide their own HDLC resources. For example, T1 and E1 FrameLine 
cards have HDLC channels integrated into the card and support Frame Relay protocols.
Other cards establish the physical connection and terminate calls. Calls on these cards do not 
require additional HDLC processing.
The following table shows a representative listing of cards in each category:
Understanding the call-routing database
The Callroute command displays entries in the call-routing database. You can display entries 
for network, host, or dual-purpose devices, or list entries by device. For example, the Callroute 
command with the -ad flag displays database entries for dual-purpose devices:
admin> callroute -ad
 device # source type  tg sa phone
 1:16:01/0 0 0:00:00/0 digital-call-type 0 0
 2:14:01/0 0 0:00:00/0 digital-call-type 0 0
 1:15:01/0 0 0:00:00/0 any-call-type 0 0
 2:04:01/0 0 0:00:00/0 any-call-type 0 0
 2:04:02/0 0 0:00:00/0 any-call-type 0 0
 2:04:03/0 0 0:00:00/0 any-call-type 0 0
 2:04:04/0 0 0:00:00/0 any-call-type 0 0
Table 19-1 describes the information contained in each field.
Network slot cards Host slot cards Dual-purpose slot cards
T1 Series56 II Digital Modem Unchannelized DS3
T3 Series56 III Digital Modem T1 FrameLine
E1 Hybrid Access E1 FrameLine
MultiDSP
Table 19-1. Fields in a call-routing database entry
Field Contains
Device The address of a device installed in the system to which calls 
matching the entry will be routed. The address has the following 
format:
shelf:slot:line/channel
For example, shelf 1, slot 2, line 1, channel 24 is addressed as 
1:02:01/24.
# The call-routing entry number. For default entries (entries 
created by the system for a device) the value is always zero. For 
entries created by Call-Route profiles, the number must be 
unique for each entry that has the same Device address. For 
details, see “Call-Route profile settings” on page 19-5.










