UC560 for Voice Only

[tekworksinc]

I have a customer that is getting a UC560 which will be used for voice only. The idea is to connect it to a 4500 switch on the voice vlan. So I am wondering what is the best way to do this? Would this be as easy as giving the WAN interface an IP address from the voice vlan on the 4500 and assigning a default route pointing to the vlan interface on the 4500 (.1). For the voicemail and AA to work just add some static routes on the 4500 saying to get to the 10.1.10.1 got to the IP Address of the UC560 WAN interface?

Thanks for anyhelp,

[johschaf]

Hello,

Usually is this situation you still put a data vlan IP on the UC, so that it can be managed from the data network. You will leave the WAN disconnected since your current router will provide the internet. You then can add a static default route on UC so that it can access the internet, and static routes on your current default gateway to permit access to the voice network and voicemail network. Then all you need to do is trunk the vlans from the UC to your 4500 series switch. If you don't want the UC to be on the data network, then just trunk the voice vlan to the 4500, and add the routes on your current default gateway

Thanks,

-john

[tekworksinc]

Thanks for replying John,

So if I got this right, say that the voice vlan is 10 with an IP address of 10.3.10.1/24 and the data vlan is 20  10.4.10.1/24 then I would create vlan 10 and 20 on the UC giving them an IP from the voice and data vlans. Configure a default route on the UC pointing to either 10.3.10.1 or 10.4.10.1 if using both data and voice?

On the 4500 I would create static routes to point to the voicemail and AA

ip route 10.1.10.0 255.255.255.0 10.3.10.X   X being the IP address that is assigned on the uc500 data or voice vlan?

I appreciate your help

[johschaf]

Hello,

Correct, create the vlans and give them IPs on the associated subnets. You would probably configure the route to go to the data vlan interface of the UC, since the 4500 also needs an IP on that interface in order to utilize the route.

Here would be the routes you would need. Please be aware 10.1.10.0 is a /30 subnet.

ip route 10.1.10.0 255.255.255.252 10.3.10.X

ip route 10.4.10.0 255.255.255.0 10.3.10.X

Thanks,

-john

[tekworksinc]

Hopefull this will be my last question John, I do appreciate the help

On the 4500

vlan 10

voice

ip add 10.3.10.1 /24

vlan 20

data

ip add 10.4.10.1/24

ip route 10.1.10.0 255.255.255.252 10.4.10.5

ip route 10.3.10.0 255.255.255.0 10.4.10.5

create trunk port for the uc to connect to

On UC

vlan 10

voice

ip add 10.3.10.5/24

vlan 20

data

ip 10.4.10.5/24

ip route 0 0 10.4.10.1

create trunk port for the 4500 to connect to

It should be ok to remove any nat and firewall statements on the uc that might be there by default right?

if the dhcp pool for the phones is on the 4500 then point the option 150 to 10.3.10.5

[johschaf · Accepted solution]

Hello,

Does the 4500 have a data vlan IP on it already? You don't really need multiple IPs on the switch unless it is acting as the gateway for the vlans. Even in that case, the UC needs to be the default gateway for the phones.

The routes look good.

The vlan configuration looks good on the UC.

Configure the trunk ports on the UC and the 4500

You can delete all NAT configurations from the UC. You can remove most of the firewall and ACL settings, there are a few ACLs that should remain, primarily on the voicemail system.

I would recommend leaving the DHCP for the phones on the UC, but if you want to move it off, set option 150 and the default gateway to 10.3.10.5.

Thanks,

-john

[tekworksinc]

Yes the 4500 is the gateway for all the networks at the site. The site has a cox Edgewater SIP device that will also be on the 4500 tagged to the voice vlan. The UC will have a SIP Trunk configured and calls will be sent to the Edgewater.