Useful Presentation and Resources for Migrating to 9.1

We are helping couple of our customers move from 7.1 and 6.1 to 9.1 .

Licensing part is the most confusing part untill you get it ,

Here are few resources that are very useful License Migration Scenarios

Area Description Mailer
All Licensing Issues Inquiries on license policy, migration and procurement, please file a case with GLO licensing@cisco.com
Technical Support Inquiries on technical difficulties during upgrade process, please file a case with TAC http://tools.cisco.com/ServiceRequestTool/create/launch.do
Upgrade Planning and Design

(Partners only)

Inquiries on preparations and project planning needed for upgrades, and  available support services, please file a case with PDI Help Desk pdihd-uc@cisco.com
Upgrade Procedures Inquiries on upgrade process documentation and upgrade scenarios ask-drive-to-9@cisco.com
Readiness Assessment Tools Inquiries on use, performance, and results interpretation for Readiness Assessment Tools (web and iPad apps) cucm-toolsupport@cisco.com
UCSS

(Unified Communications Software Subscription)

Inquiries on  Cisco Unified Communications Software Subscription(UCSS) ucss-support@external.cisco.com
Advertisements

2500 user CUCM and vCPU

Interesting note about the 2500 user CUCM virtual configs: while we plan for 1 vCPU for a 2500-user class CUCM, and the OVA deploys a 1 vCPU configuration, there’s a little footnote in the docwiki and says you *might* need two: http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unified_Communications_Manager_(CUCM)#Notes_on_2500_user_VM_configurations

 

I noticed the footnote show up sometime in the last year, but have always mostly ignored it until now.  Our own internal  cluster (which is running ~800 devices on any given day) was starting to run into issues with DRF operations impacting availability in mid-morning.  DRF (which kicks off in the middle of the EST night) appeared to be taking successively longer to run/finish, was causing successively longer CPU spiking to occur.  People in several offices recently starting reporting issues with phones responding poorly and dropping calls in the morning, traced back to this.

 

TAC’s recommend: either move to 2x vCPU per the footnote, or deploy an 8.6(2) engineering special which corrects some buggy behavior with DRF/DRS.  So be aware, and you might just want to start planning for 2x vCPU for those mid-market CUCM customers besides.

SIP URI for audio video loopback

For those of you who collect and use these sorts of things, test@webex.com, provides an open SIP URI with both audio and video loopback (intentionally delayed several seconds). Great for having conversations with yourself, validating a new VCS-E install, or verifying your audio setup in a conference room. Just manage yourself with that mute key before Doctor Who shows up.

Found it here: https://supportforums.cisco.com/docs/DOC-23175

New Cisco End Points Coming

Just Few Highlights

• Going forward most phones will not be called “phones” but “smart desk phones”
New Series collaboration end points DX600 and Conference Phones 8831 ( Cisco probably trying to shrug of Cisco branded Polycom conference phones )
• As expected phones are now mini computers , literally other than added keyboard and different shape, You can expect everything in phone that you would expect in PC
• Cucm 7.1 with latest device pack for DX650 required at minimum
• Heavy Stress on making it cloud ready
• Phones can be installed with all kind of apps such as Jabber, Webex, google Play, VDI /VMware View

MeetingPlace 8.5 issue with CUCM 9.1

Last week Cisco stated that there was an issue with MeetingPlace 8.5 and compatibility to CUCM 9.1 do to the LDAP Schema and they did not know if they would get this to work correctly.  Just found an interesting update on this 

Before I checked this and found that the Doc Wiki stated the following…

 ***CUCM 9.1 support is limited to SIP trunk integration only, customers using LDAP integration via CUCM can’t migrate to CUCM9.1 due to LDAP schema changes in CUCM9.1 release. 

 Now it states….

http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.5_–_Compatibility_Matrix#Cisco_Unified_Communications_Manager_Compatibility

  • CUCM 6.1(5), 7.0(2), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0.1,9.1.1.20000-5 (previous 9.1 builds have LDAP issue)
  • CUCM-SME 7.1(3), 8.0, 8.5

