Status Acoustics 2 Outdoor Cart User Manual


 
Internet Service Node (ISN) 2.0 Release Notes
Page 12
Identifier Severity
Headline Release-note Enclosure
CSCma23943 3
30 ms packetization doesn’t
work for Call Transfer with ISN
VB
Symptom: With ISN Voice Browser,
packetization is 20ms even if gateways are
configured for 30ms. Conditions: Using ISN
Comprehensive or queue and transfer
deployment models with ingress and egress
gateway both configured for 30 ms, the
packetization used during IVR treatment and
for IP Transfer is 20ms. Workaround: None
CSCma24354 3
Reporting for IVR time is not
available (ServiceID isn’t
configured)
Peripheral Service reports cannot be generated
for ISN calls, which means that reporting is not
available for the time spent in the IVR. The ISN
Application server sets the Service ID to -1 (not
used); it should put a configurable value in the
field so the user may set different values for
different Application Servers and get reports
that distinguish between them.
CSCma04922 4
Sometimes getting null.wav file
on first call after AS restart
After the Voice Browser and Application Server
start up, the first call occasionally fails to play
the first prompt in the application. The Voice
Browser logs an error that it is unable to
retrieve the null.wav media file, and an error is
returned to the ICM application.
CSCma05340 4
Component Selection dialog
screen shows incorrect
diskspace required
During installation of an Application Server, the
user will see an erroneous number for disk
space required. The user is protected by
underlying software that compares the actual
disk space required to the available disk space
and alerts the user.
CSCma05595 4
If transfer fails, ISN hangs up;
should play error
Without router requery enabled on the ICM,
when an attempted IP transfer fails, the ISN
simply disconnects the caller; it should playing
the critical error media before disconnecting.
The workaround (and better solution all around)
is to use router requery so the script
determines the proper action when a transfer
fails.
CSCma05858 4
Very rarely, AS receives
corrupted http messages; VB
retry works
On rare occasions, a delay is experienced by
the caller because the HTTP message is
corrupted between the Voice Browser and the
AppServer. The AppServer logs the error since
it is unable to respond; the Voice Browser
times out and retries the message, which
succeeds. In lab conditions, the problem has
been seen approximately once every 60000
requests.