On Tue, May 31, 2011 at 4:11 PM, Tony Graziano <[email protected]> wrote: > I took just the three RPM's. I did a test migration talking all the > rpm's one time briefly, but was having other issues so I rolled back > to 4.4.0 stable and then took just the three. There were no details > why regitrar failed, though I have seen this on another production > system (registrar fails silently, kicking no alarms). Unfortunately I > can see nothing in logs that indicates why. As a matter of fact you > have to view the registrar from the sipxconfig UI to see the failure > and can restart it. The details link says "no details" though. Over a > period of time the registrations are expiring on the phones though. > > That was also in a larger environment where I thought it was related > to the RLS patch being needed. > > So my real question is, does the RLS patch have anything to do with > whether or not the registrar works properly or not in this case? > Somehow I am leading myself to this conclusion, but am not sure if it > makes sense. > > I did not notice the A record issue within the sipxproxy logs and did > notice the tls record was now populated in the dns zone though. >
There were some issues with enabling only _sip._tls SRV record for SIP domain that causes sipxregistrar crash, see http://track.sipfoundry.org/browse/XX-9656. Joegen pushed in a fix for and I merged back the TLS SRV sipXconfig work done in http://track.sipfoundry.org/browse/XX-9639. Tony, is it OK with you if we'll spin new 4.4 RPMs and use the same procedure for test? Thanks, George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
