arrow_back Topology and Network configuration for CIsco VoiP ( CME router + L3 switch)?

1 vote
Good afternoon!
I am a student and I am doing a project related to IP telephony based on Cisco solutions.
I enclose a logical topology of a small business. The essence of the problem is that the CCNA Voice textbooks offer a "router on the stick" configuration for routing data and voice traffic via VLan (Data and Voice) technology. It turns out that the router is a universal fighter and does everything at the edge of the network, as well as telephony and VLan routing. I would like to use L3 switch for Inter Vlan Routinga, but I can not find such a configuration, that switch would route Vlans and Voice Vlan would reach router that processes internal calls. Is it possible and have I messed up, maybe the router is a stick, but is it practical?

1 Answer

0 votes
Perhaps what exactly is your problem?


Good afternoon, actually the problem arose in the implementation of an idea that would allow routing data traffic between VLan through the switch, with Voice Vlan to send to the router and back in the case of internal calls. In the CCNA voice manuals and various sources I have not found such examples. In general these are examples where routing Vlan is done by router, on the other hand there are many videos with examples of routing Vlan L3 switch, but it is not clear how it interacts with the router. On the third side, why put the server in a separate Vlan, if the departments of, for example, a small company will apply to it and it all will go through the router, it turns out that the channel between router and switch will be loaded with routed traffic "departments - server". So the idea was that the Vlan would route the switch, but the Voice Vlan would reach the router, but the workstations would also have access to the Internet.
Thank you.
Iarik , Start simple:
1. Transfer all interfaces from the router to the switch. interface vlan 100,101,102 and so on.
2. Between the switch and the router you need an additional LAN for routing (dynamic or static routing).
3.Choose a DHCP server: a separate server, router, or switch. If the organization is small, it is easier to raise the server on the same switch, in the future it makes maintenance easier.
The server interface is also better moved to the switch, so that unnecessary traffic does not go to the router. A separate host makes things easier, but two things come to mind so far: security and migration (if needed in the future). All these things are easier when the servers are in a separate domain.
I think, since I do not have enough brains to implement it at the moment, place the file server in Vlan 106 - department of designers, who will most need access to it, this will save from the load of connections router-switch from routing this traffic.