this is because tftp does not work over the raw internet (nat). this is a
limitation of the tftp protocol. this is why ftp is also a choice. you
m,ust nat ftp through your firewall.



On Thu, Apr 5, 2012 at 12:30 PM, Stiles Watson <[email protected]>wrote:

>
>
> I'm trying to get a Polycom 335 to work remotely without VPN. The phone
> registers and everything works except contacting the boot server.
>
> Registration Example:
>
>  sip:[email protected] <sip:141@REMOTE_WAN_IP
> :5060;x-sipX-privcontact=REMOTE_LAN_IP>
>
> On the phone, under the ServerMenu,
>
>    - ServerType: TrivialFTP
>    - ServerAddr: tftp%3a%2f%2fxxx.xxx.xxx.xxx (where xxx... is the WAN IP
>    of the company network), I've also tried just the WAN IP.
>
> Under DCHP Menu, the default is Custom+Option66. I've also tried static,
> but since the phone is getting its IP from a home router, there are no
> options setup. From the Polycom docs, it says if nothing is returned from
> the DHCP attempts, it will try what is configed in the Server Menu.
>
> I looked at the wiki but did not see anything about boot server for remote
> polycom phones.
>
> I have NAT policies and firewall rules setup to forward port 69 to the
> sipX server and allow the traffic through to the sipX subnet.
>
> Stiles
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

-- 
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to