Cisco CUCM With Cube 9.0 Configuration Guide

8/9/2019 Cisco CUCM With Cube 9.0 Configuration Guide

1/61

SIP Trunking ConfigurationGuide for Cisco UnifiedCommunications Manager(CUCM) Version 9.0.1.11005-1

with Cisco Unified BorderElement (CUBE)


2/61

SIP Trunking Conf igura t ion Guide for Cisco Unif ied Comm unicat ionManager w i th CUBE

1 Copyright 5/15/2013. XO Communications, LLC. All rights reserved. XO, the XO design logo, and all relatedmarks are trademarks of XO Communications, LLC. All other trademarks are property of their respective owners.

Table of Contents

Introduction ....................................................................................................... 3 Executive Summary..3 Equipment Hardware and Software Requirements ...............................................5Test Configurations ...............................................................................................6CUCM Configurations ..7 CUBE Configuration Details. ............................................................................... 42Equipment Configuration Files and Information 48


3/61



1. Introduction

This document contains the test results of the SIP Trunking evaluation performed on theCUCM version 9.0.1.11005-1 connected to a Cisco 2821 Integrated Services Router(ISR) running CUBE software version c2800nm-advipservicesk9-mz.151-4.M6.bin and aCisco 2432-24FXS Internet Access Device (IAD) acting as a router. The Cisco ATA187was used to test FAX pass through and FAX Relay. The ATA187 was connected to theCisco 3560 PoE switch. The Cisco IAD was connected to the Juniper Networks ERX1400 via a T1 configured for Point-to-Point Protocol (PPP). Cisco 7961 IP phonesrunning SCCP software downloaded from the CUCM were connected to the CUCM viaa Cisco 3560 Power over Ethernet (PoE) switch. The Cisco 2821 ISR was alsoconnected to the Cisco 3560. The Cisco 3560 switch is up linked to the Cisco IAD viaFast Ethernet port 0/0. The customer LAN will connect directly to the Cisco IAD via a

separate Ethernet port and not the Cisco 3560 switch which is reserved only for CiscoIP phones.

2. Executive SummaryThis configuration guide provides the settings used during the lab evaluation for theCUCM with CUBE with XO Communications SIP Trunking service. The following is asummary of the issues addressed and the limitations found during the lab evaluation.

When configuring the customer for SP1 or SP2, the MoH Server codec mustbe set accordingly.CUBE SIP Profile Rules are still required to correct the MoH problem.

CUBE ip address trusted authenticate feature command is enabled bydefault.Cisco does not support SIP REFER method for outbound calls.FAX was tested using the Cisco ATA187. FAX pass-through using SP2 doesnot work properly.

CUCM MoH Server Codec Setting:Make sure that we match the codec package to make MoH work properly. Whenconfiguring the customer for SP1 or SP2, the MoH Server codec must be setaccordingly to G.711ulaw for SP1 and G.729 for SP2 as discussed in detail insection 5.15 of this report.

CUBE SIP Profile Rules Are Required to Correct the MoH ProblemThese configuration commands are still required in the CUBE sip profile section ofthe configuration for the remote party to hear MoH when the call is placed on holdfrom a CUCM phone.


4/61



CUBE ip address trusted authenticate Feature Command is Enabled by

DefaultThis is on by default and XO IP address must be put in the proper command to allowthe XO IP address.

Cisco Does Not Support SIP Refer For Outbound CallsTransfers with CUCM will use traditional reinvites; SIP REFER not used.

SP1 and SP2 G.711 Pass-through and T.38 FAX Issues and Workarounds

Pkg Codec DTMF Fax

1 G.711 RFC 2833 (in-band DTMF isNOT supported)

G.711 pass-through andT.38 aresupported

2 G.729a/G.711 RFC 2833 (in-band DTMF isNOT supported)

(G.711 pass-through is NOTsupported.)T.38 issupported

Registration: Static


5/61



3. Equipment Hardware and Software Requirements for Testing

1. CUCM Servera. Hardware: Cisco MCS 7800 Series Product No MCS7825H3-K9-CMB2b. Software Version: CUCM 9.0.1.11005-1

