On Tue, 2008-05-27 at 20:42 +0530, VG wrote: > Hi Scott, > > Thanks for your reply. > If this is a new feature to for addition then please tell me from > where I can start it. > > how this feature can be added and TUI feature activation will be > possible.
The process for proposing and contributing a new feature is essentially the same as that to fix a bug. Have a look at http://sipx-wiki.calivia.com/index.php/How_to_report_a_problem_with_sipXecs for some of the process details. The first and essential step is to write up a thorough description of what the feature should look like from the perspectives of a user and an administrator and post that description here on the sipx-users list where it can be discussed by the community. You may want to create a tracker issue at the same time and put a link to the email thread, but I think it's better to keep the discussion on the list until some consensus is reached about the basic functionality and create the issue from that. In response to your posting on the users list, I replied: > I would suggest that something like forwarding is so error prone that a > more interactive process than the method you suggest be used, but either > could be built. By which I meant that it might be better to call some forwarding service that acted like an autoattendant - prompting the user for what they want to do and providing confirmation that the requested change has been made. It's pretty easy to misdial a number and think that you've forwarded it to one place when you've really forwarded it somewhere else. Using a star code may also be more difficult to select things like whether the forwarding should be 'after no answer' or 'at the same time', and when and how to undo the forwarding. After some agreement is reached on what the external (human-visible) functionality should be, there should certainly be a tracker issue created. Then we can discuss the design - that is which component(s) are responsible for implementing the feature and any interfaces between components. This discussion should probably move to the sipx-dev list. Try _not_ to mix the functional and design discussions as much as possible. > I can try my Best. We look forward to your contribution. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
