[Asterisk-bsd] latest zaptel drivers from pbxpress -- is SVN down?

[Aaron Seelye]

I'm getting the same, and the nightly snapshot is a 0 byte file after being 
unzipped.  Has the repository moved?  Also, have there been any changes 
since June 25 (last time I got the svn)?

-Aaron
----- Original Message ----- 
From: "Jerry B. Altzman" <jbaltz at 3phasecomputing.com>
To: <asterisk-bsd at lists.digium.com>
Sent: Tuesday, July 18, 2006 3:31 PM
Subject: [Asterisk-bsd] latest zaptel drivers from pbxpress -- is SVN down?


> Hi,
>
> I'm a relatively new Asterisk + FBSD (6.1) user -- had a bit of a time 
> getting my POS asterisk box (onboard ethernet controller conflicted with 
> TDM13B card -- saw that already in the archives) to work "just so".
>
> Saw a bunch of words go back and forth in the archives that lead me to 
> think that getting the latest-greatest zaptel drivers/kernel modules might 
> help out (I have my one FXO port keep erroring out with:
>> Ouch, part reset, quickly restoring reality (0)
>> !!!!!!! OSC1_COEF  iREG d = 0  should be 7b30
>> !!!!!!! OSC1X  iREG e = 0  should be 63
>> !!!!!!! OSC2_COEF  iREG 10 = 0  should be 7870
> ...etc.)
>
> I can't, however, get to the pbxpress SVN repository:
>> [jbaltz at iridium ~]$ svn co --username svn --password svn 
>> https://svn.pbxpress.com:1443/repos/zaptel-bsd
>> svn: PROPFIND request failed on '/repos/zaptel-bsd'
>> svn: PROPFIND of '/repos/zaptel-bsd': could not connect to server 
>> (https://svn.pbxpress.com:1443)
>> [jbaltz at iridium ~]$ openssl s_client -connect svn.pbxpress.com:1443 
>> connect: Connection refused
>> connect:errno=61
>
> Any ideas?
>
> Thanks!
>
> //jbaltz
> -- 
> jerry b. altzman  jbaltz at 3phasecomputing.com  +1 718 763 7405
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.10.1/390 - Release Date: 7/17/2006
>