Why does the Bridge connect to Genesys T-server rather than using Statserver SDK GIS?
GIS must send data to a third party application. The data sent is already compiled into a “chunk” format (Genesys has pre-compiled interval data). The data is not provided as call-by-call information and therefore makes it difficult to use the information for any other purpose. The following diagram is taken from the Genesys GIS documentation on page 14. The box labeled “Client Application” would be the third party app required to get the data into the correct text format and sending the information to IEX. As the diagram indicates, there are a number of components which can fail and create a potential risk. This diagram does not show the Tserver or the configserver database required to support this solution. The Bridge only uses the Genesys Tserver and connects directly to the configuration server database for CME information and auto-updates for adds/deletes and changes to the CME database. This architecture significantly reduces the risks associated with the interface. Because the B
