User Tools

Site Tools


eduardo:cisco:cucm:cucm-teho

Tail End Hop Off

  • PSTN breakout occurs at gateway located closest to the PSTN destination.
  • Make sure it is legal in the country you are doing this

Local Route Group

  • Implication of using Local Route Group
  • Number of of route patterns and route lists required for TEHO is reduced from N x N to N + 1 (N is the number of sites).
  • The number of partitions and CSS is reduced from N to 1
  • The number of gateways, route groups, and device pool remains the same (N)
  • If combined with globalized dialing, TEHO can be used worldwide using the simple dial plan model (N + 1 route patterns and route lists), regardless of different local dial rules.
  • Call from Boulder phone to Herndon - TEHO destination

  • Call from Boulder phone to NON TEHO destination

  • Call from Herndon phone to NON TEHO destionation

  • Call from Herndon phone to Boulder - TEHO destination

  • Call from Herndon phone to Herndon destination

Configuration

Route Pattern

  • Route pattern for each area that can be reached at different costs; one per site, in different partition
  • Putting in separate partition allow some control by placing them only on certain phone that you want to allow TEHO

Without Local Route Group

With Local Route Group

Route List

  • Route patterns point to route lists (with different priorities of gateways: cheapest gateway first, local gateway next, then other gateway for additional backup if desired)

CSS

  • Add site specific Route Pattern to the CSS of some phones that require TEHO
  • Phone CSS for correct route-pattern selection
eduardo/cisco/cucm/cucm-teho.txt · Last modified: 2024/02/23 08:20 by 127.0.0.1