> -----Original Message-----
> From: Scott Lawrence [mailto:[email protected]]
> Sent: Friday, June 12, 2009 9:25 PM
> To: Boy Aidil Sjam
> Cc: [email protected]
> Subject: Re: [sipx-users] Interconnection 2 sipXecs - solved
> 
> On Fri, 2009-06-12 at 10:03 -0400, Scott Lawrence wrote:
> > On Fri, 2009-06-12 at 17:22 +0700, Boy Aidil Sjam wrote:
> > > Hi Scott,
> > > I solved the problem.
> > > Early, I configured the gateway using full hostname.domain.name to
> the other
> > > gateway, even changed the address with IP address, but the result
> still the
> > > same.
> > > Then after I changed the gateway address using SRV, suddenly it
> work.
> >
> > I'm not sure I followed that, but if you like it...


What I mean is, if I set up unmanaged gateway using IP address or FQHN in
address field, called always failed
But if I put only domain name (DNS SRV), the call work.


> >
> > > Well, I think that's why sipXecs very dependent with DNS SRV.
> >
> > DNS SRV is the primary mechanism for HA.

No HA involved here. Only 2 server, each in their own domain.

> >
> >
> > > Next step, testing between 2 server with both server behind NAT.
> >
> > If you mean putting each server behind a different NAT, that is not
> > something that we've tested at all, and it's not a supported
> > configuration.
> 
> Sorry - I may be getting my threads mixed up.
> 
> What isn't supported or tested is having two members of an HA cluster
> behind two different NATs.  If what you have is two different systems
> (different SIP domain names) configured to talk to each other via
> site-to-site links, being behind two different NATs can be made to work
> (with the usual NAT hassles, of course).
> 





DISCLAIMER:
Information in this message is confidential and may be legally privileged. It 
is intended solely for the addressees. Access to this message by anyone else is 
unauthorised. If you are not the intended recipient, any disclosure, copying, 
or distribution of the message, or any action or omission taken by you in 
reliance on it, is prohibited and may be unlawful. Please immediately contact 
the sender if you have received this message in error.

_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to