Posts Tagged ‘Integration’

Waiting on the Beta – Where is the Beta – I want the Beta

Thursday, December 31st, 2009

While we continue to slowly open the VoiceCentral Black Swan beta to more and more people, we ask for your patience and understanding.

With all the awesome suggestions for the final name of the app, and the great press, it’s no wonder we’ve received many emails that say:

When in God’s name can I get hold of that awesome Apple Killing App? I’ve been looking for a way to stick it to them since the [wonderful people at Apple] unilaterally pulled those Google Voice apps from the Store. You should be suing [them] for the cost of supporting customers that they left stranded. The web app should send an email to [the guy who looks like Noah Wyle] on each install that says “Another one bites the dust,” and one to [The guy who personally approves each and every app], if he is real. Oh, and that tard [don't be nasty]. What a tool.

Please note that the only response you’re likely to see is:

Thank you for your interest in VoiceCentral Black Swan. The beta program is limited to a private (mostly internal) set of users at this stage. We will be opening it up to more and more users throughout January and February. Be on the lookout for an activation e-mail at the address you provided with your registration when your account is ready to use.

Just be patient, and remember how long it took Google to process your Google Voice request.

Transfer files without FTP?

Monday, January 5th, 2009

We recently had an integration where we needed to grab data, and update a patch, onto a “dumb” switch. This was part of a automated solution we were providing to a hardware vendor.

The switch had access via telnet and a stripped down http server. We needed to get on the box, run diagnostic scripts, and grab the logs. Using that data, we needed to make configuration changes, and report all of the steps to the operators for compliance and tracking.

We wrote a script that pushed up some shell code by echo-ing shell script to a file. This gave us the ability to binhex on the dumb switch. Then, after running the diagnostics and redirected the output, we could execute our binhexzip script, and echo/cat it to the terminal. We could then reconvert the hex back to the zip and back to the captured files.

Then we reversed the process pushed up the fix in the same way, and unpacked it, ran the updates and sent the notifications.