Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Phones not getting DHCP/reaching FTP from remote sites

    Hi all,
    I have a remote site that has a L2L VPN connection to my main site where all of the Shoretel gear is. From the remote site I can ping the VLAN where the Shoretel gear is and I can even open a command prompt and start a FTP session to the FTP server without a problem.

    However, when I look at the DHCP leases on my Cisco 2801 router at the remote site (sho ip dhcp bindings) I do not see the phone's MAC address. Furthermore when the phone boots up it says it cannot reach the FTP server. And the FTP server's log indicates that there was no connection made from the remote site.

    Everything at the main site is fine. The phone connects to the FTP server without a problem and I can see their leases in the DHCP the server (Windows 2003).

    I've swapped out cables and power injectors. I've looked and the switch does not have LLDP capability.

    Any ideas? Thanks!

  • #2
    Is DHCP option 156 setup on the remote router or set in the phones?

    Comment


    • #3
      yes
      copy and pasted from config:

      ip dhcp pool localDHCP
      network 192.168.11.0 255.255.255.0
      default-router 192.168.11.1
      dns-server 192.168.1.23 192.168.1.244
      netbios-name-server 192.168.1.23
      netbios-node-type h-node
      option 156 ascii "ftpservers=192.168.25.10"
      option 42 ip 192.168.1.23
      lease 4

      Comment


      • #4
        The option 156 should be configured like this:

        Option 156 (string / ascii value): ftpservers=(IP of Director), language=1, country=1, layer2tagging=(1 or 0), vlanid=(voice vlan ID)

        You really only need to worry about the ftpservers field, and the layer2tagging / vlanid if your network is configured with a vlan for the ShoreTel system.

        You should also have option 155 configured too, which is just the IP of the director. Adding an sntp server value on that dhcp server is a good idea as well.

        Comment


        • #5
          Hey everyone, I just wanted to give a followup to this.
          I did resolve the issue, it was indeed a DHCP configuration problem:
          Wrong: option 156 ascii "ftpservers=192.168.25.10"
          Correct: option 156 ascii ftpservers=192.168.25.10
          The quotes were the problem.

          Thanks for all of your help!

          Comment


          • #6
            Originally posted by DigiDT View Post
            Hey everyone, I just wanted to give a followup to this.
            I did resolve the issue, it was indeed a DHCP configuration problem:
            Wrong: option 156 ascii "ftpservers=192.168.25.10"
            Correct: option 156 ascii ftpservers=192.168.25.10
            The quotes were the problem.

            Thanks for all of your help!
            How were you able to get the quotes out? I enter them without the quote, but when I sh run the quotes are there.

            Comment

            Working...
            X