Make the destination pattern statements exact by starting with ^ and ending with $ (eg ^911$ )
DQ d...@cisco.com Sent from my iPhone On Jul 12, 2012, at 6:52 AM, "The Masterplan" <winmasterp...@gmail.com> wrote: > Hi, > > I have the following route patterns on CUCM that have a mgcp gateway in route > list: > 911 - marked as urgent priority > 9.XXXXXXX - discard digit predot > 91112.XXXXXXX - discard digit predot > Because those are overlapping route patterns, their behaviour is different > depending if enbloc dialing is used or not: > > 1)With digit by digit dialing if I dial 9111123942123 it will go to 911 > because this route pattern have urgent priority enabled. If I dial 91112345 > it will also go to 911 route pattern. > 2)With en bloc dialing if I dial 9111123942123 it will go to the third route > pattern as desired. If I dial 91112345 it will go to the second route pattern. > > So en bloc dialing will work good in this scenario. But if the routes above > are configured in a CUCME, as dial-peers, I cannot find a way to force CUCME > to have the behaviour as in the second point (en bloc dialing). CUCME uses > logest match in dial-peers by default and even if I put preferences on those > three dial-peers and force CUCME to use explicit preference first I did'n get > the desired behaviour. > > Thank you > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
