06-12-2013 11:04 AM - edited 03-16-2019 05:50 PM
Problem:
move existing ip phones off 10.0.0.x subnet and onto new subnet 192.168.20.x
testing the new configuration shows that dhcp is not being pulled by the phones off vlan20 but the default vlan 1 (192.168.0.x subnet)
The result is the phones are not pulling tftp configuration from 192.168.0.30 link
Current configuration:
Trixbox 2.6 asterisx base VoIP PBX running CentOS 2.6 w/no firewall runninng.
ip voip system: 192.168.0.30 NIC0 10.0.0.1 NIC1
192.168.0.30 is mgmt connection
10.0.0.1 is voip connection and dhcp is provided through NIC1 in the dhcpd.conf listed here.
# ddns-update-style ad-hoc;
ddns-update-style none;
ignore client-updates;
subnet 10.0.0.0 netmask 255.255.255.0 {
# --- default gateway
# option routers 10.0.0.1;
# option subnet-mask 255.255.255.0;
# option nis-domain "domain.org";
# option domain-name "dhcptrixbox";
# option domain-name-servers 208.67.222.222;
option tftp-server-name "10.0.0.1";
option time-offset -28000; # Pacific Daylight Time
# option ntp-servers 164.67.62.194; # UCLA clock
# option netbios-name-servers 192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
# option netbios-node-type 2;
range dynamic-bootp 10.0.0.100 10.0.0.200;
default-lease-time 21600;
max-lease-time 43200;
# # we want the nameserver to appear at a fixed address
# host ns {
# next-server marvin.redhat.com;
# hardware ethernet 12:34:56:78:AB:CD;
# fixed-address 207.175.42.254;
# }
}
30 Linksys SPA942 and SPA962 phones on 10.0.0.x subnet
New Configuration:
DHCP provided by core 2901 router at 192.168.0.1 VLAN 1
VLAN 20 setup for IP phones with scope of 192.168.20.100 thru 192.168.20.254
test phones are connected on Cisco 300SG-28PoE switch at 192.168.0.27
router info
Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.2(4)M2, RELEASE SOFTWARE (fc2)
ip dhcp pool VOIP
network 192.168.20.0 255.255.255.0
default-router 192.168.20.1
dns-server 208.67.222.222 208.67.220.220
option 150 ip 192.168.0.30
interface Vlan20
description VOIP
ip address 192.168.20.1 255.255.255.0
Solutions tested:
I turned off DHCP and stop it loading on reboot on the VoIP server
Disconnect and shutdown the NIC1 interface
plug in phone to switch.
Suggestions?
Do I need to define something on the Phone interface to look for 192.168.0.30?
How do I get the phones to pull DHCP from vlan 20?
Do I need to do port configurations on the switch to do vlan tagging to vlan 20?
Any help would be appreciated.
Thanks --- Steve
Solved! Go to Solution.
06-12-2013 11:42 AM
Steve,
On the Switch where the VoIP phones are connected, need to be assigned to "switchport voice vlan 20". Make sure you have a Trunk connection between the router and the switch, if the switch is not performing routing.
HTH
Regards,
Yosh
06-12-2013 11:42 AM
Steve,
On the Switch where the VoIP phones are connected, need to be assigned to "switchport voice vlan 20". Make sure you have a Trunk connection between the router and the switch, if the switch is not performing routing.
HTH
Regards,
Yosh
06-12-2013 12:46 PM
Yosh,
thanks for the response.
I set port 24 to vlan20 on one of the test phones and it is now pulling the correct DHCP addressing.
However, the same problem remains - not pulling the phone config via TFTP from 192.168.0.30
I am wondering if I will need to move the VoIP server onto the same VLAN 20 subnet or create an ACL to allow only that address access to VLAN 20. Suggestions?
Is there a special setting, if you know, for DHCP option 150 that specifies the correct directory to look in for the config files.
All I could find online in cisco docs was simple setting "option 150 192.168.0.30"
Nothing that allowed "option 150 /192.168.0.30/tftpboot" for instance.
Thanks,
Steve
06-12-2013 12:55 PM
Do you have ACLs or any security configured, that would block access from VLAN 20 to the 192.168.0 VLAN? If so, you will need to allow TFTP traffic through the ACL. If you don't have any ACLs blocking, then verify that you can ping 192.168.0.30 sourced from VLAN20.
Also as a side note, if you're wanting to use a hostname for the TFTP server instead of the IP address, you can configure option 66 followed by the hostname of the TFTP serve, under the DHCP Pool.
HTH
Regards,
Yosh
06-14-2013 10:45 AM
Yosh...thanks for the suggestions
ping ok from 192.168.0.x subnet to 192.168.20.x both directions
I did not see any ACL limitations in the router config, but could have missed it.
I added a 2nd ip address to the DHCP option 150 - 192.168.0.8 and put the config files in the same named directory.
On the test phone setup in the field "Profile Rule" I entered /tftpboot/spa$PSN.cfg to the
In the SPA942.cfg I put the new ip address 192.168.0.8 as the tftp source.
No go on auto provisioning. All I am still getting is on the basic DHCP addressing
Going to put the test unit on the 192.168.20.x subnet and then test again.
Probably some small config issue I am missing.
Thanks
Steve
06-24-2013 01:03 PM
Test results so far.
changed DHCP option to read - option 66 ip 192.168.20.230
Connected test freepbx server on eth1 and set ip to 192.168.20.230
set /etc/ixnetd.d/tftp file
server_args = -s /tftpboot -vvv
in the /tftpboot directory I copied these 2 files
spa942.cfg (product series number) is the /spa$PSN.cfg
spa000e08d34a49.cfg (mac address) is the /spa$MA.cfg
phone has Profile Rule:
/spa$PSN.cfg at factory reset status
/spa$MA.cfg after DHCP
phone gets 192.168.20.102 dhcp address and pulls spa$PSN.cfg but does not pull the spa$MA.cfg after the Profile Rule is modified by the spa$PSN.cfg file...
Suggestions?
06-24-2013 01:47 PM
Does the phone actually request the file? TFTP server logs or a packet capture should confirm this.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide