5.2.14  
Centralized Attendant Service CAS (for U.S. only) 
 

Definition  
This feature allows for the conservation of T1 TIE line trunks when the attendant at a center PBX system answers a call that originated at the store PBX (branch) and who's destination extension is also at the store PBX. Without the CAS feature, this type of scenario would force the system to use 2 T1 channels for every call that was transferred back to the branch. CAS will conserve the T1 channels by releasing the T1 channel after the call is transferred so that no T1 channels are in use for the duration of the call after transfer.
The typical CAS application for a Federated store consists of the CAS store PBX (branch), the CAS center PBX (center) and a minimum of two tie lines that function as release link trunks RLT.
The typical RLT is a channel on a T1 card in the branch PBX that is mapped in a private network to a CAS center to be answered by a pool of operators.
A typical store (branch PBX) would have a T1 card with the first 8-12 channels mapped as tie trunks to one hub to carry standard tie line traffic. 2 or more of the remaining channels on the same T1 card are mapped as RLT's.
Example for an incoming call: A customer calls the branch PBX on the main DID number. The branch PBX then routes this DID call to a RLT. The RLT carries the call to the CAS center and the CAS operator answers the call. The operator finds out what our customer is calling for and then transfers the call to the appropriate extension in the branch PBX.
If all RLT's are busy then the call will queue. The caller will hear a recording all operators are busy please hold. When a RLT becomes idle then the queued call hits the RLT.
The transfer process consists of:
 1.   The CAS center operator hits the "CAS flash" key after have talked to the customer and found out which extension number to transfer the call to.
 2.   The CAS center PBX transmits a "hook switch flash" over the RLT.
 3.   The branch PBX recognizes the "hook switch flash" and puts the DID trunk on hold and gives dial tone back to the CAS operator.
 4.   The CAS center operator dials the destination extension number.
 5.   The branch PBX receives the extension number and starts to ring the phone.
 6.   At this point the CAS center operator can
   •  stay on the call and wait for answer and do a supervised transfer, or
   •  release the call and let the transfer finish as unsupervised transfer.
 7.   When the CAS operator releases the call the RLT drops, the branch PBX finish's the transfer.
 8.   The DID trunk is directly connected to the destination extension.
 9.   The RLT is idle and ready for the next call.

Model-Specific Data  

 Subject  
 HiPath 3800  
 HiPath 3550  
 HiPath 3500  
 HiPath 3350  
 HiPath 3300  
Feature available in  
 x  
 x  
 -  
Hardware requirements  
 DIUN2, DIUT2  
 TS2 / TS2R  
 -  
Software requirements  
 V5.0 or later  
 V1.0 or later  
 -  

Dependencies/Restrictions  

 Subject  
 Dependency/Restriction  
CAS store PBX
(branch)  
HiPath 3000 supports the CAS store PBX (branch) of the application.  
CAS center PBX
(center)  
Support for the CAS center PBX (center) of the application is supplied by another type of PABX (e. g. Rolm 9005 or a Lucent switch) that supports the center where the attendants are located in the application.  

HiPath 3000/5000 V8, Feature Description, Issue 10   up Top
Disclaimer & Copyright   ID: P31003H3580F100017618   2011-02-07