[asterisk-bugs] [Asterisk 0013635]: SRV record failures on OpenBSD (all OSes?)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13635 
====================================================================== 
Reported By:                jtodd
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   13635
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 141039 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-07 02:30 CDT
Last Modified:              2008-10-07 11:56 CDT
====================================================================== 
Summary:                    SRV record failures on OpenBSD (all OSes?)
Description: 
Looks like SRV record lookups are failing on OpenBSD 4.2.  I can't tell you
if this is failing on other systems; haven't tried any others thus far.

Other DNS issues of note: system takes a LONG time to start up, halting
and waiting on the dnsmgr_lookup functions for the various SIP peers -
like, 30-40 seconds each before proceeding.
====================================================================== 

---------------------------------------------------------------------- 
 (0093287) jtodd (administrator) - 2008-10-07 11:56
 http://bugs.digium.com/view.php?id=13635#c93287 
---------------------------------------------------------------------- 
Well, I don't mind it going into /usr/local, actually.  I've always been
somewhat annoyed that it went into /usr/sbin, since that area shouldn't be
messed with.  So, I guess I agree that the current location is correct.

Of course, this doesn't actually relate to my original problem (which
perhaps has been corrected) or the actual problem that I discovered with
that revision of TRUNK code, which is that Asterisk now stops at this
point:

...
 Asterisk Dynamic Loader Starting:
Asterisk Ready.

*CLI> 

I will start a new ticket.  This one should either be closed out, or
changed to reflect the nature of the problem being worked on. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-07 11:56 jtodd          Note Added: 0093287                          
======================================================================