Only calls with numbers that start with 6 get a reorder tone, the rest of the calls go through. 1

[dmarenco]

Calls to numbers that start with 6 get a reorder tone immediately after the 8th digit is dialed, from the same phone all other calls go through ok, I took a sample of a good call vs a bad call,

on the bad call the call fails with denial event 1166: Unassigned number D1=0x9b88 D2=0x201
on the calls that fail I see that CM doesn't process all the digits as they were dialed, it blocks the call at the 8th digit and tears down the call with denial event 1166: Unassigned number D1=0x9b88 D2=0x201, CM won't let calls that start with 6 dial more than 8 digits, very strange. I ran a list ars route-chosen 16099545502 location 169 and I see that there is a matching route through pattern 2 on the ars table but it goes through route pattern 998 which belongs to the aar table

On the good call I dialed 8668475500 from 2154462017
On the bad call I dialed 6099545502 from 2154462017

any suggestions will be highly appreciated!

thanks!

 

[joe2938]

Is the 6 entry in ARS for your location table 169?

 

[dmarenco]

no there is no entry for that pattern, the ars analysis location 169 only has 511 and 911

 

[dmarenco]

this happened after the upgrade to system manager 6.3, the fix was given by avaya:

we found that the new version of SM has a new feature called "Smart Compaction" more info can be found in this document. What was happening is that some of the dial plans were missing as part of the “compaction” process. We had to increase the maximum dial plan entries from 300 to 600 – you have about 570 entries.

https://downloads.avaya.com/css/P8/documents/101014573

7.1. Session Manager The SM changes were added in 6.3.12. It should be noted that problems were encountered in the field with the PPM’s compaction algorithm which required a fix that went into 6.3.14. Specifically, PPM could compact in such a way as to generate patterns with a leading ‘x’ which caused problems in the endpoints. So as of 6.3.14, PPM will no longer generate patterns that begin with an ‘x’.

Procedure to correct the issue:

cd to /opt/Avaya/jboss-6.1.0.Final/server/mgmt/deploy/ppm.ear/ppm.war/WEB-INF/
vi file ppm-servlet.xml
arrow down to "maxDigitTerms" and change the value from 300 to 600
write the file !w
service mgmt restart

thank you for your help here

 

[joe2938]

Thanks for the update, good to know.