I plan to. I have to wait for the site to be staffed. I have also downgraded forward to 3.1.3 so I can test further. if it happens only on 3.2.x then I had an upgrade a phone and selectively test without disrupting a working sytem. otherwise I have to snapshot/calltrace then wipe and load ip 4.2.1. On Jun 20, 2011 8:07 AM, "George Niculae" <[email protected]> wrote: > On Mon, Jun 20, 2011 at 2:20 PM, Tony Graziano > <[email protected]> wrote: >> On Monday, June 20, 2011, Douglas Hubler <[email protected]> wrote: >>> On Sun, Jun 19, 2011 at 11:44 PM, Paul Curtis <[email protected]> wrote: >>>> This is a known issue with Polycom, I worked with them to resolve the >>>> missing PRACK. This also had to do with the on-hold issue I had posted a >>>> while back. That was when Polycom noticed the missing PRACK. They do >>>> have a software release fix coming 3.2.5B, surprised it hasn't posted yet. >>>> It's been well over 6 weeks. Perhaps they found other issues to add >>>> prior to releasing it. >>>> >>>> This only occurred in 4.4 (all releases). 4.2.1 worked just fine. >>>> Polycom phones that are affected in my environment were 331,335,560,670. >>>> At least that is what I have to test with. The error occurred with calls >>>> from inbound / outbound gateways of any type, even other sipx systems. >>> >>> If someone can reproduce this on 4.4, can you disable this distinct ringtones >>> http://wiki.sipfoundry.org/display/sipXecs/Distinct+ringtones+for+internal+and+external+calls >>> and see if problem persists >>> _______ >> >> Problem persists with distinctive ringtones off. > > Tony, could you take snapshot and raise a critical in JIRA? > > Thanks, > George > _______________________________________________ > 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/
