Cisco Cisco IOS Software Release 12.4(4)T

Page de 38
 
36
Cisco V.150.1 Minimum Essential Requirements Configuration Guide
  Symptoms and Possible Solutions for Cisco V.150.1 MER
Table 5
Common Issues and Possible Solutions
Symptom
Possible Solution
STE calls fail to secure
Wrong hardware such as gateway, VICs, or DSPs. Confirm that you 
have the correct configuration of DSPs (5510 family of 
DSPs—PVDMs included).
MGCP gateway is needed for trunks, and the SCCP gateway is needed 
for line-side devices. Both need to be configured on the Cisco Unified 
Communications Manager individually, but can run on same the 
physical gateway. The Cisco Unified Communications Manager 
supports MGCP version 0.1
Wrong Cisco IOS software image. Verify that the “adventerprisek9” 
image is used for trunks. 
Legacy V.150.1 features are available only in Cisco IOS 
Release 12.4(4)T adventerprisek9 T-images and later releases. 
Cisco V.150.1 MER features are available beginning in Cisco IOS 
Release 15.1(4)M adventerprise9 image. Verify that the gateway is 
running a supported Cisco IOS image.
Cisco IOS STE/V.150.1 configuration commands are not present.
Trunk-side/off-net calls fail 
to secure
The MGCP mgcp package-capability mdste-package command is 
missing from the gateway configuration.
Verify that the MGCP trunk is configured correctly on the Cisco 
Unified Communications Manager. Verify that Enable V.150.1 subset 
is checked.
Delay, jitter, loss
Verify the network topology. Verify Quality of Service (QoS) settings. 
If using high-delay or error-prone links (for example, satellite 
connections), try configuring optional modem relay parameters such as 
SSE redundancy.
Dropped secure calls
T1 clocking errors can cause intermittent and dropped secure calls. 
Verify that the clocking on the T1 is accurate and correct. 
On-net STE calls 
complete/secure, but off-net 
calls fail to secure
Unsupported PSTN gateway hardware or software. 
Missing PSTN gateway in the MGCP Cisco IOS/Cisco Unified 
Communications Manager configuration.
PSTN gateway circuit errors (slips).
Started to configure 
trunk-side V.150.1, but all 
trunk-side calls fail
Mismatched MGCP PSTN gateway configuration.
Make sure the Enable V.150.1 subset checkbox is chosen in the 
Cisco Unified Communications Manager and the package-capability 
mdste-package 
command is configured for calls to proceed. If one 
piece is configured but the other is not, all calls across the 
MGCP-controlled trunk will fail, not just STE calls.