On Mon, 2014-03-03 at 08:47 +0100, Per Jessen wrote:
Hans Witvliet wrote:
On Sun, 2014-03-02 at 10:30 +0100, Per Jessen wrote:
Yes, I would do that for e.g. asterisk itself, but without the extra hardware (multi-port ISDN cards basically), the my testing would be way incomplete. This is probably an area that receives very little testing/attention during development.
Without any spare hardware it is nearly impossible to avoid awkward situations.
At work, i tried to minimalize the impact... I separated the ISDN-trunk-line from the main PABX-functionality of asterisk. One box acting only as ISDB-bri gateway, and asterisk and the real-time-DB virtualized on other hardware. Instead of upgrading the asterisk-box, just make another virtual client, and when satisfied enough, switch one vm off, and have the new vm and the isdn-gw point to each other.
Interesting setup. What do you have running on your gateway then and how does asterisk talk to it?
The main asterisk-server, (sles as a XEN-vm) looks at the ISDN-gw as a IAX-trunk line. The gateway itself is just-enough sles + asterisk. But i was reminded lately that i could possibly use a box from AVM (fritz-7170B of 7390). These boxes are nomally sold as adsl2-anex-B-modem. These were recommended, as there are no (decently priced) single/double line ISDN-BRI gateways. Perhaps less flexible as a custom build gateway, but requiring less energy. For home use, i just ordered myself a 7930, if i succeed i'll share my findings/configs. hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org