subrigo corporation
atilla gahbro
atilla.gahbro@subrigo.net
1.213.325.2543





subrigo corporation integration project info:


currently subrigo operates many best of breed service delivery platforms that within their own right are fully qualified and capable systems

however from an overall company wide system integration perspective pertaining to data/account exchange, billing, reporting, provisioning, etcetera the systems are lacking

due to the nature of the systems involved two way integration is a must

some functions are better handled at the service delivery platform and pushed/synched to a common management system (whmcs) while other functions are better handled being created on the commom management system (whmcs) and then being pushed and synched with the service delivery platform

the decision would be largely based on the best of breed solution approach

so as an example if easysite (easysite.subrigo.net is our private labeled sitekreator [sitekreator.com] server) has a really nice customer signup portal, we would want to use it and have the end user info pushed to the common system. however please note that account functions are available using sitekreator api making it possible to create the account in whmcs and then linking the customer to the easysite portal to go through the website design selection process. this may be the best of both worlds solution for this application

on the other hand if the signup choices were more pragmatic and not stylistic in nature such as those required for easystor (our private labeled ahsay obs online data backup platform) then the signup could be handled by whmcs and pushed to the easystor server

the ultimate decision to push or pull from one system to another would depend on the easy of the module/api and the supported functions in each direction





********************************************************************************************************

whmcs integration info:



http://wiki.whmcs.com/API

http://wiki.whmcs.com/API:About

http://wiki.whmcs.com/API:Example_Usage

http://wiki.whmcs.com/API:Functions (has lots of functions listed here)





http://wiki.whmcs.com/Customising_WHMCS (has several sections, a few of which are listed below, go to url for complete list)

http://wiki.whmcs.com/Action_Hooks

http://wiki.whmcs.com/Creating_Modules

http://support.whmcs.com/dl.php?type=d&id=19 (module development kit)



http://wiki.whmcs.com/Modules



http://wiki.whmcs.com/Contributions



********************************************************************************************************


ahsay offsite data storage and backup server info:

see ahsay file section 19 for api info



********************************************************************************************************

easysite (sitekreator) integration info:



http://sitekreator.com/restutorials/manage_accounts_remotely.html    (pass:k3lpfj)







How to Manage Accounts Remotely


About

SiteKreator enables resellers and licensees to manage accounts using GET/POST HTTP requests. You can open, close, update, suspend an account as well as log-in.

Return Codes
The response to each request denotes the status of the operation. It can be either successful or may have failed. The status of the operation is represented as two lines. The first line can be SUCCESS or FAILURE. The second line is a human readable message describing the status in details.
Here's an example of a response:
FAILURE
Access denied. No APIKey specified.



URLs

Open an account

http://[RESELLER]/Tools/account_open.html?<param>=<value>[&<param>=<value>]

The parameters are:
- APIKey - unique per-reseller key that is used to identify and authorize the reseller
- SignUpPackageCode - identifies the package that will be assigned to the package upon sign-up
- DesignID

- SiteTitle
- Email
- Login
- Password
- Name

Close an account
http://[RESELLER]/Tools/account_close.html?<param>=<value>[&<param>=<value>]

The parameters are:

- APIKey

- Login

Suspend an account
http://[RESELLER]/Tools/account_suspend.html?<param>=<value>[&<param>=<value>]

The parameters are:

- APIKey
- Login


Resume an account
http://[RESELLER]/Tools/account_resume.html?<param>=<value>[&<param>=<value>]

The parameters are:

- APIKey
- Login

Update the account package
http://[RESELLER]/Tools/account_update.html?<param>=<value>[&<param>=<value>]

The parameters are:

- APIKey
- Login
- PackageCode
- ExpirationDate - if set to <empty> or not passed at all the account will not have any expiration for the specified package code


Login to an account
http://[RESELLER]/Tools/account_login.html?<param>=<value>[&<param>=<value>]

The parameters are:
- Login
- Password

********************************************************************************************************


4psa voipnow integration info:


Example PHP SOAP API Client
In order to support the third party developers, we have made available a demo client written in PHP, which is able to connect to a 4PSA VoipNow server and to create a reseller, client or extension (based on administrator choice).

Full source code is provided and the code is released under GPL. With minor modifications this example can evolve in an account sign-up page, integrated with your current website. Download the client from:


http://www.4psa.com/software/php-soap-client-0.0.1.tar.gz



You need PHP >= 5.1.2 in order to use it






http://4psa.com/docs/voipnow/api_reference/ch01.html


http://www.4psa.com/docs/voipnow/voipnow_callapi.pdf


http://www.4psa.com/docs/voipnow/voipnow_cli_reference.html


http://www.4psa.com/docs/voipnow/plesk_voipnow_integration_setup.pdf


http://www.4psa.com/software/voipnow-php-soap-client-0.2.0.tar.gz


http://www.4psa.com/software/VoipNowdotNET.zip




********************************************************************************************************


pbxnsip api info:


http://forum.pbxnsip.com/index.php?s=605f2969b45a8150fd6945216077f998&showforum=28