Hi Damian,
I've been testing the plug-in in 4.1 for a couple of weeks. It is
working fine and I had no issue so far.
I would not see anything against adding it to 4.0.1. Do you think it
would be possible to have it in a 4.0.x?
Thanks
Alberto
Damian Krzeminski ha scritto:
Alberto wrote:
Damian Krzeminski ha scritto:
Thanks a lot. I will try to find some time to check this by the end of the
week.
Thanks Damian! If it doesn't cost you too much time can you make the
snom plug-in a separate project. It would be nice to test the plug-in
just dropping a jar.
Done.
Also it's much easier to build and run the tests now.
cd sipXconfig/plugins/snom
ant precommit
There is still an open issue: languages are not loaded in the phone
firmware in v7. 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>
Very silly to say ... I don't know how to extend the plug-in to generate
a second file. It would be enough to generate it once. It's definitely
not needed to do it for every snom phone in the system.
Please tell me if there is a good place I can look to take the right
inspiration...
If the file never changes we can declare it as 'static' profile element.
<property name="staticProfileFilenames">
<list>
<value>file-name.cfg</value>
</list>
</property>
But I am pretty sure that would not take care of generating proper URL.
We can just add another ProfileType - that requires some changes to the
plugin. You can grep for getProfileTypes to see how other plugins do that.
If you wait a day or two I'll try to make some changes to SnomPhone that
would make it easier.
Well I saw I could add a static profile. But the file there is not
static. It contains a list of file the phone should load. First two are
language files (actually fw 7.3.14 specific language files), the third
is the sipxconfig phone profile. This make it non static.
Using the {mac} variable we can skip adding it for all phone and do the
thing just once.
It's actually trivial to have a file per phone (if you want to have
languages list configurable for example). We need to add another profile
type: I did not do it yet.
I was thinking a better deploy solution to handle this. It wold be
probably a good idea to extend the plug-in with an upload feature for
language files, so that administrator would have the chance to load the
right ones for their firmware version if they feel they do now want to
generate lots of wan traffic just booting the phones. It's about 120
kbytes per phone. In this case the file above would have the first two
lines pointing to some local destinations. Snom provide language files
in tgz compressed file. Can we upload and uncompress with the Upload
feature?
Makes sense.
You can have .zip files defined as upload. Not sure about .tgz. Huijun do
you remember if we can handle it?
So if you like the idea the file above, let's call it snom.xml (first
file to be loaded from the phone: dhcp option 67), will contain the
basic provisioning link in the snom site for fw 7.3.14 out of the box.
But if the sipxecs administrator load some other phone language files
snom.xml changes accordingly pointing to some local destination. Is this
possible with the current plug-in framework?
Yeah - I think that plug-in can check what types of language files are
deployed and generate proper file.
I would start by adding support for the 2nd file.
D.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
