It sounds like it is almost reproducible if you see this a few times a day. Try put logging for park and presence to DEBUG and for the proxy to info. Ask the users to note the exact time when this happens.
First thing would be to look at the logs for errors. Do you see any core dumps? --martin From: Jim Canfield [mailto:[email protected]] Sent: Wednesday, August 25, 2010 10:23 PM To: Martin Steinmann Cc: Tony Graziano; [email protected] Subject: Re: [sipx-users] Continued park issues. I wish I could intelligently describe the issue, but I simply can't duplicate it reliably. Here's my best description: Park Extension = 1 Park 1 Monitored via speed dial with presence checked Call is placed on park (Transfer-->Park BLF-->Hang-up) Call is picked up by pressing the now blinking Park BLF key ISSUE: Park will (randomly) remain stuck on park and the caller will be on-hold indefinitely. Usually the park BLF is red when it's in this state. Restarting the Park server is required to reset the Park state. I have a couple of 4.0.4 installs that have Park monitored and the issue occurs once a month sometimes longer. I have installed three 4.2.1 systems in the two weeks and tried BLF park at a small medical office with 5 phones. After less than I week I had to pull the park button completely because it was happening one or two times a day. The other install is closer to 50 phones and it's happening 4-5 times a day. NOTE: The only successful park implimention I have on the 4.2.1 release is a "Waiting" queue I created by transferring a call to a Monitired Park extension from via AA. What was originally a clever hack actually turned out to be a very useful feature. I'm inclined to think it has more to do with how the polycoms transfer to the park extensions since a transfer from AA appears to be relaible. I've yet to produce a SIP trace of the event. On Wed, Aug 25, 2010 at 7:35 PM, Martin Steinmann <[email protected]> wrote: What is different between park in 4.0.4 and 4.2? Other than maybe some fixes, there was no development done on part in that iteration AFAIK. Could someone accurately describe the problem, assuming that what you are talking about is a bug and not a new feature requirement. -
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
