I think you hit the nail on the head... those are the ones I understand are affected. I'm not sure if remote destinations are affected though. And it's all of jabber, not just click to call.
I have route patterns that know when a call is local or not, so i just add a 1 regardless using the rules. Here are what mine look like... our AD directory stores our telephone numbers with a +1 areacode number with a space and the extension. It's not pretty. In order to get around that, and to dial someone's extension, I added those last three rules. The space is interpreted as a 9, so the match works. for now. --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 [email protected] www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ----- Original Message ----- From: "Ed Leatherman" <[email protected]> To: "Cisco VOIP" <[email protected]> Sent: Friday, January 29, 2016 10:33:35 AM Subject: [cisco-voip] CUCM 10.x Application Dial Rules - When do they get used? The documents i've seen don't give a definitive list of what cases these get applied - it just says "applications such as". I want to add in some rules here for Jabber click to call stuff, for example changing 1+10 digits to sometime dialable in our current plan. I'm being a little cautious about unintended consequences. IPMA Cisco Web Dialer Jabber - Click to call, what other cases? Remote Destinations Is there a rule that gets checked to see when these rules get applied? -- Ed Leatherman _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
