Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
427 Wideband Switching 
15
Networking
All of the wideband networking is over ISDN-PRI facilities (and the emulation of 
them by ATM-CES) but may connect to a variety of networks, other domestic 
interexchange carriers’ services, private line, RBOC services, and services in 
other countries.
ISDN-PRI trunk groups and channel
allocation
Only ISDN-PRI trunks (and the emulation of them by ATM-CES) support 
wideband calls to the network. Wideband’s bandwidth requirements have 
necessitated modification of the algorithms by which trunks look for idle 
channels. The following section describes the search methods and their 
relationship to the available wideband data services.
Facility lists
The system always sends a wideband call over a single trunk group and a single 
DS1 facility (or other ISDN-PRI-capable facility). Since a trunk group may 
contain channels (trunk members) from several different DS1 facilities, the system 
maintains a facility list for each trunk group.
A facility list orders the trunk members based on signaling group. If the system is 
using non-facility associated signaling groups with multiple DS1 facilities, the 
system sorts trunk members in that signaling group according to the interface 
identifier assigned to the corresponding DS1 facility.
When searching for available channels for a wideband call placed over a given 
trunk group, the system starts with the channels in the lowest-numbered signaling 
group with the lowest interface identifier. If the system cannot find enough 
channels in a given signaling group with that interface identifier, it checks the next 
higher interface identifier. If no more interface identifiers are available in the 
current signaling group, the system moves its search to the channels in the next 
higher signaling group.
For example, if three facilities having signaling group/interface identifier 
combinations of 1/1, 1/2, and 2/1 were associated with a trunk group, then a call 
offered to that trunk group would search those facilities in the order as they were 
just listed. Also note that since trunks within a given facility can span several 
trunk groups, a single facility can be associated with several different trunk 
groups. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
428 Wideband Switching 
15
Given this facility list concept, the algorithms have the ability to search for trunks, 
by facility, in an attempt to satisfy the bandwidth requirements of a given 
wideband call. If one facility does not have enough available bandwidth to support 
a given call, or it is not used for a given call due to the constraints presented in the 
following section, then the algorithm searches the next facility in the trunk group 
for the required bandwidth (if there is more than one facility in the trunk group).
In addition to searching for channels based on facilities and required bandwidth, 
Port Network (PN) preferential trunk routing is also employed. This PN routing 
applies within each algorithm at a higher priority than the constraints put on the 
algorithm by the parameters listed later in this section. In short, all facilities that 
reside on the same PN as the originating endpoint are searched in an attempt to 
satisfy the bandwidth of a given call, prior to searching any facilities on another 
PN.
Direction of trunk/hunting within facilities
You can tell the system to search for available channels in either ascending or 
descending order. These options help you reduce glare on the channels because 
the system can search for channels in the opposite direction to that used by the 
network. If an ISDN trunk group is not optioned for wideband, then a cyclical 
trunk hunt based on the administration of trunks within the trunk group is still 
available.
H11
When a trunk group is administered to support H11, the algorithm to satisfy a call 
requiring 1,536 Kbps of bandwidth uses a fixed allocation scheme. That is, the 
algorithm searches for an available facility using the following facility-specific 
channel definitions:
nT1: H11 can only be carried on a facility without a D-channel being 
signaled in an NFAS arrangement (B-channels 1-24 are used).
nE1: Although the 1,536 Kbps bandwidth could be satisfied using a number 
of fixed starting points (for example, 1, 2, 3, and so forth), the only fixed 
starting point being supported is 1. Hence, B-channels 1-15 and 177-25 
always are used to carry an H11 call on an E1 facility.
If the algorithm cannot find an available facility within the trunk that meets these 
constraints, then the call is blocked from using this trunk group. In this case, the 
call may be routed to a different trunk group preference via Generalized Route 
Selection (GRS), at which time, based on the wideband options administered on 
that trunk group, the call would be subject to another hunt algorithm (that is, either 
the same H11 algorithm or perhaps an N x DS0 algorithm described in a later 
paragraph). 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
429 Wideband Switching 
15
Note that on a T1 facility, a D-channel is not considered a busy trunk and results in 
a facility with a D-channel always being partially contaminated. On an E1 facility, 
however, a D-channel is not considered a busy trunk because H11 and H12 calls 
may still be placed on that facility; an E1 facility with a D-channel and idle 
B-channels is considered an idle facility.
H12
Since H12 is 1,920 Kbps which is comprised of 30 B-channels, a 1,920-kbps call 
can only be carried on an E1 facility. As with H11, the hunt algorithm uses a fixed 
allocation scheme with channel 1 being the fixed starting point. Hence, an H12 
call always is carried on B-channels 1 to 15 and 17 to 31 on an E1 facility (as 
shown in the following table). When offered any other call (other than a 
1,536-kbps call), the algorithm behaves as it does when H11 is optioned.
H0
When a trunk group is administered to support H0, the algorithm to satisfy a call 
requiring 384 Kbps of bandwidth also uses a fixed allocation scheme. Unlike the 
H11 fixed scheme which only supports a single fixed starting point, the H0 fixed 
scheme supports 4 (T1) or 5 (E1) starting points. The H0 algorithm searches for 
an available quadrant within a facility based on the direction of trunk or hunt 
administered. If the algorithm cannot find an available quadrant within any facility 
allocated to this trunk group, then the call is blocked from using this trunk group. 
Again, based on GRS administration, the call may route to a different trunk group 
preference and be subject to another algorithm based on the wideband options 
administered.
Note that a D-channel is considered a busy trunk and results in the top most 
quadrant of a T1, B-channels 19 to 24, always being partially contaminated. This 
is not true for NFAS.
If this H0 optioned trunk group is also administered to support H11, H12, or N x 
DS0, then the system also attempts to preserve idle facilities. In other words, when 
offered a narrowband, H0, or N x DS0 call, the system searches 
partially-contaminated facilities before it searches to idle facilities.
DS0s Comprising Each Channel
FacilityISDN
Interface H11 H12
T1
T123B + D
24B (NFAS)-
1-24-
-
E1
E130B + D
31B (NFAS)1-15, 17-25
1-15, 17-251-15, 17-31
1-15, 17-31 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
430 Wideband Switching 
15
N x DS0
For the N x DS0 multi-rate service, a trunk group parameter determines whether a 
floating or a flexible trunk allocation scheme is to be used. The algorithm to 
satisfy an N x DS0 call is either floating or flexible.
nFloating (Contiguous) — In the floating scheme, an N x DS0 call is placed 
on a contiguous group of B-channels large enough to satisfy the requested 
bandwidth without any constraint being put on the starting channel (that is, 
no fixed starting point trunk).
nFlexible — In the flexible scheme, an N x DS0 call is placed on any set of 
B-channels as long as the requested bandwidth is satisfied. There is 
absolutely no constraint such as contiguity of B-channels or fixed starting 
points. Of course, as with all wideband calls, all the B-channels comprising 
the wideband call must reside on the same ISDN facility.
Regardless of the allocation scheme employed, the N x DS0 algorithm, like 
the H11 and H12 algorithms, attempts to preserve idle facilities when 
offered B, H0, and N x DS0 calls. This is important so that N x DS0 calls, 
for large values of N, have a better chance of being satisfied by a given 
trunk group. However, if one of these calls cannot be satisfied by a 
partially-contaminated facility and an idle facility exists, a trunk on that 
idle facility is selected, thus contaminating that facility.
There are additional factors to note regarding specific values of N and the 
NxDS0 service:
— N = 1 — this is considered a narrowband call and is treated as any 
other voice or narrowband-data (B-channel) call.
— N = 6 — if a trunk group is optioned for both H0 and N x DS0 
service, a 384-kbps call offered to that trunk group is treated as an 
H0 call and the H0 constraints apply. If the H0 constraints cannot be 
met, then the call is blocked.
— N = 24 — if a trunk group is optioned for both H11 and N x DS0 
service, a 1,536-kbps call offered to that trunk group is treated as an 
H11 call and the H11 trunk allocation constraints apply.
— N = 30 — if a trunk group is optioned for both H12 and N x DS0 
service, a 1,920-kbps call offered to that trunk group is treated as an 
H12 call and the H12 trunk allocation constraints apply. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
431 Wideband Switching 
15
Glare and blocking
Glare prevention
Glare occurs when both sides of an ISDN interface select the same B-channel for 
call initiation. For example, a user side of an interface selects the B-channel for an 
outgoing call and, before the switch receives and processes the SETUP message, 
the switch selects the same B-channel for call origination. Since any single 
wideband call uses more channels, the chances of glare are greater. With proper 
and careful administration, glare conditions can be reduced.
To reduce glare probability, the network needs to be administered so both sides of 
the interface select channels from opposite ends of facilities. This is called linear 
hunting, ascending or descending. For example, on a 23B+D trunk group, the user 
side could be administered to select B-channels starting at channel 23 while the 
network side would be administered to start selecting at channel 1. Using the same 
example, if channel 22 is active but channel 23 is idle, the user side should select 
channel 23 for re-use.
Blocking prevention
Blocking occurs when insufficient B-channels required to make a call are 
available. Narrowband calls require only one channel so blocking is less likely 
than with wideband calls which require multiple B-channels. Blocking also occurs 
for wideband calls when bandwidth is not available in the appropriate format (that 
is, fixed, floating, or flexible).
To reduce blocking, the switch selects trunks for both wideband and narrowband 
calls to maximize availability of idle fixed channels for H0, H11, and H12 calls 
and idle floating channels for N x DS0 calls that require a contiguous bandwidth. 
The strategy for preserving idle channels to minimize blocking depends on the 
channel type. The chances for blocking are reduced if you use a flexible 
algorithm, assuming it is supported on the other end.
Channel Type Blocking Minimization Strategy
H0 Preserve idle quadrants
H11 Preserve idle facilities
H12 Preserve idle facilities
Flexible NxDS0 Preserve idle facilities
Floating NxDS0 Preserve idle facilities as first priority 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
432 Wideband Switching 
15
Administering Wideband Switching
Before you start
You need a DS1 Converter circuit pack. Refer to the DEFINITY ECS System 
Description for more information on the circuit pack.
Instructions
To administer wideband switching:
1. On the Access Endpoint screen, administer all fields. 
Refer to ‘‘
Access Endpoint’’ on page 467 for more information.
2. On the PRI Endpoint screen, administer all fields. 
Refer to ‘‘
PRI Endpoint’’ on page 853 for more information.
3. On the ISDN Trunk Group screen, administer all fields. 
Refer to ‘‘
ISDN trunk group’’ on page 738 for more information.
4. On the Route Pattern screen, administer all fields. 
Refer to ‘‘
Route Pattern’’ on page 865 for more information.
NOTE:
The following is optional.
5. On the Fiber Link Administration, administer all fields. 
Refer to DEFINITY ECS Administration for Network Connectivity for more 
information.
Considerations 
nFor wideband switching with non-ISDN-PRI equipment, you can use an 
ISDN-PRI terminal adapter.
Interactions
nAdministered Connections
Provides call initiation for Wideband Access Endpoints (WAEs). All 
Administered Connections that originate from WAEs use the entire 
bandwidth administered for WAE. The destination of an Administered 
Connection can be a PRI endpoint. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
433 Wideband Switching 
15
nAutomatic Circuit Assurance 
Treats wideband calls as logical single-trunk calls so that a single 
ACA-referral call is made if an ACA-referral call is required. The call is 
referred to the lowest B-channel associated with the wideband call.
nCall Coverage
A wideband endpoint extension cannot be administered as a coverage point 
in a call-coverage path.
nCall Detail Recording 
When CDR is active for the trunk group, all wideband calls generate CDR 
records. The feature flag indicates a data call and CDR records contain 
bandwidth and Bearer Capability Class (BCC). 
nCall Forwarding
You must block Call Forwarding through Class of Service.
nCall Management System and Basic Call Management System
Wideband calls can be carried over trunks that are measured by CMS and 
BCMS. Wideband endpoints are not measured by CMS and BCMS.
nCall Vectoring
PRI endpoints can use a vector-directory number (VDN) when dialing. For 
example, PRI endpoint 1001 dials VDN 500. VDN 500 points to Vector 1. 
Vector 1 can point to other PRI endpoints such as route-to 1002, or route-to 
1003, or busy.
Call Vectoring is used by certain applications. When an incoming 
wideband call hunts for an available wideband endpoint, the call can route 
to a VDN, that sends the call to the first available PRI endpoint. 
nClass of Restriction
COR identifies caller and called-party privileges for PRI endpoints. 
Administer the COR so that account codes are not required. Forced entry of 
account codes is turned off for wideband endpoints. 
nFacility Busy Indication
You can administer a busy-indicator button for a wideband-endpoint 
extension, but the button does not accurately track endpoint status.
nFacility Test Calls
You can use Facility Test Calls to perform loop-back testing of the 
wideband call facility. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
434 CallVisor Adjunct-Switch Application Interface 
15
nGeneralized Route Selection
GRS supports wideband BCC to identify wideband calls. GRS searches a 
route pattern for a preference that has wideband BCC. Route preferences 
that support wideband BCC also can support other BCCs to allow different 
call types to share the same trunk group.
nCO Trunk (TTC - Japan) Circuit Pack
This circuit pack cannot perform wideband switching. No member of the 
circuit pack should be a member of a wideband group.
CallVisor Adjunct-Switch Application 
Interface
CallVisor Adjunct-Switch Applications Interface (ASAI) links DEFINITY ECS 
and adjunct applications. The interface allows adjunct applications to access 
switch features and supply routing information to the switch. CallVisor ASAI 
improves Automatic Call Distribution (ACD) agents’ call handling efficiency by 
allowing an adjunct to monitor, initiate, control, and terminate calls on the switch. 
The CallVisor ASAI interface may be used for Inbound Call Management (ICM), 
Outbound Call Management (OCM), and office automation/messaging 
applications.
CallVisor ASAI is supported by two transport types. These are:
1. Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) 
transport (CallVisor ASAI-BRI)
2. LAN Gateway Transmission Control Protocol/Internet Protocol transport 
(DEFINITY LAN Gateway).
CallVisor ASAI messages and procedures are based on the ITU-T Q.932 
international standard for supplementary services. The Q.932 Facility Information 
Element (FIE) carries the CallVisor ASAI requests and responses across the 
interface. An application program can access CallVisor ASAI services by 
supporting the ASAI protocol or by using a third-party vendor application 
programming interface (API).
For a simple ASAI configuration example, refer to Figure 15
. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
435 CallVisor Adjunct-Switch Application Interface 
15
Figure Notes
Figure 15. ASAI Switch Interface Link — BRI Transport
ASAI Capabilities
For information concerning the types of associations over which various event 
reports can be sent, refer to DEFINITY ECS CallVisor ASAI Technical Reference.
Considerations
nIf your system has an expansion cabinet (with or without duplication), 
ASAI resources should reside on the system’s Processor Cabinet.
Interactions
Refer to DEFINITY ECS CallVisor ASAI Technical Reference. 1. ASAI adjunct
2. ISDN Line circuit pack
3. Packet Controller circuit pack
4. Switch processing element (SPE)5. ISDN-BRI
6. Packet bus
7. Memory bus 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
436 Setting up CallVisor ASAI 
15
Setting up CallVisor ASAI
CallVisor Adjunct-Switch Applications Interface (ASAI) can be used in the 
telemarketing and help-desk environments. It is used to allow adjunct applications 
to monitor and control resources in the DEFINITY ECS.
Before you start
nOn the System Parameters Customer-Options screen, verify the:
— ASAI Interface field is 
y. If not, contact your Lucent representative.
— ASAI Proprietary Adjunct Links field is 
y if the adjunct is running 
the CentreVu Computer Telephony.
Instructions
To set up CallVisor ASAI:
1. Type 
add station nnnn and press RETURN, where nnnn is the extension you 
want to assign to the ASAI adjunct.
The Station
 screen appears.
2. In the Type field, type
nasai if this adjunct platform is other than CentreVu Computer 
Telephony, for example, IBM CallPath.
nadjlk (ASAI proprietary adjunct link) if this is for the CentreVu 
Computer Telephony using the Telephony Services Application 
Programming Interface (TSAPI).
                                                              Page 1 of X
                                          STATION
Extension: 1014                                Lock Messages? n       BCC: 0
Type: asai                         Security Code: ______   TN: 1
Port: 01A0702 Coverage Path 1: ___     COR: 1
    Name: __________________________  Coverage Path 2: ___     COS: 1
                                             Hunt-to-Station: ____
STATION OPTIONS
             Data Module? n                  Personalized Ringing Pattern: 1
        Display Module? n                              Message Lamp Ext: 1014
 
        MM Complex Data Ext: ____