On Thu, Mar 18, 2010 at 9:45 PM, Scott Howell <[email protected] > wrote:
> > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > In-Reply-To: <[email protected]> > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <43541> > Message-ID: <[email protected]> > > > > Thanks for the great info and links. I don't know why I > didn't find the info for this earlier. > > At any rate I got the auto-provisioning working rather > quickly after reading up. The only problem I found with the > docs was in opt 66 to put the http://servername:8090, but in > opt 67 you do not use the opening "/" just use > "phone/profile/docroot/{mac}.xml". However, after doing > this the phones still would not register. > > The problem ended up being in the sipX config with regards > to the domain name. In the System/Domain config I changed > it to the FQDN and they started working. Previously with > just afccom.local the softphones worked, but the Snoms would > not. Once I changed it to sipfoundry.afccom.local > everything started working fine. > > Nice observation, but realize registering by the domain name will cause other issues as you use it. This is a "falling down" issue by Snon. They don;t properly resolve SRV records for sip, and I stopped opening bug reports with them because they simply don't seem to respond. If it doesn't break anything else, it is simpler and much less problematic to add an "A" record in your DNS for the domain to point to sipx. At which point the sipxconfig works like it does for any phone it supports. It's a SNOM thing, because they can't get it right. An interesting note, I figured this out because when I would > manually configure the phone with sipfoundry.afccom.local as > the proxy the registration would succeed, but I couldn't > make any calls. If I just used afccom.local it would not > even register. I don't really know why XLite and Zoiper > worked with just afccom.local??? Must have something to do > with it running on a domain workstation and MS DNS I'm > guessing. Anyway, what I saw in wireshark was a Proxy Auth > error until I changed the DNS settings in the sipX config. > xlite and zoiper worked because they knew how to resolve SRV records. > Anyway, hope this helps someone else down the road, and > thanks a lot for the quick responses. I look forward to > getting up to speed to give back to the community. > _______________________________________________ > 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/
