Translation pattern problem

[Pawel Pietrzak]

Hi everyone,

i have a problem with one of translation rule. So,

i have that rule:

1XX

translate called to:

3264031XX

When user dial 121 to 151 its not working any other combination works fine. Here is  DNA output:

  
 Results Summary
Calling Party Information
Calling Party = 326403126
Partition = IPT-SR-WIELUN
Device CSS = VALID CSS NAME
Line CSS =
AAR Group Name =
AAR CSS =
Dialed Digits = 121
Match Result = BlockThisPattern
Route Block Cause = Unallocated Number
Called Party Number =
Matched Pattern Information
Pattern =
Partition =
Pattern Type =
Time Zone =
Outside Dial Tone = NO
Call Flow
TranslationPattern :Pattern=
Partition =
Positional Match List =
Calling Party Number = 326403126
PreTransform Calling Party Number =
PreTransform Called Party Number =
Calling Party Transformations
External Phone Number Mask = NO
Calling Party Mask =
Prefix =
CallingLineId Presentation =
CallingName Presentation =
Calling Party Number = 326403126
ConnectedParty Transformations
ConnectedLineId Presentation =
ConnectedName Presentation =
Called Party Transformations
Called Party Mask =
Discard Digits Instruction =
Prefix =
Called Number =
Alternate Matches
Partition :Name= VALID CSS NAME
Pattern
Pattern = 1XX
Pattern Type = Translation
TranslationPartition = [3c865132-f4e3-d951-e9ca-53764ebb2367]
CallManager Device Type = AccessDevice
PatternPrecedenceLevel = PlDefault
PatternRouteClass = RouteClassDefault
RouteNextHopByCgpn = false

As U see there is not hit to that translation and is marked as "Alternate matches" - i have no idea why ?

I`m really stuck with that.

Partitions are okey.

Any one has an idea ?

[Chris Deren]

See "BlockThisPattern", do you have other patterns that provide overlap which block this pattern?

[Pawel Pietrzak]

There is no other overlaping patterns.

[Chris Deren]

That is not what DNA shows, can you check under route plan report if you have anything starting with 1 or X or [ that could create this overlap?

Is your database replication working properly?

[Pawel Pietrzak]

Checked - no other similiar translations or route patterns in attached css in that translation rule. Replication have a good state - every node has a 2 Setup completed state.

[afsal abdul gafoor]

Can you send us the route plan report screen shot starting with 1XXX or XXXX.

Regards

Afsal Abdul Gafoor

[Pawel Pietrzak]

Report is empty.

[Pawel Pietrzak]

Alternate Matches
Partition :Name= VALID CSS NAME
Pattern
Pattern = 1XX
Pattern Type = Translation
TranslationPartition = [3c865132-f4e3-d951-e9ca-53764ebb2367]
CallManager Device Type = AccessDevice
PatternPrecedenceLevel = PlDefault
PatternRouteClass = RouteClassDefault
RouteNextHopByCgpn = false

Is it bolded line suspicious ? Is it not strange that there is no translation name or pattern instead that strange string ?

[afsal abdul gafoor]

Hello just for clarification,

Suppose if a user dials 155 ,will get translated to 326403155 ?.

If so there should be some other matching pattern or some other transformation pattern affecting this for this number and it seems strange.

What you can do you can assign this translation pattern in a separate partition ,and assign the partition directly to an extension and try the same.

If it is working means then we have to dig much on the existing pt/css.

Regards

Afsal Abdul Gafoor

[Pawel Pietrzak]

Suppose if a user dials 155 ,will get translated to 326403155 ?

True.

This translation is allready in separate partition and dedicated css - there is no way that it can hit any other pattern.

Take a look at this line from DNA output:

TranslationPartition = [3c865132-f4e3-d951-e9ca-53764ebb2367]

Its okey ? I suppose that is something wrong there ?

[afsal abdul gafoor]

I cannot comment that translation pattern.I am sorry.

But if the same user dials 120( provided the same partition and CSS ) it is not going means it is strange.Please send me the entire screen shot of translation pattern

Regards

Afsal