2. Cisco 2821 ISR running CUBE softwarea. Hardware: Cisco 2821 ISRb. 1 PVDM2-32 and 2 PVDM2-48 DSP modulesc. IOS software versionc2800nm -advipservicesk9-mz.151- 4.M6.bin

3. Cisco Unity Connection (CUC) Voice Mail Server

a. Hardware: Cisco MCS 7800 Series Product No MCS7825H3-K9-CMB2b. Software Version: CUC 7.0.1.11000-13-2

4. CUCM and Cisco Unity Connection (CUC) PC GUI Accessa. Microsoft Internet Explorer version 8.0.6001.18702

5. Cisco Phonesa. Cisco 7961b. Software Version: SCCP41.9-3-1-1S

6. Cisco 2432-24FXS IADa. Software Version: c2430-mz.xo

7. Cisco Catalyst 3560 PoE series P-24a. Software Version: c3560-advipservicesk9-mz.122-44.SE2.bin

8. SIP Trunking PBXs Approved for Usea. Cisco: 2811 CME, 2821 CME, Cisco UC520b. Digium IP PBXc. Avaya: IPO 406, IPO 500


6/61



4. Test Configurations4.1. Lab Configuration : CUCM with CUBE running on a Cisco 2821 ISR and the Cisco

2432-24FXS IAD Acting as a Router

The diagram below shows the configuration used during lab testing. The CUCMdoes not support fax directly. External devices such as a Cisco 2800 or 3800series ISR running CUBE software, a Cisco 2900 or 3900 Series ISR G2 runningCUBE software, a Cisco ATA187, or a CUCM SIP trunk to a Right FAX server canbe used. The lab tested FAX pass through and T.38 FAX using a Cisco ATA187.No FAX or modem testing was performed on the Cisco 2821 ISR running CUBEsoftware.

TN#6AnalogPhone

FXS Port1

XO VoIP Network

CUCM(MCS7825H3)

Cisco Catalyst3560 Series

PoE-24 Switch

XO DemarcRouter

Cisco 2821 ISR(CUBE)

Cisco ATA187

FXS Port2

TN#5FAX

TN#3Cisco IP

Phone7961

TN#2Cisco IP

Phone7961

TN#1Cisco IP

Phone7961

CUC(MCS7825H3)

Note: Above lab setup only shows main lab network elements.


7/61



5. Test Bed Configuration Files: CUCM Configuration Details

5.1 CUCM Configuration Details5.1.1 The following sections contain configuration information that is useful in configuring

the CUCM and CUBE.

5.2 CUCM Configuration Details

5.2.1 CUCM Region and Device Pool Configuration Description

5.3 The following sections contain a brief description of the CUCM region and device poolconfigurations used during testing.

5.3.1 CUCM Region and Device Pool Configuration for SP1 with CUBE

5.4 In this setup there is only one region called the default region and it is configured to

use G.711 codec. The device pool used is the default device pool. All CUCM phonesand the SIP trunk are assigned to the default device pool and use the G.711 codec tocommunicate over the default region and over the SIP trunk.

5.4.1 CUCM Region Screen Capture for SP1 with CUBE

CUCM Region Information Screen Capture for SP1 with CUBE


8/61



5.5 CUCM Device Pool Screen Capture for SP1 with CUBE

Default Device Pool Configuration Screen Capture Part 1


9/61





10/61





11/61



5.6. CUCM Region and Device Pool Configuration for SP2 with CUBEIn this setup there are two regions where one is the default region and the other isnamed the XO g729 region. The default region is configured to use the G.729codec. The XO g729 region is configured to use the G.729 codec. All CUCMphones are configured in the default device pool and the XO SIP trunk isconfigured in the XO SIP Trunk Device Pool. All phones communicate with eachother over the default region using G.711 or G.722 the largest codecs available.When the phones establish an outbound call or receive an inbound call over theSIP trunk these calls are processed over the XO g729 region configured for G.729codec. On the CUCM a single SIP trunk can only support one codec. This meansthat all calls whether they are inbound or outbound over the SIP trunk will establishusing only the G.729 codec.

5.6.1. CUCM Region Screen Capture for SP2 with CUBE

XO G.729 Region Information Screen Capture for SP2 with CUBE


12/61



5.7. CUCM Device Pool Screen Capture for SP2 with CUBE

