Hi Tony, Thanks for testing this. Unfortunately, the way we discovered this issue with the registrar was through a brute force test. Enable only TLS in the zone file. This results to an outright crash of the registrar due to the fact that when querying DNS, the lookup code was assuming _sip instead of analyzing the request uri if it has a sips scheme. This portion of the code has been fixed in sipXtackLib. There is no change required in the registrar.
On 06/17/2011 05:34 AM, Tony Graziano wrote: > 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/ >> > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
