First thing - does this happen on transfers only or on all calls? I expect on all calls as I can't think of a difference with transfers, though if you are going through a gateway it could add some things to look at.
Can you give some details? Where is the transfer to - internal IP phone or out a gateway? For outbound calls, what protocol are you using for the gateway (H323, MGCP)? Have you looked at the route plan report (show in file) to see if there are any overlapping ranges?
Bottom line - it sounds like you are encountering an inter-digit timeout, meaning that there is more than one option for routing the digits that are dialed. The timeout determines when you are done dialing. The timeout is administrable in CallManager, but you really want to find out why there are overlapping dial strings (patterns) in your dial plan in the first place.
You have overlapping dial strings. When you dial 2 + 7 digits the CallManager doesn't know if you are going to continue dialing for a 10 digit call (based on your 2xxxxxxxxx pattern) or if you are done. So, it invokes the T302 timer which is what is causing you delay. Same with every other first digit. The route patterns you have may also impact internal numbers - extensions, pickup groups, etc. - based on your ordering of partitions in Calling Search Spaces. This is why an access code (i.e. 9 in the states) is usually used to indicate an outside call, and is not used to start any other extensions.
I don't know exactly what the dialing rules are in your area. One over-all recommendation I would make is to define an access code (i.e. 9) for all outside calls. Next would be to either use Route Filters to define what a local verses service verses long distance verses international call really is, or create similar rules specifically in your patterns (effectively re-creating what has been done in route filters for the @ wildcard). Not knowing what your requirements are (i.e. users absolutely refuse to dial a 1 for long distance calls) I'm not sure what to say. If dialing an access code of 9 and a 1 for LD is OK then I'd say you can get by with patterns of 9[2-9]xxxxxx for local, 91xxxxxxxxxx for LD, 9911 with urgent priority checked for emergency. You'll also need to address 411 if you have it, etc. It doesn't appear as though you're allowing international or operator calls at all. If you want to let people keep dialing without a 1 for LD calls, then the patterns change and it becomes more difficult to avoid time-outs.
Note that since you are using an H323 gateway that there could be time-outs involved there if your dial-peers are not specific. the access code (9) will help greatly there as well.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...