I vaguely recall that you can respond address incomplete in the dialplan too, but you want to keep this to a minimum as it makes a dialplan lookup with every keypress after it starts matching the regex in mod_skinny. I generally like to make extensions that don't ever overlap local dialing patterns so you never have this issue. For example, in the US, 1 is the country code, and 0 is used for some other special dialing. Because of this I never have extensions start with 0 or 1. Also avoid extensions that overlap with 3 digit special numbers, such as an extension on 9113 is not a good idea. When doing 4 digit extensions, i try to use 2xxx,3xxx,5xxx,6xxx,7xxx or 8xxx ranges. Mike On Mar 20, 2013, at 1:16 PM, Nathan Neulinger <nneul@mst.edu> wrote:

Looking at being able to handle a variable length dial pattern with a cisco phone (for international numbers).

With a SIP phone, it's easy since the digits don't get sent incrementally, but with the SCCP phones, it seems like I get the digits one at a time, even if I dial them all and then lift the handset or press new call. This makes it so that a longer dial pattern will never match if a shorter one does.

If I change the 'continue' in the skinny-wait action to false, or remove it - it never stops waiting for another digit.

Worst case scenario - I could eliminate support for variable length dialing, and require a "#" at the end for international calls from the skinny phones, but is there a better way to accomplish this?