Technical Manual

ManualsBrandsCisco ManualsIP phonesCisco IP Telephony Locale Installer for Cisco CallManager

Call Failure to Long Distance/Mobile Destination

Document ID: 18659

Contents

Introduction

Prerequisites

Requirements

Components Used

Conventions

Problem

Solutions

Solution 1: Cisco CallManager Configuration

Solution 2: IOS Configuration

Related Information

Introduction

This document remedies the situation where calls to most locations work, but calls to mobile (cell) phones or

international locations fail. These calls typically disconnect with "recovery on timer expiry" in the Cisco

IOS® Q.931 debugs.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco CallManager 3.x and 4.x.

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.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Problem

Mobile Telephony networks typically take longer to connect, since they have to locate the user. International

calls also typically experience delays in call establishment. This causes the timer T310 to expire.

This timer is initiated when Call Proceeding is received and stopped when Alert, Connect, Disc, or Progress is

received. It is easy to determine if this is the issue by looking at debugs and/or Cisco CallManager traces. In

order to do that, locate the Call Proceeding and verify that the Disconnect is sent n seconds later for every call

that fails. You can verify that n is the value set for the T310 timer. This value is typically 10 seconds.

Summary of content (7 pages)

PAGE 1
Call Failure to Long Distance/Mobile Destination Document ID: 18659 Contents Introduction Prerequisites Requirements Components Used Conventions Problem Solutions Solution 1: Cisco CallManager Configuration Solution 2: IOS Configuration Related Information Introduction This document remedies the situation where calls to most locations work, but calls to mobile (cell) phones or international locations fail. These calls typically disconnect with "recovery on timer expiry" in the Cisco IOS® Q.931 debugs.
PAGE 2
This is sample output from the debug isdn q931 command on an IOS gateway. Feb 4 Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb 11:10:40.396: ISDN Se3/0:15: TX −> SETUP pd = 8 callref = 0x000E 4 11:10:40.396: Bearer Capability i = 0x8090A3 4 11:10:40.396: Channel ID i = 0xA9838F 4 11:10:40.396: Display i = 'John', 0x20, 'Smith' 4 11:10:40.396: Calling Party Number i = 0x0080, '123456', Plan:Unknown, Type:Unknown 4 11:10:40.
PAGE 3
2. Select Cisco CallManager from the list on the left if you use Cisco CallManager 3.x or select Cisco CallManager from the Service drop−down box if you use Cisco CallManager 4.x. Cisco CallManager version 3.x Cisco CallManager version 4.
PAGE 4
3. On the Service Parameters Configuration page, look for T310. 4. Set the value of T310 Timer (msec) to the recommended value of 60000 msec.
PAGE 5
. Scroll to the top of the page and click Update. Solution 2: IOS Configuration IOS configuration is achieved through this interface command: Router(config−if)#isdn t310 You can check the setting using the show isdn timers command. Router#show isdn timers ISDN Serial2/0:15 Timers (dsl 0) Switchtype = primary−net5 ISDN Layer 2 values K = 7 outstanding I−frames N200 = 3 max number of retransmits T200 = 1.000 seconds T202 = 2.000 seconds T203 = 10.
PAGE 6
T308 T309 T310 T313 T316 = 4.000 seconds Disabled = 60.000 seconds = 4.000 seconds = 120.000 seconds Note: In Cisco CallManager version 3.x, due to operator implementations in some countries, you can be required to include a "sending complete indicator". This parameter is located in the Cisco CallManager parameters page. Note: By default, in Cisco CallManager version 4.