>>> "Andy Spitzer" <[email protected]> 03/26/09 10:27 AM >>> Woof!
Robert wrote: > I introduced the dependency to avoid leaving the system where some basic > calls work and some don't. My own personal opinion is that this kind > of hit-and-miss behavior is worse than the system not running at all > because can give the impression that the system is fine until you try a > call that needed sipXrelay. That's no different than a POTS PBX having PRI trouble, or a bad analog PSTN line. Internal calls work, external ones don't. It would be very odd to have a PBX that cannot make internal calls because a back hoe took out the PRI line...why would't we expect the same from VoIP? If the "internet" is down, but the "intranet" is up, I sure would expect internal calls to work. If sipXrelay isn't up, the proxy can send back the appropriate cause code making it clear why the call didn't go through. --Woof! ** If the Internet goes down using sipXbridge to connect to an ITSP andyour internal users (sitting in the same place where the sipxinstallation is) can't call and tell you they can't make outgoing callsbecause sipxrelay won't let them? Of course a remote user can't jump on a cell phone and call in either because sipxrelay could block that too? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
