dialplan-pattern 1 extension-length vs. Translation
Can someone explain what is best commend to use and where you would use each one.
Example 1- A telco sends you 6 digits but your DN`s are only 4
Example 2 - Your DN`s are registered as 6 digits - all digits from the telco but you wish the users to dial only 4 digits between each other but maintain the 6 digits the phones are registered with
Also where or would use the num-exp commends
If you use the above how does effct calls - with Translation udner call-manager-fallback it only works in SRST mode but if you use the dialplan-pattern example does it effect ever call - what happens with dial-peers ?
Re: dialplan-pattern 1 extension-length vs. Translation
The dialplan-pattern command creates a global prefix that you can use to expand the abbreviated extension numbers (automatically obtained from the Cisco IP Phones) to expand into fully qualified E.164 numbers. The dialplan-pattern command is also required to register the Cisco IP Phone lines with a gatekeeper. The extension-length keyword enables the system to convert a full E.164 telephone number back to an extension number for the purposes of caller ID display, received, and missed call lists.
Use the num-exp global configuration command to define how to expand a particular set of numbers (for example, an extension number) into a particular destination pattern. With this command, you can map specific extensions and expanded numbers together by explicitly defining each number, or you can define extensions and expanded numbers using variables. You can also use this command to convert seven-digit numbers to numbers containing less than seven digits. Use a period (.) as a variable or wild card, representing a single number.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...