[Home]

Summary:ASTERISK-01251: segentation fault with qualify=yes
Reporter:senad (senad)Labels:
Date Opened:2004-03-20 07:20:22.000-0600Date Closed:2004-09-25 02:53:49
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I tried to use "qualify=XXX" on a a couple of devices (ATA 186 and Sipura 2000) on a public IP, and * goes to segmentation fault every time it starts.
[4003]
type=friend
dtmfmode=rfc2833
context=default
host=dynamic
callerid=Senad Home <4003>
mailbox=4003
incominglimit=2
outgoinglimit=1
username=4003
qualify=3000
auth=md5
secret=po12mn
disallow=all
allow=ulaw
allow=alaw


If it is meant to be used just behind NAT fine, but what and how does * monitor user agent status?

I am using CVS-03/13/04-21:45:03.

Ta
SJ
Comments:By: Olle Johansson (oej) 2004-03-20 08:20:25.000-0600

We need you to attach a core dump (or a gdb debug output) so we can check what happens on your system. Need more information on what channels you're using, what kind of O/S your running on what kind of hardware.

I answered the question on Qualify on the mailing list.

By: zoa (zoa) 2004-03-20 12:44:01.000-0600

you say when it starts, could you do asterisk -vvvvvvvgc instead of safe_asterisk and paste the last lines here ?

Are you sure its on that qualify line ? (i'm using qualify without problems)

By: Mark Spencer (markster) 2004-03-20 13:04:46.000-0600

Find me in #asterisk on irc.freenode.net if you haven't resolved this already.  i'm "kram"

By: Mark Spencer (markster) 2004-03-20 14:20:52.000-0600

Fix ast_ouraddrfor to work with extremely long interface names.