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 <[EMAIL PROTECTED]> 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. On 5/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Thanks. I had already tried going into Office B box and change host= > (office A's IP address), performed iax2 reload, and this did not work either. > > At 10:51 AM 5/22/2006, you wrote: > >Don't specify the remote side by name, specify it by IP address. If > >asterisk experiences even 1 dns failure it will not try again until > >a reload/restart/whatever. > > > >[EMAIL PROTECTED] wrote: > >> > >>SETUP: > >>OFFICE A: > >>iax_additional.conf: > >>[lpeaus] > >>username=lpeaus-user > >>type=peer > >>secret=<secret> > >>qualify=yes > >>host=officeb.kicks-ass.net > >>context=from-internal > >>[lpenb-user] > >>type=user > >>secret=<secret> > >>host=officeb.kicks-ass.net > >>context=from-internal > >> > >>OFFICE B: > >>iax_additional.conf : > >>[lpeaus-user] > >>type=user > >>secret=<secret> > >>host=officea.kicks-ass.net > >>context=from-internal > >>[lpenb] > >>username=lpenb-user > >>type=peer > >>secret=<secret> > >>qualify=yes > >>host=officea.kicks-ass.net > >>context=from-internal > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Lacy Moore Aspendora, Inc. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users