[cisco-voip] Interdigit Timeout on Translation

Daniel Rodriguez drodriguez at fidelus.com
Tue Mar 18 15:21:09 EDT 2008


Correction:
(assuming the calling party’s CSS has access to the partition assigned to the RPs).

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Daniel Rodriguez
Sent: Tuesday, March 18, 2008 3:16 PM
To: CarlosOrtiz at bayviewfinancial.com
Cc: cisco-voip-bounces at puck.nether.net; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Interdigit Timeout on Translation

You can also throw in a 9.011! pattern so the octothorpe isn’t required. Having 9.011!# and 9.011! in your route plan will allow for both scenarios (assuming the called party’s CSS has access to the partition assigned to the RPs). Both would be potential matches until the # is received by CCM, which would then explicitly match the 9.011!# and immediately begin call routing.

- Daniel

From: CarlosOrtiz at bayviewfinancial.com [mailto:CarlosOrtiz at bayviewfinancial.com]
Sent: Tuesday, March 18, 2008 3:10 PM
To: Daniel Rodriguez
Cc: cisco-voip at puck.nether.net; cisco-voip-bounces at puck.nether.net
Subject: Re: [cisco-voip] Interdigit Timeout on Translation


So I added the octothorpe to the end of the international pattern and then to the end of the translation pattern and that works.  Only downside is that now you are required to hit the "#" at the end of dialing all international calls.  That's probably a good thing, but is a change from what people are already use to.

Thanks,

Carlos
Daniel Rodriguez <drodriguez at fidelus.com>
Sent by: cisco-voip-bounces at puck.nether.net

03/18/2008 10:20 AM

To

"CarlosOrtiz at bayviewfinancial.com" <CarlosOrtiz at bayviewfinancial.com>, "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>

cc

Subject

Re: [cisco-voip] Interdigit Timeout on Translation







How are you using the octothorpe? Was it inserted at the end of the international pattern?  If at the end of the pattern, CCM should know to stop waiting to perform digit analysis once its received since you’ll be matching an explicit pattern.

Also, how are you using your translation patterns? I would make sure the called party transformation isn’t stripping the #. You want the translated called party number to match your  # international pattern (eg  9.011!#). Speed dial = 3377# --> TxPattern = 33XX#, Prefix= 9011<number> --> RP = 9.011!#

-daniel

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of CarlosOrtiz at bayviewfinancial.com
Sent: Tuesday, March 18, 2008 9:37 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Interdigit Timeout on Translation


I am setting up some speed dials using translation patterns for International locations.  Is there any way to avoid waiting for the inter digit timeout at the end of the pattern?  I thought you could bypass it with the "#" but that does not work.

Carlos_______________________________________________
cisco-voip mailing list
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/20080318/be0d0a91/attachment.html 


More information about the cisco-voip mailing list