G.729 SIP Trunk Device Pool Information Screen Capture Part 1


13/61



G.729 SIP Trunk Device Pool Information Screen Capture Part 2


14/61



G.729 SIP Trunk Device Pool Screen Capture Part 3


15/61



5.8.1. CUCM SIP Profile and SIP Trunk Configuration Screen Captures

5.8.1.1. CUCM SIP Profile Configuration Screen CaptureThis section contains the SIP Profile used during service package 1 and 2 testing.

SIP Profile Configuration Screen Capture Part 1


16/61





17/61





18/61





19/61



5.9. CUCM SIP Trunk Security Profile Configuration5.9.1. This section contains the SIP Trunk Security Profile used during SP1 and

SP2 testing.

CUCM SIP Trunk Security Profile Screen Capture


20/61



5.10. CUCM SIP Trunk Screen Captures for SP1This section contains the SIP trunk settings used during SP1 testing. Please note thatthe Media Termination Point Required box is not checked. This allows CUBE toperform the Early Offer/Delayed Offer (EO/DO) conversion. The screen captures inthis section use a 4 digit phone extension. Within the Call Routing Information, theInbound Calls section has the Significant Digits* set to 4 and the option for RedirectingDiversion Header Delivery - Inbound is checked. Within the Outbound Calls sectionthe Calling Party Selection* is set to Originator and the Caller ID DN is left blankbecause CUBE is configured to add the NPA-NXX via a SIP profile rule. The option forRedirecting Diversion Header Delivery - Outbound is checked. In the CUCM withCUBE SIP Trunk Screen Capture Part 3 under the SIP Information parameters theDestination Address must be set to CUBE's IP address. CUBE's sip-server addressmust be set to the Sonus Networks NBS signaling IP address.

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 1


21/61





22/61





23/61





24/61



5.11. CUCM SIP Trunk Screen Captures with CLID Blocked for SP1The screen captures in this section show the SIP trunk configuration settingswhere the caller ID is blocked by using a separate route pattern. In the CUCMwith CUBE CLID Blocked SIP Trunk Screen Capture Part 3 under the OutboundCalls section, the Calling Line ID Presentation* and the Calling NamePresentation* fields are set to Restricted. This SIP trunk will block the caller IDfor all outbound calls. In the same screen capture under the SIP Informationparameters the Destination Address must be set to CUBE's IP address. CUBE'ssip-server address must be set to the Sonus Networks NBS signaling IP address.

CUCM with CUBE CLID Blocked SIP Trunk Configuration Screen Capture Part 1


25/61





26/61





27/61





28/61



5.12. CUCM SIP Trunk Screen Captures for SP2This section contains the SIP trunk settings used during SP2 testing. Please notethat the Media Termination Point Required box is not checked. This allows CUBE toperform the Early Offer/Delayed Offer (EO/DO) conversion. The screen captures inthis section use a 4 digit phone extension. Within the Call Routing Information, theInbound Calls section has the Significant Digits* set to 4 and the option forRedirecting Diversion Header Delivery - Inbound is checked. Within the OutboundCalls section the Calling Party Selection* is set to Originator and the Caller ID DN isleft blank because CUBE is configured to add the NPA-NXX via a SIP profile rule.The option for Redirecting Diversion Header Delivery - Outbound is checked. In theCUCM with CUBE SIP Trunk Screen Capture Part 3 under the SIP Informationparameters the Destination Address must be set to CUBE's IP address. CUBE'ssip-server address must be set to the Sonus Networks NBS signaling IP address.



29/61





30/61





31/61





32/61



5.13. CUCM SIP Trunk Screen Captures with CLID Blocked for SP2The screen captures in this section show the SIP trunk configuration settings wherethe caller ID is blocked by using a separate route pattern. This SIP trunk will blockthe caller ID for all outbound calls. In the CUCM with CUBE CLID Blocked SIPTrunk Screen Capture Part 3 under the Outbound Calls section, the Calling Line IDPresentation* and the Calling Name Presentation* fields are set to Restricted. Inthe same screen capture under the SIP Information parameters the Destination

Address must be set to CUBE's IP address. CUBE's sip-server address must be setto the Sonus Networks NBS signaling IP address.



33/61





34/61





