Alejandro Rios wrote: > Oops, bad subject, bad fingers :s > > --- > Hi, > > I'm just trying callweaver on a rhino ceros machine with a MCFR2 E1, > > I'm using: > > callweaver-1.1.99.20070430.tar.gz snapshot, > libmfcr2-20070325.tar.gz > libunicall-20070325.tar.gz > libsupertone-20060205.tar.gz > and, > spandsp-20070502.tar.gz > > The E1 was working with asterisk-1.2.13 and old versions of unicall and > spandsp stuff (which implies I know the telco is fine and also the > signalling data), but it doesn't work with callweaver. > > When the machine starts up, zttool shows no alarms on the E1 card, and > both, > Tx and Rx ABCD bits show 1101 (blocked), but, after chan_unicall is > loaded, > only TX bits become 1001 (unblocked) and the CLI shows "local end > unblocked" > but no "far end unblocked" for each channel. > > I created a callweaver user in the system, and added it to the 'dialout' > group, which has the defaults permissions for zaptel on > /etc/udev/permissions.rules. > > What other debug info should I provide so that you may help me with this > issue? > > If zttool shows the signalling state as 1001/1101 when callweaver is running, that should be what is really happening on the wire. It sounds like something is not right beyond callweaver. Are you sure the telco hasn't disable the trunk since you disconnected it from the original working system. I can't remember anyone reporting if a rhino cards worked with MFC/R2.
Regards, Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
