Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

4.6 Release

Scaling beyond 10K users

Some inefficiencies in the way user's configuration data is replicated to all parts of the system limit the overall number of users a system can handle.

Enhanced Support for Branch survivability

In HA (High Availability) configurations, you were limited to a maximum of three proxies. For a single data center, that is usually enough but if you use HA to distribute your proxies to branch locations so achieve branch survivability then three can be quite limiting. It's not unusual for companies to have hundreds of branches that all want to be configured centrally but survive locally should connection to office be down or simply to reduce bandwidth over the WAN.

Skills based, distributed Call Center with OpenACD

OpenACD is a feature rich, open source call center. Goal is to integrated administration support that matched and in some cases exceeds the features of the current ACD application currently bundled in sipXecs.

High Availability for Voice Mail

Redundant, distributed voice mail servers. Current limitation is a single voice mail server on the master node. We look to eliminate both of these limitations.

Guard against DoS attacks.

...

sipXecs 14.10 Release

Config

Improve DNS Alarming

Need improved alarming for DNS related problems.

Improve DNS Handling

Implement Custom DNS changes and fix issues with current implementation.

DNS Advisor

DNS Advisor is broken and we also need to make it work with Regions.

( http://track.sipfoundry.org/browse/XX-11006 )

Admin Portal / GUI Simplification

Begin work on full API drive admin portal. This would entail ensuring that all functionality is performed through API’s and building a nice web front end with re-worked administrator experience. 3 phase approach design and underlying needs, then would address day to day feature admin before full-on system configuration.
1. Settle on interaction design.
2. Build API’s required for Phase 1.
3. Phase 2 & 3 - Build web application.

Phase 1 would be settle on Interaction Design and in parallel start building any missing API’s.
Phase 2 would be Users / Devices & Features menus into new portal design.
Phase 3 would be remainder of API’s
(http://track.sipfoundry.org/browse/XX-10770

Merge Logs & sipXtrace

Bring back merge logs / make sip call trace of each call in CDR available for admin to view or download. (http://track.sipfoundry.org/browse/XX-10914)

Park Orbit Service Replacement

Move Park orbits from old service to FreeSwitch and make HA. Needed for scalability and virtualization. SSS needs to accommodate BLF for park orbit so it might make sense to get this done before work on SSS begins for this feature. (http://track.sipfoundry.org/browse/XX-8473)

System Audit

Track config system changes.

( http://track.sipfoundry.org/browse/XX-9535 )

 

Voicemail to eMail Template

XX-10035 Voicemail to email template should allow custom url that can direct to a user mailbox

 

sipXcallqueue

 

Work on various sipXcallqueue issues.

Client

End User Portal

Continue to add functionality envisioned for new User Portal.

Documentation

We're considering combining sipXecs and eZuce wiki’s for a single documentation portal. This would allow for consistent quality documentation.  We need to work out how to link back to community created content.