Nkuh Rholy

SIMULATION OF THE ToIP ON GNS3 SUPERVISOR: PROFESSOR TONYE EMMANUEL DUCKY MOMO ENSP | YAOUNDE INTRODUCTION Now-a-days, communication is achieved by many ways. The most accustomed way is the phone call, which uses a circuit switch. The main idea being, when someone calls a particular circuit is allocated for him till he finishes his call. That is one of the ways. With the rapid evolution of telecoms, a new was introduced. Which is phone calling someone across the internet or a network granting access to internet. This method does not use circuit switching but packet switching. This manner of transmitting voice in packets is known as Voice over Internet (VoIP), and cell phones capable of assimilating that technology are known as IpPhones (ToIP). The practical below is aimed at a crude but concise simulation of the ToIP using the simulator GNS3. AIM: SIMULATION OF ToIP ON GNS3 REQUIREMENTS: Personal computer with GNS3 and Virtual box installed within and a virtual machine created within. PROCEDURE: The topology used was as such; As shown on the topology, the we used; A router; In which was installed the CME (Call Management Entity), that permits the router to implement ToIP protocols A switch; That puts the IpPhones in a comment subnetwork IpPhones; Which in our case were Cisco IpPhones. The cisco IpPhones used were simply nodes. i.e either a virtual machine host, a cloud node… The first thing done was to give our router the recommended capabilities to be able to transmit voice through it. So here our router played two principal roles; *Host the CME *DHCP server that will allocate addresses to our nodes. In order to that, we needed a single IpPhone and the router R1 in question, as shown below Now, we had to configure our router. As a server it needed a little disk memory, for storing the addresses of the IpPhones for a while. To do so, we added 128MB to the PCMCIA disk of our router as shown below After doing so, we proceeded to configure our router. -We first of all give our router interface an address -Then we created the dhcp server The commands above permitted the phones not have the Ip address of the router ( Ip dhcp excluded-address ), create a packet of addresses or a pool of addresses for the phones (Ip dhcp pool) and also make our router be the communicating gate way between the phones (default-router). Option 150, indicates the position of the sever to the phones. In our case it indicates our router. We then launched our virtual machine and the network access to our virtual machine was done by a bridge access. This was done so because, using a NAT, excluded the ip address of the network card of our virtual machine from the dhcp pool. This was verified as shown in the image below. The image shows that by bridge access, the address we get for our virtual machine is found in the same pool as created by our dhcp server. After that, the most crucial part was to install the tools necessary for our virtual machine to act as an Ip phone. We therefore had to transfer some tools from our main PC towards our virtual PC. This was done as follows;  We created a home group, where both the main PC and virtual PC were visible  From our main PC, we opened the image of our virtual PC, created a new folder, copied the necessary ip tools and pasted it there.  We closed the home group, opened the Virtual machine, went to the folder created opened it and decided to install them. Those tools were to help us completely transform our router in to a server. Now, that it was done we needed to install the CME in to the router. This was done from the virtual machine. Firstly, we accessed the folder where the necessary tools were found. In our case we named VoIP tools. We installed the tftpd server on the router from our virtual machine. This gave us the image shown below; We then entered the ip address of our network card and indicated in which folder the CME was found. We went back to our router and launched the file extraction command. This command was as such; archive tar /xtract tftp:// address of the card/name_folder flash:archive tar /xtract tftp://-/cme-full8.0.0.1.tar flash This command caused an upload of the archives found in the CME folder on to the router as shown in the image below And the command line interface showed the image below: Extraction of the archives takes a while, but upon completion we got the message shown in the image below All what was left was to install the Cisco Ip communicator still in the virtual machine. We therefore went back to the VoIP tool folder and launched the setup. It installed rapidly showing us the icon below; We also installed it on the main PC. Because we are trying to call the virtual machine from the Host machine though the internet. When It was installed, Cisco ip communicator was launched in both machines. As shown below: The image above shows the ip phone interface when launched in the virtual machine, and the one below when launched in the host machine. Now that the router was well configured, we proceeded to add commands that will assign phone numbers to the Ip phones. We then took 2 phones among the ten and assigned them numbers. One of the phone was the host machine and the other the virtual machine. *We first all accessed the telephone services commands present in the router as shown below *After that, we defined the maximum number of phones in our network, which was 10. *We defined numbers to our phones. The numbers 1001 and 4001 When the phone numbers were configured, the aspects of the ip phones changed, telling us that they were fully operational and just waiting to make phone calls. Their appearance for ip phone 2 on the host machinewas as such: And that of ip phone 1 on the virtual machine was as such: We then called phone 1 (Virtual machine) from phone 2 (host machine. OBSERVATION: When the call was launched from phone 2 installed in the host machine, as shown below; It was observed that, phone 1 received the call; When phone 1 picked the call, the phone counter was immediately launched And at the end of the call, the call appeared in the phone call register. CONCLUSION AND REMARKS The practical on his own required the following notions;  How to configure DHCP servers  How to install the CME on the router and manage ip addresses in order to create an effective dhcp pool.  Network access methods and the use of tftpd servers. What rendered the practical difficult was not a full grasp of network interfaces configurations, knowledge lacking and shallow comprehension on the VoIP technology. As a conclusion, the two phones were capable of communicating with each other and hence the practical was successful.