> No. DAHDI is not related to libpri at all. Asterisk would only need to > be recompiled if there were libpri API changes, or to take advantage of > new features in libpri, or if you build Asterisk with libpri statically > linked in (which would be very uncommon). > > -- > Kevin P. Fleming > Digium, Inc. | Director of Software Technologies > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > skype: kpfleming | jabber: [email protected] > Check us out at www.digium.com & www.asterisk.org
...and presumably any such features & API changes would be clearly called out in the libpri ChangeLog? In other words the best current practice would be to check the libpri changelog as an authoritative source for any such changes: If only bug fixes are called out, just bounce asterisk. If you see other changes or features, recompile Asterisk. Is that a fair summary? Thanks! _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
