Our current priority is XML-browser-based features (server side). Yealinks
are very powerful from this point of view. One of good examples is hot
desking.
2012/11/21 Matt White <***@thesummit-grp.com>
> yes, I used the wrong term. I was referring to "auto provisioning"..plug
> and play if you will, not the old scan a subnet feature.
>
> -M
>
> >>> Tony Graziano <***@myitdepartment.net> 11/21/12 10:31 AM >>>
> I would be less concerned with auto discovery (wasn't that dropped from
> sipx already?) and more concerned with auto provisioning and firmware
> management.
>
> It is good to plug in the deice and have it grab a basic config from the
> server so the admin can find the phone in unconfigured devices, assign a
> line and send it profiles/reboot, etc. like we can with Polycom.
>
> The "auto-discovery" term harkens back to the day when sipx actually could
> scan network scopes looking for known mac address ranges. I think that was
> neat but it was really problematic and it dropped off the development map
> and was removed.
>
> I am not sure if auto disocvery (the term) is used the same as I remember
> it. sipx sees a known mac address range (like 0004f2) and says "polycom"
> and makes it a manageable unprovisioned device. I think this is a good goal
> for any UA if the vendors make it possible.
>
> On Wed, Nov 21, 2012 at 9:58 AM, ÐОÑ
аОл РПЎОПМПв <***@siplabs.ru> wrote:
>
>> Hello,
>>
>> Our current plugin does firmware management and provisioning, no
>> auto-discovery yet.
>>
>> Yealink quality is very good right now - less than 1% units fail in first
>> year.
>>
>> 2012/11/21 Matt White <***@thesummit-grp.com>
>>
>>> Have you guys done any work outside the plugin with
>>> auto-discovery/provisioning? That would be a killer feature that only the
>>> polycoms have right now.
>>>
>>> About 2 years ago (or has it been longer) we were working with yealink
>>> and we too developed a plugin that worked fairly well and had just started
>>> looking at the auto-provisioning plugin. If I recall, back in the 4.2 days
>>> it wasn't a huge change, the current provisioning model is hardcoded to
>>> polycom mac address schemes, but could be updated with yealink mac's with
>>> little effort.
>>>
>>> At the time, I was very impressed with yealink support. They would
>>> have an engineer write custom firmware for feature xyz and email it to me
>>> the next day. But ultimately we decided to not purse it anymore because
>>> they had QC issues with the hardware. We had a sizable deployment of
>>> about 300 phones but about 25% would not grab dhcp. Yealink discovered an
>>> issue with the crystal used for timing and needed to go back to
>>> manufacturing. Yealink provded the phone for free but it still left us
>>> weary until they had matured.
>>>
>>> Maybe they have stabilized a bit these days.
>>>
>>> -M
>>>
>>>
>>>
>>>
>>>
>>> >>> ÐОÑ
аОл РПЎОПМПв<***@siplabs.ru> 11/20/12 7:06 PM >>>
>>> Well, I woke up and found this thread... I think I just have to defend
>>> Yealink here. We support installations with hundreds of them and they work
>>> flowlessly. Yealink's SIP support is outstanding - they are a real
>>> competitor to Polycom here.
>>>
>>> We have 4.6-compatible version of plugin for phones with upcoming v70
>>> t2x firmware in beta, will release it as RPM next week (we have 4.6
>>> installation for 100 yealinks planned there so time frame is already set
>>> for this release).
>>>
>>> So go for Yealinks and please address all questions and issues to me
>>> directly - we have direct support from Yealink R&D so even custom firmware
>>> is often no problem.
>>>
>>> 2012/11/21 Michael Picher <***@ezuce.com>
>>>
>>>> I think it's in 4.7 now... somebody will pipe up and let me know if
>>>> I'm wrong.
>>>>
>>>> It was getting pushed and prodded in and out of 4.6.
>>>>
>>>> If we can get enough testing with it we might back-port it to 4.6.0
>>>> update 1 or update 2. Not sure how that's all going to develop yet.
>>>>
>>>> Mike
>>>>
>>>>
>>>> On Tue, Nov 20, 2012 at 3:43 PM, Tony Graziano <
>>>> ***@myitdepartment.net> wrote:
>>>>
>>>>> Is vvx with firmware 4.x going to be on 4.6 or 4.7 initially or has it
>>>>> made it that far yet?
>>>>> On Nov 20, 2012 3:35 PM, "Michael Picher" <***@ezuce.com> wrote:
>>>>>
>>>>>> I think we'll get there with the others... but they are still a
>>>>>> compromise. I think some firmware and template updates might be coming
>>>>>> down post 4.6.0 for Yealink.
>>>>>>
>>>>>> I also know the Polycom vvx500 / ver 4.x firmware stuff should drop
>>>>>> in mid to late December... we'll want some testers on the 4.7 branch.
>>>>>> We'll probably be dog-fooding it once 4.6 drops too.
>>>>>>
>>>>>> There might be a couple other phones in the works too ;-)
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 20, 2012 at 2:55 PM, Geoff Musgrave <
>>>>>> ***@cacionline.net> wrote:
>>>>>>
>>>>>>> Mike/Tony,****
>>>>>>>
>>>>>>>
>>>>>>> Thanks for the replies. I had a feeling that was going to be the
>>>>>>> kind of response I got but wanted to check first. ****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> I completely agree that going with Polycoms would solve all of our
>>>>>>> problems.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Thanks for the info/insight.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> --****
>>>>>>>
>>>>>>> Geoff****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> *From:* Tony Graziano [mailto:***@myitdepartment.net]
>>>>>>> *Sent:* Tuesday, November 20, 2012 1:25 PM
>>>>>>> *To:* Discussion list for users of sipXecs software
>>>>>>> *Subject:* Re: [sipx-users] Yealink SIP-T26P/T28P + EXP38****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Shoot thyself in the foot. Snom or Yealink, both are problematic.
>>>>>>> Get thee to a Polycom...****
>>>>>>>
>>>>>>> On Tue, Nov 20, 2012 at 2:11 PM, Geoff Musgrave <
>>>>>>> ***@cacionline.net> wrote:****
>>>>>>>
>>>>>>> Has anyone used the Yealink SIP-T26P or T28P with or without the
>>>>>>> EXP38 with sipXecs 4.6? If so, I would like to hear your experience and/or
>>>>>>> opinion.****
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>> Iâm considering placing 2 of these with the EXP38 at another office
>>>>>>> due to the owners not wanting to spend Polycom prices. My other option is
>>>>>>> to go with snom 3xx with expansion modules again but Iâm still having some
>>>>>>> transferring issues with the current snom 370s at the office we did the
>>>>>>> initial deployment.****
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>> Thanks in advance.****
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>> --****
>>>>>>>
>>>>>>> Geoff****
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> sipx-users mailing list
>>>>>>> sipx-***@list.sipfoundry.org
>>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/****
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> --
>>>>>>> ~~~~~~~~~~~~~~~~~~
>>>>>>> Tony Graziano, Manager
>>>>>>> Telephone: 434.984.8430
>>>>>>> sip: ***@voice.myitdepartment.net
>>>>>>> Fax: 434.465.6833
>>>>>>> ~~~~~~~~~~~~~~~~~~
>>>>>>> Linked-In Profile:
>>>>>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>>>>>>> Ask about our Internet Fax services!
>>>>>>> ~~~~~~~~~~~~~~~~~~****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> <http://sipxcolab2013.eventbrite.com/?discount=tony2013>
>>>>>>> Using or developing for sipXecs from SIPFoundry? Ask me about
>>>>>>> sipX-CoLab 2013!
>>>>>>> <http://sipxcolab2013.eventbrite.com/?discount=tony2013>
>>>>>>> [image: Description: Image removed by sender.]<http://sipxcolab2013.eventbrite.com/?discount=tony2013>
>>>>>>> ****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> LAN/Telephony/Security and Control Systems Helpdesk:****
>>>>>>>
>>>>>>> Telephone: 434.984.8426****
>>>>>>>
>>>>>>> sip: ***@voice.myitdepartment.net****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Helpdesk Customers: http://myhelp.myitdepartment.net****
>>>>>>>
>>>>>>> Blog: http://blog.myitdepartment.net****
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> sipx-users mailing list
>>>>>>> sipx-***@list.sipfoundry.org
>>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Michael Picher, Director of Technical Services
>>>>>> eZuce, Inc.
>>>>>>
>>>>>> 300 Brickstone Square****
>>>>>>
>>>>>> Suite 201****
>>>>>>
>>>>>> Andover, MA. 01810
>>>>>> O.978-296-1005 X2015
>>>>>> M.207-956-0262
>>>>>> @mpicher <http://twitter.com/mpicher>
>>>>>> linkedin<http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
>>>>>> www.ezuce.com
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------------------------------------
>>>>>> There are 10 kinds of people in the world, those who understand
>>>>>> binary and those who don't.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sipx-users mailing list
>>>>>> sipx-***@list.sipfoundry.org
>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>>>
>>>>>
>>>>> LAN/Telephony/Security and Control Systems Helpdesk:
>>>>> Telephone: 434.984.8426
>>>>> sip: ***@voice.myitdepartment.**net<***@voice.myitdepartment.net>
>>>>>
>>>>> Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
>>>>> Blog: http://blog.myitdepartment.net
>>>>>
>>>>> _______________________________________________
>>>>> sipx-users mailing list
>>>>> sipx-***@list.sipfoundry.org
>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Picher, Director of Technical Services
>>>> eZuce, Inc.
>>>>
>>>> 300 Brickstone Square****
>>>>
>>>> Suite 201****
>>>>
>>>> Andover, MA. 01810
>>>> O.978-296-1005 X2015
>>>> M.207-956-0262
>>>> @mpicher <http://twitter.com/mpicher>
>>>> linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
>>>> www.ezuce.com
>>>>
>>>>
>>>> ------------------------------------------------------------------------------------------------------------
>>>> There are 10 kinds of people in the world, those who understand binary
>>>> and those who don't.
>>>>
>>>>
>>>> _______________________________________________
>>>> sipx-users mailing list
>>>> sipx-***@list.sipfoundry.org
>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Mikhail Rodionov*
>>> CEO
>>> E-mail: ***@siplabs.ru
>>> Tel: +7(383)363-2111
>>> Mob: +7(913)985-5212
>>>
>>>
>>
>>
>> --
>>
>> *Mikhail Rodionov*
>> CEO
>> E-mail: ***@siplabs.ru
>> Tel: +7(383)363-2111
>> Mob: +7(913)985-5212
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>> sipx-***@list.sipfoundry.org
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
> ~~~~~~~~~~~~~~~~~~
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: ***@voice.myitdepartment.net
> Fax: 434.465.6833
> ~~~~~~~~~~~~~~~~~~
> Linked-In Profile:
> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> Ask about our Internet Fax services!
> ~~~~~~~~~~~~~~~~~~
>
> Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
> 2013!
> <http://sipxcolab2013.eventbrite.com/?discount=tony2013>
>
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: ***@voice.myitdepartment.**net<***@voice.myitdepartment.net>
>
> Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
> Blog: http://blog.myitdepartment.net
>
> --
> This email was Anti Virus checked by the Summit Technology Consulting Groups Astaro Security Gateway. http://www.astaro.com
>
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
--
*Mikhail Rodionov*
CEO
E-mail: ***@siplabs.ru
Tel: +7(383)363-2111
Mob: +7(913)985-5212