Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

issue on urgent priority short dialing intra cluster

Hello All,

I have an issue with short daling within the cluster, It seems CUCM takes 6 seconds to make the second phone ring even when a TP with urgent priority is hit. As fas as my observation appropriate translation pattern hit and it actions as soon as the user presses the digits, but cucm takes time in searching the called number and it finds the number only after 6 seconds and the phone rings. There is no issues with enblock dialling.

Configuration: CUCM 8.5.1

---------------------------------------

ANI : 3573257

DNIS : 3573258

* Cisco 7942 (3573257 in partition2 dialls 3 2 5 8) --> 3XXX TP with urgent priority, prefix 357 in partiotion1 --> Cisco 7942 (3573258 in partition2 phone      rings after 6 seconds)

* Both the phone are under the same subscriber.

* If I do enblock dialling I dont see any issues.

Changes happened:

-------------------------------------

The issue happened after the site has been undegone some phones, partiotion, CSS and gateway changes with regard to implementing logical partitioning.

Kindly help me on this issue, earlier called phone rings as soon as the user do 4 digit short dial but now it has 6 seconds delay. I can post if you need the CCM traces here.

1 ACCEPTED SOLUTION

Accepted Solutions

issue on urgent priority short dialing intra cluster

I checked your traces.

in Enbloc dialing there is no potential match exist during digit analysis.

21:59:35.734 |StationInit: (0146365) EnblocCall calledParty=3257.|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14

21:59:35.735 |Digit analysis: match(pi="2", fqcn="66553077", cn="3573077",plv="5", pss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", TodFilteredPss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", dd="3257",dac="0")|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14

21:59:35.735 |Digit analysis: analysis results|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14

21:59:35.735 ||PretransformCallingPartyNumber=3077

|CallingPartyNumber=3077

|DialingPartition=SG2-ICR-PhoneDN-PT

|DialingPattern=3573257

|FullyQualifiedCalledPartyNumber=66553257

|DialingPatternRegularExpression=(3573257)

|DialingWhere=

|PatternType=Enterprise

|PotentialMatches=NoPotentialMatchesExist

but for the digit by digit dialing, it says, potential matches exist.

21:59:50.906 |Digit analysis: match(pi="2", fqcn="66553077", cn="3573077",plv="5", pss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", TodFilteredPss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", dd="3257",dac="0")|8,100,50,1.933364937^19.237.142.74^SEP001E13E61F14

21:59:50.906 |Digit analysis: analysis results|8,100,50,1.933364937^19.237.142.74^SEP001E13E61F14

21:59:50.906 ||PretransformCallingPartyNumber=3077

|CallingPartyNumber=3077

|DialingPartition=SG2-ICR-PhoneDN-PT

|DialingPattern=3573257

|FullyQualifiedCalledPartyNumber=66553257

|DialingPatternRegularExpression=(3573257)

|DialingWhere=

|PatternType=Enterprise

|PotentialMatches=PotentialMatchesExist

|DialingSdlProcessId=(0,0,0)

|PretransformDigitString=3573257

|PretransformTagsList=SUBSCRIBER

|PretransformPositionalMatchList=3573257

|CollectedDigits=3573257

|UnconsumedDigits=

not sure why this difference is? could you please crosscheck the routeplan report once again please?

//Suresh Please rate all the useful posts.
16 REPLIES

issue on urgent priority short dialing intra cluster

could you please check if there is any other pattern (RP or TP) starting with '3'

//Suresh Please rate all the useful posts.
Community Member

issue on urgent priority short dialing intra cluster

Hi Suresh,

No. I have verified the constructs and there is no overlapping pattern starting with '3'.

FYI, 4 digit enblock dialling works as expected. Issue is only with digit by digit dialling.

Thanks..

issue on urgent priority short dialing intra cluster

Hi Lajith,

in the TP: 3XXX, instead of prefixing '357' could you please apply the called party transform mask as 3573XXX and test the behaviour?

also have a look at this bug:  CSCtd69700

https://tools.cisco.com/bugsearch/bug/CSCtd69700

Symptom:

Translation pattern waits for interdigit timer.

for this call flow:

7107 -> 1234 (translation pattern) -> called party transform to 7102

we have two DN 7102 and 71021

it waits for interdigit timer before call rings the DN 7102

when you redial it works fine.

Conditions:

call manager 7.1.3.20000-1

Workaround:

none

//Suresh Please rate all the useful posts.
Community Member

issue on urgent priority short dialing intra cluster

Hi Suresh,

I have tried the same, still no luck. The problem remains. Do you need to review the CCM traces?

Thanks..

issue on urgent priority short dialing intra cluster

Sure. Please collect the ccm traces for both working and the delayed call

//Suresh Please rate all the useful posts.
Community Member

issue on urgent priority short dialing intra cluster

