The cleanup is "no sccp/sccp" which drops everything. I wouldn't want to automate that without being really careful there are no active conferences.
From: Lelio Fulgenzi [mailto:le...@uoguelph.ca] Sent: 20 February 2014 10:59 AM To: Eric Pedersen Cc: cisco-voip@puck.nether.net; Ryan Ratliff (rratliff); Brian Meade (brmeade) Subject: Re: [cisco-voip] CUCM engineering special versions Thanks Eric. It should be easy enough to set up an rsh script to monitor the IOS routers for inactive conference sessions and to clean those up as required. If the frequency gets high, then we'd have to consider the ES. Cheers,Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ________________________________ From: "Eric Pedersen" <peders...@bennettjones.com<mailto:peders...@bennettjones.com>> To: "Lelio Fulgenzi" <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>, "Brian Meade (brmeade)" <brme...@cisco.com<mailto:brme...@cisco.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>, "Ryan Ratliff (rratliff)" <rratl...@cisco.com<mailto:rratl...@cisco.com>> Sent: Thursday, February 20, 2014 12:26:02 PM Subject: RE: [cisco-voip] CUCM engineering special versions Lelio, The bug we're hitting is CSCum05362. Conference sessions are getting stuck on our ISRs: #show sccp conn sess_id conn_id stype mode codec sport rport ripaddr conn_id_tx 146265514 134359424 conf inactive UNKNOWN 20026 0 UNKNOWN Total number of active session(s) 1, and connection(s) 1 It's bad because CUCM thinks there are no active conferences, but this stuck call is consuming a conference session on the ISR. CUCM then may try to start too many conferences on the ISR, causing calls to drop. The stuck calls don't happen with every conference that's created and I couldn't figure out the exact scenario that's causing it. If you use hardware conference bridges you may want to monitor them to see if you run into this. Other than this, we haven't had any problems with 9.1(2)SU1. Eric From: Lelio Fulgenzi [mailto:le...@uoguelph.ca] Sent: 19 February 2014 6:30 PM To: Brian Meade (brmeade) Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>; Ryan Ratliff (rratliff); Eric Pedersen Subject: Re: [cisco-voip] CUCM engineering special versions That's good info. Thanks. We're planning on an upgrade at end of April and we did most of our tests with 9.1(2), but we're planning on using 9.1(2)SU1 for the upgrade, since we're rebuilding beginning mid-April. Chances are we'll stick with 9.1(2)SU1 and see what caveats SU2 fixes when it comes out. Cheers... Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ________________________________ From: "Brian Meade (brmeade)" <brme...@cisco.com<mailto:brme...@cisco.com>> To: "Lelio Fulgenzi" <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>, "Eric Pedersen" <peders...@bennettjones.com<mailto:peders...@bennettjones.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>, "Ryan Ratliff (rratliff)" <rratl...@cisco.com<mailto:rratl...@cisco.com>> Sent: Wednesday, 19 February, 2014 7:51:49 PM Subject: RE: [cisco-voip] CUCM engineering special versions Lelio, I’m not sure what the schedule is like but looking at previous SU releases, they usually come out about every 4-5 months. 9.1(2)SU1 came out 12/06/2013 so I’d say there would probably be one coming out around April. Copying Ryan to see if he knows the target date. Brian From: Lelio Fulgenzi [mailto:le...@uoguelph.ca] Sent: Wednesday, February 19, 2014 7:16 PM To: Brian Meade (brmeade); Eric Pedersen Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] CUCM engineering special versions Eric - Can you share the bug your hitting? Brian - do you know when th next SU is scheduled/planned for? Sent from my iPhone On 2014-02-19, at 6:42 PM, "Brian Meade (brmeade)" <brme...@cisco.com<mailto:brme...@cisco.com>> wrote: Eric, The SU version numbers don’t exactly line up with the ES version numbers. 9.1.2.11900-12 (9.1.2 SU1) was actually built off of the 9.1.2.11006-1 Engineering Special so the 9.1.2.11021.1 ES he told you to go to will indeed be a newer release. Thanks, Brian From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Eric Pedersen Sent: Wednesday, February 19, 2014 6:13 PM To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: [cisco-voip] CUCM engineering special versions TAC is suggesting we go to CUCM 9.1.2. 11021.1, which is an engineering special, to fix a defect. We're already on 9.1.2 SU1. The version number for this is 9.1.2.11900-12 which is higher than the ES. I thought patches always meant going up in version numbers. Do SU versions work differently than ESs or is the engineer offering the wrong version? Thanks, Eric The contents of this message may contain confidential and/or privileged subject matter. If this message has been received in error, please contact the sender and delete all copies. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish us to communicate with you by e-mail, please notify us at your earliest convenience. In the absence of such notification, your consent is assumed. Should you choose to allow us to communicate by e-mail, we will not take any additional security measures (such as encryption) unless specifically requested. _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip The contents of this message may contain confidential and/or privileged subject matter. If this message has been received in error, please contact the sender and delete all copies. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish us to communicate with you by e-mail, please notify us at your earliest convenience. In the absence of such notification, your consent is assumed. Should you choose to allow us to communicate by e-mail, we will not take any additional security measures (such as encryption) unless specifically requested. The contents of this message may contain confidential and/or privileged subject matter. If this message has been received in error, please contact the sender and delete all copies. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish us to communicate with you by e-mail, please notify us at your earliest convenience. In the absence of such notification, your consent is assumed. Should you choose to allow us to communicate by e-mail, we will not take any additional security measures (such as encryption) unless specifically requested.
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
