I think it's fine if you have one phone. I am not sure it is useable with multiple unique handsets as it is though.
With multiple handsets you have to still login and manage the identity and line for each at the base station, which means if you push a change from sipxconfig you have to login to the base station all over again. Essentially doing it twice each time. On Wed, Oct 27, 2010 at 10:11 AM, George Niculae <[email protected]> wrote: > On Wed, Oct 27, 2010 at 2:39 AM, Tony Graziano > <[email protected]> wrote: > > In looking at the snom m3 plugin in a working system, here are my first > > impressions: > > I think 'server is local" should be set to NO by default. I think most > > people will deploy this on a LAN, so (reading the logic for Snom) YES > means > > behind NAT, NO means not behind NAT. > > I think FORCE DOMAIN should be default, and I think only safe codecs > should > > be chosen by default (G77u/a), but I didn't see them in the UI. > > What I did not see was the ability to set the line identity for each > handset > > on the base and to set the handset "name" for the display. It uses the > same > > config file, so it should be settable. > > In a normal environment where there are four handsets and one base > station, > > you would want to be able to set the handset NAME and configure which > lines > > ring on it. By default all lines are on every phone I think, which is > > problematic. > > My call is to push the plugin as it is in main so we have a starting > point and then open JIRA for tracking enhancements. What do you guys > think? > > George > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== 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
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
