search for: contexttech

...d do it. I have done it a few times at this point. Additionally, I have mine in a vserver so, I REALLY didn't want to have to do anything to zaptel... Would have meant more annoyance. Hope that helps. :) Later, ~G -- Senior Engineer Context Technologies, Inc. (585) 586-6775 x8195 millerg@contexttech.com http://www.contexttech.com -- This message has been scanned for viruses and dangerous content, and is believed to be clean.

Hello all, We have a TE405P set up with span 1 running to a channel bank, a PRI running into span 2, and a PPP internet T1 running into span 3. We have the first 2 spans up and running without a problem. We have hdlc compiled into the kernel and after making the appropriate changes to zaptel.conf and loading the zaptel, wct4xxp, and hldc modules we can bring up the third span with the internet

Hello All, I have downloaded and installed spandsp and downloaded rxfax, etc and rebuilt asterisk with app_rxfax. I have added the following to my extensions.conf: [macro-faxreceive] ; ${ARG1} - sendto e-mail exten => s,1,Wait(2) exten => s,2,Answer exten => s,3,SetVar(FAXFILE=/var/spool/asterisk-fax/fax-${MACRO_EXTEN}-${TIMESTAMP}) exten => s,4,SetVar(EMAILADDR=${ARG1}) exten =>

Hello All, I downloaded the ChanSpy patch from Mantis and updated to the latest asterisk source from cvs. Everything seems to have installed fine and everything works as it had before, but I can't get ChanSpy to work. I added a line to extensions, as a test: exten => *53,1,ChanSpy(scan) When I dial this extension from a SIP phone, and then make a call (which I am trying to monitor) from

Hello, I have been running some tests to get a better understanding of PRIs and the HANGUPCAUSE variable and I'm not having any luck. I have tried calling disconnected numbers and the call is connected through to my extension and I hear the tri-tones. And it looks like HANGUPCAUSE is always 16 (AST_CAUSE_NORMAL_CLEARING). Am I doing something wrong, or am I just misunderstanding? Also,