Configuring Individual WAN Connections
Configuring MP, MP+ and BACP connections
MAX 6000/3000 Network Configuration Guide 4-61
Figure4-7. Hunt groups for a MAX stack handling both MP and MP+ calls
In Figure 4-7, suppose an MP+ call is connected to MAX #1. When that call needs to add a
channel, it requests an add-on number from the MAX unit, and the unit returns 12 (for
555-1212) as long as a channel in the local T1 lines is available. That is, the bundle does not
span multiple MAX units as long as a channel is available in the local hunt group.
The Figure 4-7 configuration tends to break down if MAX units receive MP-without-BACP
calls. Spreading the calls across the MAX stack (by dialing the global hunt group) results in the
worst possible performance, because MP without BACP must know all of the telephone
numbers before the caller places the first call.
MP-without-BACP calls
Figure 4-8 shows a site that supports only MP-without-BACP calls. For this site, the telephone
company has set up a global hunt group that first completely fills MAX #1, then continues to
MAX #2, and so on. This arrangement tends to keep the channels of a call from being split
across multiple MAX units, keeping overhead low.
Figure 4-8. Hunt groups for a MAX stack handling only MP-without-BACP calls
MP+ calls and MP calls with or without BACP
For a MAX unit that receives MP+ calls and MP calls with or without BACP, you can use a
configuration similar to the one shown in Figure 4-8. In this case, however, you set up the
global hunt group differently than explained in “MP+ and MP-with-BACP calls.” You set up
the global hunt group to help prevent MP-without-BACP calls from being s plit across multiple
Three T1 lines, all in 555-1212
and 555-1215 hunt groups
Three T1 lines, all in 555-1213
and 555-1215 hunt groups
Three T1 lines, all in 555-1214
and 555-1215 hunt groups
MAX #3
MAX #2
MAX #1
Three T1 lines, all in 555-1212 hunt group
Three T1 lines, all in 555-1212 hunt group
Three T1 lines, all in 555-1212 hunt group
MAX #1
MAX #2
MAX #3