Dear All,
As the deployment of the iptel.org ser package has increased, the number of questions being asked on the 'serusers' mailing list have also increased, a significant proportion of them from people who are just beginning to comprehend the usage of ser and the associated modules.
A group of experienced ser users have decided to help the community and are working on a 'Getting Started' document that will detail how to deploy a working ser environment and then configure it to support authentication, MySQL, PSTN Gateways, NAT and many other facilities.
The same group have also noticed that creating a common repository of files and modules that support ser is also greatly needed. This is not a replacement of the iptel.org and cvs.berlios.de sites or the serusers list, but an extension of their existing capability to support the practical side of deploying ser into live environments.
It is hoped to release the first draft of this 'Getting Started' document into the community within the next few weeks.
The community site is already now open at http://onsip.org/ http://onsip.org/. Please register and have a look!
So watch this space and we hope that the community will appreciate this work
Paul ( phazlett@gmail.com ), Simon ( simon@SystemsRM.co.uk ), Greger ( greger@teigre.com )
Hi!
Up to now I can only find the README of the lcr module and the README of the xlog modul on the website.
IMO it is a bad idea to put README files on this website. Who will update these files if the original files in CVS will change. This will lead to inconsistence.
I rather would like to see, if the site would be like voip-info: Publishing user experiences and documentation which can't be found on the iptel site. e.g.: - snippets of ser.cfg for certain features - complete ser.cfg's - description of undocumented functions (until they are in the original documentation. This way everbody can easily write documentation and after some time a serdeveoper with cvs acces and sgml knowledge can copy-past it into the offical documentation) - architecture (HA, ser+asterisk, ser+gateways) - NAT traversal
Only tested and working ser.cfg's should be posted here. No discussions, feature requests ... --> these belong to the mailinglist.
regards, klaus
Simon Miles wrote:
Dear All,
As the deployment of the iptel.org ser package has increased, the number of questions being asked on the 'serusers' mailing list have also increased, a significant proportion of them from people who are just beginning to comprehend the usage of ser and the associated modules.
A group of experienced ser users have decided to help the community and are working on a 'Getting Started' document that will detail how to deploy a working ser environment and then configure it to support authentication, MySQL, PSTN Gateways, NAT and many other facilities.
The same group have also noticed that creating a common repository of files and modules that support ser is also greatly needed. This is not a replacement of the iptel.org and cvs.berlios.de sites or the serusers list, but an extension of their existing capability to support the practical side of deploying ser into live environments.
It is hoped to release the first draft of this 'Getting Started' document into the community within the next few weeks.
The community site is already now open at http://onsip.org/. Please register and have a look!
So watch this space and we hope that the community will appreciate this work
Paul ( phazlett@gmail.com ), Simon ( simon@SystemsRM.co.uk ), Greger ( greger@teigre.com )
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi Klaus, I think we all agree that there has been a gap between needs and what has been available. The serusers list has been suffering and people have spent too many hours trying to track down information they need. Many people do not have the technical capabilities you have and are not capable to sort through unstructured information and sort the wheat from the chaff. This is also extremely difficult when you are new the ser (and maybe SIP).
Exactly what should fill the gap is still open. We have made an attempt at providing a space for user-contributed, semi-structured information at http://onsip.org/. In my opinion it should not be like voip-info.org, there is a need for somebody taking a moderator role to secure the accessibility of the information (this is the "structured" part). Also, being able to comment directly on downloads, posts, etc is often extremely valuable. The PHP.net online (commentable) documentation is a very good example of this "semi-structured" approach.
We don't have the answers, only some ideas, and it's up to the community to vote forward the good ideas with clicks and contributions and the bad by ignoring them (and maybe voip-info will come out as the better alternative).
Anyway, as you are one of the authoritative people on many ser issues, I sincerely hope you take ONsip.org for what it is and contribute positively to making ser more accessible to more people. You will hopefully find that our intentions of posting complete ser.cfg examples from our Getting Started document will cover some of the things on your list below. We had intended to launch ONsip.org when the first draft was ready, but decided that the recent discussion on the list would benefit from the information about our current activities.
Best regards, Greger
Klaus Darilion wrote:
Hi!
Up to now I can only find the README of the lcr module and the README of the xlog modul on the website.
IMO it is a bad idea to put README files on this website. Who will update these files if the original files in CVS will change. This will lead to inconsistence.
I rather would like to see, if the site would be like voip-info: Publishing user experiences and documentation which can't be found on the iptel site. e.g.:
- snippets of ser.cfg for certain features
- complete ser.cfg's
- description of undocumented functions (until they are in the
original documentation. This way everbody can easily write documentation and after some time a serdeveoper with cvs acces and sgml knowledge can copy-past it into the offical documentation)
- architecture (HA, ser+asterisk, ser+gateways)
- NAT traversal
Only tested and working ser.cfg's should be posted here. No discussions, feature requests ... --> these belong to the mailinglist.
regards, klaus
Simon Miles wrote:
Dear All,
As the deployment of the iptel.org ser package has increased, the number of questions being asked on the 'serusers' mailing list have also increased, a significant proportion of them from people who are just beginning to comprehend the usage of ser and the associated modules.
A group of experienced ser users have decided to help the community and are working on a 'Getting Started' document that will detail how to deploy a working ser environment and then configure it to support authentication, MySQL, PSTN Gateways, NAT and many other facilities.
The same group have also noticed that creating a common repository of files and modules that support ser is also greatly needed. This is not a replacement of the iptel.org and cvs.berlios.de sites or the serusers list, but an extension of their existing capability to support the practical side of deploying ser into live environments.
It is hoped to release the first draft of this 'Getting Started' document into the community within the next few weeks.
The community site is already now open at http://onsip.org/. Please register and have a look!
So watch this space and we hope that the community will appreciate this work Paul ( phazlett@gmail.com ), Simon ( simon@SystemsRM.co.uk ), Greger ( greger@teigre.com )
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Simon Miles wrote:
The community site is already now open at http://onsip.org/. Please register and have a look! So watch this space and we hope that the community will appreciate this work
Have looked on this site... I think, it's very overloaded... too hard to use... and some type of inconvinient... I think, community need to decide, what type of engine will used on site.
-
Alexey N. Kovyrin ＠ Home -
Greger V. Teigre -
Klaus Darilion -
Simon Miles