08-04-2010 05:25 PM - edited 03-16-2019 12:05 AM
Hi
I have a CME 7.1, who is going to replace and old system. The end user is not using any prefix. The extension are 11XX.
I notice that some extension match with the fisrt 4 digits of some PSTN numbers (local calls).
e.g. extension 1115 mach with PSTN local number 1115XXXX
If I set the secondary dial tone I can solve the problem but I would like to know if there is other option so that the end user can dial without any prefix
Regards
Solved! Go to Solution.
08-05-2010 08:01 AM
Filliberto,
You have what is called an overlapping dial-plan. I would recommend you pay attention to your dialplan design so that you don't have an overlapping plan, and don't have to worry about thinks like call loops.
This is why most people dial a trunk access code to acces the PSTN. If you have your users dial a 9 in front of the PSTN number, you won't have overlap.
Make your POTS peers look like this, which will match 91115XXX and strip the 9 out:
dial-peer voice 1 pots
destination-pattern 91115....
prefix 1115
The long answer is when you configure CME DNs, it adds an internal dial-peer with
You can verify outbound dial-peer matching order with 'sh dialplan number
Workarounds where you don't have to dial a trunk access code are:
1) Change your internal extensions so they don't start with the numbers that your POTS peers start with.
or
2) Configure 'preference 2' under all of your CME DNs.
3) Change the dial-peer huntiong algorithm with 'dial-peer hunt 1'. I wouldn't recommend this unless you understand dial-peer matching fundamentals very well.
-Steve
08-05-2010 08:01 AM
Filliberto,
You have what is called an overlapping dial-plan. I would recommend you pay attention to your dialplan design so that you don't have an overlapping plan, and don't have to worry about thinks like call loops.
This is why most people dial a trunk access code to acces the PSTN. If you have your users dial a 9 in front of the PSTN number, you won't have overlap.
Make your POTS peers look like this, which will match 91115XXX and strip the 9 out:
dial-peer voice 1 pots
destination-pattern 91115....
prefix 1115
The long answer is when you configure CME DNs, it adds an internal dial-peer with
You can verify outbound dial-peer matching order with 'sh dialplan number
Workarounds where you don't have to dial a trunk access code are:
1) Change your internal extensions so they don't start with the numbers that your POTS peers start with.
or
2) Configure 'preference 2' under all of your CME DNs.
3) Change the dial-peer huntiong algorithm with 'dial-peer hunt 1'. I wouldn't recommend this unless you understand dial-peer matching fundamentals very well.
-Steve
08-05-2010 11:19 AM
2) Configure 'preference 2' under all of your CME DNs.
That is not going to help. Since DP matching is done digit by digits, as soon a match is reached (perfect overlap), extnesion will be selected no matter the preference.
You could reconfigure the overlapping extension with final T so interdigit timeout determines the match, bt it is an ugly and anifunctional solution.
Just avoid overlapping extensions.
08-05-2010 08:02 PM
Hi bevilacqua,
thanks for your comments
regards
08-05-2010 07:58 PM
Steve
Thanks for your clear explanation
regards
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide