Thanks for the info and you are on track. I just cannot pin point the root cause.
User’s MiCollab status forwards to a 10 digit cell number “1234567890”. MiCollab adds dialing prefix 9.
Primary MCD has an ARS Digits Dialed of 9NXXXXXX entry (I assume hits this one as the others are not close to matching) Unknown digits to follow List “10”
Secondary MCD has both an ARS Digits Dialed of 9NXXXXXX and 9 + 10 to follow – not sure which one it would fall into.
The 9NXXXXXX 0 digits to follow > List “9” = Route “9” w/ Digit Mod “9”. Digit mod “9” absorbs 1 and inserts “214”.
I would assume that would work although pointless as a different area code is added.
The 9 + 10 > List “10” = Route “10” = Route “10” w/ Digit Mod “10”. Digit mod “10” absorbs 1 and no insert.
I would say this is the right one to use… and setup correctly.
The COR is fine to the best of my knowledge.
Now that user works from home the majority of the time, the SDS error appears more often.
Any insight as to which List would be used on the Secondary based on the information provided?
Much appreciated.
Look at the SDS error and see what number is being pushed and failing (let's say 912122221234), then go to the resilient controller and go to maintenance commands and enter:
DGT TRACE 912122221234
and you should get some output like this:
DGT Trace started:
912122221234 : ARS 91 + 10, ARS 91 + 10, Route (2)
DGT Trace completed.
Which will tell you what exactly it is matching to, otherwise if there is no match you will see:
DGT Trace started:
No definition found.
DGT Trace completed.
My guess is that you will get the later because there is no proper match.