35/61





36/61



5.14. CUCM Phone Configuration Using a Four Digit Extension

CUCM Phone Screen Configuration Using a Four Digit Extension


37/61



5.15. CUCM MoH Server Codec SelectionWhen configuring the customer for SP1 or SP2, the MoH Server Codec settingunder CUCM administration, Service Parameters, Cisco IP Voice Media Streaming

Application, Clusterwide Parameters, the codec selection displayed underSupported MoH Codecs must be set to G.711ulaw for SP1 and G.729 for SP2accordingly. G.711ulaw is the system default. The codec must be selected andsaved as shown in the screen captures below. The highlighted codec indicates thecodec that is currently in use.

MoH Server Codec Screen Capture Part 1


38/61



MoH Server Codec Screen Capture Part 2


39/61



5.16. CUCM Enterprise Parameters: DSCP Bit Settings for Signaling and MediaThe screen capture below shows the DSCP bit settings for the CUCM phones forsignaling and media. The DSCP for Cisco CallManager to Device Interface*parameter is the signaling setting which is AF31 and the DSCP for PhoneConfiguration* parameter is the media setting which is EF. The CUCM servermust be rebooted for these changes to take effect.


40/61



5.17. CUCM Conference Bridge Configuration for SP1The screen capture below shows the CUCM conference bridge resourceparameters listed under CUCM Administration, Media Resources for the defaultCUCM conference bridge. The CUCM software conference bridge was used toverify SP1 three and four way conference bridging test cases. This is asoftware resource that runs on the CUCM server itself versus the externalconference bridge resource for SP2 which must run on CUBE due to the G.729codec requirement discussed in the next section. This screen can also be usedto verify that the CUCM conference bridge resource is registered by checkingthe registration state of the device.


41/61



5.18. CUCM Conference Bridge Configuration for SP2The screen capture below shows the Conference Bridge resource parameterslisted under CUCM Administration, Media Resources. An external conferencebridge resource is configured using CUBE which registers with the CUCM. Thisconference bridge resource was used in testing SP2 conference bridging forthree and four way conference calls. When the CUCM is configured for SP1which uses the G.711 codec, the CUCM uses its own software conferencebridge. However when the CUCM is configured for SP2 which uses the G.729codec, the conference bridge must be supported on an external device such asCUBE. This screen can also be used to verify that the CUBE conferencebridge resource is registered with the CUCM by checking the registration state.


42/61



6. CUBE Configuration Details

6.1. The following sections provide a brief description regarding CUBEs flow -throughversus flow-around modes for media and which was used during lab testing.6.1.1. Correcting the CUCM Diversion Header Problem With CUBE When Using

4 Digit CUCM Phone Extensions6.1.2. A diversion header problem was discovered where the NPA-NXX is not

prefixed to the four digit extension number for the user portion of thediversion header. This problem affected PSTN-to-PSTN call transfers thatuse Call Forward Always (CFA), Call Forward On Busy (CFOB), and CallForward No Answer (CFNA) where a four digit extension is used for theCUCM phones because the original caller ID is not delivered to the finalPSTN destination. When the CUCM is configured to use CUBE running ona Cisco 2821 ISR, a SIP profile can be used to modify the diversion header

to correct this problem. For the lab scenario a SIP profile was written forCUBE to modify the diversion header by adding the NPA-NXX to the 4 digitextension in the user portion of the diversion header. What follows is thesip profile rule used during lab testing:

6.1.3. voice class sip-profiles 16.1.4. request INVITE sip-header Diversion modify ""

""

6.1.5. Please note that a customer CUCM environment may have several NPA-NXXs or other phone extension digit configurations that will require differentSIP profile rules and translation rules to be designed using CUBE that are

unique to each customer environment.6.1.6. CUBE SIP Profile Rules to Correct MoH Issue6.1.7. These configuration commands are still required in the CUBE sip profile

section of the configuration for the remote party to hear MoH when the callis placed on hold from a CUCM phone.

6.1.8. CUBE SIP Profile Rules for MoH to Work Properly:6.1.9. voice class sip-profiles 16.1.10. request REINVITE sdp-header Audio-Attribute modify "inactive"

"sendrecv"6.1.11. request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv"

