Ideas on Hackfest

Developer Setup in less than 10 minutes

Coordinator: Douglas
Summary: Get development environment setup quickly and reduce setup mistakes.

Description:
This idea was sparked because Douglas and George will be coming to hackfest w/o their workstations but instead laptops. Instead of not participating in hackfest, the day can be spent optimizing the steps to building a workstation. Once the goal is met, they can participate in other projects.

This project is particularly important going forward because 4.6 exposes more plugin APIs then ever before. Lowering the barrier to assembling a build system is crucial to extending sipXecs and therefore adoption of sipXecs..

Goals:

• System dependencies installed
• Full source tree compiled
• RPMs built for all distributions
• Eclipse installed with setup instructions (Eclipse is preferred IDE for Java apps)
• Easy to follow instructions.

Non-Goals:

• Not creating a "wrapper script" for system setup, but leverage standard tools and checks
• Not creating a virtual machine for setup, virtual machines get out of date fast and pain to maintain.

Integrate homer, a sip stack trace utility into sipXecs

Coordinator: ? (Douglas added idea but may not have time to work in it)
Summary: Embed Homer in sipXecs to capture message call flow

Description:
Whether you're a newbie or veteran SIP engineer, when there's a problem getting a call through the system, you need to see the call flow to all components. sipXsipViewer is a nice utility to see the call flow, but it can be cumbersome to collect the logs. Homer offers web based sip call flow complete with db query interface.

*Resources

• http://www.sipcapture.org/

Goals:

• Find active or past calls and see visual of call flow.
• Interface should be accessible from sipXconfig admin UI
• Optional install, e.g. not a required install for systems that do not want the overhead.

Develop plugin to store voicemails on other type of storage but local filesystem

Coordinator: George
Summary: Develop sipXivr plugin to store and retrieve voicemails from a ftp server

Description:
Porting sipXivr to Spring in 4.6 opens the door for various plugins like multiple voicemail storage support. More, these plugins could be developed in dynamic languages as JRuby or Groovy. Easy as implementing the right API, rewriting mailbox manager definition, packing it as a plugin (jar file) and deploying it in sipXecs.

Goals:

• Voicemails stored on chosen storage (could be ftp server or db)
• Voicemails retrieved from chosen storage

sipXecs administration via XMPP

Coordinator: George (originally suggested by Joegen some time ago)
Summary: Develop XMPP bot to perform admin functionality (similar with sipXconfig admin functionality)

Description:
Thanks to sipXecs 4.6 architecture and extensive usage of Spring (in projects like sipXconfig), any java based component could register as an XMPP user and interpret messages as commands. We'll walk together through all the steps required for learning sipXconfig to "talk" XMPP and perform common administration commands (like the one performed from CLI or sipXconfig UI).

*Resources

• http://static.springsource.org/spring-integration/docs/2.0.x/reference/html/xmpp.html

Goals:

• Query services status via XMPP command
• Start / stop services via XMPP command