Hi, I'm taking a look at issues: http://track.sipfoundry.org/browse/XX-7342 and http://track.sipfoundry.org/browse/XX-6944 which relate to the handling of configuration changes for the internal SBC.
This issue appears to be related to confusion in sipXecs between sipXbridge's role as a service and its role as a device. Currently sipXconfig provides a service to handle configuration for the Internal SBC, but the Internal SBC is also treated as a device. In configuration when we do a "Send Profile" to the Internal SBC it replicates sipxbridge.xml, and (after a delay of approx 20 seconds) it reports the device "Restarting: sipXbridge-1/Internal SBC" in Job Status, which marks the SIP Trunking service "restart required" (but doesn't actually restart it). This doesn't seem right, I would expect the "Send Profile" to actually restart the Internal SBC. However if you just change Internal SBC configuration (and don't do a "Send Profile") this also (after a delay) reports the device "Restarting: sipXbridge-1/Internal SBC" in Job Status, which marks the SIP Trunking service "restart required". In this case I would expect it to not restart the device since the installer has not actually sent the profile yet. In general I would recommend that we should try to make the Internal SBC behave more like a device, and try to avoid the (rather annoying) delayed Restart Required state on the SIP Trunking service. Any comments or suggestions? Thanks... Dave.
_______________________________________________ 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/
