Steve Underwood <[EMAIL PROTECTED]> escribió: >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
I'm sure the telco hasn't disabled the trunk, since I'm testing callweaver in a parallel machine that I use in non-working hours to make migration tests from the current production system, which runs Asterisk as I mentioned before. But the asterisk machine works just fine with the trunk at normal working hours. Regarding the rhino cards and MFC/R2. I have another asterisk system that works just fine whit a dual E1/T1 Rhino card. I'm not an expert in MFC/R2 signalling (or any other), but a support guy from the Telco told me that they didn't needed to make any change in their configuration if I have just the same configuration on both PBX systems, and I have the same zaptel.conf and unicall.conf files in both asterisk and callweaver, maybe should I change something in there?. Best regards, Alejandro Rios. _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
