RE: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Douglas Garstang
ailto:[EMAIL PROTECTED] Sent: Mon 1/23/2006 10:49 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Cc: Subject: RE: [Asterisk-Users] Re: Polycom FW On Mon, 23 Jan 2006, Douglas Garstang wrote: > We c

RE: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread steve
On Mon, 23 Jan 2006, Douglas Garstang wrote: > We conducted focus groups, looking at several different vendors, before > we decided to go with the Polycom. From the user interface perspective, > the Polycom's won hands down. I was never involved with it, but > apparently to configure the Cisco's

Re: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Anthony Rodgers
Thread hijack - grr! On 23-Jan-06, at 7:37 AM, Brian Capouch wrote: Doug Lytle wrote: > Douglas Garstang wrote: > >> We conducted focus groups, looking at several different vendors, >> before we decided to go with the Polycom. From the user interface >> perspective, the Polycom's won ha

Re: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Brian Capouch
Doug Lytle wrote: Douglas Garstang wrote: We conducted focus groups, looking at several different vendors, before we decided to go with the Polycom. From the user interface perspective, the Polycom's won hands down. I was never involved with it, but apparently to configure the Cisco's you nee

Re: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Doug Lytle
Douglas Garstang wrote: We conducted focus groups, looking at several different vendors, before we decided to go with the Polycom. From the user interface perspective, the Polycom's won hands down. I was never involved with it, but apparently to configure the Cisco's you need to be converting

RE: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Douglas Garstang
hex??? Yuk! -Original Message- From: Wilson Pickett [mailto:[EMAIL PROTECTED] Sent: Monday, January 23, 2006 6:19 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Re: Polycom FW > I don't think you can beat the Polycom's for design, features, c

Re: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Wilson Pickett
> I don't think you can beat the Polycom's for design, features, configuration > options and functionality tho. :) Polycoms (I only have experience with a ip500) have many qualities. However, I think it's only a matter of time before entries at the $180-$200 price point begin beating it in many w

Re: [Asterisk-Users] Re: Polycom FW

2006-01-23 Thread Andrew Furey
On 1/23/06, Doug Lytle <[EMAIL PROTECTED]> wrote: > > Further, Polycom SIP phones have the longest boot time of any phone > > I've ever seen (something like 5 min, compared to a Sipure, less than > > Give a SIP based Cisco 79XX phone a try, just about as long in boot time. Huh? My 7905 takes well

Re: [Asterisk-Users] Re: Polycom FW

2006-01-22 Thread Doug Lytle
Wilson Pickett wrote: Further, Polycom SIP phones have the longest boot time of any phone I've ever seen (something like 5 min, compared to a Sipure, less than Give a SIP based Cisco 79XX phone a try, just about as long in boot time. Doug -- Ben Franklin quote: "Those who would give up Es

RE: [Asterisk-Users] Re: Polycom FW

2006-01-22 Thread Douglas Garstang
List - Non-Commercial Discussion Cc: Subject: Re: [Asterisk-Users] Re: Polycom FW > I second your opinion that Polycom needs to change their policy on this. > "Strengthening the Reseller Channels" is one of the more nonsensical

Re: [Asterisk-Users] Re: Polycom FW

2006-01-22 Thread Wilson Pickett
> I second your opinion that Polycom needs to change their policy on this. > "Strengthening the Reseller Channels" is one of the more nonsensical > justifications for not publicly providing updates for their own product. Especially in light of the fact that you can easily and legally get the sourc

[Asterisk-Users] Re: Polycom FW

2006-01-20 Thread Noah Miller
Hi Bill - > Thank you to all who responded to my inquiry below. As explained by a > few people, Polycom has a policy of withholding current firmware > releases from users, thus forcing them to contact "authorized" resellers > for support should they need this code. Similar to another reported >