© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Deployment of a Dial Plan on Cisco Unified CallManager Release 5.0 Configuring Cisco Unified CallManager Trunks

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Cisco Unified CallManager Trunks Trunks are VoIP signaling interfaces between Cisco Unified CallManager clusters: Either H.323 or SIP: –H.323 Nongatekeeper-controlled –H.323 Gatekeeper-controlled SIP trunks also used to interwork with other voice elements: –SIP service providers –PBX –Applications IP ICT

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v H.323 Nongatekeeper-Controlled ICT IP Cluster-to-cluster full mesh Call routing configuration multiplied Limited CAC capabilities ICT SFO SJC LAX

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v SFO SJC LAX H.323 Gatekeeper-Controlled ICT Cluster-to-gatekeeper signaling with H.323 RAS Only one trunk to gatekeeper is needed per cluster H.323 CAC and bandwidth management available Improved scalability ICT RAS GK

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v SFO H.323 Gatekeeper-Controlled H.225 Trunk PSTN VoIP H.225 Trunk H.323 Gateway Similar to the H.323 gatekeeper-controlled ICT. Cisco Unified CallManager can communicate to any H.323 endpoint. Used for combinations of H.323 gateways and Cisco Unified CallManager clusters. GK

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v SIP Trunk Cisco Unity Gateways Cisco Unified Presence Server Other Carriers Cisco CallManager Express SIP Primarily connects to non-CiscoCallManager clusters No support for Secure Real-Time Transport Protocol (SRTP) and Q.SIG tunneling Annex M1 Can point to only one IP address or DNS SRV record name –Configure multiple trunks for failover/load balancing for trunks that do not support DNS SRV record names.

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v SIP Trunk Supported Features These SIP trunk features are supported: Additional security (TLS and Digest Authentication) Multiple Transport Layer protocols (TCP, UDP, TLS) Multiple SIP trunks per incoming port number Call preservation –Active calls are preserved when a node fails. Video support T.38 fax relay Any-to-any protocol interworking (SIP-Q.SIG, SIP-MGCP, SIP- H.323, SIP-SCCP, SIP-CTI)

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Nongatekeeper-Controlled Intercluster Trunks IP LAX-ICT Cisco Unified CallManager nongatekeeper-controlled ICT configuration steps: 1. Add nongatekeeper-controlled ICT at SFO 2. Configure the ICT parameters at SFO 3. Repeat Steps 1–2 at LAX SFOLAX

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Nongatekeeper-Controlled Intercluster Trunks: Add ICT Click Add New. 2 Choose Device > Trunk. 1

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Nongatekeeper-Controlled Intercluster Trunks: Add ICT (Cont.) Select Inter-Cluster Trunk (Non-Gatekeeper Controlled). 3 Click Next. 4

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Nongatekeeper-Controlled Intercluster Trunks: Configure ICT Enter the trunk name, description and Choose the device pool. 5 Scroll to the end of the page. 6

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Nongatekeeper-Controlled Intercluster Trunks: Configure ICT (Cont.) Enter IP addresses of remote Cisco Unified CallManager cluster. 7 Confirm the popup window by clicking OK. 9 Click Save. 8

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Nongatekeeper-Controlled Intercluster Trunks: ICT Successfully Added Nongatekeeper-controlled ICT successfully added

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v H.323 zone: east Configuring Gatekeeper-Controlled Intercluster Trunks IP GK-ICT Cisco Unified CallManager gatekeeper-controlled ICT configuration steps: 1. Add gatekeeper at SFO. 2. Add gatekeeper-controlled ICT at SFO. 3. Configure the ICT parameters at SFO. 4. Repeat Steps 1–3 at NY. 5. Configure Cisco H.323 gatekeepers. SFONY GK-ICT H.323 zone: west GK

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: Add Gatekeeper Click Add New. Choose Device > Gatekeeper. 2 1

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: Add Gatekeeper (Cont.) Click Save. 4 Enter gatekeeper name or IP address and description. 3

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: Add ICT Click Add New. 6 Choose Device > Trunk. 5

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: Add ICT (Cont.) Select the Inter-Cluster Trunk (Gatekeeper Controlled). 7 Click Next. 8

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: Configure the ICT Enter the Trunk Name, Description and choose the Device Pool. 9 Scroll to the end of the page. 10

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: Configure the ICT (Cont.) Click Save. 13 Confirm the popup window by clicking OK. 14 Select the gatekeeper and enter the gatekeeper information. 11 Enter the Technology Prefix and the H.323 zone. 12

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Gatekeeper-Controlled Intercluster Trunks: ICT Successfully Added Gatekeeper-controlled ICT successfully added

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v H.323 zone: east IP GK-ICT SFONY GK-ICT H.323 zone: west GK Configuring Gatekeeper-Controlled Intercluster Trunks: Configure Cisco IOS H.323 Gatekeeper west#configure terminal west(config)#gatekeeper west(config-gk)#zone local west cisco.com west(config-gk)#zone remote east cisco.com west(config-gk)#zone prefix west 1* west(config-gk)#zone prefix east 2* west(config-gk)#gw-type-prefix 1#* default-technology west(config-gk)#no shutdown west(config-gk)#end

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring H.225 Trunks IP H225TRK Cisco Unified CallManager H.225 trunk (gatekeeper-controlled) configuration steps: 1. Add gatekeeper to SFO. 2. Add H.225 trunk (gatekeeper-controlled) to SFO. 3. Configure the H.225 trunk parameters at SFO. 4. Configure Cisco IOS H.323 gatekeeper H.323 zone: west RAS H.323 Gateway SFO GK

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring H.225 Trunks: Add Trunk Select the H.225 trunk (gatekeeper-controlled). 1 Click Next. 2

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring H.225 Trunks: Configure Trunk Enter the trunk name, description, and choose the device pool. 3 Scroll to the end of the page. 4

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring H.225 Trunks: Configure Trunk (Cont.) Select the gatekeeper and enter the gatekeeper information. 5 Click Save. 6 Confirm the popup window by clicking OK. 7

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring H.225 Trunks: H.225 Trunk Successfully Added H.225 trunk successfully added

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v IP H225TRK H.323 zone: west RAS H.323 Gateway SFO GK Configuring H.225 Trunks: Configure Cisco IOS H.323 Gatekeeper west#configure terminal west(config)#gatekeeper west(config-gk)#zone local west cisco.com west(config-gk)#zone prefix west 1* west(config-gk)#zone prefix west 3* west(config-gk)#gw-type-prefix 1# default-technology west(config-gk)#no shutdown west(config-gk)#end

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Q.SIG for Trunks Cisco Unified CallManager Q.SIG Any intercluster or H.225 trunk can be configured for Q.SIG: Achieved through trunk configuration settings Existing trunk converted to tunnel the Q.SIG Support for additional features, such as callback or path replacement ICT/H.225 PBX E1 with Q.SIG

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring Q.SIG for Trunks: Converting an Existing Trunk to Q.SIG Select the Q.SIG as Tunneled Protocol. Verify that the service parameter Protocol Profile is set to FALSE. 1 2

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring SIP Trunks IP Cisco Unified CallManager SIPTRK Cisco Unified CallManager SIP trunk configuration steps: 1. Add SIP trunk 2. Configure SIP trunk Public SIP Server SIP Provider Service

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring SIP Trunks: Add SIP Trunk Click Add New. 2 Select Device > Trunk. 1

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring SIP Trunks Select the SIP trunk type. 3 Click Next. 4

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring SIP Trunks Enter the unique SIP trunk name and description. 5 Select the device pool. 6 Scroll to the end of the page. 7

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring SIP Trunks (Cont.) Enter the SIP proxy IP address (or DNS SRV record name). 8 Select the SIP Trunk Security Profile. Select the SIP Profile Confirm the popup window by clicking OK. 12 Click Save. 11

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Configuring SIP Trunks: SIP Trunk Successfully Added SIP Trunk successfully added!

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Verifying Trunk Configurations: Verify Cisco Unified CallManager Trunk Select Device > Trunk. Click Find. 1 2 Click on the trunk from the list to verify its configuration. 3

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Verifying Trunk Configurations: Verify Gateway and Gatekeeper Gateway verification tips: Display running configuration. Examine VoIP dial peer call statistics. Use debug to verify H.225 or SIP signaling exchange. Place test call. Gatekeeper verification tips: Display running configuration. Verify registration of the Cisco Unified CallManager. Use debug to verify RAS signaling exchange.

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v Summary Cisco Unified CallManager supports intercluster trunks to interconnect multiple clusters. Cisco Unified CallManager intercluster trunks can be direct or gatekeeper-controlled. H.225 trunks can be used in mixed gatekeeper, cluster, and gateway environments. Any intercluster trunk can be converted to support Q.SIG signaling. SIP trunks are also used to interconnect Cisco Unified CallManager with other SIP networks and applications. General trunk configuration procedure adds a new trunk first and then continues with trunk configuration. Cisco Unified CallManager trunk configuration can be verified on gateways and gatekeepers using show and debug commands.

© 2006 Cisco Systems, Inc. All rights reserved. CIPT1 v