Translation Rules DID

Answered Question
Jul 22nd, 2010

Hello. I am very thankful to have you reading my post and thanks beforehand to everyone helping around. You are doing a great job.

I am currently configuring a CUCM cluster.

Problem is as follows.

We have a standalone cluster with a Publisher and Subscriber

We have a PRI line with head-end number 2046800 configured on an MGCP gateway (2821 router)
The DID range for this line is 204-6100 to 204-6899.

Extensions to each IP phone have been assigned in the format 6yxx, where y is a number between 1 and 8, and x can be anywhere from 0 to 9.

Thus all internal extensions are 4 digits long and corresponding external number is the same extension prepended with 204; e.g:
extension 6100 (internal) maps to 204-6100 (external)
This setup is functionning normally as should and all users are able dial in and out using their DIDs.

Eg: If I call 204-6123, extension 6123 will ring inside  and;
      if extension 6123 calls me on my landline, the caller-id of 203-6123 will appear on my phone.

  
   The problem is as follows:
    The management has decided that it will keep only the last 3 digits as extension number:
    Hence the leading "6" will be opted out for all extensions.
   
    All new extensions will be within the range 100 to 899
   
      I have already tried creating extension number 101 and assigned it to a phone to test.
  
      Problem(a): The phone loses its DID, that is, outgoing calls proceed with the Head-number which is 204-6800, incoming and 204-6101 gets a "no answer"
   on the caller side.
  
As solution, I have tried

       (1) to create a transformation pattern from 101 to 6101. By this, it was expected that calls to 204-6101 from an external
        landline would ring on extension 101.
       
       This was not the case. The problem remains the same as described above in problem(a)

I know this might be a very small issue and I am missing something somewhere. The reason being I am really new to CUCM and weak in translation stuff.

Thanks again.
      
      
      
    Can you suggest a solution please?
     

I have this problem too.
0 votes
Correct Answer by rynard.coetzee about 6 years 4 months ago

