CUCM Route Plan: Understanding Route Plan Devices

  • H.323 Gateways
  • MGCP Gateways
  • SIP Trunks
  • Intercluster Trunks – CUCM Cluster to CUCM Cluster via IP Communication

Devices/Gateways – Can be added to Route Groups

Add new H.323 Gateway to CUCM

CUCM has no keepalive with the Gateway, hence the Unknown status

H225 starts calls
H245 exchanges features

9.@ go to Gateway via the Route Pattern (In its most basic form)

Gateway then has a Dial Peer to send digits to the PSTN (CVOICE)

Add new MGCP Gateway to CUCM

Domain Name (No IP Address) Has to match on the GW itself

Call Agent concept

Slots/WICs added to GW within CUCM, then configured

MGCP Syntax (Confusing… Slot/Subunit etc… Analog Line etc..)

Attendant DN: Where to route call when it receives inbound?

With MGCP, Endpoints/Interfaces will be available individually such as FXO port etc…

SIP Trunks

Device -> Trunk -> Add New -> SIP Trunk

Logical Name
Destination Address (IP of endpoint)

Security Profile (Customised dependant on provider)

Intercluster Trunks

Connections between CUCM clusters via IP WAN

Device -> Trunk -> Add New -> InterCluster Trunk Non Gatekeeper Controlled

*Gatekeeper optional for centralised control (GK can be in a pair with L3 gateway redundancy such as HSRP/VRRP etc…)

So the Route Pattern can deliver digits to a Route List or directly to a Gateway/Trunk/Intercluster Trunk