asterisk users - Nov 2003 - IAX2 connectivity problem (qualify=yes)

Hi there,

I still have issues with the IAX connection between two servers (one 
static (server A), one dynamic (server B), none behind NAT):

B registers with A, and "iax2 show registry" shows that everything is 
fine. However, after a while if I check on server A with "iax2 show 
peers" I see a status of UKNOWN (in iax.conf there is a qualify=yes 
statement for server B).

The problem is that the connection to server B regularly gets worse than 
2000 ms and is thus temporarily listed as unavailable - fine so far, that 
is correct. But at some point server A stops to pick up the working (!) 
connection and permanently shows status UNKOWN although the connection 
is fine again (40 ms or so). It does help to issue a "reload" on
server
A, but that's for sure not the way it should be... without that
"reload"
server B will be permanently unavailable.

Has anyone else seen this? Suggestions?

Cheers, Philipp

Philipp von Klitzing wrote:
>Hi there,
>
>I still have issues with the IAX connection between two servers (one 
>static (server A), one dynamic (server B), none behind NAT):
>
>B registers with A, and "iax2 show registry" shows that everything
is
>fine. However, after a while if I check on server A with "iax2 show 
>peers" I see a status of UKNOWN (in iax.conf there is a qualify=yes 
>statement for server B).
>
>The problem is that the connection to server B regularly gets worse than 
>2000 ms and is thus temporarily listed as unavailable - fine so far, that 
>is correct. But at some point server A stops to pick up the working (!) 
>connection and permanently shows status UNKOWN although the connection 
>is fine again (40 ms or so). It does help to issue a "reload" on
server
>A, but that's for sure not the way it should be... without that
"reload"
>server B will be permanently unavailable.
>
>Has anyone else seen this? Suggestions?
>
>Cheers, Philipp
>
>
>  
>
Try "qualify=3000" which will increase the time between checks.. 
Although it sounds like there is more to this problem than just 
increasing the time..

Later..

Hi!
> Try "qualify=3000" which will increase the time between checks.. 
> Although it sounds like there is more to this problem than just 
> increasing the time..
That's not really what I want to do - quality is really bad if you go 
above 2000, so it makes sense to keep it at this. I can schedule a 
reload, of course, e.g. once an hour, but that can't be the correct way 
to do this... is there really no-one else out here who has seen this??

Cheers, Philipp