Rumor is Cisco is no longer going to do any further feature development for Jabber besides some features coming up in the next release. They want everyone to move to Spark. They have given Jabber 3-4 years more before they announce end of life. Anyone here knows if this is true?
Solved! Go to Solution.
We heard this announcement directly from Cisco SE/AM. They advised us to start moving to Spark if its a green field install, they were told Jabber had reached feature maturity and would eventually be end of sale. We were about to deploy Jabber with the possibility of removing over our current Lync environment. But this announcement has now made us re-evaluate removing Lync
Having dealt with many customers I can tell you there are various tools for various purposes. On one hand some customers have migrated to a texting/messaging tool and others rely on ad-hoc 1:1 with classic IM/P with a s strong set of telephony features. You can't tell all customer's to just leave one way and adopt another overnight, there is a bridge and while the world is infatuated by spark like messaging tools the reality is there are many who are fine with Jabber/Lync style tools. Can we see the whole world adopt to one style(maybe) but that is a long way away and varies based on customer/vertical industry.
So the messaging from your account team is frankly a bit rough around the edge. Spark definitely is where Gartner and the industy seems it going i.e. work stream oriented tools and there is only so much you can keep adding to Jabber. After all what more is left to add to IM/P to begin with, most of those features already exist on Jabber
The key on your end is to evaluate your end user interactions and decide which tool makes the most sense.
Good day Pedro,
Based on our insights, Jabber is here to stay for the foreseeable future. True, their is a big marketing push for Spark. However, your choice is dependent upon your or your customer's business requirements. We actually just released a new technical article regarding Jabber and the next major iOS release. You can read it here:
Jabber 12.0 is about to be released in March 2018 with Multi-line support (8 lines), a full complement of mid call features, a new Phone mode with contacts deployment option, single number reach control, and a brand new Jabber BOT SDK for building automated bots for use within Jabber. Please join the Customer Connection Program product roadmap sessions to find out what is being planned after 12.0!
How is that any different what MSFT is doing for that matter? They are doing very much the same and investing only in Teams. Next version of SFB is also the exact same just a maintenance release to bridge them to teams
The point is vendors have to pivot where the market is heading at least jabber has multi line which sfb still doesn’t have after all these years.
If you want to blame anyone blame slack or the million other work stream vendors pitching this type of solutions. Even Ring central with glip is doing the same
Point is if a vendor has to pick and choose between clients and all your competitors and customers are also moving in that direction what do you expect to happen?
@Srini -- I'm just pointing it out.... I agree, this is an industry-wide thing.
@thlamber - As my timetable above highlights, there is a change in the release schedule (almost 2x as slow) which is indicative of a dying product. I am seeing this happen with all kinds of different on-prem products; Jabber is nothing different. Call my observations whatever you want.. the timetable shows a decline.
@thlamber, I'll just let the facts talk.. as I mentioned before.. talk is cheap.
Average before v11.9: (122+98+130)/3 = 117/30 = 3.8mo
Average v11.9 and after: (246+205)/2 = 226/30 = 7.5mo
7.5 / 2 = 3.75 which oddly enough, lines up pretty much exactly with my "almost 2x as slow" statement.
Dang I'm good.