Most stable SS7 Implementation WAS: facing problem with libss7
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Most stable SS7 Implementation WAS: facing problem with libss7
- From: krzysztofdrewicz@xxxxxxxxx (Krzysztof Drewicz)
- Date: Thu, 17 Mar 2011 14:27:05 +0100
- In-reply-to: <AANLkTi=dhipyXvER+RoUA8Hqk0on_v9_ow-6o03x+iPL@mail.gmail.com>
- References: <AANLkTi=dhipyXvER+RoUA8Hqk0on_v9_ow-6o03x+iPL@mail.gmail.com>
2011/3/17 Jeremy Parr <jeremyparr at gmail.com>:
>
> On that note, which flavour of SS7 driver provides the best support and
> stability. It appears that Sangoma have their own SS7 implementation, as
> does Digium.
Well, Sangoma's libss7 does not have HA capability when you want to
split: one Signalling Point of your * (many CICs and at least two
signaling TS) on different hardware PC, so Sangoma's LIBSS7 is no good
for me. The slides from Sangoma, look the very same as they have been
3 years ago.
[Index of Archives]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite Backpacking]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]
[Asterisk Books]