Hi,
We have a CAS setup where incoming calls to one location are routed over RLT (TIE) trunks to attendants in another switch. Operators then transfer the calls back to the original PBX.
When call volume is high, at times, callers get a busy even though the trunks are idle. To fix the problem we busy/release the RLT trunk group at the distant PBX. There are no alarms or errors in the switch when this is happening.
This has happened at multiple locations for us (all Avaya CM R15) and we would like to fix it.
Anybody have a similar problem?
Good description of RLT trunks below;
The original purpose of Release Link Trunks was for multiple PBXs sharing a pool of attendant resources(Centralized Attendant Services (CAS)) at one PBX. Attendant seeking calls were sent over the RLTs to be answered. The attendant then 'flashed' the trunk to request a TT receiver at the originating PBX. The attendant dialed the extension for the caller and the RLT was released. These trunks were designed for alot of calls with a very short holding times. THe term RLT has evolved to mean services like Transfer Connect (AT&T) and Take-back and Transfer (MCI) where rather than tandem a call through a PBX, which uses 2 trunks, the network is 'flashed' and the call transferred in the 'cloud' and the network to PBX trunk is released for another call.
Thanks for your help.
Posted in another forum also.
We have a CAS setup where incoming calls to one location are routed over RLT (TIE) trunks to attendants in another switch. Operators then transfer the calls back to the original PBX.
When call volume is high, at times, callers get a busy even though the trunks are idle. To fix the problem we busy/release the RLT trunk group at the distant PBX. There are no alarms or errors in the switch when this is happening.
This has happened at multiple locations for us (all Avaya CM R15) and we would like to fix it.
Anybody have a similar problem?
Good description of RLT trunks below;
The original purpose of Release Link Trunks was for multiple PBXs sharing a pool of attendant resources(Centralized Attendant Services (CAS)) at one PBX. Attendant seeking calls were sent over the RLTs to be answered. The attendant then 'flashed' the trunk to request a TT receiver at the originating PBX. The attendant dialed the extension for the caller and the RLT was released. These trunks were designed for alot of calls with a very short holding times. THe term RLT has evolved to mean services like Transfer Connect (AT&T) and Take-back and Transfer (MCI) where rather than tandem a call through a PBX, which uses 2 trunks, the network is 'flashed' and the call transferred in the 'cloud' and the network to PBX trunk is released for another call.
Thanks for your help.
Posted in another forum also.