As stated ,that depends on your locale, in the US even, larger markets tend to require 11 digit dialing, some use 10 for in state and 11 for out of state, some just allow 10.
But anywhere in the states is always ‘closed dialing’ so if you are in a 10/11 locale, identify the smaller unique group
presumably the few area codes that require 10 and put them earlier in the dialstring as soon as it is uniquely matched, it will dial out without a # , if you have any overlap then you will need to wait for timeout on those area codes, the last string before international will be 1nxxnxxxxxx.
If you post your dialstring and your areacode then someone can go to Wikipedia and look up dialing rules for your state/area_code (or you could save yourself time and do it yourself )
I have the following NXXNXXXXXX which will prepend a 1 since the carrier requires it. Then I have toll free dial plans for example: 1877NXXXXXX since the carrier also requires that as well. That’s all I have
There are two things here, the dialstring on the phone , which is driven by wet-wear and the more methodical soft-ware approach of routes and trunks.
The wet-ware’s requirements is what are discussing here. So all that stuff in trunks and routes won’t apply until your phone side dialstring is “closed”, that is that there is one match arrived at as soon as the most significant numbers are successively matched uniquely against one of your patterns , if not unique, you will always need a # or a digit timeout
that’s interesting. I have yealink and can test in my lab. so do you have an example of adding the # or matching the dial plan to make this work? The screenshot above doesn’t seem to do that. On my phone it’s blank