CUCM always does the analysis digit by digit, you can open a CUCM trace and look at this.

The behavior is different because the phone is on-hook and then you press dial button. CUCM then considers you have dialed all the digits and does not need to wait for anything else (same way as you going offhook and pressing #)

If you want to understand how it works look CUCM traces.

HTH

java

if this helps, please rate

thanks for everyone

but if I am sending "2222" and CUCM does digit by digit, it means phone 2 will never ring

but when I press 2222 then press dial, the phone 2 ring, so it can not explain CUCM is doing digit by digit

any update?

There already 3 explanations, what you say does not makes sense unless you're calling translation patterns or route patterns with urgent priority checked, and you said this were phones, right?

If you have 222 and 2222 all that will happen is there will be IDT when you dial 222 if you're offhook.

Simply an overlapping will happen, read the dial plan section from SRND to understand overlapping and it's effects.

When i was at TAC you have no idea how all of us hated the "any updates?" comments

HTH

java

if this helps, please rate

So, assuming that the urgent priority is not checked on the route pattern, there is a difference between dialing the number, then pressing dial versus picking up the handset then dialing.

Specifically, when pressing the dial button, there is no need to wait for any inter-digit timeout. Therefore, it can be thought of as going out as one block, however it appears in the trace logs. The behavior is what is important.

Java,

I can not agree with you.

your explanation did not explain my situation even I knew "any update" may not the prefer language as your expectation

there is no route-pattern or xlate patten at all, only 3 DNs on the system

222

2222

333

I want to 100% understand how CUCM doing digit analysis while I am dialing "2222" ONHOOK compare OFFHOOK

use OFFHOOK method, 2222 can never be reached because CUCM doing digit by digit and as long as after 3*2s, 222 ring

use ONHOOK method, 2222 can be reached, so how CUCM doing digit analysis in this case?

looking for your reply

thanks again

From the CUCM SRND i instructed you to read:

Dial Plan

Avoiding Overlap of Extension Dialing

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/dialplan.html#wp1043611

-There cannot be overlapping strings of different length. For example, a system with extensions 1000 and 10000 would force users to wait for the interdigit timeout when they dial 1000.

The behavior is explained above, and backs what i've told you.

If you really want to understand gather CUCM traces and look at them.

DA is ALWAYS done digit by digit with SCCP endpoints, only SIP endpoints with dial rules on it can send them enblock.

When you dial onhook cucm detects you never went offhook, does not provide dial tone. Therefore it already knows that when you press dial is because you've already dialed all the digits you want and immediately sends the call, the same would happen if you go offhook and press #.

HTH

java

if this helps, please rate

Thanks

I don't think I am going to design two DNs like 222 and 2222

based what I read from SRND, 2222 should never be reached but it does, so a little confused how CUCM performing digit analysis.

so correct me if wrong, with ONHOOK method, CUCM would ignore the digit by digit logic, furthermore, it will ignore any urgent priorty xlate pattern/route-pattern as well. otherwise, 2222 can not be reached

one example could be

I do have 91.12222222 translation pattern (pre-dot,urgent priorirty default on CUCM6)and 911 route-pattern, with ONHOOK dialing, I should be able to dial 9112222222 without any problem, right?

thanks agian

No, read again the SRND. Your understanding is wrong.

java

regardless urgent priority or not, with ONHOOK method, I can reach both 2222 and 9112222222 (911 route pattern urgent priority checked)

so either CUCM break the digit by digit analysis rule or CUCM treat "2222" "9112222222" as single digit