Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Shooter on February 18, 2016, 11:56:56 AM

Title: Call Handling Capacity- URS, SIP, T-server
Post by: Shooter on February 18, 2016, 11:56:56 AM
How many calls URS/SIP/T-servers can handle simultaneously ?
Title: Re: Call Handling Capacity- URS, SIP, T-server
Post by: hsujdik on February 18, 2016, 01:53:48 PM
It depends on some things:
1. Number of licenses - URS has a license feature called router_seats. This is the number of concurrent calls URS can route. Older versions of FlexLM only allow to check out 9999 licenses at once, that means that 9999 calls at most can be handled by a given URS on these conditions. Other than that; For T-Server/SIP Server, the number of calls on Technical DNs (Routing Points, Virtual Queue, etc) is currently unlimited, while the number of Seat DNs (Extensions and ACD Queues) are limited to the number of tserver_sdn feature on your license file.

2. Hardware - Genesys is a software and depends on the upper layers to work (Operating System, Host, Network, Storage, RAM, etc). You can find some sizing guides on Genesys Documentation website (https://docs.genesys.com/Home) pointing how to perform a sizing based on your hardware specs. The "Genesys Hardware Sizing Guide" states that, in general, a single instance of SIP Server can handle 15,000 simultaneous calls

3. Your call flow - Some call flows may consume more resource than others. That is very deployment specific and a LSST (Large-scale Stress Test) should be performed.

Those are the ones that I remember
Title: Re: Call Handling Capacity- URS, SIP, T-server
Post by: cavagnaro on February 18, 2016, 02:50:10 PM
A point is also which codec you will use, g711 is easy to handle as no conversion is needed, g723 on the other hand needs more CPU as needs to be decompressed or compressed depending on what you are doing
Title: Re: Call Handling Capacity- URS, SIP, T-server
Post by: hsujdik on February 18, 2016, 03:34:15 PM
As far as I am aware about, this should not really impact SIP Server, T-Server or URS, but its a valid information for future reference about Stream Manager and Media Control Platform / Media Server capacity.