HI Jester
Hope you are well.
there was a note about discontinuing bristuff ...
Yes... and that was our intention. Let me try and explain where we are with SARK/SAIL and then answer your question. We wanted (still want) to go with mISDN in 1.4 because it doesn't require any patches to asterisk. For a long time, we've wanted to drop our own asterisk rpms and use more generic items (in particular the ATRPMS products). Unfortunately, mISDN doesn't quite cut it at the moment because it doesn't seem to offer any soft echo cancellation. Bristuff, on the other hand, can run with both OSLEC and HPEC. Echo is still a major issue for Asterisk based systems. You can't predict in any given installation whether or not you will experience echo but if you do, then you have to have some way of fixing it. The latest generation of echo cancellers (OSLEC, HPEC and the Octasic hardware boards) are truly excellent and, more than any other improvement, have made asterisk based systems a true alternative to conventional TDM gear. For the first time, you can confidently install a system knowing in advance that you willl not experience echo problems on your TDM circuits.
2.1.15 was put together as a development mule for 1.4 and mISDN. Herve built the mISDN code and did a truly excellent job of it. Unfortunately, while we were experimenting with 2.1.15, 2.1.14 continued to gain new functionality and the two bases diverged somewhat.
2.2.1 is essentially a late release of 2.1.14 modified to run with Asterisk 1.4 and the ATRPMs. The next step is to fetch forward the mISDN functionality from 2.1.15 and merge it into 2.2.1. However, in the meantime, we need to support ISDN2E in 1.4 for our existing customers and Junghanns have produced a Bristuff for 1.4.
So, for now we have 2.2.1 with either ATRpms or Bristuff 4 rpms (built by us). Bristuff 4 seems to run well and we've had it in production on our own office switch for over a month without problems. However, we still would really like to go with mISDN
provided someone cracks the echo issue (we won't do it - it's too far outside our brief) because then we don't have to produce any asterisk rpms.
So that's where we are. Not quite where we planned but not too bad when you consider all of the conflicting currents swirling around in the asterisk world.
Unfortunately for you, 2.2.1 SAIL will NOT run with the selintra asterisk 1.4 rpms becasue there is currently no support in it for mISDN.
We would recommend, for the moment that all of our users plan to move to 2.2.1. It is very nearly ready for production and we will begin moving our own customers in the next month or so.
Re buildsys.contribs.org... I've seen references to this system but it isn't obvious how to use it. Currently, we handbuild our own custom .iso (which we've never distibuted except to our customer base) by breaking into the SME7.2 .iso. It isn't hard but it does take time.
Kind Regards
S
24 Replies
4053 Views