×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Local Route Group and CallForward All Dailplan Design

Unanswered Question
Nov 15th, 2010
User Badges:

I am curious to know a best practice for a dial plan based on Local Route groups and the behavior of CFWDAll.


Assume all NANP patterns point to the SLRG and the CFA CSS is the same as the Line/Device(whether it's Activating Device/Line CSS or default). If a phone in site A calls a phone in Site B, which is CfwdAll to a PSTN number, the call will egress the Site A's Gateway, which is undesirable.


A solution is to use site specific CSS/Patterns, RL->RG's...but this negates the advantage of non-site specific patterns you've gained by using the SLRG in the first place.


Any work around for this?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jonathan Schulenberg Mon, 11/15/2010 - 17:21
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Besides what you have already mentioned (site-specific route patterns), no. This is how the LRG is intended to function. FYI you will see the same behavior with Unified Mobility calls. 


In environments where there is decentralized PSTN connectivity I find this to be the desirable behavior because it minimizes the call legs crossing the WAN. May I ask why this is undesirable in your environment?

Ryan Schwab Mon, 11/15/2010 - 17:51
User Badges:

If SiteA is long distance to SiteB.


SiteB is CFA to a number local to itself but long distance for other sites. This would not work using the LRG feature.

Jonathan Schulenberg Mon, 11/15/2010 - 18:16
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Ah ok. Configure TEHO to route calls local to each site through a specific route group regardless of the originating site. That way anything long distance from all of your sites doesn't cross the WAN and anything local to a site always prefers the appropriate site's Route Group first and then falls back to the LRG if necessary.

Ryan Schwab Mon, 11/15/2010 - 19:42
User Badges:

I'm unsure on configuring TEHO in your example.


Did you mean CFA instead?


As always, your input and knowledge is greatly appreciated!

Jonathan Schulenberg Mon, 11/15/2010 - 19:48
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

I meant Tail End Hop Off (TEHO). This is not necessarily limited or specific to the Call Forward settings. All calls can take the least-cost route out the nearest gateway. Configuring this varies depending on the specifics of your dial plan.


Here are a few documents to get you started:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_0_1/ccmfeat/fslrg.html#wp1048957

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/dialplan.html


The very high-level summary is that you create route patterns - available enterprise wide - for all of the local calling prefixes and attach those patterns to route lists that prefer a specific site before falling back to the LRG.

Actions

This Discussion