Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Router for Central Site and Branch Office

We are planning to deploy unified communication in our network... there will be central site in data center and more than 50 remote branch office

For branches with 20 users who will concurrently use VOIP/Video and web collaboration along with internet browsing what will be a good router to propose.

Also at central data center site which will server all the branch users -- 4000 users in total what router model will be best suited.

Pls suggest.

  • WAN Routing and Switching
New Member

Re: Router for Central Site and Branch Office

For branch offices, it depends on what type of bandwidth is required.

If your planning on running a single t1 or 2xT1(bonded) then you can run a 2800 series ISR.

2800 series routers can run fractional T3 but be careful. If you plan on running a T3, its best to do it on a 3800 ISR.

If your getting an "ethernet handoff" then you can use a L3 switch like 3560/3750.

Central Site should be either a 7600 or 6500 depending on what type of connection will terminate. Dont go with anything lower than a sup720. Research what you need as the sup720 come with 256k or 1 million route support.

Think about implementing the 3-tiered Cisco model (Core/dist/access).

Best way would be to call up Cisco and get rep to come out and survey your environment.

Super Bronze

Re: Router for Central Site and Branch Office

Like Ralph, I too would recommend 2800 series to support various T1 speeds (higher model numbers if more T1s) and 3800 series to support T3.

For the HQ WAN edge, besides the 6500/7600 series, depending on the overall bandwidth and number of ports needed there's also the 7200 and 7300 series, and the new ASR 1000 series to consider too.

This widget could not be displayed.