6.1.12. response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv"6.1.13. CUBE DSCP Bit Settings for Signaling and Media6.1.14. The CUBE voip dial peer default DSCP bit settings for signaling is AF31

and for media is EF. These settings do not appear in the configurationwhen a show configuration is executed at the CLI prompt. However, thesettings can be display ed by executing the command show dial -peer voice# at the CLI prompt for each voip dial peer where the # represents the dialpeer number.


43/61


44/61



Cisco ATA187 Device Information Configuration Screen Capture 2


45/61



6.4. Configuring the Cisco ATA187Using the Cisco provided instructions for the ATA187, configure the device such thatit shows up in the Cisco Unified CM Administration under Device, Phones asregistered with the CUCM as shown in the first line item entry under Device NameATAF02572784B29 in the screen capture below.


46/61


47/61



6.6. Configuring the Cisco ATA187 for T.38 FAX RelayIn the CUCM screen capture above, click on the ATA187 in question, then scrolldown to the Product Specific Configuration Layout section and set the Fax Mode*option to T.38 Fax Relay as shown in the screen capture below and save. No othersettings were modified.

ATA187 Fax Relay Screen Capture

6.6.1. CUBE FAX Pass Through and T.38 FAX Relay Commands

This section contains the FAX specific commands that are required in the CUBEconfiguration for FAX Pass Through and T.38 FAX Relay to work properly.

For FAX pass through, under the voice service voip section of the configuration,add the command fax protocol pass -through g711ulaw. For FAX relay underthe voice service voip section of the configuration, add the command faxprotocol t38 version 0 ls-redundancy 0 hs- redundancy 0 fallback none.


48/61



7. Equipment Configuration Files and Information

This section contains the Cisco 2821 ISR running CUBE, Cisco 3560 PoE, andCisco 2432-24FXS IAD and Juniper 1400 ERX configuration files used duringtesting. It also contains a BroadSoft and Sonus Networks PSX screen capturefor settings that need to be checked for CUCM with CUBE to work properly inproduction.

7.1. Cisco 2821 ISR Running CUBE SoftwareThe following sections contain the CUBE test configuration used during SP1 andSP2 testing.

7.1.1. CUBE Configuration File for Service Package 1

CUBE's sip-server address must be set to the Sonus Networks NBS signaling IPaddress.

C2821CUBE#wr tBuilding configuration...

Current configuration : 2982 bytes!! Last configuration change at 18:42:51 UTC Mon Apr 8 2013version 15.1service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname C2821CUBE!boot-start-markerboot-end-marker!!no logging bufferedenable secret 5 $1$dgKR$TQ5lvonJvCjRAWx7.cyIX0!no aaa new-model!!dot11 syslogip source-route!!ip cef!


49/61



!!no ip domain lookupno ipv6 cef!multilink bundle-name authenticated!!!!!!!voice service voipip address trusted listipv4 205.158.163.0 255.255.255.0

allow-connections sip to sipno supplementary-service sip moved-temporarilyredirect ip2ipfax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-

through g711ulawno fax-relay sg3-to-g3sipheader-passingerror-passthruearly-offer forcedmidcall-signaling passthrusip-profiles 1

!voice class media 1!voice class codec 1codec preference 1 g711ulaw

!voice class sip-profiles 1request INVITE sip-header Diversion modify ""

""request REINVITE sdp-header Audio-Attribute modify "inactive" "sendrecv"request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv"response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv"

!!!!voice translation-rule 1rule 1 /^$....$$/ /469387\1/


50/61



!!voice translation-profile Sonus_NBS_Outgoingtranslate calling 1

!!voice-card 0dsp services dspfarm

!crypto pki token default removal timeout 0!!!!license udi pid CISCO2821 sn FHK1023F1J8archivelog confighidekeys

!redundancy!!!!!!!!!!interface GigabitEthernet0/0description Connection to CUCM3560 port 23ip address 201.1.3.252 255.255.255.0duplex autospeed auto

!interface GigabitEthernet0/1no ip addressshutdownduplex autospeed auto

!no ip forward-protocol ndno ip http serverno ip http secure-server!


51/61



