Yea, that works too... On Thu, Jan 20, 2011 at 8:46 AM, Tony Graziano <[email protected] > wrote:
> OR.... > > Update to firmware 3.1.3RevC, then remove the presence stuff from the > phones and use XMPP for presence so the phone is not trying to parse and > monitor that, I've always found that the older phones use a lot of resources > to monitor BLF and you might be hitting some reliability limits. Alternately > you can grab some newer phones/sidecars, or maybe try the new version of > voice operator panel per the posing from yesterday > > Voice Operator Panel / XMPP : User Presence, Messaging and File Transfer. > > On Thu, Jan 20, 2011 at 8:27 AM, Michael Picher <[email protected]> wrote: > >> This is a common problem with the older phones / firmware. >> >> 3.1.3c is the best firmware on those phones... >> >> You might try upgrading your answering positions to 650's and rotate the >> 601's out. >> >> You'll need new sidecars too unfortunately. >> >> Mike >> >> >> On Wed, Jan 19, 2011 at 1:51 PM, Chris St Denis < >> [email protected]> wrote: >> >>> Sipx version 4.2.1 >>> >>> I am running 16 polycom 501's and 2 polycom 601's. >>> >>> The 2 601 phones have sidecars and are configured with speed dials for >>> the 17 other phones with presence. Mostly this works fine, but sometimes >>> it seems to miss messages with a phone showing incorrect status such as >>> staying on ringing status for an extended period. This will usually >>> clear itself after 10s of minutes. The phones also occasionally lock up >>> placing outgoing calls when this happens. >>> >>> A packet sniff shows sipx is sending out the correct status information, >>> but for some reason the phones don't seem to be processing it reliably. >>> >>> What can be done to resolve this? I've experimented with firmware >>> versions from 3.1.1 to 3.1.4 with the same results in them all. 3.1.6 >>> seems to break everything and anything else new doesn't support the x01 >>> phones. >>> >>> >>> Also, If the phone has speed dial + presence of itself it has much more >>> severe stability issues and will generally lock up after placing 2 >>> calls. This isn't really a problem since I can work around it, but that >>> should be mentioned in the documentation if it can't be fixed. >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> There are 10 kinds of people in this world, those who understand binary >> and those who don't. >> >> [email protected] >> blog: http://www.sipxecs.info >> call: sip:[email protected] <sip%[email protected]> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: > http://support.myitdepartment.net > > <http://support.myitdepartment.net>Blog: > http://blog.myitdepartment.net > > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected] <sip%[email protected]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
