DarrylJR
Technical User
- Sep 2, 2014
- 1
It seems from experience that the ESI 50L automated attendant is limited to processing at most two calls at the same time, but I have not found this limitation in any ESI spec sheet or manual. Can anyone confirm that what I think I see as a limit is the real limit? I have looked at a lot of spec sheets and manuals for the ESI 50L, but have not found a capacity/limit for the number of simultaneous calls the automated attendant can handle. Can anyone point me to any official ESI documentation that lists this capacity/limit?
What should happen when the auto attendant is busy on two calls and a third incoming call is received? We switched from trunks via an MCI fractional T-1 service to trunks via a SIP provider to a Cisco SPA 8000 ATA to which the ESI 50L connects. After this switch, a caller on a third incoming call (when the automated attendant is busy on two other calls) gets either a busy, fast busy, or dead air and a disconnect, depending on what carrier is used to make the call. This does not seem reasonable and I suspect the SIP provider is generating this, not the ESI 50L. I never explicitly tried to check this capacity/limit when the ESI 50L was connected to the MCI fractional T-1 trunks. Is this what I should expect from an ESI 50L?
What should happen when the auto attendant is busy on two calls and a third incoming call is received? We switched from trunks via an MCI fractional T-1 service to trunks via a SIP provider to a Cisco SPA 8000 ATA to which the ESI 50L connects. After this switch, a caller on a third incoming call (when the automated attendant is busy on two other calls) gets either a busy, fast busy, or dead air and a disconnect, depending on what carrier is used to make the call. This does not seem reasonable and I suspect the SIP provider is generating this, not the ESI 50L. I never explicitly tried to check this capacity/limit when the ESI 50L was connected to the MCI fractional T-1 trunks. Is this what I should expect from an ESI 50L?