Jump to content

Cisco Voip Long Local


systemd0wn
 Share

Recommended Posts

I have several Cisco 7961 VoIP phones connecting to a Cisco Call Manager several hops away (Long Local). The telephones are on their own voice VLAN and DHCP gives out IPs, default gateway, and two TFTP servers.

When the phones first come online they get their settings from the DHCP server (router), reboot and start to download the latest firmware files. This takes aprox. two hours. It's a high latency sat network so it's to be expected somewhat. Is there anyway i can make a local TFTP server with those files so that i don't have to download them across this link? I'm not incredibly savvy with call manager or voip or what role the TFTP server plays in it all. Just looking for some ideas.

-systemd0wn

Link to comment
Share on other sites

The TFTP server is what holds the files they are trying to install and is what the phones will look for to grab their updated firmware.

Not sure how your phones work(never actually played with setting up VOIP and CallManager), but we used to fix our Cisco routers, where you put the router into ROMmon mode via serial interface(breaking out of the boot sequence), then configure one its ethernet ports to point to the desktop machine, then have a TFTP server on the desktop machine just listening for requests. Once you configure all the settings such as the file name to grab, the IP of the TFTP server, etc, you would save and reboot the router and it would automatically grab the firmware from the desktop machine. You could then configure everything else on the router and save your settings with the updated firmware, and remove ROMmon mode afterwards.

You should be able to set up your own TFTP server to do the same thing, but if they are getting this info via DHCP for the TFTP servers, then they will still look there for the file.

You would have to disconnect them from the network and set up a local GATEWAY/DHCP/TFTP server to do the same process. It would have to be on the same VLAN, do the DHCP process, and host the correct firmware as well as run a TFTP service of some manner. Once done, you could then plug it back into the network and it should be fine. This is all in theory, as I have never worked with setting up VOIP and don't know the exact steps to updating a VOIP phone.

Might be simple, but have you checked the Cisco site itself? They usually have a lot of documentation on setting things up.

Some links that may help:

http://www.cisco.com/en/US/products/hw/phones/ps379/tsd_products_support_install_and_upgrade.html

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_example09186a00805a2fa5.shtml

Edited by digip
Link to comment
Share on other sites

Thanks for the information. The IOS & TFTP discussion is a bit off topic but the bottom link did help. I'll post more of my findings but it looks like the best idea would be for me to setup my own Cisco TFTP server (free) and mirror their files. I can then give this TFTP server to the VoIP phones via DHCP and set it as the primary TFTP server. Thanks for your response.

systemd0wn

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...