OK, applied that to a non-production system. No complaints of TLS in logging but still the A record complaint.
"2011-06-16T21:29:41.509416Z":157:SIP:WARNING:pbx.voice.phoneutopia.com:SipSrvLookupThread-22:B5FF8B90:SipXProxy:"DNS query for name 'voice.phoneutopia.com', type = 1 (A): returned error" I see the TLS record is now in the dns zone. Can someone clarify what has (or has not) been done to get the registrar to look at TLS and keep from dying? I ask because if the registrar was or was not happy it might be a while before I saw the issue. Did it ever log any exceptions anywhere? On Thu, Jun 16, 2011 at 4:15 PM, Douglas Hubler <[email protected]> wrote: > On Fri, May 27, 2011 at 9:06 AM, Tony Graziano > <[email protected]> wrote: >> im happy to test. > > thanks tony > > http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/ > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
