1 / 15

Preparing your telcom network for the data world

Preparing your telcom network for the data world . Gina Eiden – Telecommunications Coordinator Jennifer Ruetten – Network Technician Winnebago County. Project Plan: Upgrade (4) G3si’s and (4) EPNS under one S8720 media server.

konane
Download Presentation

Preparing your telcom network for the data world

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Preparing your telcom network for the data world Gina Eiden – Telecommunications Coordinator Jennifer Ruetten – Network Technician Winnebago County

  2. Project Plan: Upgrade (4) G3si’s and (4) EPNS under one S8720 media server. • Connectivity: Use existing Single-mode & Multi-mode dedicated fiber. • Survivability: Determine what buildings need survivability if the Network connection is down to the main S8720 Server. Determine what locations will have S8500ESS. • Converge network: The County would run the voice network separate from the data network. • Data Switches –Purchase the same HP data switch that is deployed throughout the County or go with EXTREME an Avaya supported product and add this to our maintenance. • Maintenance Support – Do we need 24/7 , 8/5, or parts only.

  3. TELECOM NETWORK CONSIDERATIONS • QAR - Quality Assurance Report will provide you with the functional requirements to maintain the performance of Voice over IP (VOIP) or you may already have an in house network analysis done and will be using your data switches. Your vendor will request this. • Be aware of the distance between your connecting data switches and replace Gbics (gigabit interface converter) w/long haul Gbicswhere necessary. (testing done through your QAR should determine any issues you may have) • Redundancy – what is needed? Switches – Gateways -IPSI’s etc. • E911 Locator ID – Software to define exact location of the DID extensions on your switch. Especially important as you deploy IP stations.

  4. TELECOM NETWORK CONSIDERATIONS cont’d. • Be aware of any uniform dial plan conflicts. • Display dialplan analysis for each location. • As you merge your locations you will perform all admin changes through ASA on your main S8700 media server. • This your chance to clean up any dup coverage paths. If you do have duplicates when combining your locations the # of the network region will be placed in front of it. 25= 225 in network region 2. • To display all stations using a coverage path: Disp coverage sender-group XX • Your SAT terminal will no longer be used to make changes at site locations. Use a laptop loaded with ASA. Connect to your network to make any station changes.

  5. Share your resources. A music source residing in location 4 can be used in location 9.Display music source – to find the tenant with the source of music you want to use at another location.

  6. Change tenant 9 – insert a “4” to use the music source from tenant 4 in location 9

  7. New Terms to become familiar with. Nodes are now Network Regions. list ip-network-region

  8. Station Form will refer to the Network region the station resides in as tenants.

  9. When making changes to your ARS Analysis Table the network region is defined as location.Command: Change arsana XXX loc 4.

  10. Network Considerations • Have correct data person (not necessarily network admin) involved from the beginning • First question to answer – Will your voice network be integrated with your data network or will it be completely separate? • Switches – Do you stay with the make that you already own? • Monitoring Tools – Avaya provided or existing network tools

  11. Setting Standards • Media Server and Switch names • Do you want to follow the naming convention of your data network? • IP address assignment • EVERYTHING has an IP address • Assign a sequential range of numbers to each type of card (i.e., IPSIs all end in xx, CLANs all end in yy) • This gives you be benefit of always knowing that an IPSI will be within a range of numbers • It allows you to add cards and still keep within your designated range • Switch port connections • IPSI on switch port x • CLAN on switch port y • Same benefit as above, you know what card is connected to which port without having to look at a spreadsheet or map

  12. Servers to configure • FTP – Media Server & MM backups • DHCP – Have to setup scopes so that the phones know where to find the HTTP server • HTTP – Phone firmware updates and backups • Different model phones use different backup methods • TFTP – Extreme switch configurations • SNMP community strings • Offsite backup of above

  13. monitoring Tools and update software • Many of this software needs to be installed in a Windows Server environment, not your standard PC • Software Update Manager • Network Management Console • VOIP Monitoring Manager • Switch monitoring – EPICenter, Cisco, HP, etc • Third party software like What’s Up Gold may already be in use for data network monitoring

  14. Phone backup methods supported by each phone type

  15. Other Issues to address • Subscribe to Avaya email notifications for firmware updates, product correction notices , etc • Windows servers (such as MAS) • Anti-virus • Windows updates • On-call considerations • Do you involve your network team?

More Related