Under the Route Pattern on CUCM ,under the Calling Party Transformations ,check the box that says use calling Party`s External Phone number Mask ,just make sure that yoy still have the External Phone number mask configured under the Line config on the Device Profile ,also have you spoken to the Telco to make sure they are not masking the number on their side ?

Correct Answer by rynard.coetzee about 6 years 4 months ago

No worries glad to help ,you might just want to change the Translation Pattern to include the whole number range ,so for instance if your number range is 4000-4100 i would make the TP 4XXX and make the Called Number Transform XXX ,this should then change the 4 digit number into a 3 digit number ,using the last 3 digits

Correct Answer by rynard.coetzee about 6 years 4 months ago

Sure ,the Translation pattern will be the number that the Telco sends to you ,eg 7101 ,then at the bottom of the Translation Pattern Page make the "Called Party Transform Mask" 101

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Sadaseeven Saminaden Thu, 07/22/2010 - 05:04

Thanks for the answer, Can you guide me on the values to be filled in the translation pattern.

fyi: Callmanager version is 7.1.3.

Correct Answer
rynard.coetzee Thu, 07/22/2010 - 05:11

Sure ,the Translation pattern will be the number that the Telco sends to you ,eg 7101 ,then at the bottom of the Translation Pattern Page make the "Called Party Transform Mask" 101

Sadaseeven Saminaden Fri, 07/23/2010 - 02:23

Hello. I have created this translation pattern on the Callmanager but I continue to get "unknown number.

Were there any other values to be configured besides the 2 that you suggested?

Sadaseeven Saminaden Fri, 07/23/2010 - 02:28

Hi again rynard.coetzee. I made a mistake. The translation you gave works very fine indeed,

Only I forgot to include CSS.

Now it is okay. Calls are being translated inside.

I have to verify for DoD also.

Thank you very much.

High five for you

Correct Answer
rynard.coetzee Fri, 07/23/2010 - 02:34

No worries glad to help ,you might just want to change the Translation Pattern to include the whole number range ,so for instance if your number range is 4000-4100 i would make the TP 4XXX and make the Called Number Transform XXX ,this should then change the 4 digit number into a 3 digit number ,using the last 3 digits

Sadaseeven Saminaden Fri, 07/23/2010 - 02:38

Hi again rynard.coetzee.

Hope you are doing fine.

I am okay for the incoming calls. they get translated to the right DN.

But when I try calling from the same DN(phone) , I go out through the Head number.

Can you kindly suggest a way to set that right?

Thanks

rynard.coetzee Fri, 07/23/2010 - 03:00

On your Device Profile under the Line Config ,do you have a External Number

Mask configured ?

rynard.coetzee Fri, 07/23/2010 - 04:11

Ok ,you need to configure a mask or change the dialling number under your outgoing Route Pattern to your Telco. If you do it under the device profile just make the External number mask something like 2146XXX depending on what your number is ,here in South Africa we use 10 digit numbers in the format of XXX(Area Code)XXXXXXX(7 digit number) so i would have my external mask configured as 0115757XXX if i was using 3 digit extensions ,this will take the 3 digit extension and prepend the 0115757 to it before sending it out.

Sadaseeven Saminaden Mon, 07/26/2010 - 00:07

Hello rynard.coetzee . Hope you are doing well.

Thank you for the info last time, I have tried your suggestion of putting the mask in the line config for the phone.

However I am still going out with the Head-end number.

Please see the screenshot below:

Also, please find the line config below:

After configuring the mask I have run a "debug isdn q931" on the voice gateway. Below is the output according to which, the Headnumber of 2046800 is still being sent. Any ideas, please suggest.

TBS-SRV01-GW2811-01#debug isdn q931
debug isdn q931 is              ON.
TBS-SRV01-GW2811-01#
000172: Jul 26 07:05:30.738: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0xF4D5
        Cause i = 0x8290 - Normal call clearing
000173: Jul 26 07:05:31.262: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x74D5
000174: Jul 26 07:05:31.302: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0xF4D5
000175: Jul 26 07:05:32.690: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x8187
        Cause i = 0x8090 - Normal call clearing
        Progress Ind i = 0x8288 - In-band info or appropriate now available
000176: Jul 26 07:05:32.734: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x0187
000177: Jul 26 07:05:32.930: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8187
000178: Jul 26 07:05:46.353: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0188
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
        Calling Party Number i = 0x0081, '846'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0x80, '2046846'
                Plan:Unknown, Type:Unknown
000179: Jul 26 07:05:46.861: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8188
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
000180: Jul 26 07:05:47.149: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x74D6
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98392
                Exclusive, Channel 18
        Calling Party Number i = 0x2183, '2046800'
                Plan:ISDN, Type:National
        Called Party Number i = 0x81, '6846'
                Plan:ISDN, Type:Unknown

karamalomari Mon, 07/26/2010 - 01:07

Dear,

Can you let me know whats ur DID number and once you recive the call on your router what are digits that are send from the ISP to you.

Then you can create the translation rule based on the incoming digits.

Also can you make a call from 101 to outside and what number are you getting on the other side when you make an outgoing call from 101?

Sadaseeven Saminaden Mon, 07/26/2010 - 01:19

Hello karamalomari. And thanks for helping out.

My DID Head-end number is 2046800

The DID range is from 204-6100 to 204-6899

The ISP sends in the last 4 digits.

Right now all extensions are 4 digits long and everything is working perfectly. (6100 to 6899 consistent to the DID range which is 204-6100 to 204-6899)

Management has decided to stick to 3-digit extensions. So the leading 6 will be dropped in extensions and all extensions will become 100 to 899.

As our friend kindly suggested earlier, I created a translation pattern that maps 684X to 84X so that, for example, any call to 2046846 will be mapped to extension 846.(At this stage, since the site is in production, I have taken  extension 6840 to 849 for testing and my own extension is 846)

Calls are being translated inside. So when I call 2046846, the calls effectively gets connected to extension 846.

But the problem is when I call an outside number, say 9510502, the receiver will find that "2046800", the head-end number, calling, instead of the desired 2046846.

Please drop a thought on this..

thank you again

rynard.coetzee Mon, 07/26/2010 - 01:22

Is your Telco allowing CLI ? Also use Dialed Number Analyzer and check if there are perhaps any number translations happening anywhere else on the CUCM

karamalomari Mon, 07/26/2010 - 01:28

ok you need to create a translation rule for the outgoing calls as the following and then apply it on the out going dial peer pots as the following:

voice translation-rule 1
rule 1 /8/ /2046/
!
!
voice translation-profile out
translate called 1
!

dial-peer voice xxx pots
description "outgoing calls to E1 PRI"
  translation-profile outgoing out

!

hope this will work

Sadaseeven Saminaden Mon, 07/26/2010 - 01:40

Hello again karamalomari and thank you for nice suggestions.

On the Voice gateway I have two dial-peers.

Do I have to apply it to both?

Here are the config

dial-peer voice 1 pots
service mgcpapp
direct-inward-dial
port 0/1/0
forward-digits all
!
dial-peer voice 3 pots
service mgcpapp
incoming called-number .
direct-inward-dial
forward-digits all

Also, I have tried the cofiguration you gave on both dial-peers alternately, without any success.

For info, I have a CUCM Cluster with 7.1.3 Publisher and Subscriber and a 2811 Voice gateway to which the PRI line is connected.

Also, where can I obtain the Dialer Analyzer you were referring to?

rynard.coetzee Mon, 07/26/2010 - 02:12

MGCP gateway so don`t need dial-peers unless it is setup for SRST ,go to Serviceablity page ,then Tools and then Dialed Number Analyzer.

Sadaseeven Saminaden Mon, 07/26/2010 - 02:42

I Hello Rynard and karamalomari

I have done an analysis for my phone via the Dialed Number analyser.

I have analyzed testing of external phone number 9510502 through my internal extension which is 846.

Please find attached the result from the analysis..

Also I would like you thank you for your kind collaboration

Regards

Correct Answer
rynard.coetzee Mon, 07/26/2010 - 02:49

Under the Route Pattern on CUCM ,under the Calling Party Transformations ,check the box that says use calling Party`s External Phone number Mask ,just make sure that yoy still have the External Phone number mask configured under the Line config on the Device Profile ,also have you spoken to the Telco to make sure they are not masking the number on their side ?

Actions

This Discussion

Related Content