Call for testers

	I've done some progress on zaptel-bsd recently,
preparing project to new release. Two definite bugs
with memory corruption has been fixed. Several possible
lock-ups(witness(9) complaints) have been addressed as
well for wct4xxp and wct1xxp. I'll continue working out
witness things for TDM/wcfxo cards next week, but meanwhile
any testing for current subversion snapshot is welcome.

Thanks!

-- 
Sincerely,

Oleksandr Tymoshenko
PBXpress Communications, Inc.
http://www.pbxpress.com
Tel./Fax.: +1 866 SIP PBX1  Ext. 656
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

Oleksandr Tymoshenko wrote:
>     I've done some progress on zaptel-bsd recently,
> preparing project to new release. Two definite bugs
> with memory corruption has been fixed. Several possible
> lock-ups(witness(9) complaints) have been addressed as
> well for wct4xxp and wct1xxp. I'll continue working
out
> witness things for TDM/wcfxo cards next week, but
meanwhile
> any testing for current subversion snapshot is welcome.
> 
> Thanks!

As I don't have any zaptel hardware and am using
zaptel/ztdummy combo, 
can I be of help testing this combination?

Currently it still panics the server during kldunload on 75%
of 
zaptel.sh stop runs.

Vahan
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

Vahan Yerkanian wrote:
> Oleksandr Tymoshenko wrote:
> As I don't have any zaptel hardware and am using
zaptel/ztdummy combo, 
> can I be of help testing this combination?
> 
> Currently it still panics the server during kldunload
on 75% of 
> zaptel.sh stop runs.
     Argh! Thanks for pointing out. Should be fixed now,
I've just 
committed new version.
-- 
Sincerely,

Oleksandr Tymoshenko
PBXpress Communications, Inc.
http://www.pbxpress.com
Tel./Fax.: +1 866 SIP PBX1  Ext. 656
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

On 06/25/06 21:35 Oleksandr Tymoshenko said the following:
>     I've done some progress on zaptel-bsd recently,
> preparing project to new release. Two definite bugs
> with memory corruption has been fixed. Several possible
> lock-ups(witness(9) complaints) have been addressed as

well done, oleksandr. it'd be good if we can get this done
(and released) 
soon, before i start on work towards getting zaptel-bsd up
to spec to work 
with asterisk trunk. kim has pointed out that recent changes
to asterisk, 
including codec_zap.c, break functionality. as of now, only
the 1.2 branch 
works with zaptel-bsd, trunk wont work with it.

-- 
Regards,                           /\_/\   "All dogs
go to heaven."
dineshalphaque.com                (0 0)   http://www.openmalay
siablog.com/
+==========================----oOO--(_)--OOo----============
==============+
| for a in past present future; do                          
             |
|   for b in clients employers associates relatives
neighbours pets; do   |
|   echo "The opinions here in no way reflect the
opinions of my $a $b."  |
| done; done                                                
             |
+===========================================================
==============+
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

I have reinstalled the asterisk port and the
asterisk-addons port. My system is working but still
no luck with conference rooms. I am getting this error
message block at the CLI console:

    -- Executing MeetMe("SIP/2000-e1b6",
"1234|i|5678") in new stack
  == Parsing '/usr/local/etc/asterisk/meetme.conf':
Found
Jul 10 20:53:17 WARNING[9724]: chan_zap.c:916 zt_open:
Unable to open '/dev/zap/pseudo': No such file or
directory
Jul 10 20:53:17 ERROR[9724]: chan_zap.c:7444 chandup:
Unable to dup channel: No such file or directory
Jul 10 20:53:17 WARNING[9724]: app_meetme.c:464
build_conf: Unable to open pseudo channel - trying
device
Jul 10 20:53:17 WARNING[9724]: app_meetme.c:467
build_conf: Unable to open pseudo device
    -- Playing 'conf-invalid' (language 'en')
  == Spawn extension (default, 1234, 1) exited
non-zero on 'SIP/2000-e1b6'

I don't have any zaptel hardware in my system but the
docs say I need the ztdummy driver to use conference
rooms. So it appears I don't have the setup just
right. Can anyone tell me what else I should try?


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection
around 
http://mail.yahoo.com 
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

On 07/11/06 17:54 Frank Griffith said the following:
> I don't have any zaptel hardware in my system but the
> docs say I need the ztdummy driver to use conference

have you loaded the zaptel.ko and ztdummy.ko modules ?
MeetMe requires a 
timing device to work.

-- 
Regards,                           /\_/\   "All dogs
go to heaven."
dineshalphaque.com                (0 0)   http://www.openmalay
siablog.com/
+==========================----oOO--(_)--OOo----============
==============+
| for a in past present future; do                          
             |
|   for b in clients employers associates relatives
neighbours pets; do   |
|   echo "The opinions here in no way reflect the
opinions of my $a $b."  |
| done; done                                                
             |
+===========================================================
==============+
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

I missed the first part of this thread, but it occurred to
me here as I am 
sitting in a small Asterisk testing lab, that maybe I could
help with some 
testing.

I have a dual Xeon/SCSI machine with one wildcard in it,
lots of Aastra SIP 
phones, and a good amount of peering infrastructure.  I
would probably be 
better at testing SIP and IAX stuff, as I have access to
these resources, but 
I could also test FXS functionality to a limited extent.  I
have lots of 
bandwidth if need be.  I have a triple Xeon production
machine sitting on a 
10Mb connection to an ATM/fiber backbone.  I am in the
process of writing 
some load test scripts that will do 10 or 20 channel SIP and
IAX tests, as 
well as meet-me tests.

Let me know if that is of any use to whoever needs testing
done.  I am quite 
happy to compile, but please give me a working port with a
makefile, or a 
good tutorial on how to use CVS or whatever else you use.  


-Tim
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd