[cisco-voip] how to add 9 for redial

Sun Jan 30 01:07:48 EST 2011

Not to violate NDA, but studying for a certain four-letter certification clued me into that, so I can’t take too much credit.

James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com<mailto:jbuchanan at ctiusa.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<http://www.presidio.com/>
CCIE #25863, Voice

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Saturday, January 29, 2011 11:57 PM
To: Joel Perez
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] how to add 9 for redial

Actually, that's a great idea. If I can get it to appear in the directory, but not on the screen, that would go a long way.

Ditto on looking into that!

Sent from my iPhone

On Jan 30, 2011, at 12:54 AM, Joel Perez <tman701 at gmail.com<mailto:tman701 at gmail.com>> wrote:

Hi James,
Hadn't thought about using that. Gonna give it a try.
Thanks,
Joel P
On Jan 30, 2011 12:45 AM, "Buchanan, James" <jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>> wrote:
> You can use a calling number transformation pattern to remove the 9 so that the 9 does not show when the call is coming in, but does show in the directory.
>
> James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions
> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com<mailto:jbuchanan at presidio.com><mailto:jbuchanan at ctiusa.com<mailto:jbuchanan at ctiusa.com>>
> D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<http://www.presidio.com><http://www.presidio.com/>
> CCIE #25863, Voice
>
>
> From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Tanner Ezell
> Sent: Saturday, January 29, 2011 10:54 AM
> To: Lelio Fulgenzi
> Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] how to add 9 for redial
>
> 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.
>
> 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.
> On Sat, Jan 29, 2011 at 7:01 AM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca><mailto:lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>> wrote:
> 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.
>
> Sent from my iPod
>
> On Jan 28, 2011, at 11:25 PM, Joel Perez <tman701 at gmail.com<mailto:tman701 at gmail.com><mailto:tman701 at gmail.com<mailto:tman701 at gmail.com>>> wrote:
> Hi Bill,
>
> 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.
>
> 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.
> 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)
>
> 2) If its an h323 GW then you can try a translation rule to prefix what you need. Example:
>
> voice translation-rule 1
>
> rule 1 /^/ /9/
>
> voice translation-profile InboundVoice
>
> translate calling 1
>
>
>
> 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.
>
>
>
> 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.
>
> I havent done this in a while so results may vary. Im just going by memory here.
>
> Hope that helps, and hopefully someone can chime in if they have found an easier way or better way of doing it.
>
> Joel P.
>
>
> On Fri, Jan 28, 2011 at 8:22 PM, Tanner Ezell <tanner.ezell at gmail.com<mailto:tanner.ezell at gmail.com><mailto:tanner.ezell at gmail.com<mailto:tanner.ezell at gmail.com>>> wrote:
> Bill,
>
> 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.
>
> Cheers
> Tanner Ezell
>
> On Fri, Jan 28, 2011 at 1:28 PM, Burnam, William <WBurnam at mapei.com<mailto:WBurnam at mapei.com><mailto:WBurnam at mapei.com<mailto:WBurnam at mapei.com>>> wrote:
> I have a request from my management to do the following:
> 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.
>
> 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.
>
> Is there a way to do this in CUCM 7?
>
> Thanks,
> Bill
>
>
> Bill Burnam
> Systems Engineer, IT
> MAPEI Corp.
> 1144 E. Newport Center Drive
> Deerfield Beach, FL 33442
>
> CONFIDENTIALITY NOTICE
> 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.
>
>
> ________________________________
> ------------------------------------------------------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.
> ________________________________
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110130/c98ed67c/attachment.html>