Tony,
Firstly, thanks for the quick response. I think I covered, or at least tried to, most of what you have suggested already. You must have also enabled sipx to support remote workers and the server is behind NAT. "I have all my internal and external SRV records configured, and have followed every document I can find including DNS Concepts for sipXecs By: Michael W. Picher, and the Configuring remote workers cheat sheet." Sipx is configured to support remote workers and NAT per the document "Configuring remote workers cheat sheet". If it is was not, this should still not prevent the 450 from attempting to communicate which I would see in the firewall traffic logs. Confirm your firewall at the remote end does not have an ALG or SPI turned on. Confirm your firewall where sipx is installed is handling NAT via symmetric port nat "I have a test remote network setup, and have verified that if I send any traffic from it to my sipx proxy I can see the traffic at my local firewall. I am allowing all traffic from the remote network and can see UDP, TCP and ICMP traffic that I manually generate". My firewall is a linux based router that has no Application level support I know of, The NAT is one-to-one (no PAT) both ways. All traffic to my public IP is translated to the gateway and vice versa, with no port translation. Again, even if it was translated differently or wrongly, I would see the 450 attempting a connection. All other traffic from the remote network shows in the logs. The issue is the phone is NOT trying to communicate at all. Try and register a softphone FIRST. After your softphone registers properly, make sure you manually set the FTP address for the remote phone to the public IP of the sipxecs installation. This also means FTP must be NAT'ed to sipx from that firewall. "If I fire up a soft-phone on the remote net and point it to my proxy it registers and works fine too, so the routing and firewall settings are good". Ok, I am confused about the "FIRST". If I try to connect x-lite from the remote network I have no problem, regardless of the order of which I attempt to do it in relation to the attempt to connect the 450. The x-lite client connects, works, and all SIP traffic shows in my firewall log. The 450 FTPs fine... , "it appears the FTP traffic from the phone contacting the configuration server is all that gets generated. No other SIP, TCP, UDP, ICMP, etc, traffic is logged." It downloads it's config and goes about its business... never ever trying to contact my proxy. Do not use above firmware 3.1.3RevC on 4.0.4 "Wiping the configs and updating the firmware/software to 3.2.3, back reving to 3.1.30" Tried that too. Though I am on 3.2.2 trying to troubleshoot at this point. I will try again revert to 3.1.3 if that is what is need to do, though as I mention I tried that as well. It seems something is missing in the config, that the 450 needs to tell it to try and contact my proxy. It is probably something incredibly simple, but I can't make it do it if I use sipx to generate configs first, even if afterwards I manually set the parameters through the phones web or panel interfaces. "I have tried making all the changes above thru the sipxecs web manager as well as local to the phone, with no success. However, if I wipe the phone and load vers 3.x.x and manually configure the phone, it registers." Thanks again. John Clark Small Business Systems Fort Worth: 817-834-0364 x102 Dallas: 972-248-4455 x102 [email protected] www.sbsproactive.com From: Tony Graziano [mailto:[email protected]] Sent: Tuesday, April 06, 2010 7:22 PM To: John Clark Cc: [email protected] Subject: Re: [sipx-users] Remote Polycom registration - not working You must have also enabled sipx to support remote workers and the server is behind NAT. On Tue, Apr 6, 2010 at 7:56 PM, John Clark <[email protected]> wrote: Hoping maybe someone has some ideas about why I cannot get a Polycom 450 remote phone to register. I have a test remote network setup, and have verified that if I send any traffic from it to my sipx proxy I can see the traffic at my local firewall. I am allowing all traffic from the remote network and can see UDP, TCP and ICMP traffic that I manually generate. If I take a working (locally connected) Polycom 450 and move it to the remote network, it will not register. If I check the firewall traffic, it appears the FTP traffic from the phone contacting the configuration server is all that gets generated. No other SIP, TCP, UDP, ICMP, etc, traffic is logged. If I manually clear the configuration server IP in the phone and reboot it, then no traffic is generated to my sipx proxy from the phone at all. This holds true no matter what settings I make to the phone, and I have tried all of the following settings manually at the phone which I understand overrides any config files applied. Setting the phones IP to a static and dynamic configurations. Setting the Outbound Proxy to static IP, Proxy name, static port, and tried all transport settings. Setting the Call server Settings to static IP, Proxy name, static port, and tried all transport settings. Setting line settings to static IP, Proxy name, static port, and tried all transport settings. Setting the local DNS name to the local and external domains. Wiping the configs and updating the firmware/software to 3.2.3, back reving to 3.1.3 Holding tongue to left and right side of mouth while making changes. It seems to me the phone is not functioning correctly, since it is not even attempting to contact my proxy, but if I set it to DHCP and boot it to the local net, it works fine. If I fire up a soft-phone on the remote net and point it to my proxy it registers and works fine too, so the routing and firewall settings are good. I am at a loss. Anyway, based on the last statement, my conclusion is regardless of what changes I manually make to the phone, that the configs must be taking precedence, and my changes are not having affect, but this is counter to my interpretation of the Polycom docs. Further proof to this is that this is only the case after the phone has been configured via sipxecs. I have tried making all the changes above thru the sipxecs web manager as well as local to the phone, with no success. However, if I wipe the phone and load vers 3.x.x and manually configure the phone, it registers. I have all my internal and external SRV records configured, and have followed every document I can find including DNS Concepts for sipXecs By: Michael W. Picher, and the Configuring remote workers cheat sheet. DNS aside, if manual phone configs take precedence I can't figure out why the 450 is not making any attempt to contact my sipx proxy when given the IP, Port, and Protocol. Any suggestions would be appreciated. Thanks. John Clark Small Business Systems Fort Worth: 817-834-0364 x102 Dallas: 972-248-4455 x102 [email protected] www.sbsproactive.com _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
