I had this exact problem at 1 site. It happened on 4.2.1 and 4.4. It happened on multiple versions of polycom firmware. People here that analyzed the trace said something along the lines of an ack or something appeared to not be occurring fast enough. I can't remember the exact description. I can look it up when I get to a PC. On the main phone that answered all the calls, it would happen about 30% of the time. This building had old wiring. It was the first site that we converted from a key system that had ethernet wiring, so were able to reuse the wiring. It was cat 5, but it was old. There was an old patch panel, multiple cross connects and couplers, etc. I tried replacing that 1 drop with a home runned cat 6 drop. It basically fixed it. It now does it maybe 1 time a month. -----Original Message----- From: Jeff Gilmore <[email protected]> Sender: [email protected] Date: Thu, 15 Sep 2011 16:02:27 To: Discussion list for users of sipXecs software<[email protected]> Reply-To: Discussion list for users of sipXecs software <[email protected]> Subject: [sipx-users] Call pickup problem on Polycom
I am sending this a second time, because I don't see it appearing on list or forum. I have started having a problem with a Polycom IP320. The problem is that, on incoming outside calls, when I pick up the call, the phone displays <ignore> <answer><more> instead of answering the call. Pressing the buttons does nothing, and the caller hears dead air. If I call this phone from an internal extension, it works OK. It used to work fine. I had posted a question about this problem to the list a few weeks back, and was advised that it was a likely a problem solved in recent 4.4 builds. I updated to the later 4.4 last night ( I believe it is at level 4.4 update 10; sipxconfig displays "4.4.0- 2011-09-02EDT15:37:13 domU-12-31-39-15-62-46") and the problem persists. I am running 3.1.3.0439 on the phone. The problem started happening when my vendor moved me to a different SBC on their Metaswitch. But since everything else works fine on my other devices (mostly ATA2102s), I don't know what to tell them to change (and I don't trust them to figure it out themselves)! Is anyone willing to look at a trace to see if you can help me understand how/why it is failing? Thanks, Jeff _______________________________________________ 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/
