When certain redirect server features, including ISN dialing and ENUM dialing, are activated, the result is a change to the file /etc/sipxpbx/registrar-config.in
That file is modified on the host where sipXconfig is running, but it is not propogated to any distributed servers.
This results in some features working or not depending on the (deliberately random) selection of which proxy is used for a request.
The workaround is to make the change and then manually copy the registar-config.in file to any distributed servers. Make sure that any other differences are resolved.
Description
When certain redirect server features, including ISN dialing and ENUM dialing, are activated, the result is a change to the file /etc/sipxpbx/registrar-config.in
That file is modified on the host where sipXconfig is running, but it is not propogated to any distributed servers.
This results in some features working or not depending on the (deliberately random) selection of which proxy is used for a request.
The workaround is to make the change and then manually copy the registar-config.in file to any distributed servers. Make sure that any other differences are resolved.
sipXconfig only supports changing configuration files locally: there is no configuration API to change those files on distibuted hosts
There were numerous discussions and proposals on how to fix it. I'll try to link other issues to this one.
Damian Krzeminski - 2007-10-30 12:40 sipXconfig only supports changing configuration files locally: there is no configuration API to change those files on distibuted hosts
There were numerous discussions and proposals on how to fix it. I'll try to link other issues to this one.
There were numerous discussions and proposals on how to fix it. I'll try to link other issues to this one.