From 51c06791324573a771799dd3f39efa8fb72516d9 Mon Sep 17 00:00:00 2001 From: Tzafrir Cohen Date: Mon, 16 Mar 2009 15:01:14 +0000 Subject: dahdi.init: call xpp_sync a bit later. xpp_sync needs to only be called after dahdi_cfg was run, because the application of system.conf may change the priority of a PRI module span (If it is a sync provider, "NT", priority is lower). Also some documentation-only changes for xpp_sync. git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@6167 a0bf4364-ded3-4de4-8d8a-66a801d63aff --- xpp/README.Astribank | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'xpp/README.Astribank') diff --git a/xpp/README.Astribank b/xpp/README.Astribank index fc3d4df..05c8a74 100644 --- a/xpp/README.Astribank +++ b/xpp/README.Astribank @@ -1112,6 +1112,19 @@ parameter <<_zap_autoreg>> in the modprobe configuration file (A file under options xpp zap_autoreg=1 +Astribanks Synchronization Source +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +If there is more than one Astribank on the system, all the Astribanks +keep their clock in sync. Optionally the Astribanks can synchronize +their clock to the master DAHDI device (in case it is a different DAHDI +device). Normally you just use the default init.d script or run +explicitly: + + xpp_sync auto + +(For now see the man page of xpp_sync for more information) + + DAHDI And Above ^^^^^^^^^^^^^^^ From here you get a standard DAHDI span. The next step is to configure -- cgit v1.2.3