We are using Release Link Trunks for our Centralize Attendant Service and since I'm not very familiar with this type of trunk, I'm not sure where to look to solve my problem... When a user dial "0" and ask a transfer to "911", the CAS operator can't transfer the call as he gets a "Fast Busy".
The user is on PBX "A" and the operator is on PBX "B". I have 6 Release Link Trunks between the two PBX's. On PBX "A", 911 is programmed as an ESA DN pointing to ESRT XX (PRI). Route XX is fed right back in to PBX "A" thru Route YY (PRI)which members auto-terminate to extension 1234.
We have our own Emergency Services so locally, when a user dials 911, he ends up at extension 1234 which is our Emergency Call Center. But if a user dial "0" and asked to be transferred to 911, the CAS Operator gets a Fast Busy and can't transfer the call.
I suspect that it might have to do with the fact that the transfer is seen as a "trunk to trunk" call so PBX "A" won't let the call go thru. If I use a local Console, I can transfer the call no problem.
Any idea anyone?
The user is on PBX "A" and the operator is on PBX "B". I have 6 Release Link Trunks between the two PBX's. On PBX "A", 911 is programmed as an ESA DN pointing to ESRT XX (PRI). Route XX is fed right back in to PBX "A" thru Route YY (PRI)which members auto-terminate to extension 1234.
We have our own Emergency Services so locally, when a user dials 911, he ends up at extension 1234 which is our Emergency Call Center. But if a user dial "0" and asked to be transferred to 911, the CAS Operator gets a Fast Busy and can't transfer the call.
I suspect that it might have to do with the fact that the transfer is seen as a "trunk to trunk" call so PBX "A" won't let the call go thru. If I use a local Console, I can transfer the call no problem.
Any idea anyone?