V.25: Getting Started Notes

Here's a list of startup notes as I attempt to get V.25 up and running.

  1. Download and first install. Both downloading the software and running the installer proceeded witthout a hitch.
  2. Runing VoiceCenter home. That's the first glitch: there's no "Voxeo" folder on my start menu; somehow it wasn't put there by the installer.

    And, actually, now I'm a bit stuck. The only executable in Program Files/Voxeo is "voxeo.exe." If I use an iconic view, double-clicking on voxeo brings up a command-line window which disappears immediately.

  3. After a bit of fooling around in a command-line window, I type "voxeo status" to discover that vxml is running but none of the other services are installed. "voxeo install" gets everything installed. "voxeo run vmanagerlink" should bring up the VoiceCenter control panel, but fails. The web browser is launched and goes to 127.0.0.1:8888, but there's nothing there.
  4. I note that the previous command attempted to connect to port 8888, but Voxeo's download web page said to expect the web server to at either 8080 or 8081. I am unable to connect to either port either by web browser or telnet. Ah... "voxeo status" reveals that I've installed the services but they're not started. "voxeo start" starts all running services.
  5. "voxeo run vmanagerlink" now magically brings up the -- what? Instead of a local page, I get a Voxeo-based page with a link back to my home page. Odd. I'd expect that page to be local.
  6. Clicking on the "admin" link — and in this release, admin/admin is right there where you can't miss it — I log into the admin web page.
  7. Warning: I can log into the admin page from a remote machine. I of course find this very convinient, but it does mean you have to manage your firewalls.

In my next post, I will discuss whether or not I can get Free World Dialup to work.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More install notes

Although you can access the admin page remotely, saving configuration changes works intermittently. I've successfully configured prophecy as an asterisk extension, and gotten a modified version of the vxml-home.xml script to work correctly, accurately and consistently, recognizing and speaking back a choices from a list of 25, even over a cellphone speakerpone, over a sip connection, trhough asterisk, to prophecy. I have yet to be able to get prophecy to recognize asterisk as a sip provider and will advise on further progress. Prophecy platform is a clean WinXP Pro install. Asterisk is asterisk@home 2.2 (asterisk version 1.2).