...@list.sipfoundry.org
sipx-users-boun...@list.sipfoundry.org
To: Discussion list for users of sipXecs software
sipx-users@list.sipfoundry.org
Sent: Tue Sep 21 12:01:58 2010
Subject: Re: [sipx-users] SRV records for ftp
OK, I think I'm down to my last issue.
What works:
* I can place incoming
...@list.sipfoundry.org
sipx-users-boun...@list.sipfoundry.org
To: Discussion list for users of sipXecs software
sipx-users@list.sipfoundry.org
Sent: Tue Sep 21 12:01:58 2010
Subject: Re: [sipx-users] SRV records for ftp
OK, I think I'm down to my last issue.
What works:
* I can place incoming
-
From: sipx-users-boun...@list.sipfoundry.org
sipx-users-boun...@list.sipfoundry.org
To: Discussion list for users of sipXecs software
sipx-users@list.sipfoundry.org
Sent: Tue Sep 21 12:01:58 2010
Subject: Re: [sipx-users] SRV records for ftp
OK, I think I'm down to my last issue.
What works
mailto:sipx-users@list.sipfoundry.org
mailto:sipx-users@list.sipfoundry.org
Sent: Mon Sep 20 13:06:57 2010
Subject: Re: [sipx-users] SRV records for ftp
That is very true.
Interesting development: I pulled down
@list.sipfoundry.org
mailto:sipx-users@list.sipfoundry.org
mailto:sipx-users@list.sipfoundry.org
Sent: Mon Sep 20 13:06:57 2010
Subject: Re: [sipx-users] SRV records for ftp
That is very true.
Interesting development: I pulled down
software
sipx-users@list.sipfoundry.org
Sent: Tue Sep 21 12:01:58 2010
Subject: Re: [sipx-users] SRV records for ftp
OK, I think I'm down to my last issue.
What works:
* I can place incoming calls from the PSTN through flowroute
* From the PSTN, I can dial the remote extension from the auto
Still working through the options you've given me, but the Polysom should
be able to register remotely without ftp if everything is configed
correctly, right?
Stiles
On Fri, 17 Sep 2010 20:43:24 -0400, Tony Graziano
tgrazi...@myitdepartment.net wrote:
By the way... the first sentence in this
-users@list.sipfoundry.org
Sent: Mon Sep 20 07:50:59 2010
Subject: Re: [sipx-users] SRV records for ftp
Still working through the options you've given me, but the Polysom should
be able to register remotely without ftp if everything is configed
correctly, right?
Stiles
On Fri, 17 Sep 2010 20:43:24
://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
sipx-users-boun...@list.sipfoundry.org
To: Discussion list for users of sipXecs software
sipx-users@list.sipfoundry.org
Sent: Mon Sep 20 07:50:59 2010
Subject: Re: [sipx-users] SRV records for ftp
:33 2010
Subject: Re: [sipx-users] SRV records for ftp
The registration request is getting to sipx. I turned the logging level
to DEBUG, restarted the services and executed following:
tail -f /var/log/sipxpbx/sipXproxy.log | grep REGISTER sip | grep
1...@datatek-net.com regdebug141.log
After
: [sipx-users] SRV records for ftp
The registration request is getting to sipx. I turned the logging level
to DEBUG, restarted the services and executed following:
tail -f /var/log/sipxpbx/sipXproxy.log | grep REGISTER sip | grep
1...@datatek-net.com regdebug141.log
After the polycom reboot
Sep 20 13:06:57 2010
Subject: Re: [sipx-users] SRV records for ftp
That is very true.
Interesting development: I pulled down the polycom ip 335 admin guide
and on the top of page 41 (3-5) there is the following note:
Setting Option 66 to tftp://192.168.9.10 has the effect of forcing a
TFTP
@list.sipfoundry.org
Sent: Mon Sep 20 13:06:57 2010
Subject: Re: [sipx-users] SRV records for ftp
That is very true.
Interesting development: I pulled down the polycom ip 335 admin guide
and on the top of page 41 (3-5) there is the following note:
Setting Option 66 to tftp://192.168.9.10 has
@list.sipfoundry.org
mailto:sipx-users@list.sipfoundry.org
Sent: Mon Sep 20 13:06:57 2010
Subject: Re: [sipx-users] SRV records for ftp
That is very true.
Interesting development: I pulled down the polycom ip 335 admin
guide
and on the top of page 41
OK Tony, shoot me down:
I'm attempting to do what you suggested and use FTP instead of TFTP for
remote provisioning the Polycom IP 335. The problem is that we already
use FTP and we can not move our customer facing FTP to another port. I
figured I could just configure the phone to use ftp on
Er.. Bang?
I could assume the FTP NAT/PAT (NAT with port translation) from 21 to 844
would work...
PHONE--(grab file at ftp://1.2.3.4:8444)--INTERNETfirewall--oh, its
for 192.168.2.2:21, sending it onvsftpd
1. I don't think the polycom is sophisticated enough to do any type of DNS
lookup
Well, not so happy about that.
Thanks for the explanation though.
So ... why can I not use TFTP?
Stiles
Tony Graziano wrote:
Er.. Bang?
I could assume the FTP NAT/PAT (NAT with port translation) from 21 to
844 would work...
PHONE--(grab file at ftp://1.2.3.4:8444)--INTERNETfirewall--oh,
Crap. That's a loaded question.
It all in the protocol, and ANY nat translation.
TFTP (nothing to do with sipx, its the nature of tftp) must use a pseudo
random port or your remote firewall must have a way to punch through udp in
NAT mode, which is not the same as ANY NAT translation, which
Thanks, you are a wealth of info! I'll try the several options you've
given me.
FYI, I had an Aastra 67301i auto provisioning with trixbox CE via TFTP.
The phone made its request to the public IP and all I had to do on the
local firewall was open the port for WAN to trixbox subnet and create
Realize the Aastra is a different client, and how the manufacturer
implements a protocol is VERY different from another one...
FTP is the way to do it, and these days PASV FTP is pretty much needed to do
bootrom updates with Polycom. Even in their http/https provisioning they
won't do bootrom and
By the way... the first sentence in this thread is:
OK Tony, shoot me down:
It's actually the IETF and Polycom who did the shooting here...
IETF should write two papers on an RFC. Once for engineers, and one for
everyone else instead of trying to deciper what they mean with loosely
selected
21 matches
Mail list logo
