Hello guys , I am trying to update my CISCO VoIP phone CP-7961G with new firmware and want after that to use it in my home network. For this I need DHCP server to give the phone TFTP IP address . I tried to make config but it seems it does not work.
ps - i was not successful in using routeros tftp or centos atftp, i had to use windows tftpd32 version 3.23 on the local subnet to make it work. not sure why, files would time out using routeros and atftpd, probably some EOF block that it didnt like or something.
and configure TFTP server properly to hand you requested files. Check compatibility of the TFTP client you are going to use as different clients support different features that vary from RFC.
If I define it on linux isc dhcp server it works without problem. On the Mikrotik it seems there is compatibility issue.
The client is a Cisco phone.
Any suggestion will be appreciated.
We are migrating couple of branches from cisco to MT and need to push two values via option 150 (primary and secondary tftp servers to phone configurations).
Only first option is written into phones configuration. “secondarytftp” is just ignored.
I’m feeling that MT requires that both values have to be defined under ONE “dhcp-server option name=x”, but MT rejects this kind of input. Tried comma;semicolumn,space as delimiters.
question:
how to feed several values within one dhcp option (150 / tftp).
ps:
config from cisco which i’m trying to replicate on MT ip dhcp pool VOIP
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
option 150 ip 10.10.10.10 10.10.10.11
Also the option is defined for all dhcp server on all interfaces. Is there a way to define an option for one interface/dhcp server only.
I need option 150 with different value on different interfaces…
can you try to set this up custom 150 option as you already did but in a way that is described in RFC as when you define custom options they are used as you wrote them.
Code Len IPv4 Configuration Server Address(es)
±----±----±----±----±----±----+
| 150 | n | IPv4 address | …
±----±----±----±----±----±----+
Figure 1
The option minimum length (n) is 4.
The “Len” field must specify a length that is an integral multiple of
4 octets (4, 8, 12, etc.). If an option is received where this is
not the case, the option information MUST be ignored, but further
option processing may continue. Dividing this “Len” value by 4 will
give the number of IPv4 VoIP configuration server addresses that are
specified in the option
so the result should look something like this:
/ip dhcp-server option
add code=150 name=customtftp value=0x0a0a0a0a0a0a0a0b
“Next Server” worked for me. I tried all sorts of other settings with option 66 and option 150, adding them to an option sets, putting a 0x04 in front of the IP address in hex, configuring the individual options in the DHCP server and network, configuring the option sets there too. The only thing that worked was Next Server
I am using phones 7941 and 7940 and using Tftpd64 on a windows box. I simply set Next Server to the IP of my windows box and everything suddenly started working. Before that the tftp server didn’t get any connections.
Decided to step in because i was battling exactly with the same problem, although this is a rather old thread.
After spending a fair amount of time i took a closer look at the webfig interface and it was all in the rationale.
From the examples above you are simply defining existing options but you are not applying them.
After defining a certain number of options, 66(tftp server), 42(ntp server), 15(dns suffix), etc, you need to group them in the Option Sets. Create a new option set and then go in the specific DHCP server configuration (i’m just using defconf from the list) and set the appropriate Option Set.
It all started to magically working.
