Transfer delay issue

[Lance Cutler]

We recently added a site to our system.  CUCM 7.1.3, UCCE 7 CVP 7 CUPS 7 and UC 7.  This is not tied to UCCE/CVP and goes to CUCM directly from 2811 via SIP.  When a call is answered and transferred to extensions all works well except to one extension.    When calls are transferred to 74455 there is a 20 sec pause before it rings the phone with 74455.  The DN is unique (74455), no route patterns even close to it.  It can transfer to other lines fine and DID calls work with the line as well.

[Jonathan Schulenberg]

Just to be sure I am following you correctly in this call flow:

• Call arrives on gateway which immediately sends a SIP INVITE to CUCM.
• CUCM immediatly routes the call to the appropriate DN which is then answered.
• The user then goes to transfer the call to 74455.
• A 20 second delay is experienced after providing the fifth digit before ringback is heard.

If so, a few questions:

1. What is 74455? Another DN, a translation pattern, CTI Port, etc?
   1. If it is a route pattern that exits CUCM, does the outgoing SETUP/INVITE/etc sent before or after the 20 seconds? (This answer helps us focus inside or outside of CUCM).
2. What is the value of your T302 timer (Service Parameters)? Remember there is one per-protocol.
3. Have you checked under the Route Plan Report for something higher-up? Perhaps begins with 74 or 744.

[Lance Cutler]

1. What is 74455? Another DN on a phone in same office
   
   1. If  it is a route pattern that exits CUCM, does the outgoing  SETUP/INVITE/etc sent before or after the 20 seconds? (This answer helps  us focus inside or outside of CUCM).  N/a
2. What is the value of your T302 timer (Service Parameters)? Remember there is one per-protocol.  Default 15000
3. Have you checked under the Route Plan Report for something higher-up? Perhaps begins with 74 or 744  I only see the phones with dn 74440 - 74459.  No other patterns starting with 744

[Jonathan Schulenberg]

If it's another DN then we really only have one option to see what's going on here. I'm going to give you the instructions; however, I recommend doing this with the assistance of TAC for two reasons:

1. This generates an enormous amount of log output. It will take some time to sort through.
2. This can severly degrade the system performance or even crash the node.

The Dialed Number Analizer will show us the end result; however, it won't show us the digit-by-digit evaluations including what other potential matches existed at each position in the dialed string. You can perform a Dialing Forest Dump to see this though. The SDI traces for the CallManager process will show the analysis after every digit pressed including every matched pattern in the database. You should be able to spot whatever's overlapping this way.

Performing a Dialing Forest Dump

1. Log into UCM Administration and choose System > Service Parameters.
2. Select a node and the Cisco CallManager service.
3. Click the Advanced button.
4. Change the Dialing Forest Dump Enabled parameter to true. Read the warning carefully!
5. On a SCCP phone press **##*2; this enables the dump for this phone.  You will hear the annunciator reorder. Hang up.
6. Now dial parttern you want to dump.
7. Dial **##*4 to disable dumps from that phone.
8. Pull the CallManager SDI logs from that node. Review and/or attach to this thread and we'll try to look for you. Just note the time you made the call.
9. CRITICAL: Change the service parameter back to false!