Incorrect route pattern selected

Unanswered Question
Aug 20th, 2008

My one location has route patterns out of which one is local,long, international

Wwhen I make 7 digit local calls, it is not using local rp but using long distance inspite of the fact, device CSS has local partition in priority first than long distance

Here is DA for the call.

Can anyone point why it selects long and says local rp as ALTERNATE.

08/20/2008 09:13:46.052 CCM|Digit analysis: match(pi="1", fqcn="3204", cn="3204",plv="5", pss="Part-Fontana-911:Part-Line1:Part-Voicemail:Part-Fontana-Local:Part-Fontana-LongDistance:Part-Fontana-International:Part-Fontana-Internal:Part-Telescams", TodFilteredPss="Part-Fontana-911:Part-Line1:Part-Voicemail:Part-Fontana-Local:Part-Fontana-LongDistance:Part-Fontana-International:Part-Fontana-Internal:Part-Telescams", dd="93228189",dac="1")|<CLID::CCMPUB01-Cluster><NID::10.0.1.3><CT::2,100,119,1.486372><IP::10.0.2.7><DEV::SEP000DED9572AB>

08/20/2008 09:13:46.052 CCM|Digit analysis: analysis results|<CLID::CCMPUB01-Cluster><NID::10.0.1.3><CT::2,100,119,1.486372><IP::10.0.2.7><DEV::SEP000DED9572AB>

08/20/2008 09:13:46.052 CCM||PretransformCallingPartyNumber=3204

|CallingPartyNumber=3204

|DialingPartition=Part-Fontana-LongDistance

|DialingPattern=9.@

|DialingRoutePatternRegularExpression=(9)([2-9][02-9]X)(XXXX)

|DialingWhere=

|PatternType=National

|PotentialMatches=ExclusivelyOffnetPotentialMatchesExist

|DialingSdlProcessId=(0,0,0)

|PretransformDigitString=93228189

|PretransformTagsList=ACCESS-CODE:OFFICE-CODE:SUBSCRIBER

|PretransformPositionalMatchList=9:322:8189

|CollectedDigits=3228189

|UnconsumedDigits=

|TagsList=OFFICE-CODE:SUBSCRIBER

|PositionalMatchList=322:8189

|VoiceMailbox=5189

|VoiceMailCallingSearchSpace=

{

E67375C8-5665-4473-8949-0DAC99129481}

|VoiceMailCallingSearchSpace=Part-Line1:Part-Voicemail:Part-Fontana-LongDistance

|VoiceMailPilotNumber=5099

|AlertingName=

|RouteBlockFlag=RouteThisPattern

|RouteBlockCause=0

|InterceptPartition=

|InterceptPattern=

|InterceptWhere=

|InterceptSdlProcessId=(0,0,0)

|InterceptSsType=0

|InterceptSsKey=0

|OverlapSendingFlagEnabled=0

|WithTags=

|WithValues=

|CallingPartyNumberPi=NotSelected

|ConnectedPartyNumberPi=NotSelected

|CallingPartyNamePi=NotSelected

|ConnectedPartyNamePi=NotSelected

|CallManagerDeviceType=NoDeviceType

|PatternPrecedenceLevel=Routine

|CallableEndPointName=[ED20D4AD-0B98-440C-B14C-5F0E019F5C18]

|PatternNodeId=[709BCDC2-D1BE-49CB-84E7-5A312008D28C]

|AARNeighborhood=[]

|AlternateMatches=

{

|Partition=Part-Fontana-Local

{

<

|RoutePattern=9.[2-9]XXXXXX

|PatternType=Enterprise

|NetworkLocation=OffNet

|CallManagerDeviceType=NoDeviceType

|PatternPrecedenceLevel=PlDefaultOutsideDialtone=

|DeviceOverride=

>

}

}

{

|Partition=Part-Fontana-LongDistance

{

<

|RoutePattern=9.@

|Pattern=(9)([2-9]X[02-9])(XXXX)

|TagsList=ACCESS-CODE:OFFICE-CODE:SUBSCRIBER

|PatternType=National

|NetworkLocation=OffNet

|CallManagerDeviceType=NoDeviceType

|PatternPrecedenceLevel=PlDefaultOutsideDialtone=

|DeviceOverride=

>

}

}

|TranslationPatternDetails=

|OffNetPattern=OffNetOutsideDialtone=

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Michael Owuor Wed, 08/20/2008 - 10:18

Hi Kadambari,

Closest-match routing is used to determine which route pattern matches the number most closely and the call is routed using that route pattern. Order of partitions in the CSS is only used to break a tie when two or more patterns in different partitions match equally.

The route pattern in the LD partition is 9.@, which includes several patterns, including (9)([2-9]X[02-9])(XXXX) which is a closer match for the dialed number than the route pattern in the local partition, which is 9.[2-9]XXXXXX.

If the route pattern in the local partition should be matched instead, change it from 9.[2-9]XXXXXX to 9.[2-9]x[02-9]XXXX. Since the device CSS has local partition above the long distance partition, the order will break the tie.

Does this help?

Regards,

Michael.

Actions

This Discussion