Status Acoustics 2 Outdoor Cart User Manual


 
Internet Service Node (ISN) 2.0 Release Notes
Page 23
5.3. ISN 1.0.1 Defects Fixed in ISN 2.0 (ordered by ID)
Identifier Severity
Headline Release-note enclosure
CSCma06207 4
AF port update is not consistent Changing the Alarms Forwarder (AF) port on
the App Server does not work, and causes
the communication to break. If left as the
default, it works correctly.
CSCma06906 6
Caller does not hear ringing
during transfer to CCM before
answer
When a call is being transferred to Call
Manager, the caller hears only silence while
the outgoing call is being connected.
CSCma08761 4
dumplog installed with VB
Administration alone doesn’t
work
If you have installed ISN "Voice Browser
Administration" without a Voice Browser,
Application Server, or SDDSN, dumplog
doesn't work for ISN logfiles (local or remote).
The workaround is to uninstall ISN, then
reinstall "Voice Browser Administration"
along with "Update External SDDSN
Components".
CSCma08953 5
Voice Browser occasionally
retries messages to AppSvr
(Tomcat)
The Voice Browser occasionally needs to
retry it's communication message to the
Application Server. This results in a delay in
responding to the caller for that step of the
IVR.
CSCma11283 4
Benign invalid grammar
message upon startup
On rare occasions at startup, the Application
server logs an error "invalid grammar" for a
single call; the ICM script error handling from
that node will be used to process the call.
CSCma15111 5
Document that outbound
alternative endpoints should not
be used
Outbound alternate endpoints should not be
used for the egress leg of the call (to the
agent), as the retries invokes may take longer
than the time for which the agent is reserved.
This is not documented adequately in the
user manuals.
CSCma16835 3
AS does not handle ICM VRU
Script timeout
If the ICM is misconfigured with a VRU script
timeout which is shorter than the amount of
time required for the script execution, the ISN
will not correctly respond to the timeout. It
will continue with the existing script until it
ends or the caller hangs up. If the ICM script
has reached a RELEASE node, the following
error message will be listed in the App Server
logs: Timed out waiting for Call Result from
Voice Browser, timeout is: 10 seconds The
symptom for this problem may be observed
by monitoring the path the call takes in the
script.