Hi Suresh,

Can you help?

Thanks

issue on urgent priority short dialing intra cluster

Did you check the T302 timer in that subscriber and other nodes?

//Suresh Please rate all the useful posts.
Community Member

Re: issue on urgent priority short dialing intra cluster

6000

We have several other sites configured on the same subscriber but those sites does not have any issues in dialing.

I have attaced the CCM traces, Kindly review it.. Calling Party: 3573077, Called Party: 3573257

There is one correction TP is XXXX not 3XXX. I have tested with both - not working.

Thanks

issue on urgent priority short dialing intra cluster

I checked your traces.

in Enbloc dialing there is no potential match exist during digit analysis.

21:59:35.734 |StationInit: (0146365) EnblocCall calledParty=3257.|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14

21:59:35.735 |Digit analysis: match(pi="2", fqcn="66553077", cn="3573077",plv="5", pss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", TodFilteredPss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", dd="3257",dac="0")|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14

21:59:35.735 |Digit analysis: analysis results|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14

21:59:35.735 ||PretransformCallingPartyNumber=3077

|CallingPartyNumber=3077

|DialingPartition=SG2-ICR-PhoneDN-PT

|DialingPattern=3573257

|FullyQualifiedCalledPartyNumber=66553257

|DialingPatternRegularExpression=(3573257)

|DialingWhere=

|PatternType=Enterprise

|PotentialMatches=NoPotentialMatchesExist

but for the digit by digit dialing, it says, potential matches exist.

21:59:50.906 |Digit analysis: match(pi="2", fqcn="66553077", cn="3573077",plv="5", pss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", TodFilteredPss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", dd="3257",dac="0")|8,100,50,1.933364937^19.237.142.74^SEP001E13E61F14

21:59:50.906 |Digit analysis: analysis results|8,100,50,1.933364937^19.237.142.74^SEP001E13E61F14

21:59:50.906 ||PretransformCallingPartyNumber=3077

|CallingPartyNumber=3077

|DialingPartition=SG2-ICR-PhoneDN-PT

|DialingPattern=3573257

|FullyQualifiedCalledPartyNumber=66553257

|DialingPatternRegularExpression=(3573257)

|DialingWhere=

|PatternType=Enterprise

|PotentialMatches=PotentialMatchesExist

|DialingSdlProcessId=(0,0,0)

|PretransformDigitString=3573257

|PretransformTagsList=SUBSCRIBER

|PretransformPositionalMatchList=3573257

|CollectedDigits=3573257

|UnconsumedDigits=

not sure why this difference is? could you please crosscheck the routeplan report once again please?

//Suresh Please rate all the useful posts.
Cisco Employee

issue on urgent priority short dialing intra cluster

Could you please paste screenshot of  the RP and TP ? probable reason could be overlaping might getting detected.


Br,
Nadeem 

Please rate all useful post.

Br, Nadeem Please rate all useful post.
Community Member

Re: issue on urgent priority short dialing intra cluster

Please find the TP and RP attached..

issue on urgent priority short dialing intra cluster

when you dial 4 digit extn XXXX, it is translated to 357XXXX but again there is a translation pattern with 357XXXX. Perhaps the call is trying to match this TP. Does the phone CSS has SG2-ICR-PSTNTrans-PT?

could you please try removing the partition: SG2-ICR-PSTNTrans-PT from the device css? also you may try modifying that TP for testing purpose as *357XXXX check?

//Suresh Please rate all the useful posts.
Cisco Employee

issue on urgent priority short dialing intra cluster

You can try as Sureshsub2 suggested..RP seems ok and only thing suspecting which sureshsub2 already pointed out


Br,
Nadeem 

Please rate all useful post.

Br, Nadeem Please rate all useful post.
Community Member

Re: issue on urgent priority short dialing intra cluster

Hi All,

I have verified both device and line CSS and it does not have SG2-ICR-PSTNTrans-PT included.

Also I have tried modifiying the pattern as *357XXXX but that could not help.

Please suggest

Thanks.

Community Member

Re: issue on urgent priority short dialing intra cluster

Hi All,

I have figured out the issue. There is one phone DN with ! infront under the same partition of called phone (like the same kind we have in RP - !3573888). So it seems phone is expecting more digits and when only 4 digts dialled it completes it interdigit time out, matches the XXXX and routes the call.

But I have another concern here, when you changes the Block this pattern for XXXX pattern and when you do digit by digit dialling it hits the XXXX pattern and getting fast busy. Might be block pattern takes higher preference over the !.

Thanks all for looking into this issue and helping me here.

issue on urgent priority short dialing intra cluster

HI Lajith, good to know the issue is fixed. thanks for the rating

//Suresh Please rate all the useful posts.
410
Views
0
Helpful
16
Replies
CreatePlease to create content