Mitel 3300 ARS without an access code (Direct to ARS)

[ralph]

but I dictate the internal dial plan.

When I was designing I always tried to dictate the internal dial plan.   The though being:  "That's why they call me the designer, because I know what will work best."   Didn't always fly.

Ralph

[Mattmayn]

Ralph, I'm not a big fan of not using an access digit because you can lose too many possible extension ranges on a large system. 1000s are out and here locally I would need to stay away from anything that had 404, 706, 770, 678 and 978 because they are all local area codes. I guess I could use a 2, 3, 5 or 8000 series for extensions.

[ralph]

In the US it depends on what the local dialing plan is.   For example, in some LATAs you need to dial 1+area code + number.
In others you can just dial the number.   For example, some areas would make you dial "1-555-666-1234"  other areas you only need to dial "666-1234".   In those areas the "1+<area code>" is reserved for LD.

In the case where you are forced to dial the 1+<area code> then you would use the '1' as your ARS access code.  The digit mod wouldn't delete the '1' and it would simulate direct to ARS.

Ralph

[MrVOIP]

You sometimes run in to customers who are stuck on this.  The approach we took in a very similar situation was as follows:

• All internal extension numbers were in the 1000 range.  (In a small system you could use the 100 range)
  
• Numbers 2 through 9 and 0 (for international calls) were ARS leading digits  (Second Dial Tone set to "NO")
• All feature codes started with a * or #

This worked great for this particular customer.  I suppose if a 1+ prefix was required by the carrier it could be inserted in the digit modification plan for a particular route.  In this case the carrier accepted 10 digits for all calls.

MV