remote phone install

[southeasternMI]

Trying to get a ip 230 to installed over the WAN. Site in FL and MI, FL has the server and when we try adding a phone in MI off the FL system, the phone contacts the server, but can't load the customsev.txt file for the phone.
If the phone can contact the ftp server, then why won't it grab the config file?
Can I grab that file and upload to phone?

[Jason Learmouth]

Why won't it pull the file? Not sure, firewall? As a work around you could run an FTP server at the local site, the FTP server doesn't have to be a DVM as long as it has the files the phone needs.

Don't forget to copy across the FTP dir every time you upgrade.

[southeasternMI]

No idea why, they are looking at what could be blocking it, my guess a fire wall. So if I added an FTP server on site, won't the phone need to contact the main server for any applications? (answer my own question) So basically the phone only uses the main server for its config and after that it uses extensions and the switches to get around.

[Tenny321]

Do a manual setup on the phone. Maybe DHCP is giving it the wrong FTP? Make sure you firewall is forwarding port 21 to the ftp.

[Jason Learmouth]

Manual setup is a good idea, finding the root cause of FTP isues should be a priority.

One of the files on the FTP server (shore_XXX.txt) tells the phone where to go look for config switches to join the system. It doesn't matter where the phone gets this file from, once it joins the system it will need to talk to all the other devices on the system. I suspect your issue is related to FTP handling somewhere between sites.

[Tenny321]

Manual setup is a good idea, finding the root cause of FTP isues should be a priority.

One of the files on the FTP server (shore_XXX.txt) tells the phone where to go look for config switches to join the system. It doesn't matter where the phone gets this file from, once it joins the system it will need to talk to all the other devices on the system. I suspect your issue is related to FTP handling somewhere between sites.

I agree it sounds like FTP problem

You could even make a custom config file. Do shore_(mac address).txt ex "shoretel_0054a4112342.txt". Then copy the info from the correct shore_ file of you phone. The location of the txt files are in: C:\Inetpub\ftproot (DO NOT EDIT ANY FILES HERE!!!). This part might be a little extreme though, but just tossed it out there.

[eazeaz]

remote phone

I have had a bad network cable do that (strangely enough). It was good enough to provide power, boot the phone, pull an address, but it would fail during larger data transfers.

New end, no problem.

I did not believe it until I saw it either.

[southeasternMI]

No DHCP, its a manual setup. That makes me think its port 21 on the firewall.

[Jlorenz]

No DHCP, its a manual setup. That makes me think its port 21 on the firewall.

Yes, that maybe one point of failure

MTU mismatch as well (Default 1500)
Duplex Mismatch
Speed Mismatch

1: Ensure MTU is the same across all Subnets
2: Ensure all Duplex and Speed is the same
3: In IIS, make sure your set to anonymous FTP and that your directory is set to Read and Log

Many times the Admin will turn off Anonymous FTP access

To test FTP login you can try it two ways

From the Serve CMD prompt
ftp localhost


from the Remote PC (Where the Phone is) try
ftp (IP ADDRESS OF SERVER

Login in
remember no password
do a get on the file you want

[southeasternMI]

Thanks for the info.
Can I use the shore_serv.txt file from my system and put it on a local server at their site and then just modify the file with their system info, just so I can get the phone to come up. See any issues with that?

[Jlorenz]

Thanks for the info.
Can I use the shore_serv.txt file from my system and put it on a local server at their site and then just modify the file with their system info, just so I can get the phone to come up. See any issues with that?

Nope cannot do that, Everything aka SG's, IP Phones, PCM all must point to HG server FTP, if the phone is assigned to a site it will automatically proxy to that site. It first must read the info from HQ.

[southeasternMI]

So I would have to put the whole ftp directory on a server at the remote site in order for the phone to grab the config and point to the main server.
This is just a single phone at a remote site, no switches or DVM. If I put the ftp directory on a local server and the phones gets it's config locally as long as there is connectivity, it should work.

[Jlorenz]

So I would have to put the whole ftp directory on a server at the remote site in order for the phone to grab the config and point to the main server.
This is just a single phone at a remote site, no switches or DVM. If I put the ftp directory on a local server and the phones gets it's config locally as long as there is connectivity, it should work.

Nope, leave the ftp directories as they are. Simply point the Phones FTP to the HQ server, it will do the rest.

Also if you know the IP address will be constant on the phone, you can create a IP Map for that phone associated to that Site / DVM

Do this in IP Phones > IP Map (Be sure to check teleworker (Best Quality enables g729 automaticly)

this will tell the phone to grab the appropriate info from the approprate server "AFTER IT HAS CONTACTED HQ"

[Jason Learmouth]

I think the orriginal problem was that FTP wasn't working between sites. Why is the actual location of the FTP server important? I have seen installs where a local FTP server was setup, local DHCP 156 pointed to the local FTP server which has a copy of the same files as the HQ server. The phone finds out what HQ servers IP address is from one of the text files it downloads from the FTP server. The IP address of the FTP server doesn't have to be the HQ server.

The points

[Jlorenz]

I think the orriginal problem was that FTP wasn't working between sites. Why is the actual location of the FTP server important? I have seen installs where a local FTP server was setup, local DHCP 156 pointed to the local FTP server which has a copy of the same files as the HQ server. The phone finds out what HQ servers IP address is from one of the text files it downloads from the FTP server. The IP address of the FTP server doesn't have to be the HQ server.

The points

You can most certainly setup the FTP server through DHCP option 156, and bypass the initial problem with FTP

However, what about the SG's at that site, if FTP is not workign How will SG's get its firmware upgrade? they have to be pointed to the HQ.

In a scenareo that you want redundancy you can establish the FTP on the DVM. I am saying it is not best practice to do so, the Phone still has to traverse the the WAN to get its config from the HQ. There is no database on the DVM, it all resides with the HQ.

Initial FTP location is not the issue, maybe I misunderstood the main issue