Dave wrote: ... > We also need to consider HA systems, e.g. > sipXbridge-1 (primary server) > sipXbridge-2 (distributed server) > Currently they can each be configured with different SIP > settings, but once we switch to a service they will both have > the same settings. > I think that's OK?
Ah yes, I forgot. Despite the fact that the configuration is displayed as per-server, it is not actually server-specific. (XX-7252) I guess the "SIP Trunking" service configuration is the exception, since it is actually quietly mapped to a server-specific "sipXbridge-N" instance. > Suggested handling of jira issues: > XX-7342 - This issue is only complaining about the false restart > job status message. Since the fix is planned for 4.1.6 I've provided > a patch that will generate a valid message for the Internal SBC. I don't think that solves XX-7342. The Job Status message would no longer be inaccurate, but the bigger problem is the large delay before "SIP Trunking" is prompted for restart. How can we fix that? -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
