cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
277
Views
3
Helpful
7
Replies

Cisco IP Phone initiate internal call after 10 seconds

salsyed01
Level 1
Level 1

Hello,

This issue just started happening with one user. when he Call from his extension to any other extension the call initiate after 10 to 12 seconds. 

 

Thank you, 

2 Accepted Solutions

Accepted Solutions

@Roger Kallberg The Dialed Number Analyzer will show what is the final selection for the call, but I think using the Route Plan Report (navigate to Call Routing > Route Plan Report) and looking for patterns that 'begin with' will be an easier way to find the culprit.

Maren 

View solution in original post

It appears to be another pattern match for the calls he made to other extensions. The CUCM is waiting for the inter-digit timing to expire before routing the calls to the extensions he dialed. This problematic user likely has a CSS with access to a partition that might have an alternative matching pattern.

The user’s issue might not occur if they dial the full number and press the call soft key.

DNA won’t be very helpful as it uses the full dialing number to show the route. The Route Plan report would be the best option to check for the alternative match causing the CUCM to wait for the inter-digit timeout to expire.

For example, if you have router patterns 234X and 2345X, and you use DNA with the dialed number 2345, it won’t show an alternative route even though there exists a pattern 2345X . Or if you mention the dialed number as 23, it will show as blocking the calls in the DNA result. Therefore, the Dial Plan report would be the best way to find the alternative route



Response Signature


View solution in original post

7 Replies 7

Sounds like a classic case of inter-digit timeout. It happens when there are more than one possible match to the dial plan search. If you search for what patterns are visible for the CSS you’ll very likely find that there is multiple match options. One handy tool for this is Dialed Number Analyser, or DNA in short.



Response Signature


@Roger Kallberg The Dialed Number Analyzer will show what is the final selection for the call, but I think using the Route Plan Report (navigate to Call Routing > Route Plan Report) and looking for patterns that 'begin with' will be an easier way to find the culprit.

Maren 

Thank you for your solution

It appears to be another pattern match for the calls he made to other extensions. The CUCM is waiting for the inter-digit timing to expire before routing the calls to the extensions he dialed. This problematic user likely has a CSS with access to a partition that might have an alternative matching pattern.

The user’s issue might not occur if they dial the full number and press the call soft key.

DNA won’t be very helpful as it uses the full dialing number to show the route. The Route Plan report would be the best option to check for the alternative match causing the CUCM to wait for the inter-digit timeout to expire.

For example, if you have router patterns 234X and 2345X, and you use DNA with the dialed number 2345, it won’t show an alternative route even though there exists a pattern 2345X . Or if you mention the dialed number as 23, it will show as blocking the calls in the DNA result. Therefore, the Dial Plan report would be the best way to find the alternative route



Response Signature


Thank you for your response 

there was multiple DN matches after deleting the unuse DN the calls start working fine.

some one configured that by mistake 

Glad you found the solution. However I think that you should have selected @Maren Mahoney answer as the solution to your question as she provided you the answer to this the first.



Response Signature


Thanks to every one