Status Acoustics 2 User Manual
Internet Service Node (ISN) 2.0
Release Notes
Page 5
•
Automated codec negotiation between ingress and egress gateway/endpoint
during IP Transfer.
during IP Transfer.
•
Metrics have been added to the Application Server to measure it’s internal
response time and the ICM response time. Metrics have been added to the
ISN Voice Browser to measure call arrival and transfer rates (cps). The
transfer latency metrics in the ISN Voice Browser logs have been separated
into the time to alerting and time to off-hook.
response time and the ICM response time. Metrics have been added to the
ISN Voice Browser to measure call arrival and transfer rates (cps). The
transfer latency metrics in the ISN Voice Browser logs have been separated
into the time to alerting and time to off-hook.
•
The RNA timer for transferred calls is user configurable at the ISN Voice
Browser.
Browser.
•
The Voice Browser and the Application Server may now be configured to not
connect to SDDSN server.
connect to SDDSN server.
•
The call will be restarted if certain egress endpoints fail. Specifically, when a
transfer has succeeded, and the egress is a Voice Gateway that fails, the call
will be restarted rather than disconnecting the caller.
transfer has succeeded, and the egress is a Voice Gateway that fails, the call
will be restarted rather than disconnecting the caller.
•
The Voice Browser can now be configured to pass either the Dialed Number
(DNIS) or Calling Line Identification (CLI) in the Calling Party Number
parameter of the Setup message during IP Transfer.
(DNIS) or Calling Line Identification (CLI) in the Calling Party Number
parameter of the Setup message during IP Transfer.
•
Support for ringback and other tones (like tone on hold) have been added
during Supplementary services (like Transfer, Hold, and Conference) invoked
at Cisco CallManager.
during Supplementary services (like Transfer, Hold, and Conference) invoked
at Cisco CallManager.
1.2. Changes from Release 1.0.1
•
The default locale strings changed from en_US to en-us and from en_GB to
en-gb to be compatible with current industry nomenclature. This affects the
location for the media server system files used for built-in types such as
numbers and currencies. The actual grammar definitions will work for both
formats (en_US as well as en-us).
en-gb to be compatible with current industry nomenclature. This affects the
location for the media server system files used for built-in types such as
numbers and currencies. The actual grammar definitions will work for both
formats (en_US as well as en-us).
•
If upgrading from a system where the locale default is used, move the existing
media server system files (e.g., 1.wav) from …/en_US/… directory to …/en-
us… directory.
media server system files (e.g., 1.wav) from …/en_US/… directory to …/en-
us… directory.
If the locale is not defaulted, there are three approaches:
Option 1: Change the scripts to use en-us rather than en_US and move
the existing media server system files (e.g., 1.wav) from …/en_US/…
directory to …/en-us… directory.
the existing media server system files (e.g., 1.wav) from …/en_US/…
directory to …/en-us… directory.
Option 2: Move the new prompt files (installed as part of the upgrade,
e.g., USD_dollar.wav) from …/en-us/… directory to …/en_US…
directory. This is the easiest approach, but will continue to be an issue with
each release.
e.g., USD_dollar.wav) from …/en-us/… directory to …/en_US…
directory. This is the easiest approach, but will continue to be an issue with
each release.