This document describes and provides a solution for one reason why
Cisco Unified CallManager fails to load large Music on Hold (MOH) audio source
Cisco recommends that you have knowledge of Cisco Unified
The information in this document is based on Cisco Unifed
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
Active server pages set a limit for the amount of time that a given
page can execute. The rationale is that if a page takes too much time to
execute and return results, the user becomes frustrated and presses the Stop
button in the browser.
The default timeout in all versions of Internet Information Server
(IIS) is set to 90 seconds. However, in the case of a file upload, the page
must execute for the duration of the upload. If a user transfers information
over a slow line or transfers a large quantity of information, it is easy to
exceed this limit.
A scripting error happens when you insert a new large MOH audio source
file. The new MOH audio source file is successfully transcoded to ULAW.wav,
ALAW.wav, G729.wav and WB.wav but fails to insert (see arrow A in
Figure 1—Insert New MOH Audio Source
This error message displays (see Figure
Figure 2—Remote Scripting Error
Server returned HTTP response code: 500 for URL:
error message is identified as this
example output shows when you review the corresponding IIS error log file. The
log file is located in the c:\WINNT\System32\LogFiles\W3SVC1 directory:
2006-01-30 21:46:40 10.174.129.246 - 10.174.129.246 80 GET
500 0 Mozilla/4.0+(compatible;+MSIE+6.0;+Win32) -
The ScriptTimeout property specifies the
maximum amount of time that a script can run before it is terminated. The error
is generated when the processing time of the script exceeds the maximum value
that has been designated for the ScriptTimeout
property. It explains why this problem only happens when you insert large MOH
audio source files.
You can increase the time that is allowed to process ASP scripts for a
particular website. Change the metabase value in IIS in order to accomplish
Complete these steps:
Select Start > Programs > Administrative Tools >
Internet Services Manager to open Internet Services
Expand the tree and Default Web Site.
Right-click CCMAdmin under Default Web
Click the Home Directory tab.
Click Configuration located under Application
Click the App Options tab.
The Application Configuration window displays (see
Figure 3—Application Configuration
Increase the ASP Script Timeout value to a number high enough to
prevent script timeouts.
In this case, the value is increased to 180 seconds (see arrow A
in Figure 3) in order to load large MOH source files
If you receive an error that states the file is too
large when you try to upload any audio source file that is
longer than 8 seconds, it might be due to the browser you are using. The
official supported browsers for Cisco Unified CallManager Administration
to Cisco CallManager Administration for more information.
When you attempt to upload the MOH audio source file, the process fails
with this error:
Unknown CM_Media_PayloadType 262
This error occurs when the wav file is
not in the required format. Audio files must be in one of these formats:
G.711 A-law or mu-law
G.729 Annex A
Also, make sure that it is in 8000 MHz and 16-bit sampling.
Refer to Cisco Bug ID
(registered customers only)
for more information.