At Percona’s web store you can order full Percona Database Performance Audit in minutes. Find out the health of your database, and how to improve it. Pay online with a credit card. Improve your database performance now!
COURSE of the MONTH
10 days, 22 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
transitioning voice and data service
Posted on 2012-12-30
We are about to upgrade our voice and data system.
They just brought an OptEman and we will have fiber services available to us. The question I have is that what changes will need my attention for our network.
I have the DHCP server on our LAN and DNS server on our LAN. We have port forwarding setup on the firewall which belongs to our service provider. The only thing that I see that I need to worry during this transition is the port forwarding.
Are there any other things you experts can think of that I should be asking?
We currently have a T1 line which will be upgraded. We also currently have VoIP
We also have two separate domains, that we are thinking about consolidating, which we will do at this time. Our email server operates on a separate domain than from our current network domain.
They just brought an OptEman and we will have fiber services available to us. The question I have is that what changes will need my attention for our network.
I have the DHCP server on our LAN and DNS server on our LAN. We have port forwarding setup on the firewall which belongs to our service provider. The only thing that I see that I need to worry during this transition is the port forwarding.
Are there any other things you experts can think of that I should be asking?
We currently have a T1 line which will be upgraded. We also currently have VoIP
We also have two separate domains, that we are thinking about consolidating, which we will do at this time. Our email server operates on a separate domain than from our current network domain.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
- +1
5 Comments
Heres one (hard earned) suggestion:
Before switching your systems over to the new service, I would strongly suggest that you test the new connection to confirm the ISP is not blocking any of the inbound ports you need. They will deny they block any ports, but dont belive them: test it anyway, in both directions.
Before switching your systems over to the new service, I would strongly suggest that you test the new connection to confirm the ISP is not blocking any of the inbound ports you need. They will deny they block any ports, but dont belive them: test it anyway, in both directions.
Is the external address space you are using changing? Unless you have a direct address allocation, this will likely come from your ISP. If your address space is changing and you are offering any external services you will need to make sure your DNS gets updated in a timely fashion. Services would include Email (MX records if you host your own email), Web (CNAME or A records if you host your own web servers). If you're doing a hot cut from your old service provider, you'll need to coordinate DNS changes so that you are not "off the air" for an extended period of time. When preparing for a transition that includes IP address changes, you will want to lower the time to live (TTL) values for your critical DNS records to some small value (30 minutes or so) prior to your change. 48 hours is the common default TTL for most records, so you'll need to do your changes several days prior to the cut-over.
Do you host your own externally facing DNS? If so, it would be on that/those systems. If your external DNS is hosted (like Network Solutions, GoDaddy, DynDNS, etc), it would be through their tools. There are default TTLs for the DNS server as well as per record TTLs. Some solutions also allow per zone defaults. It will just depend on what is seving your external DNS as to how easy it will be to modify.
I'll second the DNS checks on any kind of public facing. if you're runningg your own servers, that's doubly importing for things like MX records and making sure the new public IP block you're assigned isn't on mailing blacklists.
Also if you're running VoIP, check with your ISP and VoIP provider for any kind of QOS that might need to be setup on the new WAN link. Additionally for VoIP, if you're setup like a hosted VoIP environment confirm whether or not you need to worry about far-end NAT traversal or you may run into situations where inbound calls from the PSTN to your phones fail while outbound calls are fine. If you're setup with something like a SIP Trunk going to an IP PBX check to see if your VoIP provider has that SIP Trunk setup by static IP address, in which case you'll want to let them know the new public IP to use to setup that SIP Trunk.
If the ISP is replacing the WAN router you shouldn't have to verify physical interfaces (T1, Ethernet) but you may also want to make sure whatever you have connected to that WAN router (firewalls, proxies, etc.) have necessary interfaces and / or config options to run in parallel while you test out the new connection. And if they don't then you'll want to setup a plan to be able to swing services back quickly to minimize service interruptions if there are any isues with the new ISP connection.
Also if you're running VoIP, check with your ISP and VoIP provider for any kind of QOS that might need to be setup on the new WAN link. Additionally for VoIP, if you're setup like a hosted VoIP environment confirm whether or not you need to worry about far-end NAT traversal or you may run into situations where inbound calls from the PSTN to your phones fail while outbound calls are fine. If you're setup with something like a SIP Trunk going to an IP PBX check to see if your VoIP provider has that SIP Trunk setup by static IP address, in which case you'll want to let them know the new public IP to use to setup that SIP Trunk.
If the ISP is replacing the WAN router you shouldn't have to verify physical interfaces (T1, Ethernet) but you may also want to make sure whatever you have connected to that WAN router (firewalls, proxies, etc.) have necessary interfaces and / or config options to run in parallel while you test out the new connection. And if they don't then you'll want to setup a plan to be able to swing services back quickly to minimize service interruptions if there are any isues with the new ISP connection.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
As companies replace their old PBX phone systems with Unified IP Communications, many are finding out that legacy applications such as fax do not work well with VoIP. Fortunately, Cloud Faxing provides a cost-effective alternative that works over an…
Not everyone has adapted to a rapid advancement in technology; there are people who are reluctant or afraid to delve into this brave new world of IT. If you have a friend or a family member who suffers from the so-called technophobia, here is how yo…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, just open a new email message.
In the To field, type your recipient's fax number @efaxsend.com.
You can even send a secure international fax — just include t…
Internet Business Fax to Email Made Easy -
With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number.
You'll receive secure faxes in your email, fr…
Suggested Courses
Course of the Month10 days, 22 hours left to enroll
770 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.