Jump to content

Doman Management tool for many domains


gotvoip
 Share

Recommended Posts

We have a prospect that is interested in running pbxnsip on a blade server with many instances of pbxnsip bound to different cores and across 10 blades. There could be 500 domains if all goes well. They are asking for a tool to manage all the domains instead of http'ing into each system to manage the individual domains on that system. Any ideas on how to do this without to much effort?

Link to comment
Share on other sites

We have a prospect that is interested in running pbxnsip on a blade server with many instances of pbxnsip bound to different cores and across 10 blades. There could be 500 domains if all goes well. They are asking for a tool to manage all the domains instead of http'ing into each system to manage the individual domains on that system. Any ideas on how to do this without to much effort?

 

Sooner or later they have to write some shell scripts that automate their processes. curl can be of great help, as most of the day to day steps can be done through the web interface. But other jobs like managing DNS obviously needs to be done outside of the PBX itself.

 

The big question is if they want to give the customers access to the self-adminstration web interface or they want to do this through a set of scripts that use SOAP to change certain settings on the PBX.

Link to comment
Share on other sites

  • 2 weeks later...

The customer commented on what is needed.

 

1. A step by step provisioning tool that dummies can use.

2. A reporting tool for registered handsets to what business or domain.(at least monthly)

3. A domain control that can search any domain across multi servers.

4. Agent resellers security level (not important to us. Well not yet)

 

Couldn't 1. use the configuration wizard from 1.5? Maybe that code could be put in the public domain and the community can maintain it to free up pbxnsip engineering. 2. would be need the system to total the number of handsets registered in the domain and make and snmp attribute so it could get pulled. 3. would need pbxnsip to push the xml into a central database so it could be queried to find say what domain a user or DID is from.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...