!ip route 0.0.0.0 0.0.0.0 201.1.3.1!!!!!!!control-plane!!!mgcp fax t38 ecm!mgcp profile default!!dial-peer voice 10 voipdescription Outgoing dial-peer to Sonus NBStranslation-profile outgoing Sonus_NBS_Outgoingdestination-pattern .Tsession protocol sipv2session target sip-servervoice-class codec 1voice-class sip dtmf-relay force rtp-ntevoice-class sip early-offer forcedvoice-class sip profiles 1dtmf-relay rtp-nteno vad

!dial-peer voice 11 voipdescription Outgoing dial-peer to CUCMdestination-pattern 46938739..session protocol sipv2session target ipv4:201.1.3.254voice-class codec 1voice-class sip dtmf-relay force rtp-ntevoice-class sip early-offer forceddtmf-relay rtp-nteno vad

!!sip-uasip-server ipv4:205.158.163.138

!


52/61



!!banner login ^C** Welcome to the Cisco2821 running CUBE **^C!line con 0session-timeout 120exec-timeout 60 0absolute-timeout 180flowcontrol hardware

line aux 0line vty 0 4exec-timeout 3600 0password labbgp1logintransport input all

!scheduler allocate 20000 1000end

C2821CUBE#

7.1.2. CUBE Configuration File for Service Package 2CUBE's sip-server address must be set to the Sonus Networks NBS signaling IPaddress.

C2821CUBE#wr tBuilding configuration...

Current configuration : 3378 bytes!! Last configuration change at 19:01:56 UTC Mon Apr 8 2013version 15.1service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname C2821CUBE!boot-start-markerboot-end-marker!!no logging bufferedenable secret 5 $1$dgKR$TQ5lvonJvCjRAWx7.cyIX0


53/61



!no aaa new-model!!dot11 syslogip source-route!!ip cef!!!no ip domain lookupno ipv6 cef!multilink bundle-name authenticated!!!!!!!voice service voipip address trusted listipv4 205.158.163.0 255.255.255.0

allow-connections sip to sipno supplementary-service sip moved-temporarilyredirect ip2ipfax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-

through g711ulawno fax-relay sg3-to-g3sipheader-passingerror-passthruearly-offer forcedmidcall-signaling passthrusip-profiles 1

!voice class media 1!voice class codec 1codec preference 1 g729r8codec preference 2 g711ulaw

!voice class sip-profiles 1


54/61


55/61



!interface GigabitEthernet0/1no ip addressshutdownduplex autospeed auto

!no ip forward-protocol ndno ip http serverno ip http secure-server!!ip route 0.0.0.0 0.0.0.0 201.1.3.1!!!!!!!control-plane!!!mgcp fax t38 ecm!mgcp profile default!sccp local GigabitEthernet0/0sccp ccm 201.1.3.254 identifier 1 version 7.0sccp!sccp ccm group 1bind interface GigabitEthernet0/0associate ccm 1 priority 1associate profile 3 register CFB0018191A4CB0

!dspfarm profile 3 conferencecodec g729ar8codec g729r8codec g711ulawmaximum sessions 8associate application SCCP

!dial-peer voice 10 voipdescription Outgoing dial-peer to Sonus NBS


56/61



translation-profile outgoing Sonus_NBS_Outgoingdestination-pattern .Tsession protocol sipv2session target sip-servervoice-class codec 1voice-class sip dtmf-relay force rtp-ntevoice-class sip early-offer forcedvoice-class sip profiles 1dtmf-relay rtp-nteno vad

!dial-peer voice 11 voipdescription Outgoing dial-peer to CUCMdestination-pattern 46938739..session protocol sipv2session target ipv4:201.1.3.254voice-class codec 1voice-class sip dtmf-relay force rtp-ntevoice-class sip g729 annexb-allvoice-class sip early-offer forceddtmf-relay rtp-nteno vad

!!sip-uasip-server ipv4:205.158.163.138

!!!banner login ^C** Welcome to the Cisco2821 running CUBE **^C!line con 0session-timeout 120exec-timeout 60 0absolute-timeout 180flowcontrol hardware

line aux 0line vty 0 4exec-timeout 3600 0password labbgp1logintransport input all

!scheduler allocate 20000 1000end


57/61



C2821CUBE#

7.2. Cisco 3560 PoE Configuration FileThis file contains the device configuration used during the evaluation.

