cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
877
Views
0
Helpful
4
Replies

Translation Pattern CSS for CLIR (not solved, just pushed wrong button)

paulheilmeier
Level 1
Level 1

Hi guys,

i'm little bit confused about TPs.

I created some TPs for CLIR, cause i have a phone group, which should do CLIR to external/internal calls.

The TPs has only CLIR enabled and the configured CSS includes the partitions of the Route Patterns.

The Phone/Line CSS didn't includes the Partitions of the Route Patterns only the Partitions of the TP.

Config:

Partition:

1. PSTN_LOCAL_PT

2. PSTN_LOCAL_CLIR_PT

3. IP_PHONES_PT

CSS:

1. TRANSLATION_CLIR_CSS

|......... PSTN_LOCAL_CLIR_PT

2. PSTN_LOCAL_CSS

|......... PSTN_LOCAL_PT

|......... IP_PHONES_PT

TP:

0.X!

Partiton: PSTN_LOCAL_CLIR_PT

CSS: PSTN_LOCAL_CSS

CLIR enabled

Route Pattern:

0.X!

Partition PSTN_LOCAL_PT

Phone A (should do CLIR)

Partition: IP_PHONES_PT

CSS: TRANSLATION_CLIR_CSS

Phone B (shouldn't do CLIR)

Partition: IP_PHONES_PT

CSS_ PSTN_LOCAL_CSS

The problem:

The call didn't work if the Partion of the Route Pattern isn't included in the CSS of the phone, which should do CLIR.

After i include the partition PSTN_LOCAL_PT (last entry at the CSS order), the call work (with CLIR!)

I thought after a call matched a TP, the configured CSS inside the TP is the new starting point for CSS/PT matches, and the CSS of the Line/Device isn't the after that determined factor.

Thanks in advanced.

Regards

Paul

1 Accepted Solution

Accepted Solutions

ashok_boin
Level 5
Level 5

Hi Paul,

The configuration looks ok to me.

Did you try using Cisco Dialed Number analyzer tool which will give more insight into actual call flow while dialing out with specific CLI etc?

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/dna/4_0_1/dnaan.html#wp1049190

Regards...

-Ashok.


With best regards...
Ashok

View solution in original post

4 Replies 4

ashok_boin
Level 5
Level 5

Hi Paul,

The configuration looks ok to me.

Did you try using Cisco Dialed Number analyzer tool which will give more insight into actual call flow while dialing out with specific CLI etc?

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/dna/4_0_1/dnaan.html#wp1049190

Regards...

-Ashok.


With best regards...
Ashok

Oh i push the wrong button, the question isn't answerd to me now ... :-(

Ashok, the curios is, the DNA says "RouteThisPattern" but i hear the annunciator "the number you dialed..."

  • Results Summary
    • Calling Party Information
      • Calling Party = 8927030
      • Partition = MH2_IP_PHONES_PT
      • Device CSS =
      • Line CSS = MH2_NATIONAL_CLIR_CSS
      • AAR Group Name =
      • AAR CSS =
    • Dialed Digits = 002434000
    • Match Result = RouteThisPattern
    • Matched Pattern Information
      • Pattern = 0.0243[1246]!
      • Partition = PSTN_LOC_PT
      • Time Schedule =
    • Called Party Number = 02434000
    • Time Zone = Europe/Amsterdam
    • End Device = MH2_S2M_AMT_RL
    • Call Classification = OnNet
    • InterDigit Timeout = NO
    • Device Override = Disabled
    • Outside Dial Tone = NO
  • Call Flow
    • TranslationPattern :Pattern= 0.0243[1246]!
      • Partition = PSTN_LOCAL_TRANS_CLIR_PT
      • Positional Match List = 02434000
      • Calling Party Number = 7030
      • PreTransform Calling Party Number = 7030
      • PreTransform Called Party Number = 002434000
      • Calling Party Transformations
        • External Phone Number Mask = NO
        • Calling Party Mask =
        • Prefix =
        • CallingLineId Presentation = Restricted
        • CallingName Presentation = Restricted
        • Calling Party Number = 7030
      • ConnectedParty Transformations
        • ConnectedLineId Presentation = Restricted
        • ConnectedName Presentation = Restricted
      • Called Party Transformations
        • Called Party Mask =
        • Discard Digits Instruction = None
        • Prefix =
        • Called Number = 002434000
    • Route Pattern :Pattern= 0.0243[1246]!
      • Positional Match List = 02434000
      • DialPlan =
      • Route Filter
        • Filter Name =
        • Filter Clause =
      • Require Forced Authorization Code = No
      • Authorization Level = 0
      • Require Client Matter Code = No
      • Call Classification =
      • PreTransform Calling Party Number = 7030
      • PreTransform Called Party Number = 002434000
      • Calling Party Transformations
        • External Phone Number Mask = NO
        • Calling Party Mask =
        • Prefix = 892
        • CallingLineId Presentation = Default
        • CallingName Presentation = Default
        • Calling Party Number = 8927030
      • ConnectedParty Transformations
        • ConnectedLineId Presentation = Default
        • ConnectedName Presentation = Default
      • Called Party Transformations
        • Called Party Mask =
        • Discard Digits Instruction = PreDot
        • Prefix =
        • Called Number = 02434000
    • Route List :Route List Name= MH2_S2M_AMT_RL
      • RouteGroup :RouteGroup Name= MH2_S2M_AMT_RG
        • PreTransform Calling Party Number = 7030
        • PreTransform Called Party Number = 002434000
        • Calling Party Transformations
          • External Phone Number Mask = Default
          • Calling Party Mask =
          • Prefix =
          • Calling Party Number = 7030
        • Called Party Transformations
          • Called Party Mask =
          • Discard Digits Instructions =
          • Prefix =
          • Called Number = 002434000
        • Device :Type= MGCPE1PRIPort
          • End Device Name = S2/DS1-0@MH2VG02
          • PortNumber = 0
          • Device Status = Registered
          • AAR Group Name =
          • AAR Calling Search Space =
          • AAR Prefix Digits =
          • Call Classification =
          • Calling Party Selection =
          • CallingLinePresentation =
          • ConnectedLinePresentation =
          • Number Of Strip Digits =
          • CallerID DN =
        • Device :Type= MGCPE1PRIPort
          • End Device Name = S1/DS1-1@MH2VG01
          • PortNumber = 0
          • Device Status = Registered
          • AAR Group Name =
          • AAR Calling Search Space =
          • AAR Prefix Digits =
          • Call Classification =
          • Calling Party Selection =
          • CallingLinePresentation =
          • ConnectedLinePresentation =
          • Number Of Strip Digits =
          • CallerID DN =
        • Device :Type= MGCPE1PRIPort
          • End Device Name = S2/DS1-1@MH2VG02
          • PortNumber = 0
          • Device Status = Registered
          • AAR Group Name =
          • AAR Calling Search Space =
          • AAR Prefix Digits =
          • Call Classification =
          • Calling Party Selection =
          • CallingLinePresentation =
          • ConnectedLinePresentation =
          • Number Of Strip Digits =
          • CallerID DN =
        • Device :Type= MGCPE1PRIPort
          • End Device Name = S2/DS1-1@MH2VG01
          • PortNumber = 0
          • Device Status = Registered
          • AAR Group Name =
          • AAR Calling Search Space =
          • AAR Prefix Digits =
          • Call Classification =
          • Calling Party Selection =
          • CallingLinePresentation =
          • ConnectedLinePresentation =
          • Number Of Strip Digits =
          • CallerID DN =
  • Alternate Matches
    • Partition :Name= PSTN_NAT_TRANS_CLIR_PT
      • Pattern
        • Pattern = 0.0[2-9]!
        • Pattern Type = Translation
        • TranslationPartition = [584eea9c-a6c8-091d-bacf-111bc6a90369]
        • CallManager Device Type = AccessDevice
        • PatternPrecedenceLevel = ExecutiveOverride
  • Hi Paul,

    Hmm. As per DNA output, it SHOULD work based upon Calling party and called party number. I guess the annunciator message talks about non-reachability to the dialed number which is nothing but not able to match the Translation pattern in your original config.

    Though it's pretty much small item, did you reset or restart the IP phone from Cisco Callmanager from Admin interface? Or, have you tried from any other IP phone in the same CSS?

    If yes, then we can find out quick clue by enabling SDL trace specific to IP Phone "7030" which tracks the practical call flow at Callmanager while making calls from 7030?

    Regards...

    -Ashok.


    With best regards...
    Ashok

    Yes, i restart the phones a lot... and this phone 7030 is only an example.

    Yes my next step would be SDI tracing, i only would know that my TP-knowledge a right or wrong.

    If i see something at the trace or have questions or a solution, i post it here!

    Many thanks Ashok!!!

    Getting Started

    Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: