[Asterisk-Users] Office to Office via IAX2 problems

[asterisk at txpe.net]

Well, I changed host=ip address, qualify=2000, and rebooted computer 
and now it connects.  Hopefully, this will allow Office B to stay 
connected to Office A.

Thanks everyone.

Doug

At 03:30 PM 5/22/2006, you wrote:
>Hi Doug -
>
>>Office A routinely looses connection to Office B. When typing IAX2
>>Show Peers, it will show as Unreachable. I issue IAX2 Reload and it
>>will work again for 1-3 days (haven't narrowed the time down yet). My
>>theory is that the DSL at Office2 is changing IP addresses regularly
>>and this is the cause of the problem??? This has been going on since
>>I set up Office B (2-3 weeks). I never had to touch Office B box.
>>Office B seemed to maintain connection, until now (see Issue 2).
>
>Just to cover all the bases.  Can one machine talk to the other at
>all?  Can you ssh from one box to another (if you don't use ssh, can
>you telnet to an open tcp port)?  If not, it is surely a routing
>issue.
>
>If you can connect via non-asterisk methods, you might try increasing
>your qualify value to something higher (qualify=1500), or just remove
>it altogether for testing.  It might be that the latency is high
>enough that the connection consistently fails to qualify.  (What are
>the ping times, BTW?)
>
>I'll second Eric's advice to not use a DNS name for the host, even in
>your final setup.
>
>- Noah
>
>
>On 5/22/06, Lacy Moore - Aspendora <aspendora at gmail.com> wrote:
>>
>>SInce you say it was working, I am assuming that both officea.kicks-ass.net
>>and officeb.kicks-ass.net resolves to the real IP address and not an
>>internal address, correct?
>>
>>Also, are you providing DNS or someone else?  Is this domain registered to
>>you?  I ask that because if it is not, and you are not providing DNS, it may
>>be resolving to another IP address.  But, since you said it is the same
>>using an IP address, this should not be the real issue.
>>
>>I'm not sure this would really have anything to do with it, but, if it was
>>me, I would not have the two offices on the same subnet.  I'd use 192.168.1
>>for one and 192.168.2 for the other.  It just keeps things a little simpler
>>routing wise.