cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1253
Views
0
Helpful
9
Replies

Abbreviated internal dialing with CME

aoster
Level 1
Level 1

Hello all,

I am currently searching for an easy solution to allow CME users to dial each others seven digits

internal extensions as an abbreviated, shorter version using "*" as the first digit folloed by the last

three digits of their extension. Currently only the last three digits are different for all extensions so

I thought about a translation rule like:

voice translation-rule 1

rule 1 /^*\(...\)/ /100\1/

!

voice translation-profile abbrvDial

translate called 1

!

Is it possible on CME to use a dial-peer to translate the called number for internal calls ? If so how does

the dial-peer have to look like ?

Thank you for your kind help.

regards

Andreas

1 Accepted Solution

Accepted Solutions

Jonathan Schulenberg
Hall of Fame
Hall of Fame

To answer the original question: yes you can do that. You would associate the translation profile on the ephone-dn or ephone-dn-template. IMO it's easier to centralize this sort of thing onto a dn template.

ephone-dn tag

translation-profile {incoming | outgoing} name

Another option you can try is to use the dialplan-pattern command. This should allow you to get it done in a single command vs. adding a bunch of speed dials.

telephony-service (or voice register global)

dialplan-pattern 1 100.... extension-length 4 extension-pattern *.... no-reg

Please remember to rate helpful responses and identify helpful or correct answers.

View solution in original post

9 Replies 9

paolo bevilacqua
Hall of Fame
Hall of Fame

No translation rule is needed, you can configure these a global speed-dial, and then press softkey AbbrDial to call.

Or you can configure a secondary number the 3 digits extension and achieve the same.

Hello Paolo,

thank you for your fast response. The global speed-dial sounds good to me,can you

point me to some documentation or give a shot example how this is done ?

Thank you very much.

best regards

Andreas

Hello Paolo,

would something like that work ? :

abbrvList:

100,1000100,user1,,

101,1000100,user2,,

102,1000100,user3,,

103,1000100,user4,,

telephony-service

bulk-speed-dial list list-id flash:/abbrvList

bulk-speed-dial prefix prefix-code *

Thanks

Andreas

You can use that or if isn't t than many, the speed-dial entries under ephone-template.

Please remember to rate useful posts clicking on the stars below.

Jonathan Schulenberg
Hall of Fame
Hall of Fame

To answer the original question: yes you can do that. You would associate the translation profile on the ephone-dn or ephone-dn-template. IMO it's easier to centralize this sort of thing onto a dn template.

ephone-dn tag

translation-profile {incoming | outgoing} name

Another option you can try is to use the dialplan-pattern command. This should allow you to get it done in a single command vs. adding a bunch of speed dials.

telephony-service (or voice register global)

dialplan-pattern 1 100.... extension-length 4 extension-pattern *.... no-reg

Please remember to rate helpful responses and identify helpful or correct answers.

Hello Jonathan,

thank you very much for your help. I will implement the translation rule using the ephone-dn-template.

Obviously I have to ask the users to utilize another digit for abbreviation dialing ( mybe '9' )  as the *

is not allowed in translation rules.

Thank you very much.

best regards

Andreas

It is allowed, prefix with \.

Hello Paolo,

thank you very much for this info it actually works with:

voice translation-rule 1

rule 1 ^\*\(...\) /1000\1/

best regards

Andreas

aoster wrote:

Hello Paolo,

thank you very much for this info it actually works with:

voice translation-rule 1

rule 1 ^\*\(...\) /1000\1/

Actually that can be be written more concisely

rule 1 /^\*/ /1000/