<font size=2 face="sans-serif">Peter,</font>
<br>
<br><font size=2 face="sans-serif">On the translation patten you match
for on incoming calls all I have done is at the (prefix digits) outgoing
calls is used 91.. This will add the 91 for USA based calls. </font>
<br>
<br>
<br>
<br><font size=2 face="Verdana">Regards,<br>
<b><br>
John Van Laecke </b></font><font size=2 color=#5f5f5f face="Verdana"><b><br>
</b></font><font size=1 color=#5f5f5f face="Verdana"><b>Senior Voice Engineer<br>
</b></font><font size=2 color=#0060a0 face="Verdana"><b><br>
GHD</b></font><font size=1 color=#0060a0 face="Verdana"><b>
</b></font><font size=1 face="Verdana"><b>Accomplish </b></font><font size=1 color=#0060a0 face="Verdana"><b>More</b></font><font size=1 face="Verdana"><b>
Together</b></font><font size=1 color=#5f5f5f face="Verdana"><br>
T: 61 7 3316 4456 | M:0427 015 232 | V: 414456 | E: John.vanlaecke@ghd.com</font><font size=1 color=#808080 face="Verdana"><br>
</font><font size=1 color=#808080 face="Arial">Level 2, 201 Charlotte Street
QLD AUSTRALIA</font><font size=1 color=#808080 face="Verdana"> | </font><a href=http://www.ghd.com.au/_><font size=1 color=#808080 face="Verdana"><u>www.ghd.com.au</u></font></a>
<p><a href=http://www.ghd.com/sectors/water/><font size=1 color=#0060a0 face="Verdana"><u>Water</u></font></a><font size=1 color=#0060a0 face="Verdana">
| </font><a href="http://www.ghd.com/global/sectors/energy--resources/"><font size=1 color=#0060a0 face="Verdana"><u>Energy
& Resources</u></font></a><font size=1 color=#0060a0 face="Verdana">
| </font><a href=http://www.ghd.com/sectors/environment/><font size=1 color=#0060a0 face="Verdana"><u>Environment</u></font></a><font size=1 color=#0060a0 face="Verdana">
| </font><a href="http://www.ghd.com/global/sectors/property--buildings/"><font size=1 color=#0060a0 face="Verdana"><u>Property
& Buildings</u></font></a><font size=1 color=#0060a0 face="Verdana">
| </font><a href=http://www.ghd.com/global/sectors/transportation/><font size=1 color=#0060a0 face="Verdana"><u>Transportation</u></font></a><font size=1 color=#0060a0 face="Verdana"><br>
</font><font size=1 color=#008000 face="Verdana"><br>
Please consider the environment before printing this email</font><font size=1 face="Verdana">
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Peter Slow <peter.slow@gmail.com></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">Lelio Fulgenzi <lelio@uoguelph.ca>,
WBurnam@mapei.com</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">"cisco-voip@puck.nether.net"
<cisco-voip@puck.nether.net></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">31/01/2011 03:13 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: [cisco-voip] how to add 9 for redial</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">cisco-voip-bounces@puck.nether.net</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>I am doing this right now for a few thousand phones on
a callmanager cluster. i cant talk to what steps you really need to take
to accomplish that if you want to look at it,,.<br>
<br>
-Pete<br>
</font>
<br><font size=3>On Sat, Jan 29, 2011 at 12:00 PM, Lelio Fulgenzi <</font><a href=mailto:lelio@uoguelph.ca><font size=3 color=blue><u>lelio@uoguelph.ca</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>Can you elaborate on "fair undertaking" ?</font>
<br>
<br><font size=3>From what I understand, all that is required is to modify
(or copy) route patterns so they understand the normalized patterns. And
then to begin marking inbounds calls appropriately with the normalized
characters. Now, obviously that's oversimplified, namely because
of the potential number of route patterns, but are there more significant
steps? Admittedly I haven't read to deeply into this section, so I'm shooting
from the hip a bit here. :)<br>
<br>
Sent from my iPhone</font>
<br><font size=3><br>
On Jan 29, 2011, at 11:53 AM, Tanner Ezell <</font><a href=mailto:tanner.ezell@gmail.com target=_blank><font size=3 color=blue><u>tanner.ezell@gmail.com</u></font></a><font size=3>>
wrote:<br>
</font>
<br><font size=3>This is correct and is becoming very popular; eventually
everyone will be E164 compatible. That said, if you're not already using
this it would be a fair undertaking to convert your cluster over.</font>
<br>
<br><font size=3>Using the Device Pool to prefix a 9 looks ugly when it
rings (as it will show the 9 prefix) but it is the easiest way to make
this work without serious changes to your dial plan configurations.<br>
</font>
<br><font size=3>On Sat, Jan 29, 2011 at 7:01 AM, Lelio Fulgenzi <</font><a href=mailto:lelio@uoguelph.ca target=_blank></a><a href=mailto:lelio@uoguelph.ca target=_blank><font size=3 color=blue><u>lelio@uoguelph.ca</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>There is also the concept of normalized dial plans. I
have not got my head completely around this yet, but I think it works that
offnet calls are marked with a + sign and no longer require a 9 to get
out. It's obviously a bit more involved than that, but it should work.
Users can still use a 9 to get an outside line, if you so program the system. <br>
<br>
Sent from my iPod</font>
<br><font size=3><br>
On Jan 28, 2011, at 11:25 PM, Joel Perez <</font><a href=mailto:tman701@gmail.com target=_blank></a><a href=mailto:tman701@gmail.com target=_blank><font size=3 color=blue><u>tman701@gmail.com</u></font></a><font size=3>>
wrote:<br>
</font>
<br><font size=3>Hi Bill,</font>
<br>
<br><font size=3>Unfortunately that is one "feature" that isnt
handled in an elegant/easy fashion at all on CUCM. At least nothing that
I have seen in my search for similar solutions.</font>
<br>
<br><font size=3>There are 3 easy ways of trying to handle that issue that
have worked for me in the past, even though it has been a while since ive
done it. Most customers just accept it. </font>
<br><font size=3>1) If its an MGCP gateway then you can handle it using
the "Service Paramaters -->CallManager Service" section and
set the prefix to 9, 91...etc. (you'rs isnt an MGCP GW)</font>
<br>
<br><font size=3>2) If its an h323 GW then you can try a translation rule
to prefix what you need. Example:</font>
<br><font size=1 color=#2f2f2f><b>voice translation-rule 1</b></font>
<br><font size=1 color=#2f2f2f><b>rule 1 /^/ /9/</b></font>
<br><font size=1 color=#2f2f2f face="Arial"><b>voice translation-profile
InboundVoice</b></font>
<br><font size=1 color=#2f2f2f face="Arial"><b>translate calling 1</b></font>
<br>
<br><font size=1 color=#2f2f2f face="Arial"><b>3) You can also try going
to translation patterns and adding the prefix on your inbound translation
patterns under "Calling Party Transformations" you add the "9"
prefix.</b></font>
<br>
<br><font size=1 color=#2f2f2f face="Arial"><b>The one caveat to the above
is that callers will see all their inbound calls prefixed with a "9"
on their display. I suggest #3 as a quick and easy way of doing it and
testing it on one translation pattern using a DID not used or your own
DID pointed at your DN.</b></font>
<br><font size=1 color=#2f2f2f face="Arial"><b>I havent done this in a
while so results may vary. Im just going by memory here.</b></font>
<p>
<br><font size=1 color=#2f2f2f>Hope that helps, and hopefully someone can
chime in if they have found an easier way or better way of doing it.</font>
<br>
<br><font size=1 color=#2f2f2f face="Arial">Joel P.</font>
<br>
<br>
<br><font size=3>On Fri, Jan 28, 2011 at 8:22 PM, Tanner Ezell <</font><a href=mailto:tanner.ezell@gmail.com target=_blank></a><a href=mailto:tanner.ezell@gmail.com target=_blank></a><a href=mailto:tanner.ezell@gmail.com target=_blank><font size=3 color=blue><u>tanner.ezell@gmail.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>Bill,</font>
<br>
<br><font size=3>The one way is to use the device pool settings. Under
Incoming Calling Party Settings you have the ability to add prefix digits
for National, International, Unknown and Subscriber. In most cases it would
be a 9, 9011, 91, 9 but is highly dependent on your dialplan and current
configuration.</font>
<br>
<br><font size=3>Cheers</font>
<br><font size=3>Tanner Ezell</font>
<br>
<br><font size=3>On Fri, Jan 28, 2011 at 1:28 PM, Burnam, William <</font><a href=mailto:WBurnam@mapei.com target=_blank></a><a href=mailto:WBurnam@mapei.com target=_blank></a><a href=mailto:WBurnam@mapei.com target=_blank><font size=3 color=blue><u>WBurnam@mapei.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>I have a request from my management to do the following:</font>
<p><font size=3>From their Cisco IP phones, when they view a number from
the RECEIVED or MISSED calls directory they want to be able to simply highlight
one of those OUTSIDE numbers and press dial and it will actually dial the
number.</font>
<p><font size=3> </font>
<p><font size=3>The current problem is that we require a “9” to get an
outside line. They don’t want to press edit and add the 9 in front
of these numbers, they believe they should simply be able to highlight
those numbers, press dial and the system will know dial 9 for the outside
line then dial the number that was highlighted.</font>
<p><font size=3> </font>
<p><font size=3>Is there a way to do this in CUCM 7?</font>
<p><font size=3> </font>
<p><font size=3>Thanks,</font>
<p><font size=3>Bill</font>
<p><font size=3> </font>
<p><font size=2> </font>
<p>
<p><font size=4>Bill Burnam</font>
<p><font size=3>Systems Engineer, IT</font>
<p><font size=3>MAPEI Corp.</font>
<p><font size=3>1144 E. Newport Center Drive</font>
<p><font size=3>Deerfield Beach, FL 33442</font>
<p><font size=3> </font>
<p><font size=1 color=#3f8080><u>CONFIDENTIALITY NOTICE</u></font>
<p><font size=1 color=#3f8080 face="Times New Roman">THIS COMMUNICATION,
INCLUDING ANY ATTACHMENT, CONTAINS INFORMATION THAT IS CONFIDENTIAL AND
THAT MAY ALSO BE LEGALLY PRIVILEGED, AND IS INTENDED ONLY FOR THE EXCLUSIVE
USE OF THE INDIVIDUAL NAMED AS THE RECIPIENT. IF THE READER OF THIS
MESSAGE IS NOT THE INTENDED RECIPIENT, YOU HAVE RECEIVED THIS TRANSMISSION
IN ERROR AND ANY REVIEW, DISSEMINATION, DISTRIBUTION OR COPYING OF THIS
COMMUNICATION OR ANY ATTACHMENT TO THIS TRANSMISSION IS STRICTLY PROHIBITED.
IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE IMMEDIATELY NOTIFY
THE SENDER BY REPLY E-MAIL AND DELETE AND DESTROY ALL COPIES OF THE ORIGINAL
MESSAGE. THANK YOU</font><font size=1 color=#3f8080>. </font>
<p><font size=3> </font>
<p><font size=2><b><br>
</b></font>
<hr><font size=2><b>------------------------------------------------------CONFIDENTIALITY
NOTICE ---------------------------------------------------- THIS COMMUNICATION,
INCLUDING ANY ATTACHMENT, CONTAINS INFORMATION THAT IS CONFIDENTIAL AND
IS INTENDED ONLY FOR THE EXCLUSIVE USE OF THE INDIVIDUAL NAMED AS THE RECIPIENT.
IF THE READER OF THIS MESSAGE IS NOT THE INTENDED RECIPIENT, YOU HAVE RECEIVED
THIS TRANSMISSION IN ERROR AND ANY REVIEW, DISSEMINATION, DISTRIBUTION
OR COPYING OF THIS COMMUNICATION OR ANY ATTACHMENT TO THIS TRANSMISSION
IS STRICTLY PROHIBITED. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR,
PLEASE IMMEDIATELY NOTIFY THE SENDER BY REPLY E-MAIL AND DELETE AND DESTROY
ALL COPIES OF THE ORIGINAL MESSAGE. THANK YOU. <br>
</b></font>
<hr>
<br>
<br><font size=3>_______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:cisco-voip@puck.nether.net" target=_blank></a><a href="mailto:cisco-voip@puck.nether.net" target=_blank></a><a href="mailto:cisco-voip@puck.nether.net" target=_blank><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank></a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank></a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank><font size=3 color=blue><u>https://puck.nether.net/mailman/listinfo/cisco-voip</u></font></a><font size=3><br>
</font>
<br><font size=3><br>
<br>
_______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:cisco-voip@puck.nether.net" target=_blank></a><a href="mailto:cisco-voip@puck.nether.net" target=_blank></a><a href="mailto:cisco-voip@puck.nether.net" target=_blank><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank></a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank></a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank><font size=3 color=blue><u>https://puck.nether.net/mailman/listinfo/cisco-voip</u></font></a><font size=3><br>
</font>
<br>
<br><font size=3>_______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:cisco-voip@puck.nether.net" target=_blank></a><a href="mailto:cisco-voip@puck.nether.net" target=_blank><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank></a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank><font size=3 color=blue><u>https://puck.nether.net/mailman/listinfo/cisco-voip</u></font></a>
<br>
<br><font size=3><br>
_______________________________________________<br>
cisco-voip mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:cisco-voip@puck.nether.net"><font size=3 color=blue><u>cisco-voip@puck.nether.net</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank><font size=3 color=blue><u>https://puck.nether.net/mailman/listinfo/cisco-voip</u></font></a><font size=3><br>
</font>
<br><font size=3><br>
<br>
_____________________ <br>
This e-mail has been scanned for viruses by MessageLabs.</font><tt><font size=2>_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
</font></tt><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><tt><font size=2>https://puck.nether.net/mailman/listinfo/cisco-voip</font></tt></a><tt><font size=2><br>
</font></tt>
<br><BR>
_____________________ <BR>
This email and all attachments are confidential. For further important information about emails sent to or from GHD or if you have received this email in error, please refer to http://www.ghd.com/emaildisclaimer.html .<BR>
_____________________ <BR>
This e-mail has been scanned for viruses by MessageLabs.<BR>