Frequently Asked Questions
Does FastIVR for Cisco for Cisco actually play the audio, or just
simulates the call flow?
FastIVR for Cisco does play audio and DMTF tones using
local system's audio capabilities, so developer will
of course hear everything that the real user would
hear. FastIVR for Cisco is like having Cisco with IVR
functionality running on our laptop or desktop
computer. The only difference there's no
transmission of IP packets involved.
Does FastIVR for Cisco support tftp?
It does not support tftp as such, but it supports
emulated file systems including ftp, tftp, or http.
So it is possible to configure that tftp://some.host.com/sounds/
will actually point to the some local folder which
has the sound files, so you can use "real"
configuration. So when your application will try to
play tftp://some.host.com/sounds/welcome.au file
from your local hard drive will be played, this
happens absolutely transparently for the
application. This way developer is not dependent on
the tftp server and can work even on the internal
network behind a firewall.
What AAA backend support does FastIVR for
Cisco have?
Does it talk to a real AAA server?
Yes, there are actually two options:
- Communication with real AAA Server (New
version only)
- Current version also emulates work of the AAA
subsystem, where the authentication/authorization
source is local. Any possible VSA attributes you
need (credit-amount, etc.) can be added.
Will FastIVR for Cisco handle very large applications
that are 5000 or more lines long?
FastIVR for Cisco is perfect for this task since testing
such applications involves symbol compression to get
them into the 100K Cisco limit, loading the script,
and restarting Cisco etc.(such a waste of time).
FastIVR for Cisco uses "real" TCL environment, so we're not
bound by the IOS limitations. For example,
FastIVR for Cisco.tcl itself has more than 11,000 lines.
Is FastIVR for Cisco able to handle all the VSAs of
Cisco?
Yes, you can configure any VSA pairs there (even
your own custom ones not supported by default Cisco
applications).
Is FastIVR for Cisco flexible enough to simulate some
exceptions like insufficient fund, destination
restrictions, long pound and so on?
This does not really apply to the FastIVR for
Cisco.
Insufficient fund and etc. is just a case of
authorization failure (triggered in the AAA) and
corresponding functionality in the IVR script.
FastIVR for Cisco is just a tool which executes that script.
New version of FastIVR for Cisco will be able communicate with
a real AAA system, and the existing one "talks" to
the local AAA source. For example, to emulate "zero
balance" condition, VSA attribute "credit-amount"
for that user should be set up with 0 value. Also,
since we provide real TCL environment, for debugging
custom functions can be used, so basically any
response from the AAA can be emulated.
