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 22
Identifier Comp. Severity Headline Release-note Enclosure
CSCea03950 GW 3
FetchTimeout not
working
Symptom: The HTTP response timeout does
not timeout as specified in vxml script.
Workaround: None.
CSCma21753 ICM 3
Router never
disconnects on just
Release Node after
Network Transfer
Symptom: Router is not sending a Release
message to any routing client or VRU if the
script after network Transfer just immediately
Released the call without even running a "Run
VRU Script".
Conditions: The attempt to network Transfer
will never succeed and call will never be
released. Router will however report that route
request is complete.
Workaround: None.
CSCma24039 ICM 3
Agent app shows
call after ring no
answer via ISN
network transfer
Symptom: Call is ringing at agent A but cannot
answer. "Call identifier is invalid"
Condition: ISN 2.0 IPCC 5.0 Ring No Answer
had been triggered. The call is with agent B.
Workaround: Set the script node to re-query In
the Agent Desk Setting: Set the Ring No
Answer timeout = ISN RNA Timeout - 2
(Suggested) Set the Ring No Answer Dialed
Number = <None>
CSCea60562 IP Phone 3
Choppy or missing
voice when using
multiple SSRCs in
a call
Symptom: Call originating from a 7960 IP
Phone and terminating on an IOS Voice
Gateway doing both TTS and playing
prerecorded prompts does not hear all IVR
prompts or hears some very crackly prompts.
Con
ditions: This occurs when the call originates
from a 7960 and terminates on an IOS Voice
Gateway performing IVR treatment that
includes both TTS prompts and pre-recorded
prompts (.wav files). Very often the caller will
mot hear the .wav files that play after the TTS
prompt. Gateway logs clearly show the RTP
packets leaving the gateway with proper
sequence numbers and timestamps.
Suspected to be related to the fact that multiple
SSRC's are included in the call.
Workaround: None
CSCma23310 ICM 5
ICM shouldn’t
return
DIALOG_FAIL/UNS
PEC for ReqInstr
with abandoned call
When using a type 3/7 network VRU, if a call
is abandoned immediately after/during an
explicit/implicit SendToVRU node, an error
message about UNSPECIFIED_FAILURE from
ICM is logged by ISN.