Ah, and if using dns on sipx the named.conf file should be edited to manual.
This is reminiscent of snom issues with no srv lookup. ============================ 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/ ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Tue Jun 15 08:41:28 2010 Subject: Re: [sipx-users] 407 Authentication required >>> On 6/15/2010 at 08:11 AM, in message >>> <[email protected]>, Osmose <[email protected]> wrote: > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <47777> > Message-ID: <[email protected]> > > > > Hello > > I have installed SipX 4.2 as a test machine to our lab. > > I manage to register 2 SIPphones (Yealink T28s) and a > softphone (3CXphone). > I am trying to make an internal call from one to the other, > for example from 200 to 201 or 202. > > I am taking a resonse on the phones not found. > I am tracing the call. > After the initian INVITE from the phone the sipX responds to > the phone 100 Trying and then 407 Proxy Authentication > required. > The phone respods with: Request ACK > and just after that Request INVITE (propably to initiate the > call again.) > The sipX responds 100 Trying and just after that with 404 > Not found. > The phone then initiates an ACK request and there are no > responses from the SIPX. > > I assume from this that all though the phones are registered > there are not Authenticated. > > > Can anybody help me? > > Thanks a lot. The yealinks do not support DNS SRV. As such the only way we could get them to sorta work was to create an A record that pointed to the sip domain. Registering using the ip address and FQDN did not work. So for example if the FQDN is sipx.testdomain.com, create a DNS record that points testdomain.com to the ip of the sipx server. Then set the yealink to register to testdomain.com As you can imagine, this is really only an acceptable solution for testing and not production. _______________________________________________ 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/ _______________________________________________ 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/
