Did some more experimenting: - Since we have working installation on remote site which is only couple of patches behind I re installed 4.4, did not apply any "yum update", and finally I restored config - problem persists - "Virgin" installation, no patches, only two phones configured - problem ppersists. - To rule out cabling issues plugged two phones directly into a switch - problem persists - Used different switch - problem persists - Finally reverted back to 4.2.1 - problem has gone away !?!?!
Has anyone else experience similar problem with 4.4 and not in 4.2.1? Regards, Dragan On Fri, Jun 17, 2011 at 8:08 AM, Dragan Jurkovic <[email protected]> wrote: > No BLAs. > > On Thu, Jun 16, 2011 at 4:49 PM, Nathaniel Watkins > <[email protected]> wrote: >> Are you using BLA (shared lines) on these phones? I've had some odd issues >> in the past that were related to certain firmware and using BLA. >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Todd Hodgen >> Sent: Thursday, June 16, 2011 4:05 PM >> To: 'Discussion list for users of sipXecs software'; >> [email protected] >> Subject: Re: [sipx-users] Problem with internal calls Polycom to Polycom >> -PRACK missing >> >> There are several on this list, including myself, that have been burned by >> Netgear switches. If resetting your switch fixes a problem, there is an >> issue with the switch, or the power feeding that switch. Personally, I'd >> replace the switch, and I'd also ensure it is on a quality UPS. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Dragan Jurkovic >> Sent: Thursday, June 16, 2011 1:00 PM >> To: [email protected]; Discussion list for users of sipXecs software >> Subject: Re: [sipx-users] Problem with internal calls Polycom to Polycom >> -PRACK missing >> >> For me it happens even if phones are plugged directly to Netgear GS748TP >> switch. When I restarted the switch problem went away for a while, but it >> seems it is back. Could it be faulty switch? >> >> Dragan >> >> On Thu, Jun 16, 2011 at 3:27 PM, Matthew Kitchin (usenet/public) >> <[email protected]> wrote: >>> Me too! >>> It happened on 4.2.1 with pcom firmware 3.2.4 and still with 4.4.0 and >> 3.2.5. After going through some traces, we replaced an old cat 5 drop with >> several cross connects with a cat 6 home run it seems. To have helped. >>> -----Original Message----- >>> From: Tony Graziano <[email protected]> >>> Sender: [email protected] >>> Date: Thu, 16 Jun 2011 12:29:05 >>> To: Discussion list for users of sipXecs >> software<[email protected]> >>> Reply-To: Discussion list for users of sipXecs software >>> <[email protected]> >>> Subject: Re: [sipx-users] Problem with internal calls Polycom to >>> Polycom - >>> PRACK missing >>> >>> On Thu, Jun 16, 2011 at 12:20 PM, Dragan Jurkovic <[email protected]> >> wrote: >>>> Hi all, >>>> >>>> I have a strange problem with internal calls between Polycom phones >>>> (IP 331 boot rom 4.1.3, SIP 3.2.4.B). sipXecs is 4.4 with all latest >>>> patches applied. >>>> When calling from one station to another an attempt to answer >>>> incoming call will result in following: screen still shows Ignore, >>>> Answer, More options, ringing stops, and caller's phone will show >>>> that call is answered. The only way to stop the call on called phone >>>> is to go to reject option. This happens randomly but very often. >>>> Attached logs show that PRACK is not issued in failed call case. >>>> >>>> Is this Polycom or sipXecs issue? Has anyone stumbled on this. >>>> >>>> What is more puzzling - we have remote site with identical >>>> configuration and this never happens there! >>>> >>> I have also seen this with firmware 3.2.5 on a limited basis but have >>> not tracked it down. It also happens on incoming trunk calls. In the >>> one instance where it is happening we're in the process of replacing a >>> crappy switch though, and I wanted to get that out of the way before I >>> pointed fingers. >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 10.0.1382 / Virus Database: 1513/3707 - Release Date: 06/16/11 >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> This message and any files transmitted with it are intended only for the >> individual(s) or entity named. If you are not the intended individual(s) or >> entity named you are hereby notified that any disclosure, copying, >> distribution or reliance upon its contents is strictly prohibited. If you >> have received this in error, please notify the sender, delete the original, >> and destroy all copies. Email transmissions cannot be guaranteed to be >> secure or error-free as information could be intercepted, corrupted, lost, >> destroyed, arrive late or incomplete, or contain viruses. Garrett County >> Government therefore does not accept any liability for any errors or >> omissions in the contents of this message, which arise as a result of email >> transmission. >> >> >> Garrett County Government, >> 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 >> www.garrettcounty.org >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
