SipSupport
Version 6 (Adrian Georgescu, 03/13/2009 02:11 pm) → Version 7/38 (Adrian Georgescu, 03/13/2009 02:13 pm)
= Support =
The project is developed and supported by [http://ag-projects.com AG Projects]. Established in 2002, AG Projects has specialized in serving companies like cable operators and Internet service providers, by providing simple solutions for their complex problems. The solutions include the analysis of requirements, tailoring of our standard products to meet the customer's requirements, project management, implementation, after sales training and support activities. AG Projects is an active developer of OpenSIPS project and is the driving force behind the open source projects OpenXCAP, MediaProxy, CDRTool and MSRPRelay.
We have long time commitments with our customers. We typically support our customers for several years.
== Free support ==
Free support is provided on a best-effort basis. "best-effort" means that we try to solve the bugs you report or help fix your problems as soon as we can, subject to available resources.
To request support you must use the [http://lists.ag-projects.com/mailman/listinfo/sipclient mailing list].
Bug reports must be submitted by opening a [http://sipsimpleclient.com/newticket ticket]. To open ticket please Register first.
== Paid support ==
If you require commercial grade support you may contact Adrian Georgescu by:
* tel: +31-20-8005169
* sip: !info@ag-projects.com
* email: sales-request@ag-projects.com
== Contributing ==
If you want to help us fixing a bug that you found or if you want to contribute with a new feature you must be familiar with the darcs version control system from http://darcs.net.
First make sure you are using the latest version by doing a 'darcs pull'.
Then record your changes using 'darcs record'. Follow the following guidelines for recording your changes:
* Keep a patch name under 74 characters, so that a darcs changes in a 80 char console is consistent and readable. If you need to write more than that, use --edit-long-comment or do not specify -m "patch name" and it will automatically ask for a patch name and a long comment. Also keep the long comment inside the 80 char frame
* When you add a long comment, you have the patch name on the first line. After that, leave an empty line and then add the long comment starting from the 1st column. If you need to add bulleted entries in the long comment, use a dash (-) not an asterisk (*), to avoid confusion with the asterisk darcs places before every patch name.
* Record separate patches for each distinct changes you make. Do not mix different changes in a single record.
* Use darcs replace to rename tokens if possible instead of using a search and replace in your editor. It correctly handles cases where someone else still kept using the old name (it will automatically rename this uses of the old name when he pull the darcs replace patch, which a simple token rename done by the editor and recorded as a standard diff will never do, requiring further patches to rename the old tokens that the other developer added in his code while you were doing the renaming).
Finally open a ticket at http://sipsimpleclient.com/newticket describing your patch and the problem solved and submit the patch using:
{{{
darcs send --to devel@ag-projects.com
}}}
See also [wiki:SipContributions Third-party contributions] page.
The project is developed and supported by [http://ag-projects.com AG Projects]. Established in 2002, AG Projects has specialized in serving companies like cable operators and Internet service providers, by providing simple solutions for their complex problems. The solutions include the analysis of requirements, tailoring of our standard products to meet the customer's requirements, project management, implementation, after sales training and support activities. AG Projects is an active developer of OpenSIPS project and is the driving force behind the open source projects OpenXCAP, MediaProxy, CDRTool and MSRPRelay.
We have long time commitments with our customers. We typically support our customers for several years.
== Free support ==
Free support is provided on a best-effort basis. "best-effort" means that we try to solve the bugs you report or help fix your problems as soon as we can, subject to available resources.
To request support you must use the [http://lists.ag-projects.com/mailman/listinfo/sipclient mailing list].
Bug reports must be submitted by opening a [http://sipsimpleclient.com/newticket ticket]. To open ticket please Register first.
== Paid support ==
If you require commercial grade support you may contact Adrian Georgescu by:
* tel: +31-20-8005169
* sip: !info@ag-projects.com
* email: sales-request@ag-projects.com
== Contributing ==
If you want to help us fixing a bug that you found or if you want to contribute with a new feature you must be familiar with the darcs version control system from http://darcs.net.
First make sure you are using the latest version by doing a 'darcs pull'.
Then record your changes using 'darcs record'. Follow the following guidelines for recording your changes:
* Keep a patch name under 74 characters, so that a darcs changes in a 80 char console is consistent and readable. If you need to write more than that, use --edit-long-comment or do not specify -m "patch name" and it will automatically ask for a patch name and a long comment. Also keep the long comment inside the 80 char frame
* When you add a long comment, you have the patch name on the first line. After that, leave an empty line and then add the long comment starting from the 1st column. If you need to add bulleted entries in the long comment, use a dash (-) not an asterisk (*), to avoid confusion with the asterisk darcs places before every patch name.
* Record separate patches for each distinct changes you make. Do not mix different changes in a single record.
* Use darcs replace to rename tokens if possible instead of using a search and replace in your editor. It correctly handles cases where someone else still kept using the old name (it will automatically rename this uses of the old name when he pull the darcs replace patch, which a simple token rename done by the editor and recorded as a standard diff will never do, requiring further patches to rename the old tokens that the other developer added in his code while you were doing the renaming).
Finally open a ticket at http://sipsimpleclient.com/newticket describing your patch and the problem solved and submit the patch using:
{{{
darcs send --to devel@ag-projects.com
}}}
See also [wiki:SipContributions Third-party contributions] page.