CUCM3560#wr tBuilding configuration...

Current configuration : 3963 bytes!version 12.2no service pad

service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname CUCM3560!boot-start-markerboot-end-marker!enable secret 5 $1$T/F4$rIWfQ68OVzIO7yXqFxU0z1!no aaa new-modelsystem mtu routing 1998vtp mode transparentip subnet-zero!!!crypto pki trustpoint TP-self-signed-3561089152enrollment selfsignedsubject-name cn=IOS-Self-Signed-Certificate-3561089152revocation-check nonersakeypair TP-self-signed-3561089152

!!crypto pki certificate chain TP-self-signed-3561089152certificate self-signed 0130820240 308201A9 A0030201 02020101 300D0609 2A864886 F70D0101

0405003031312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D

4365727469666963 6174652D 33353631 30383931 3532301E 170D3933 30333031

30303030


58/61



35305A17 0D323030 31303130 30303030 305A3031 312F302D 0603550403132649

4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D3335363130

38393135 3230819F 300D0609 2A864886 F70D0101 01050003 818D003081890281

8100A233 FA77DC4C 79C0503F E8067FFD 629619E3 12F8CE94 ACBAB5B9 A7A6787F

DF892A30 8B0ADB48 869FF69D 14D3E262 FCC507AD 7FE382C10D1C3527 A1248C79 A0E58516 A8AA5928 7F66A66B B11C8C9B 50AE7253 CFFE55C3 58879021

9790C69697C57B28 8C387F05 0EBBFF92 B630154D 516B9AAE 6127E87C 490C57B6

E294A5A2F6A70203 010001A3 68306630 0F060355 1D130101 FF040530 030101FF

30130603551D1104 0C300A82 0843434D 33353630 2E301F06 03551D23 04183016

801405B276A81F94 38A596E0 20B6DCE5 9975EF1A 714B301D 0603551D 0E041604

1405B276 A81F9438 A596E020 B6DCE599 75EF1A71 4B300D06 092A8648 86F70D01

0104050003818100 6E703269 5AC65206 E33DB499 5D0A7BC5 25331F18 DB839656

96D586DE25BF6112 81585C1E 08A2331F AFE173E1 587BEE7C 4A726698 C3DA2709

C0E36E459F7881BE 8E707424 CB5EE28E 446402E2 0217A5FD F25D5D0D F0A045C0

AD8D830579B1C9E5 7DBF1E6B 4AA13B9A 75DF2E79 8A948C0C F8A65AEA

8E2E105C 961ABD0F FFB8A470quit

!!!!!spanning-tree mode pvstspanning-tree extend system-id!vlan internal allocation policy ascending!vlan 10,99-101,200!!!!


59/61



interface FastEthernet0/1description Connection to Cisco Unified Call Managerswitchport access vlan 10switchport mode accessspeed 100duplex full

!interface FastEthernet0/2description Connection to Cisco Unity Connection Voice Mailswitchport access vlan 10switchport mode accessspeed 100duplex full

!interface FastEthernet0/3switchport access vlan 10switchport mode access








!


60/61



interface FastEthernet0/11switchport access vlan 10switchport mode access

!interface FastEthernet0/12!interface FastEthernet0/13!interface FastEthernet0/14!interface FastEthernet0/15!interface FastEthernet0/16!interface FastEthernet0/17!interface FastEthernet0/18!interface FastEthernet0/19!interface FastEthernet0/20!interface FastEthernet0/21!interface FastEthernet0/22!interface FastEthernet0/23!interface FastEthernet0/24switchport access vlan 10

!interface GigabitEthernet0/1!interface GigabitEthernet0/2!interface Vlan1no ip addressshutdown

!interface Vlan10description CUCM3560 Telnet Connectionip address 201.1.3.249 255.255.255.0

!ip classlessip http serverip http secure-server


61/61


!!!control-plane!banner login ^C** Welcome to the CUCM 3560PoE **^C!line con 0line vty 0 4password labbgp1login

line vty 5 15password ciscologin

!end

CUCM3560#

Cisco CUCM With Cube 9.0 Configuration Guide

Documents

Transcript of Cisco CUCM With Cube 9.0 Configuration Guide