Â
sipXconfig replication triggers
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
In this wiki article we'll detail each service replication mechanism. You can get some general information about the replication mechanism by looking at SipXecs replication mechanism
Remember, sipXecs services are configured in service.beans.xml
sipXecs Supervisor Service
Configurations |
Type |
Restart required |
|---|---|---|
serviceConfigurationFile |
No |
Triggers
Class |
Method |
Details |
|---|---|---|
onSave(Object) |
Config replicated at a specific location when that location is saved |
|
initLocations() |
Replicates IMDB data sets and files that are not declared as a service dependency but needs to be present before sipXconfig attempts to restart the services. |
sipXecs Proxy Service
Configurations |
Type |
Restart required |
|---|---|---|
sipxProxyConfiguration |
serviceConfigurationFile |
NO |
peerIdentitiesConfiguration |
defaultConfigurationFile |
YES |
Triggers
Class |
Method |
Details |
|---|---|---|
saveTlsPeer(TlsPeer) |
Triggered when TLS peer is saved. sipXecs Bridge Service is also replicated here. |
|
deleteTlsPeers(Collection<Integer>) |
Triggered when TLS peer is deleted. sipXecs Bridge Service is also replicated here. |
sipXecs Registrar Service
Configurations |
Type |
Restart required |
Replicable |
|---|---|---|---|
sipxRegistrarConfiguration |
serviceConfigurationFile |
YES |
if service is installed at location |
redundantSipRouterBundle |
defaultConfigurationFile |
NO |
 |
Triggers
Class |
Method |
Details |
|---|