Hi Tony, replies below. Il 27/10/2010 01:39, Tony Graziano ha scritto: > 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 really feel the snom wiki here is not clear at all. http://wiki.snom.com/Snom_m3/Settings/SRV_0_SIP_UA_DATA_SERVER_IS_LOCAL At the question "the server is local" I would say yes it's on my lan no firewall in between, but reading the wiki it seems the meaning is the exact contrary. It would be interesting to explore this setting further.
> 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. http://wiki.snom.com/Snom_m3/Settings/SRV_0_SIP_URI_DOMAIN_CONFIG Have you found a case where using just add domain cause any fault? Force domain seems to change the domain if it is different from the one configured. Don't know if it could compromise calls. I'm sure sipxecs won't forget to add the domain part to its call. But it maybe routes call from different domain to the phone. And in this case force domain might add troubles. I believe some test should be done. Changing the defaults it's just a quick edit. I haven't add codec choices on the plug-in intentionally. The option is complicate to adapt to sipxconfig. See below ... > > 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. > Yes you're right, but I left this option out by design. The issue I had is: I cannot reproduce the matrix you see on the phone config in sipxecs. Or maybe it's just me that don't know how to do it! The fact is every cordless has a single option to add lines. Depends of the option value what lines are currently assigned to the phone. 8 lines max, two possible state per line: this gives 256 different options per cordless. Creating a setting in sipxconfig with a drop down list with 256 choices is definitely a long job, and worse it's a terrible user unfriendly experience. So I left this setting out but hardwiring the concept of one line to one phone. Line 1 - cordless 1, line 2 - cordless 2, etc. To make it better I need some discussion from the user community. What would you like best? A simplification with a single option to assing to cordless 1 line (None, Line 1, Line 2 .. Line8, All) would be acceptable? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
