I just did it like 4 times on and off hold, inbound from wireless phone to voip.ms trunk terminated on sipXbridge to a remote phone coming in from remote NAT.
Polycom firmware 3.2.4b, bootrom 4.3.1, latest build. Mike On Fri, Nov 4, 2011 at 1:38 PM, Paul Curtis <pcur...@uws.edu> wrote: > This also occurred while using Cisco 2811 gateways. The Polycom does > not respond correctly when initiating the Hold, it does not send a PRACK > when it should. I had worked with polycom on this issue earlier this year > and they gave me a patched version that they still have not released which > is 3.2.5.b. Seems to be coming up more and more on this list.**** > > ** ** > > *From:* sipx-users-boun...@list.sipfoundry.org [mailto: > sipx-users-boun...@list.sipfoundry.org] *On Behalf Of *Tony Graziano > *Sent:* Friday, November 04, 2011 10:09 AM > *To:* Discussion list for users of sipXecs software > *Subject:* Re: [sipx-users] Hold BUG on 4.4 using HOLD on Polycom phones** > ** > > ** ** > > ok. I will see if I can reproduce in the lab and submit a tracker.**** > > On Nov 4, 2011 12:46 PM, "Kevin George" <kevincgeo...@gmail.com> wrote:*** > * > > Sounds almost exactly like the issue I described in July. In my situation > when I put the (sip trunk) caller on hold, then resume, then hold again, > then resume the call messes up everytime. If I remove the moh config from > the polycom config manually, the problem doesn't occur. > > I'm still running the old version though. (sipxproxy-4.4.0-235.g353d7) > Bandwidth.com sip trunks > Polycom 550 3.2.4b and 3.2.5 > > I do see the ~mh~ entries in my CDR stuck also.**** > > On Fri, Nov 4, 2011 at 8:50 AM, Tony Graziano < > tgrazi...@myitdepartment.net> wrote:**** > > Numerous firmware/bootrom versions, what I am seeing is using 4.4 > (latest) if someone calls in via siptrunk on internal, and puts the > caller on hold (using the hold button) then resumes the call, the > calls is stuck in CDR as ~mh~ while the call is resumed. Occasionally, > the call cannot be resumed, and the phones start locking up and have > to be unplugged. > > It's odd the calls stuck in CDR showing ~mh~ happens and sometimes the > call is actually stuck in the media server too. > > This only started happening when putting on the last update. > (2011-10-12). Can anyone else duplicate this? > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: tgrazi...@voice.myitdepartment.net > Fax: 434.465.6833 > > Email: tgrazi...@myitdepartment.net > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: helpd...@voice.myitdepartment.net > > Helpdesk Customers: http://myhelp.myitdepartment.net > Blog: http://blog.myitdepartment.net > > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/**** > > > > > -- > Kevin George > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/**** > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
