[VoIP] Unknown problem ?

Ian Jolly ian at uax.org.uk
Tue Aug 14 10:55:13 CDT 2007


Thanks folks for the comments. Looks as though we just "switch off" the 
qualify statement and the problem goes away :-)

I was just wondering if it was a genuine problem or not.

Ian Jolly
+64 85 32 889
+44 (0)  352      82 26 (via a 1929 GPO Rural Automatic eXchange!) from 
CNET - the Heritage Telephone Network
+44 (0)1352 83 82 26 (via a 1929 GPO Rural Automatic eXchange!) from  Public 
Telephone Network
FWD Telephone No  83 2230

----- Original Message ----- 
From: "John Novack" <jnovack at stromberg-carlson.org>
To: "Voice Over IP Tandem for Analog Switches" <voip at lists.ckts.info>
Sent: Tuesday, August 14, 2007 3:12 PM
Subject: Re: [VoIP] Unknown problem ?


>
>
> Rusty Dekema wrote:
>> On 8/13/07, Greg Blakely <greg at vyger.net> wrote:
>>
>>> If you have either your sip or iax2 clients tagged as anything other 
>>> than QUALIFY=NO, then asterisk will check them on a continual basis to 
>>> see if they are reachable.  If they're not, then calls won't even be 
>>> attempted to them.
>>>
>>> You'll also get notice on the console when reachable/unreachable status
>>> changes.
> I don't see these with my install of 1.2, probably because I have
> removed notices from logger.conf
>
> I also don't use qualify, and don't have any issues with SIP devices on
> my LAN.
>
> Perhaps the simple solution is to remove "notice" from the console line
> in logger.conf. Especially if the SIP devices all work.
>
> John Novack
>
>
>> In my experience running Asterisk 1.2, the qualify feature was
>> absolutely useless. SIP devices (of all kinds; various softphones,
>> hardware-based ATAs, etc) would habitually "flap" back and forth from
>> reachable to unreachable even though they were connected to my
>> Asterisk server on a completely non-loaded 100mbit local ethernet,
>> even though the Asterisk server and the PCs running the soft phones
>> had no other CPU load, and even though I increased the qualify= time
>> to over 2000ms.
>>
>> Since these SIP devices otherwise worked perfectly, it was quite clear
>> that they were not truly "unreachable" for periods approaching
>> anything like 2 seconds. I don't know what the problem was, and I
>> don't know whether it still exists in Asterisk 1.4 since, although I
>> run it, I have not bothered to turn the qualify option back on.
>>
>> Rusty
>> _______________________________________________
>> VoIP mailing list
>> VoIP at lists.ckts.info
>> http://lists.ckts.info/mailman/listinfo/voip
>> Project Web Page: http://www.ckts.info/
>>
>>
>
> -- 
> Dog is my co-pilot
>
> _______________________________________________
> VoIP mailing list
> VoIP at lists.ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.11.17/951 - Release Date: 
> 13/08/2007 10:15
> 



More information about the VoIP mailing list