Damian Krzeminski ha scritto:
>>
>> We know which revisions to merge :-)
>> What Mircea (and users) would need to understand is what changes in
>> functionality of the SNOM plug-ins it's causing. I know we changed the
>> profile format. Does it affect the subset of firmware versions it
supports?
>> And features dropped? Added?
>>
Damian I thought I mentioned it in a comment in the issue:
http://track.sipfoundry.org/browse/XX-5478
In fact is what you pasted in the commit. I will rewrite it here for you
both:
Snom v7 xml file format. It's a port of the previous v6 plug-in!
- Ported all features working in the v6 plug-in to a v7 xml file format.
Address books were not working with a v7 phone and the v6 plug-in.
- Ported setting permissions as done in the previous plug-in: adding an
extra char (! or $) in the <profileName> value.
- config file generated will be named {mac}.xml. Sipfoundry wiki, regard
dhcp options 66/67, should be updated.
- Workaroud for Snom and TCP problem setting tcp port on snom to 5060 by
default. Snom defaults to random.
- Added Snom 370. No specific 370 functions. Remember this is a just a
port. No VPN sorry!
- Updated jUnit test.
- Added a minimal subset of v7 new options: Some new function keys value
(BLF and others); Tone schemes for new countries; New languages for the
phone interface and the web interface.
- Fixes XX-5477as well.
Minimum v7 firmware version is 7.3.14, but actually very few settings I
added will need this version. Of course it won't work with a v6.x firmware.
There is still an open issue (aka something not working): languages are
not loaded in the phone firmware in v7. This is actually a v7 firmware
change to allow more space in the phone flash. To load a language we
need to provide the links to them in a different file. The file should
look like this:
<?xml version="1.0" encoding="UTF-8"?>
<setting-files>
<file url="http://provisioning.snom.com/config/web_lang2.xml"; />
<file url="http://provisioning.snom.com/config/gui_lang2.xml"; />
<file
url="http://ourSipXecs.example.com:8090/phone/profile/docroot/{mac}.xml"; />
</setting-files>
This is issue is not affecting someone using just English. The trivial
workaround is to upload an xml file (let's call it snom.xml) with the
contents above in the http profiles dir. Of course
ourSipXecs.example.com should be rewritten using the FQHN of our local
sipxconfig machine. We need then to edit option 67 in our dhcp pointing
to snom.xml. Those urls are for languages files of firmware 7.3.14.
Different firmware versions, different urls. This will make things
tricky. That's why I proposed to extend the plug-in allowing the user to
upload language files generating our snom.xml accordingly. But I did not
have a look at this mechanism yet.
>> There is still an open issue that I will try to work out soon with
>> another patch. Language (other than English) support. It's trivial to
>> manually add the missing piece. Not as trivial for a scared plug in
>> developer as I am.
>
> You're doing great.
>
Thanks, we will laugh at it when people will start complaining for the
bad snom plug-in. :-)
Many people said to be interested in the plug-in. But I had no request
to actually test it ... :-(
If something goes wrong, I'm here to fix it.
>
>> Any chance that the 4.0.x branch will be built regularly? I really want
>> to test it throughly but I cannot afford it to run it in a development
>> environment.
>
> 4.0 nightly builds for testing are here:
> https://sipxecs.sipfoundry.org/temp/sipXecs/4.0
I know where to look for rpm builds :-)
Please look here:
https://sipxecs.sipfoundry.org/temp/sipXecs/4.0/CentOS/5/i386/RPM/
This build is not much newer than 4.0 stable. I have no means to
investigate what went wrong ...
Alberto
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
