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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Oct 7 03:28:51 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13635 
====================================================================== 
Reported By:                jtodd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13635
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
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 03:28 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0093270) jtodd (administrator) - 2008-10-07 03:28
 http://bugs.digium.com/view.php?id=13635#c93270 
---------------------------------------------------------------------- 
I see what's happened. Default install locations have changed. 
/usr/local/sbin/asterisk is the new binary location.  Though now I get an
even more unusual result back, in that the Dynamic Loader seems to have
halted the startup of Asterisk.  I'm going to let it alone and go to sleep.
 More on this tomorrow AM if it's running by then. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-07 03:28 jtodd          Note Added: 0093270                          
======================================================================




More information about the asterisk-bugs mailing list