TFTP provisioning not working?

[J.T. D]

25.01u7

Configured option 66/160 in DHCP to point to sipxcom IP address.  Reset phones to clear old configuration.  Phones not picking up provisioning files.

Investigating a little further, I'm not able to tftp to retrieve the config files: When I run a command line for testing tftp, I get "resource unavailable" then it times out and closes the connection. Checking on the server, generated device files are confirmed to be in the tftproot folder.

It's acting like the tftp server is pointed to the wrong directory where the device provisioning files are located?

[Support]

Hello,

We use / recommend / test / support FTP provisioning so please try that and we will note this down as an open issue.  

_______________________

 

OnRelay Support

US: +1 415 523 6400 

AU: +61 285 038 070 

UK: +44 208 629 1460 

NO: +47 21 93 72 27 

sup...@onrelay.net | www.onrelay.com

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/454fbe0b-4906-422f-8380-eaed0a8e4d41n%40googlegroups.com.

[Paul Herron]

Have you tried DHCP options 66 and 120 instead?

[J.T. D]

Yes, all my provisioning is config'd through DHCP options and not manually on the desk phones (Polycom VVX 450s.)

[Support]

Tracked at https://github.com/onrelay/sipxecs/issues/66

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/260e1771-6467-44ab-943f-530af35ad19en%40googlegroups.com.

[Support]

The TFTP service not starting error is due to xinetd being replaced by tftp.socket in Rocky Linux 9.  The TFTP folder structure is correct and works with FTP.

The fix is a simple CF engine config change, and we will go ahead and publish update 8 as soon as we have tested it.

Two other open issues, including the internal custom dial plan problem and the missing SBC authentication statuses, are already fixed, tested and committed for inclusion in update 8.