2002 - cesnet
2002 - cesnet 2002 - cesnet
Figure 14.1: Call distribution information displayThe basic ICM components are CallRouter, Logger, Peripheral Gateway, and CTIServer. If ICM is running only on one server, it works in sprawler mode.14.4 Cisco Agent DesktopCisco Agent Desktop (CAD) provides tools for agents (operators) and supervisors(administrators). An example can be the screen pop (possibility for anadministrator to communicate with operators), software IP phone, and supervisorsoftware.The Desktop supervisor software features a detailed display of information onagent statuses and call statuses, the possibility to send messages to agents, callsrecording, and extended monitoring functions.14.5 Progress of WorkThe entire system is very demanding in terms of configuration, which wasproved many times during the installation. In the first half of 2002, we implementeda basic distributed workplace of the VoIP-based contact centre (IPCC).After the difficult installation of all components of the distributed contact cen-166 High-speed National Research Network and its New Applications 2002
tre, when we were forced to handle the installation of some components incollaboration with experts from Cisco Systems, we managed to implement thecontact centre in its minimal functional form. Our further step was to test theactual IPCC function in a testing environment.The automatic call distribution system works in the following way – operatorsregister their phones into the IPCC system through a workstation and incomingconnections are then forwarded to them using a round-robin method. If all operatorsare processing a phone call, i.e., no operator is free, music is played forthe caller until one of the operators becomes available. Operators can forwardcalls to one another – if one of the operators cannot handle a client’s request,he/she can forward the call to his/her colleague. The configuration of scripts,such as “what shall I do with an incoming call/call in progress”, is not difficult.The scripts can be modified in quite a simple way using a graphic editor andthen are sent directly to the ICM server.Within the tests, we tested a simulated failure of each component of the contactcentre. In the case of the CallManager operation failure, phones were automaticallyreregistered to the CCM2 backup server. While performing the tests, wedid not encounter any connection breakdowns, i.e., none of the active callswere disrupted. Concerning the IVR or ICM server failure, we did not detect anyconnection breakdown, either. In this case, however, we noticed a temporarilyprolonged response (up to 5 seconds) when establishing a new connection.The delay was probably caused by the time necessary for the transition fromthe primary server to the backup one. In this way, we tested redundancy of thewhole solution and obtained satisfactory results.We prepared our testing workplaces at ČVUT, where we could not integratethem to the operating VoIP network, however, as we did not have the dialingprefixes assigned that are needed for making the service available to the outsideworld.After all tests were completed, we installed the operating configuration of thecontact centre. In the second half of 2002, we made both workplaces operational– one of them in Prague (CESNET) and the second one in Ostrava (TechnicalUniversity of Ostrava). In both localities, there are currently three of the abovedescribed basic components installed, i.e., the CCM server, IVR server, and ICMserver.After performing the installation at the defined localities, we tested the practicalfunctionality of the basic distributed IPCC solution again, including the resistanceof this solution to simulated breakdowns (failures of individual components).Call Manager, operating as a publisher, is located in Prague, ensuringdistribution/replication of databases in collaboration with the backup server atthe Ostrava workplace (subscriber).High-speed National Research Network and its New Applications 2002167
- Page 115 and 116: • Extensive possibilities for the
- Page 117 and 118: H.323 WorldSIP PhoneMS Messengerand
- Page 119 and 120: ation with students at the Strahov
- Page 121 and 122: 9 Quality of Service in HighspeedNe
- Page 123 and 124: In addition, Juniper routers make u
- Page 125 and 126: We tried to divide the capacity of
- Page 127 and 128: low with respect to the capacity of
- Page 129 and 130: Figure 9.10: Loss rate on Prague-Po
- Page 131 and 132: sendingapplicationTCP senderseqackp
- Page 133 and 134: Figure 9.13: Example of a course of
- Page 135 and 136: Part IIInternational Projects
- Page 137 and 138: 10 GÉANTSince 1996, CESNET has bee
- Page 139 and 140: Figure 10.2: Utilization of individ
- Page 141 and 142: 11 DataGridSince 2001, our research
- Page 143 and 144: Therefore, we organized a meeting w
- Page 145 and 146: 12 SCAMPISCAMPI (Scaleable Monitori
- Page 147 and 148: 12.3.1 WP0 - Requirement AnalysisTh
- Page 149 and 150: 1 6 12 18 24 30requirements analysi
- Page 151 and 152: Part IIIOther Projects
- Page 153 and 154: 13 Online Education Infrastructurea
- Page 155 and 156: 13.1.2 Construction of a Teleinform
- Page 157 and 158: with high-capacity disk memories co
- Page 159 and 160: If the collaboration of individual
- Page 161 and 162: ten, whereas items in the hyperlink
- Page 163 and 164: Besides that, we processed some lec
- Page 165: CallManager was designed using open
- Page 169 and 170: 15 Intelligent NetFlow AnalyserThe
- Page 171 and 172: In the second half-year, we complet
- Page 173 and 174: 15.4 ConclusionDuring 2002, our tea
- Page 175 and 176: • data space consolidation (easy
- Page 177 and 178: ecord size [kB] 256 512 1024 2048 4
- Page 179 and 180: Figure 16.3: Nishan-Linux measureme
- Page 181 and 182: 16.3.1 No SecurityThe initiator is
- Page 183 and 184: vices. These features mainly involv
- Page 185 and 186: Figure 17.1: www.cesnet.cz• We ha
- Page 187 and 188: The meeting was broadcast live via
- Page 189 and 190: Most of the problems connected with
- Page 191 and 192: Standard manipulator (privileged us
- Page 193 and 194: 19 Security of Local CESNET2Network
- Page 195 and 196: Moreover, the program was complemen
- Page 197 and 198: in the network of AV ČR Praha-Krč
- Page 199 and 200: 19.5 Future Plans, Expected Further
- Page 201 and 202: InternetNTPEthernetKPCPPSLabelPPSLa
- Page 203 and 204: generated by the NTP server. Its ou
- Page 205 and 206: 21 Platforms for Streaming andVideo
- Page 207 and 208: streaming serverAAA (LDAPS) server1
- Page 209 and 210: 21.5 Video Content CollaborationPla
- Page 211 and 212: First of all, we had to define an a
- Page 213 and 214: international-scale broadcast will
- Page 215 and 216: Part IVConclusion and Annexes
tre, when we were forced to handle the installation of some components incollaboration with experts from Cisco Systems, we managed to implement thecontact centre in its minimal functional form. Our further step was to test theactual IPCC function in a testing environment.The automatic call distribution system works in the following way – operatorsregister their phones into the IPCC system through a workstation and incomingconnections are then forwarded to them using a round-robin method. If all operatorsare processing a phone call, i.e., no operator is free, music is played forthe caller until one of the operators becomes available. Operators can forwardcalls to one another – if one of the operators cannot handle a client’s request,he/she can forward the call to his/her colleague. The configuration of scripts,such as “what shall I do with an incoming call/call in progress”, is not difficult.The scripts can be modified in quite a simple way using a graphic editor andthen are sent directly to the ICM server.Within the tests, we tested a simulated failure of each component of the contactcentre. In the case of the CallManager operation failure, phones were automaticallyreregistered to the CCM2 backup server. While performing the tests, wedid not encounter any connection breakdowns, i.e., none of the active callswere disrupted. Concerning the IVR or ICM server failure, we did not detect anyconnection breakdown, either. In this case, however, we noticed a temporarilyprolonged response (up to 5 seconds) when establishing a new connection.The delay was probably caused by the time necessary for the transition fromthe primary server to the backup one. In this way, we tested redundancy of thewhole solution and obtained satisfactory results.We prepared our testing workplaces at ČVUT, where we could not integratethem to the operating VoIP network, however, as we did not have the dialingprefixes assigned that are needed for making the service available to the outsideworld.After all tests were completed, we installed the operating configuration of thecontact centre. In the second half of <strong>2002</strong>, we made both workplaces operational– one of them in Prague (CESNET) and the second one in Ostrava (TechnicalUniversity of Ostrava). In both localities, there are currently three of the abovedescribed basic components installed, i.e., the CCM server, IVR server, and ICMserver.After performing the installation at the defined localities, we tested the practicalfunctionality of the basic distributed IPCC solution again, including the resistanceof this solution to simulated breakdowns (failures of individual components).Call Manager, operating as a publisher, is located in Prague, ensuringdistribution/replication of databases in collaboration with the backup server atthe Ostrava workplace (subscriber).High-speed National Research Network and its New Applications <strong>2002</strong>167