Yes, sipXecs can act as "just a proxy". In fact, that's how it was first designed.
Assuming that you've got NATs or firewalls, you have to get the NAT/firewall configuration in sipXecs set correctly. sipXecs will insert media relaying into the path of incoming/outgoing calls as necessary. As always, turn off any "SIP ALG" support in firewalls -- sipXecs is better at doing this than they are. OTOH, sipXecs assumes that the other end of any direct-Internet-SIP connection supports the same functions that it demands of a local phone. Remarkably, some SIP systems aren't that powerful. (Unfortunately, many VoIP providers have that problem.) Papering over that is more complicated; I'm not sure of the details, but I *think* that you can add an entry that treats a deficient destination as an ITSP, and then sipXbridge will be activated to handle SIP for it. The worst problem is "How do I dial destinations in other domains?". IIRC, you can configure dial plan rules to map particular digit strings to destinations in other domains. But often the easiest is to enable ISN dialing, which makes it easy for users to dial outside destinations. Dale _______________________________________________ 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/
