Snapper's Panasonic VoIP Provisioning Server

Forums › IT Pro and developers › Snapper's Panasonic VoIP Provisioning Server

Dynamic

2463 posts

Uber Geek
+1 received by user: 735

Trusted

Lifetime subscriber

Topic # 146871 31-May-2014 23:26

Hi Team,

Is anyone making use of Snapper's provisioning server for Panasonic VoIP handsets? I'm configuring one for the first time and testing with a manual web config went fine, but I'm having trouble using the local provisioning server. Keen to get it resolved this weekend as I want to leave the handset in a remote location but me able to tweak the config if necessary (the 'proper' way though I know there are other options).

After not being able to get the phone to download a config I have been trying to test the config download from Windows:

C:\>tftp x.x.x.x GET /xyz/ConfigCommon.cfg C:\Users\Dynamic\Downloads
Error on server : ????????
Connect request failed

In the example above the x.x.x.x is the IP as shown in the "Handset specific CFG file link" area on the provisioning server and xyz is the folder name shown in the same area. The second two lines are the results I get. I have also tried file name Config000000000000.cfg where the 0's are the device's MAC address as defined in the MAC ADDRESS area of the Basic Setup window for the individual handset on the provisioning server.

Am I doing something dumb or am I missing some vital information?

Thanks in advance
Mike

EDIT - Due to a premature mouse click

"4 wheels move the body. 2 wheels move the soul."

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

Dynamic

2463 posts

Uber Geek
+1 received by user: 735

Trusted

Lifetime subscriber

Reply # 1057311 31-May-2014 23:41

I don't like long tales, but this one has just grown from the original slightly blank post!

"4 wheels move the body. 2 wheels move the soul."

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

sbiddle

27264 posts

Uber Geek
+1 received by user: 6692

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 1057376 1-Jun-2014 08:01

I had no idea Snappernet were running a provisioning server, but typically speaking tftp isn't routable so isn't something you use to connect to a different network so assuming your test is to connect to a remote network it's giving is giving the correct result - ie not working.

Dynamic

2463 posts

Uber Geek
+1 received by user: 735

Trusted

Lifetime subscriber

Reply # 1057599 1-Jun-2014 16:25

Thanks for the comment, sbiddle.

While I've only ever used TFTP on local subnets in the past, I'm 99% confident that TFTP is routable. It is just based on UDP but that has the fill IP layer behind it so it is no more or less routable than TCP.

PXE network booting of a workstation is partly based on TFTP for getting the initial boot image to the workstation, and any corporate using it would not be limited to a single subnet.

Has anyone else used any Panasonic VoIP provisioning server - particularly with TFTP as the transmission method for CFG files?

"4 wheels move the body. 2 wheels move the soul."

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

sbiddle

27264 posts

Uber Geek
+1 received by user: 6692

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 1057611 1-Jun-2014 16:33

I've provisioned Panasonic phones, but never against the Snappernet server.

nigelj

856 posts

Ultimate Geek
+1 received by user: 125

Reply # 1057622 1-Jun-2014 16:46

sbiddle: ...but typically speaking tftp isn't routable so isn't something you use to connect to a different network...

whisky tango foxtrot? TFTP is a UDP service and follows the standard rules of UDP, but is typically limited to whatever limitations placed in the PXE environment (some are worse than others (especially consumer grade PXE environments) at following specs). Generally in my experience TFTP through subnets has worked not too bad, I had a deskphone provisioned on my desk at home here in NZ off a TFTP server cluster (typically contacting US due to gDNS choices) that worked flawlessly, it'd take a minute or two to boot, but typically it'd still beat me booting up my company laptop/lab/etc and logging into everything unless there was a firmware update.

In addition, plenty of examples of TFTP used to update say Cisco routers cross subnet, or even over the internet.

The only thing TFTP and PXE isn't really good at these days is large files and EFI based PXE-booting (at least my experience due to the ultra-small chunking of files).