Filter
Top Products
Special offers from our partners!
Find Replacement BBQ Parts for 20,308 Models. Repair your BBQ today.
Internet Service Node (ISN) 2.0 Release Notes
Page 13
Identifier Severity
Headline Release-note Enclosure
CSCma05957 4
Unknown MicroApp needs to
return an error code to the ICM
In the ICM configuration manager "Network
VRU Script List", if the "VRU script name"
contains an invalid MicroApp name, the error
code returned to the ICM is not correct. In the
ScriptEditor, call execution will continue out of
the "X" branch of the RunScript node, but the
ECC variable user.microapp.error_code will be
unchanged. A workaround is to make sure the
MicroApp name used in the "VRU script
name" field is correct.
CSCma06146 4
When VB retry for call with
ICM error, retried answer is
different
On rare occasions when a call processing
error is encountered (e.g. DNIS not
configured), the caller will simply be
disconnected rather than hearing the critical
error message. This happens when the
message from the Application Server to the
Voice Browser is not received and the Voice
Browser retries.
CSCma06721 4
AS engine leaks memory when
there is no call traffic
The AppServer leaks around 20M in 3 months,
even when there is no call activity. There is no
workaround except to restart the AppServer if
the system available free memory in use gets
low
CSCma07496 4
If no GK configured and try to
transfer, should play critical
error
Theoretically, if the customer wants to use IP
transfer, they will have configured a gatekeeper
for the VB. However, if they forget and an IP
transfer request comes to the Voice Browser
from the ICM without a gatekeeper configured,
we hang up the caller without playing a critical
error message.
CSCma08681 4
callerId=NULL:shows
callerId=0 on IP transfer if
sending DNIS to GK
The caller ID appears to called party as "0"
instead of NULL when caller Id is either NULL
or Blocked and the Voice Browser is
configured to pass DNIS to H.323 Gatekeeper
for billing.
CSCma08711 4
MS on same machine with VB
takes a long time to fetch
media using host name
When media server and Voice Browser are on
the same machine it takes longer to fetch the
media than if the media server is on a separate
machine; if the media server URL is defined as
a host name rather than an IP address, then it
takes even longer. The increase in time is
dependent on the call load on the server. The
preferred mechanism for this environment is to
fetch the media files directly from the file
system using a base URL "file:" rather than
"http:".