Release Notes and TODOs

SipExchange R 0.0.4a

1. SipExchange now is developed using the EJB3 architecture. The EJB3 architecture is the latest J2EE specification for enterprise application development. Although the end user do not see any difference but it is now much easier to develop back-end business logic because of this new technology.
   
2. Initial (experimental) support for web services is provided.
3. The automated unit tests have been revamped.
4. A number of bugs have been fixed.
   

SipExchange R 0.0.3a

1. The following subscriber features have been added:
1. Call forwarding
2. Call Screening.
2. The following system-level features have been added:
1. Multiple Appearance Address: One number rings many phones
2. SIP Gateway: Allows communication with a SIP carrier or service provider.
3. Code coverage tool added (only of importance to developers).
   
4. Many bugs have been fixed.

SipExchange R 0.0.2a

1. An early version of the presence service has been implemented. The presence service allows subscribers to add other subscribers to their contact list and monitor their presence. The feature allows subscribers to authorize or block request for subscriptions. There are many limitations that will be fixed in the next release.
2. An early version of the Subscriber Console has been implemented.  The subscriber console is a web-based user interface using which subscribers can manage their account, contacts and their features.
   
3. The proxy code has been re-written to handle proxy-related issues that caused SipExchange to not work with many SIP phones.
4. The administration console has been revamped. Administrator accounts can now be  managed from the console and domain parameters can now be configured. There are many other look and feel changes as well.
5. Email templates have been added. This feature will allow emails sent out by SipExchange to be customized on a per-domain basis using the powerful Apache Velocity templates.
6. Many bugs have been fixed.
   

SipExchange R 0.0.1a

1. Registration service: On SIP registration, the system authenticates the subscribers and stores their locations for routing inbound call sessions.
2. Proxy service: Supports SIP to SIP call session setup and tear-down. Inbound calls to SipExchange subscribers are routed to the subscribers' current locations. The service also allows subscribers to make outbound calls to other subscribers and non-subscribers.
3. CDR generation: The SipExchange server produces call detail records (CDRs) and stores them in the database for billing and reporting applications.
4. External call control: The basic framework for external call control using IN/AIN-like triggers is included.
5. Web-based administration and reporting: System administrators can administer SIP domains and subscribers. They can also tune system parameters and manage CDRs. The reports allow the system administrators to view user locations and CDRs.

TODOs

1. Enhancements to the external call control feature:
• Support media services for playing voice announcements, collect in-band DTMF digits and report them to the SCP (service logic), perform speech recognition, etc.
• Registration-time triggers.
• Presence-related triggers.
2. Subscriber and domain features. Namely:
1. Voice mail
2. Operator
   
3. Call queues
   
4. On-demand media streaming
3. Interface to SIP carriers: Will allow administrators to define rules that the proxy will use to route sessions to SIP carriers.
   
4. Statistics:  The system will monitor load and performance of the system and generate reports.
   
5. Load-sharing and Fail-over: You will be able to add additional servers for the purpose of load-sharing and fail-over.
   

Search this website 

Send questions or comments about this web site to webmaster@cafesip.org.
Copyright © 2005, CafeSip.org.
Licensed under the CafeSip License.
The CafeSip.org projects, web site and web facilities have been sponsored by QUIK Computing

Top of page