Alejandro Rios wrote: > 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. > That sounds fairly conclusive that the line is OK. If the connections to your new machine were bad you would expect alarms, so we must assume that part is OK, too. > Regarding the rhino cards and MFC/R2. I have another asterisk system that > works just fine whit a dual E1/T1 Rhino card. > I don't know anything about the Rhino cards. Its quite possible the driver for one is OK, and the other has a bug. The CAS mode used for R2 is rarely used for anything else, so a bug affecting just that mode could well be in there. :-) > 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?. > What he said is correct. If one machine works, then plugging into another similarly configured machine should just require you to wait a few seconds for the alarms to clear.
Can you try experimenting with the card from one of these other machines at night? Regards, Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
