Anytime a vendor fixes an issue and either claims they did nothing or provides no detail about the resolution I refer to it as “pulling a Verizon” or say that they “Verizoned” the issue. I think it comes from a culture of protecting their co-workers and it is pretty commonplace.
I had a customer in NJ that watched a Verizon tech drive up, climb the pole outside the facility and after about 5 minutes the sites PRIs dropped. He spoke to the tech who said that he didn’t do anything related to the PRIs. The customer calls in a ticket and tells them that the tech was working on the pole. Of course they have to run automated testing, etc. so a full 24+ hours later, he sees another tech pull up, climb the pole, and within a few minutes the PRIs were back up. Verizon closed the ticket as “No Problem Found”. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lisa Notarianni Sent: Thursday, May 07, 2015 11:02 AM To: cisco-voip voyp list Subject: Re: [cisco-voip] Temp Fail since upgrade FYI on this issue – some asked me to post once it was resolved. The problem disappeared and resolved itself once I reported it to Verizon. I believe Verizon made changes on their end they found were incorrect but never reported to me what they did. There are so many people at Verizon buried deep in the Central Offices that we do not have direct contact with anymore there is no way to find out what the solution was. Thank you for all of your responses. [LNsignatureFile] From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Daniel Pagan Sent: Monday, April 06, 2015 11:13 AM To: Ryan Ratliff (rratliff); Jason Aarons (AM) Cc: cisco-voip voyp list Subject: Re: [cisco-voip] Temp Fail since upgrade Adding to Ryan’s suggestion re: ACKs - I took a snip of some internal documentation I wrote re: MGCP debugs that might help. The MGCP transaction ID, in a CCM SDL trace or MGCP packet debug output, would look similar to this: http://i.imgur.com/O1YGnUO.png. Just showing the transaction ID matching between the MGCP command and 200 response. The observed event and Line package /hd (off-hook) highlighted can be ignored. It might also be helpful to debug MGCP packets on the voice router… just make sure to disable console logging before leaving something like that running and increase the buffer size so you capture a failure. Seeing a missing 200 MGCP response in SDL traces doesn’t mean the router didn’t send one, and same the other way around where seeing an MGCP command sent from CUCM doesn’t mean it arrived at the router. In any case MGCP debugs off the router would come in handy in tandem with CCM traces. Hope this helps. - Dan From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan Ratliff (rratliff) Sent: Monday, April 06, 2015 10:37 AM To: Jason Aarons (AM) Cc: cisco-voip voyp list Subject: Re: [cisco-voip] Temp Fail since upgrade The first place to look is MGCP packets being lost. Search for “Retry” in the ccm traces similar to: CCM|MGCPHandler TransId: 1476004 Timeout. Retry#1 That example is from a case in 2008 so what you see may not look exactly the same. This type of message is an indicator that CCM is resending an MGCP message that wasn’t Ack’d by the gateway. After 3 or so of those CCM will unregister the gateway and any phones talking to it will get Temp Fail. Aside from lost messages it could be a RSIP or something that is gateway initiated causing the reset. -Ryan On Apr 5, 2015, at 10:15 AM, Jason Aarons (AM) <jason.aar...@dimensiondata.com<mailto:jason.aar...@dimensiondata.com>> wrote: Nothing has changed with MGCP for a long time…Cisco just doesn’t test older IOS. Pull normal debugs and traces, RTMT alerts, etc. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Kevin Przybylowski Sent: Monday, March 30, 2015 5:10 PM To: Lisa Notarianni; Ryan Huff; cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Temp Fail since upgrade Are the mgcp gateways on a supported IOS for 10.5? From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Lisa Notarianni Sent: Monday, March 30, 2015 5:02 PM To: Ryan Huff; cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Temp Fail since upgrade 2 PRIs one each Communication Media Module– MGCP gateways. 2 Call Managers set up as redundant. Cisco TAC looked at RTMT with me today. They want us to set up packet captures and try to duplicate the problem tomorrow. I am just wondering if this is an upgrade issue that anyone else may be experiencing since we had no problems before the upgrade. From: Ryan Huff [mailto:ryanh...@outlook.com] Sent: Monday, March 30, 2015 4:52 PM To: Lisa Notarianni; cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Temp Fail since upgrade Lisa, SIP or TDM/PRI? Have you gandered into RTMT and taken a look at any active / recent alerts? Thanks, Ryan -------- Original Message -------- From: Lisa Notarianni <lisa.notaria...@scranton.edu<mailto:lisa.notaria...@scranton.edu>> Sent: Monday, March 30, 2015 04:48 PM To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: [cisco-voip] Temp Fail since upgrade A few weeks ago we upgraded Call Manager and Unity Connection from 8.6.2 to 10.5.1. We have experienced 2 intermittent outbound calling issues: 1. “Temp Fail” shows on phone display and only option on phone button is “End Call” 2. Outbound callers dial a number and hear nothing but notice the phone display says “Connected”. Caller cannot hear anything. Person they called cannot hear anything. ***These issues are only intermittent.*** We had no issues before the upgrade. Is anyone experiencing the similar issues? Thank you in advance. itevomcid _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
