There are a bunch of dates on the end of life milestone datasheets, and I'm looking for some clarification on what some of them signify: 1. End-of-SW Maintenance - This is the last date Cisco will release new code, or fix non-security related bugs. 2. End-of-Failure Analysis - I'm not sure what this date actually means?   Can someone expand on it? 3. End-of-Security Support - The last date a software fix will be released to fix a security issue. The other dates make sense to me (End-of-Sale, Last Ship, End-of-Contract Renewal, Last Date of Support, etc). I'm going to focus on the 3560G; the End-of-Life milestone dates are seen here: End-of-Sale and End-of-Life Announcement for the Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches - Cisco The last date of maintenance releases is listed as Jan 2014.      If I go to the download page for that product, I see multiple software images released after that date, with the latest being February 2015 (12.2(55)SE10).    A year after the listed end-of-SW date. The release notes show multiple caveats resolved in versions released after Jan2014 which don't appear to be security related.   Release Notes for the Catalyst 3750, 3560, 2975, 2960-S, and 2960 Switches, Cisco IOS Release 12.2(55)SE and Later - Cis… Is it true to say that Cisco still releases some non-security bug fixes after the End-of-SW date?    If so, what does this date actually signify?   That Cisco isn't obligated to fix it, but they usually do? I need to explain what these dates mean to a customer to help them determine which milestone date to focus on when refreshing switches.  I dont want to tell them to go by the End-of-SW date because bug's wont be fixed after that....then have them look into it and see that isn't true. ... View more

I can't seem to find this information in the data sheet or release notes...   The 4300 ISR routers are positioned to replace the G2 ISRs going forward.   Does anyone know if they support MGCP?   If so, what versions of CUCM are required? I have a new install of CUCM v10.5 and the only models listed are the 4431 and 4451.    The model I am most interested in right now is the ISR 4331.  We have customers using MGCP controller PRIs and FXS ports on G1 routers, so I'd rather stick with that design than move them to SIP/H323 integration. ... View more

I am doing a cobra migration from Unity 4 to Unity Connections 8.5 and have a question about what to expect with the import.   When I move their voice messages over, I have heard that in older cobra imports it would mark all messages as unread with a time stamp of the import.   Is this still the case with 8.5? ... View more

I am looking for a TCL script that can be run on a SRST/CME gateway for backup to a unity connection call handler.   After looking at the BACD scripts for CME I dont think it will work because it requires the phones to be registered locally so it can watch the on-hook/off-hook status.    I have tested this out, and if you config a aa-hunt option for a number that isnt a configured ephone or ephone hunt group you get stuck in the queue. So the question is, do you guys know of any basic AA tcl scripts?    It just needs to play a prompt, and dial an extension based on a DTMF input of 1-9 (and 0).    I will then config dial-peers to send those extensions back to UCM.     This will only be used in UCN failure situations, so it really doesnt have to be fancy at all. ... View more

I have calling party transformation setup, and working correctly when a phone has a DID associated to it.    Unfortunately if a caller goes to a call handler, then dials the users extension it no longer works. Working:    Dial 555-1212 (DID) --> Rings on cisco phone with the proper localized number displayed. Not Working:    Dial 555-1213, at Call Handler dial DN 1234 -->   Rings on cisco phone with the full globalized number Is there a way to make this work going thru the call handler?   My guess is that the phone is seeing the call comming from Unity CN first, not appying the transformation, then the display is updated to show the outside callers info. -Mike ... View more

I am configuring an SSL and IPSec VPN where I would like to tunnel all traffic except for traffic going to 10.0.0.0/16. For the group policy I set the policy to "Exclude Network List Below", and then specified a network list which has a permit 10.0.0.0/16 statement (I have also tried making this deny). At that point I connect to the VPN and it shows that it is "Mode: All Traffic".   When I go to the route detail tab it shows a 0.0.0.0/0.0.0.0 for Secured Routes, but nothing under the Non-Secured Routes. I've tried configuring it again from scratch, and making sure the Connection Profiles are using the correct group policy.   I verified this buy changing it to split tunnel, and at that point when I connect it sets the correct network under "Secured Routes". Any suggestions? ... View more