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 <[email protected]>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: [email protected] > Fax: 434.465.6833 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > 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 > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Kevin George
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
