help with two DID ranges on CME needed

Answered Question
Jul 3rd, 2007
User Badges:

Hi

I have a CME sytem with two E1's and two DID ranges

the first is

22223XXX and my extensions are 3XXX

i have a "dialplan-pattern 1 22223... extension-length 4" statement under telephony services and this works fine.

Now ihave added the 2nd E1 with range

33330XXX (this is a backup line but i want to be able to allow it to call my extensions 3XXX.I tried "dialplan-pattern 2 33330... extension-length 4 extension-pattern 3..." but this didnt work. Is this the correct way to handle incoming DID with multiple ranges? or is there a smarter way?

regards

colin

Correct Answer by Paolo Bevilacqua about 9 years 8 months ago

Hello,


please apply the translation-profile to the voice port and not to the dial-peer.

Or, make the "incoming called-number to be "^225280...$".

But I usually prefer do the translation at voice-port or trunkgroup level.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Paolo Bevilacqua Tue, 07/03/2007 - 01:24
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Yes, that would be the right command but I think it overlaps with the first and doesn't work.

Use a translation-profile instead.


voice-port x/y:15

translation-profile makedid


voice translation-profile makedid

translate incoming 100


voice translation-rule 100

rule 1 /^33330/ //


Hope this helps, please rate post if it does!

ReadersUK Tue, 07/03/2007 - 02:03
User Badges:

Hi

thanks for your reply, i played with translation profile but doesnt work.

I made the numbers up in my first post to make it easy to explain. But see my real config attached and test results. Any help appreciated.


Colin



Paolo Bevilacqua Tue, 07/03/2007 - 02:24
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hello,


please write the translation rule as per my example. Just change the made up number to the correct one. Do not mess with parenthesis, backslashes and match sets because thanks IOS, that is not necessary.

After, test the translation rule as you were doing in your attachment.


EDIT Woops I take it back. You have four-digits extensions so in fact the match set is necessary. Let me go over your config again and I will post below.

Paolo Bevilacqua Tue, 07/03/2007 - 02:40
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Here the correct rule:


voice translation-rule 3

rule 1 /^\(225280\)\(...\)/ /3\2/


Note it translates directly to the extension format.


Let us know!


Correct Answer
Paolo Bevilacqua Tue, 07/03/2007 - 04:44
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hello,


please apply the translation-profile to the voice port and not to the dial-peer.

Or, make the "incoming called-number to be "^225280...$".

But I usually prefer do the translation at voice-port or trunkgroup level.

ReadersUK Tue, 07/03/2007 - 04:58
User Badges:

Hi


Just before i read your reply i set

incoming called-number 225280... under dial peer and it worked.

it was set to just .

Thanks for your help, and i appreciate the advice


colin

Paolo Bevilacqua Tue, 07/03/2007 - 05:06
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Glad to know it worked, thanks for the nice rating and good luck!

Actions

This Discussion