On Tue, Mar 10, 2009 at 09:38:34AM -0700, Vieri wrote: > > > --- On Tue, 3/10/09, Tzafrir Cohen <tzafrir.co...@xorcom.com> wrote: > > > But it will still be able to build vs. zaptel, and read > > configuration > > from zapata.conf . > > > > See > > http://svn.digium.com/svn/asterisk/branches/1.4/Zaptel-to-DAHDI.txt > > Sorry to get back on this silly compilation issue. Also, I'll probably > be migrating to dahdi anyway but nevertheless I'd like to understand > why I can't upgrade seamlessly from 1.4.21.2 to 1.4.23.1 w/zaptel.
You can. I can't think of any operational change. Except that "zap" CLI commands are now considered deprecated (that is: they work, only print a slightly scary warning occasionally). When migrating to 1.6.0 you *will* have to change the name to DAHDI in the dialplan and other places. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir _______________________________________________ -- 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