Notes:

  • MeetingPlace with sRTP enabled requires UC Manager 7.0 and above to support sRTP.
  • CUCM 8.0(3) supports SIP Refers for multinode Cisco Unified MeetingPlace systems. Open a case with Cisco TAC against the Cisco Unified Communications Manager to obtain the latest Engineering Special (ES) or Service Update (SU) version of CUCM 8.0(3).
  • Ad-hoc (SCCP) meetings are not supported with CUCM 8.5 per known bug issue on UC Manager.
  • For more information, see Cisco Unified Communications Manager Compatibility
    • CUCM 9.1 support is limited to SIP trunk integration only, customers using LDAP integration via CUCM must use 9.1.1.20000-5 build

Thought I would pass this on for those who may be working a 9.1 upgrade but the customer is not ready to move from Meetingplace 8.5.

LAN QoS CCIE Voice Notes 6- Most Freaking Complex Thing I ever Learned –

If you can understand LAN QoS for CCIE Voice , Hats off to you , you have been blessed with patience , ambition and courage to deal with adverse adversity and other good motivation words you can think of ,

or in short you are just  smart ass ..

I had created following table to maintain my sanity and not be cranky and curse at CCIE voice program creator..

Lot of credit goes to Vik of ipexpert , His blogs are like my bible .. He has awesome 3 part series Campus QoS guide that is must read

http://blog.ipexpert.com/2011/05/16/campus-qos-part-1-classification-and-marking-on-the-catalyst-3750/

My Trick was run auto qos and then change only whats requested in question , I have listed in table what happens after you run Auto Qos

But before you know what to change , you have to know whats the current value ..So this table summarizes that.

Input Q AFTER AUTO QOS

sh mls qos inter queueing

If >>> Q says trust layer 2 markings or trust cisco phone ,

>>>then “auto qos voip trust” along with “mls qos trust cos”

 sh mls qos input-queue

DEFAULT TABLE AFTER AUTO QOS Q1 Q2 To Change this ( use this command )
Buffers 67 33 Global #mls qos srr-q input buffers 50 50
Bandwidth 90 10 Mls qos srr-q input 5 5 ( BE CAREFUL THIS IS WEIGHT )
Priority 0 10 Mls qos srr-q input priorty-q 2 ?( GENERALLY MIGHT HAVE TO CHANGE 15)
T1 8 34 mls qos  srr-queue input threshold 2 25 25
T2 16 66 mls qos  srr-queue input threshold 2 25 25
T3 Cannot be configured, CLEAR TILL its completely full

ON INPUT SIDE  ( Default Cos-3 and Cos5 values )after auto qos

sh mls qos maps cos-input-q

Queue Threshold To Change this
Cos 5 2 3 mls qos srr-queue input cos-map q 2 3
Cos 3 2 3 mls qos srr-queue input cos-map threshold 1 3

                              OUTPUT Q AFTER RUNNING AUTO QOS ON EGRESS SIDE

Step 1 : Priority Q is enabled by default after running auto QoS ( Make sure to confirm the Question )

Step 2:  Default QSet is 1  –Make sure you are modifying QSET 1 or if Question ask , change the QSET

sh mls qos queue-set 1

DEFAULT TABLE AFTER AUTO QOS 1 2 3 4 To Change this ( use this command )
Buffers 10 10 26 54 mls qos queue-set output 1 buffers 20 10 26 54
Threshold 1 138 138 36 20 mls qos queue-set output 1 threshold 1 135 135 92 138
Threshold 2 138 138 77 50 mls qos queue-set output 1 threshold 1 135 135 92 138
Reserved 92 92 100 67 mls qos queue-set output 1 threshold 1 135 135 92 138
Maximum 138 400 318 400 mls qos queue-set output 1 threshold 1 135 135 92 138

ON OUTPUT ( EGRESS ) SIDE  ( Default Cos-3 and Cos5 values )after auto qos

sh mls qos maps cos-input-q

Queue Threshold To Change this
Cos 5 1 3 mls qos srr-queue output cos-map queue 1 5
Cos 3 2 3 mls qos srr-queue output cos-map queue 1 5

CCIE Voice Notes 5 Steps for Configuring Phoneview for Cisco Unity

PhoneView for Cisco Unity

1)     Make end user >>associate phone >>standard cti enabled

2)     Enter that username in PhoneSystem >enable phoneview>>> username password

3)     Go to cisco unity message box >>>skip pin when calling from known extension >>

4)     Go to Edit >>phone menu >>Check finding message by locator >>

5)     After Logon, Play >>check third box >>users new messeges automatically

%d bloggers like this: