http://blog.gmane.org/gmane.comp.voip.sipx.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.voip.sipx.devel/12019 Picher, Michael 2008-08-30T11:26:47 http://comments.gmane.org/gmane.comp.voip.sipx.devel/12017 rabail javed 2008-08-29T20:06:29 http://comments.gmane.org/gmane.comp.voip.sipx.devel/12010 I am working on what I believe is the last of the -config.in changes and I have a couple questions. First, I don't see any support in sipXconfig currently for mediaserver-config. Is sipXconfig resposible for any of the generation of this file, or is it always edited by hand? I am assuming that sipXconfig dos not have a hand in generating this file currently. I have created a Velocity template so that sipXconfig can generate the file, taking the place of running the .in through config.defs. However, I have had to change the formatting of the comments and line breaks in the template. Also, the generated file has no comments at all, as it should never be edited directly. Does anyone see a problem with this? As soon as I can get my builds running again (having problems with jain-sip) I will post a patch for this issue. In the meantime comments are welcome. Thanks, Kevin Kevin Thorley 2008-08-29T10:28:16 http://comments.gmane.org/gmane.comp.voip.sipx.devel/12008 Paul Mcdaid 2008-08-29T09:22:06 http://comments.gmane.org/gmane.comp.voip.sipx.devel/12006 http://track.sipfoundry.org/browse/XCF-2396 Andrei: Thanks for the patch but I do not think I can accept it. GatewayContext is a generic class: it cannot have any specific knowledge of parameters. What we need here is probably some kind of simple mechanism that would let plugins (or anyone for that matter) register for parameter changes and react accordingly. Other ideas welcomed (as long as we keep specific parameter names out of core classes). D. Damian Krzeminski 2008-08-29T00:32:29 http://comments.gmane.org/gmane.comp.voip.sipx.devel/12005 If you compare Andrei's patch for XCF-1098 with what I ended up committing you notice that I ended up committing much simpler version of this feature. I removed restart persistence (scheduling restarts surviving sipXconfig restart) and status reporting (new columns for devices table, new error messages). I significantly simplified the UI. The only addition is the date/time field that let's you to specify the restart time when generating the profile. By default it's pre-filled with current date/time. I wanted to commit such simple implementation first. It's hard to get all details right (although Andrei did in most cases) and I would not want this to stand in the way of implementing background profile generation. DeviceStatus is a good concept - but it's probably better if such status is mainained by profile manager and not by Phone/Sbc/Gatewat context. The fact that someone scheduled device restart is an interesting data point, but it should not prevent me from regenerating the profile and restarting devi Damian Krzeminski 2008-08-28T16:55:24 http://comments.gmane.org/gmane.comp.voip.sipx.devel/12002 As Kevin mentioned, we are working on config file generation for the various sipX services. I am currently working on XCF-2683, generating sipXdialog-config. I noticed, though, that sipXdialog is not listed as a sipX process when I type the sipxproc command, and there is no sipxdialog.process.xml in /etc/sipxpbx/process.d. Should I create one, so that it is a process? Or should I piggyback its config generation to another service (like sipXpbx), if such a thing is possible? Joseph Attardi 2008-08-28T13:52:28 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11999 Hi All, I am working on issue XCF-2391 : for the support of SNOM v.7 firmware, and have a query related to XML format configuration files. Snom's firmware version 7 and above, supports XML format configuration files. But firmware version lesser than 7 does not support XML format configuration files. Hence, I feel that we need to have an option to select the firmware version from the configui (similar to Polycom phones). To avoid providing the entire list of firmwares that the sipx supports and to make a clear distinction between the XML and non XML file formats, I am planing to give the following options in config ui. Firmware version : version less that 7 version 7.X/higher Please advise/comment. Thanks, Shruthi shruthi.j 2008-08-28T12:17:59 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11997 Version is now 1.2.79. Please update the RPM as well. ( Not sure I agree with having both the sipx-commons and RPM -- both with the same jar file). Thanks Ranga M. Ranganathan 2008-08-27T18:02:17 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11994 The RPM build of sipXpbx fails with the following error: RPM build errors: File not found: /var/tmp/sipxpbx-3.11.5-root/usr/bin/sipxrls-config Could this be related to Kevin's recent changes that remove configuration files? Just a guess... :-) Misha Misha Vodsedalek 2008-08-27T17:11:06 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11992 On August 25th, two properties files were added to sipXconfig/plugins/linksys/etc/linksysPhone (phone_pl.properties and line_pl.properties). The RPM build fails because these files are installed but not packaged. Misha Misha Vodsedalek 2008-08-27T16:07:29 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11988 Hi, I am trying to update the version of jain-sip in sipXcommons and observe that I need to update versions in all the config.properties.in in all build directories where the file is referenced. It would have been easier to create a symbolic link for the jar file and hence avoid this. Any reason why we cannot do that? Ranga M. Ranganathan 2008-08-27T14:56:33 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11984 Anand Yogas 2008-08-27T12:56:12 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11983 Manoj Gupta 2008-08-27T12:38:12 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11981 Hi, in the last few days the build system is not succeeding in packaging a CentOs 5 image. Unfortunately it's not possible to access the build summary page that was before available at http://sipxecs.sipfoundry.org/build/ At least this issue seems related to the recent DNS changes for pingtel.com. Hope someone can work it out. Thanks in advance Alberto Alberto 2008-08-27T06:53:16 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11977 Nikolay Kondratyev 2008-08-26T17:06:24 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11975 Joe and I are working on finishing up the migration of *-config.in files to sipXconfig so that we can eliminate config.defs. I started looking at http://track.sipfoundry.org/browse/XCF-2682 which deals with mediaserver-config. However, Damian mentioned that this may no longer be required with the introduction of sipXivr. So, what is the status on this? Should we bother migrating the generation of mediaserver-config to sipXconfig, or is it going to disappear? Thanks, Kevin Kevin Thorley 2008-08-26T14:02:21 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11973 I think that devs can can should get on freenode.net sipxecs-dev to make communiction easier Richard Neese 2008-08-25T20:47:01 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11959 I attached to the JIRA issue XCF-2692 (http://track.sipfoundry.org/browse/XCF-2692) the UI proposal for this feature. Please comment. Regards, Laurentiu Laurentiu Ceausescu 2008-08-25T11:58:51 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11958 Manoj Gupta 2008-08-25T11:35:06 http://comments.gmane.org/gmane.comp.voip.sipx.devel/11951 Hi, Anyone cares to apply the following Polish properties update patch to 3.10 branch ? http://www.voiceworks.pl/pub/polish-3.10.2.13245_v1.diff.gz Pawel, junk< at >urtho.net 2008-08-22T22:52:58 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.voip.sipx.devel