Poi is becoming an important alternative to the daily used telephone system, not only in terms Of economic aspects but also in quality of service for both, professional and private use.
A successful IP Telephony deployment is assisted by an awareness Of where you are going-this comes from considering all of the elements required to deploy and maintain a converged, Voice-over-IP capable network. This project involves physically connections of Poi using hardware such as routers, switches, call manager, and IP phones.Also, the project presents the hardware configurations o establish the Poi network solution for an enterprise, These elements are discussed in this paper, along with guidelines for setting up a pilot project. Ill. Goals / Objectives The goal of my first project executable to provide the understanding of the configurations required to implement the fundamental elements a model application of Poi with a call manager in the business enterprise. Will design a business scale network with routers and switches that support Cisco Call manager equipment and IP phones, deploy the physical network and configure each device to operate.
I will have programmed the switch and router with the infuriation to provide connectivity to the call manager and IP addresses for the IP_phones. IV. Background / Introduction This a Vision diagram Of my proposed network. Poi (voice over IP) is an IP telephony term for a set of facilities used to manage the delivery of voice information over the Internet. Poi involves sending voice information in digital form in discrete packets rather than by using the traditional circuit-committed protocols of the public switched telephone network (EST.
).A major advantage of Poi and Internet telephony is that it avoids the tolls charged by ordinary telephone service. Sing Poi, an enterprise positions a “Poi device” at a gateway. The gateway receives picketed voice transmissions from users Within the company and then routes them to Other parts Of its intranet (local area or wide area nonvoter) or, using a T-carrier system or E- carrier interface, sends them over the public switched telephone network. The gateway of these “Poi devices” i. E. Switches and routers are actually ports.By default all port connected to a layer 2 switch operate within the same domain, which means that if device A attach to a port 1 off particular switch, send a frame that is a broadcast.
The frame will be copied to all other devices attached to another ports on that switch. This is layer 2 limitation, However with PLANS Spiritual Local Area Nortek) you are able to segment that same switch to operate like multiple layer 2 bridges, so thereby providing segmentation, flexibility and security. Understanding and configuring PLANS on switches is essential to creating a secure connection in an efficient Poi network.In my project created PLANS on a Catalyst 3550 multilayer switch, a PLAN is a switched network that is logically broken up by function, project team, or application, without regard o the physical locations of the users. Plans can have the same attributes as physical Lana, but you can group their end stations even if they are not physically located on the same LANA segment. Each PLAN is considered a logical network, and packets destined for stations that do not belong to the PLAN must be foundered through a router or bridge.
Because a PLAN is considered a separate logical network, it contains its own management information base (MOB) information and can support its own operation of spanning tree. Before you decide to set create your Plans you must decide Whether to use PLAN trucking rotator (PPTP to maintain configuration for your network. Plans also tend to be commonly associated With IP subroutines, major because Of their ability to manually assign the switch’s PLAN membership; also known as static AVIAN membership.These switches can route traffic between Plans by utilizing switch virtual interfaces, or Sip, which also must be configured and given a designated IP address to route the in between traffic of the Plans. This is essential because traffic between Plans have to be routed, PLAN Port membership modes play a major role in helping the PLAN to manage traffic. A port can be configured to belong to a VI-AN by assigning a membership mode that designates the appropriate kind of traffic the port carries, and also the number of Plans it can belong to, V. Methodology/Approach With the network chose to use the Catalyst 3550 switch as a PLAN.
In order to do so: I had to make sure that any prior PLANS were not created on the switch by using the “show PLAN” command, If there is a PLAN already created, you can remove the PLAN by entering the PLAN database mode and bye in the command “no PLAN and apply Once in enabled mode then begin to issue the PLAN database command. To start off configuring a PLAN, I issued the PLAN the name of ‘VI_AN 100” then repeated this process for five additional PLANS with different ID numbers, i. E. 200, 300… Etc. With the network design setup, I first had to set up an IP address on the same subnet for VILLAIN of each device.
PLAN I is for management purposes. In configuration mode I first used the command “INTO PA 0/1” to choose the selected port in order to create a trunk between the two devices. The trunk allows the PLANS access to the individual devices. In configuration mode I first used the command “INTO PA 0/5” to choose the elected port I would use to connect one of the IP_phone. Then used the command “switcher mode access” to allow that port access followed by no shut to exit the configuration. I also used the command “switcher access PLAN 100” to assign this individual PLAN ability to use this port as its vehicle of transmitting voice traffic. Hen repeated this process for five additional ports with different PLAN, i. E.
200, 300… Etc was able to establish connectivity between the multilayer switch 3550 and the router 261 ISM. The 7960 IP-Phones were able to extract an IP address from the HCI pool in the router 261 ISM, These paths for signal transmission are essential to enable communication between one end user and another. Did encounter some challenges relating to a faulty multilayer switch 3550. While configuring the switch, without warning, the switch crashed and immediately flushed all Unfortunately, I did not have a chance to save the configuration.Fortunately, there were other switches available for me to configure and all was well.
In this project, the Router 261 ISM contains two Easterner interfaces that can be used in order to connect to the core switch. However, want to be able o use only one interface in order to transmit the voice traffic, and have access to the Internet through the default gateway. A good method that permits this is called Interview?N communication, in Which the router has the capability to divide one of its interfaces into several substantiates in order to create different logical segments or Plans.With this feature, the router can receive packets on one AVIAN and forward them to another PLAN. After the IP addresses are configured on substantiates, the router is aware of the network associated with every PLAN as a directly connected network. VI. Outcomes / Results This is a screenings to illustrate the successful completion of the proposed networks router, switch and IP_phones connectivity, displaying the IP address of the IP_phone which was assigned by the DDCD server in the router, VII.
Discussion / Benefits In this case, the Router 261 ISM contains two Easterner interfaces that can be used in order to connect to the core switch. However, I wanted to be able to use only one interface in Order to transmit the data traffic, the voice traffic, and have access to the Internet through the default gateway. I chose to use a method hat permits this is called Interval communication, in Which the router has the capability to divide one of its interfaces into several substantiates in order to create different logical segments or PLANS.With this feature, the router can receive packets on one PLAN and forward them to another PLAN. After the IP addresses were configured on substantiates, the router is aware of the network associated with every AVIAN as a directly connected network.
On the Catalyst Switch 3550, I created different PLANS in order to separate the voice traffic of one IP_phone line from the other, In doing this I created six logical subnets that rate multiple broadcast domains and prevent the possibility of loops in the networks.