|Professional Services||Second Signal||Presentations||Andrew's Blog||Support|
The remote software I use for Second Signal to relay audio data to the PBX and also to pick out the activation tones is written in Visual Studio, while the web server is Lotus Domino, and the PBX is Asterisk. The remote client communicates to the Domino server using Web Services, but until now it has only really been to post log data and send an alert when a tone-activation occurs. Setting up, configuring, and managing the the remote software had to be done using something like VNC to remotely control the desktop on which it runs.
That's all changed now.
The new version of the remote software that I'm in test with now synchronizes all of its local configuration data with the server. For each install case, I can manage a distinct configuration set at the server and specify which settings should be controlled locally, which should always be overridden by the setting defined at the server, or even do a "one-time push" of a set of configuration settings to the client and the let the client manage it from there. If a remote machine is replaced, the new software installation will pull down all the correct settings for that account the first time it starts up. This is all done with Web Services.
That said, using Visual Studio.NET on one screen and Domino Designer in the other really services to highlight the strengths (and more so) the weaknesses in the products. As you can imagine, there's a blog post coming about that. I'm still debating, but the title may be something like "Dear IBM, please get your shit together." More on that later.
Please wait while your document is saved.