Hi Cuneyt,
 
If you're still seeing freezes, then you should take the issue up with
Polycom.  Definitely do all your logging and reporting with 3.1.1
firmware, since that is what 3.10.3 supports.
 
Polycom first level support may try to tell you your config files are
too old, due to some legacy text in XML comments near the top of
<MAC>-cfg.  (I had this problem once.)
 
If that happens, you should insist that the config files are 100%
compliant with 3.1.1.  Tell them to contact me if they require
clarification.
 
sipXecs 4.0 will have these files cleaned up so that it is more easily
apparent to Polycom support that they are indeed compliant.
 
I hope that helps.
 
-Paul
 


________________________________

        From: Picher, Michael [mailto:[email protected]] 
        Sent: February 3, 2009 4:59 AM
        To: Cuneyt M; Mossman, Paul (CAR:9D30)
        Cc: [email protected]
        Subject: RE: [sipx-users] Most Stable Firware for Polycom 330
        
        

        I'm running 3.10.3 with Polycom 3.1.1 firmware and 4.1.2 bootrom
on Polycom 601's, 330's and 650's with excellent results.  No freezes
that I have been told about.

         

        Mike

         

        From: [email protected]
[mailto:[email protected]] On Behalf Of Cuneyt M
        Sent: Monday, February 02, 2009 10:30 PM
        To: Paul Mossman
        Cc: [email protected]
        Subject: Re: [sipx-users] Most Stable Firware for Polycom 330

         

        Hi Paul,
        
        Thank you for your reply.
        
        I am indeed using 3.10.3. I've first attempted 3.1.2 with 4.1.2
ROMS and then switched back to 3.1.1 with 4.1.1 ROM.
        
        Yet still, i've feedback from some users having random freeze
(phone do not respond and hangs).
        
        Not sure what might be the problem or what should i look for the
resolution. Andy advice?
        
        Following is the extract of the yum update from 3.8 to 3.10.3
        
        
        

         --------------------- yum Begin ------------------------ 
         
         
         Packages Installed:
            rrdtool-perl - 1.2.26-5.i386
         
         Packages Updated:
            sipxproxy - 3.10.3-014144.i386
            sipxconfig-tftp - 3.10.3-014144.i386
            sipxconfig-report - 3.10.3-014144.i386
            sipxtacklib - 3.10.3-014144.i386
            sipxportlib - 3.10.3-014144.i386
            rrdtool - 1.2.26-5.i386
            sipxacd - 3.10.3-014144.i386
            sipxmedialib - 3.10.3-014144.i386
            sipxconfig-agent - 3.10.3-014144.i386
            sipxpublisher - 3.10.3-014144.i386
            xerces-c - 2.8.0-1.i386
            sipxtools - 3.10.3-014144.i386
            sipxvxml - 3.10.3-014144.i386
            sipxcommserverlib - 3.10.3-014144.i386
            sipxproxy-cdr - 3.10.3-014144.i386
            sipxconfig-ftp - 3.10.3-014144.i386
            sipxregistry - 3.10.3-014144.i386
            sipxmediaadapterlib - 3.10.3-014144.i386
            sipxconfig - 3.10.3-014144.i386
            sipxcalllib - 3.10.3-014144.i386
            sipxpbx - 3.10.3-014144.i386
         
         Packages Erased:
            perl-rrdtool
         
         **Unmatched Entries**
         sipxpublisher: ts_done name in te is sipxconfig-tftp should be
sipxpublisher
         sipxproxy-cdr: ts_done name in te is sipxpublisher should be
sipxproxy-cdr
         rrdtool: ts_done name in te is sipxproxy-cdr should be rrdtool
         sipxconfig-agent: ts_done name in te is rrdtool should be
sipxconfig-agent
         sipxregistry: ts_done name in te is sipxconfig-agent should be
sipxregistry
         sipxtools: ts_done name in te is sipxregistry should be
sipxtools
         sipxconfig-report: ts_done name in te is sipxtools should be
sipxconfig-report
         sipxcommserverlib: ts_done name in te is sipxconfig-report
should be sipxcommserverlib
         sipxconfig: ts_done name in te is sipxcommserverlib should be
sipxconfig
         sipxacd: ts_done name in te is sipxconfig-ftp should be sipxacd
         sipxportlib: ts_done name in te is sipxconfig should be
sipxportlib
         sipxpbx: ts_done name in te is sipxacd should be sipxpbx
         perl-rrdtool: ts_done name in te is sipxportlib should be
perl-rrdtool
         
         
         
        ------------------
         
        cheers!
         ---------------------- yum End ------------------------- 

        
        Paul Mossman wrote: 

        Cuneyt M wrote:
          

                I have recently upgraded to latest stable (thanks
shruthi for the
                pointers) 3.102 via yum update.
                 
                We have Polycom 330 and we were using 2.1.2 with bootrom
4 
                while we were at sipx 3.8
                 
                As the natural step (and understanding that 3.10
supports 
                firmware 3 config inis (the UI dropdown still show 1.x
and 
                2.0 though for Polycom 330), uploaded Polycom 3.1.2 and 
                Bootrom 4.1.2 to phones.
                    

         
        I know of a number of problems with the Polycom generated config
files
        in sipXecs 3.10.1 and 3.10.2.
         
        You should upgrade to sipXecs 3.10.3, which fully supports
Polycom SIP
        Application 3.1.1.
         
        Polycom SIP Application 3.1.2 won't be supported until sipXecs
4.0.
        (I'm working on it right now.)
         
         
        -Paul
        [email protected]
         
         
          

         

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to