Avaya today announced an upgrade to its core Communications Manager software package, to release 5.0. The company's headline for the release is "End to End SIP," and indeed they appear to be incorporating more SIP functionality into CM. But they haven't eliminated the need for the SIP Enablement Server (SES)as a separate entity, and according to Anne Coulombe, who briefed me on the announcement, that's reflective of where the market is relative to SIP.
Avaya today announced an upgrade to its core Communications Manager software package, to release 5.0. The company's headline for the release is "End to End SIP," and indeed they appear to be incorporating more SIP functionality into CM. But they haven't eliminated the need for the SIP Enablement Server (SES)as a separate entity, and according to Anne Coulombe, who briefed me on the announcement, that's reflective of where the market is relative to SIP."We continue to add more and more SIP functionality with each release" of CM, Anne told me. For example, support for SIP trunking moved from SES to the core CM even before this most recent release. With the 5.0 release, this capability has been enhanced to support alternate routing through multiple SIP trunks to deal with potential congestion on a primary SIP trunk provider's line.
But SES is still needed for SIP enablement on the phone side, and Anne says this tracks with where the market is regarding SIP endpoint adoption.
