login | register
Fri 09 of May, 2008 [16:54 UTC]

voip-info.org

Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Shoutbox
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
  • Christopher Faust, Wed 07 of May, 2008 [15:28 UTC]: When I try to startx I ge input not supported. Though before installing asterisk I had no video issue to start the GUI
  • Christopher Faust, Wed 07 of May, 2008 [15:26 UTC]: Hi Nick, I got centos 5.1 and asterisk up But now I cannot start startx I have set the depth from 24 to 16 for the video i810 driver for the i845 on my netvista machine but I cannot start GNOME. Please advise
  • Nick Barnes, Wed 07 of May, 2008 [10:01 UTC]: Howard - You'll need to provide a lot more information if you really want help.
  • Nick Barnes, Wed 07 of May, 2008 [10:00 UTC]: Christopher - Search the Wiki and you'll find a page I wrote detailing exactly what you have to do for Asterisk 1.4 + CentOS 5.1.
Server Stats
  • Execution time: 0.73s
  • Memory usage: 2.19MB
  • Database queries: 29
  • GZIP: Disabled
  • Server load: 0.63

Asterisk bounty FreeBSD zaptel



This page is outdated. See here for the current working zaptel drivers on FreeBSD.


BOUNTY: FreeBSD Zaptel Drivers


  • Maintainer: Troy
  • Opening date:
  • Status: Open
  • Total value:
  • Contributors: gunk ($250), chris coleman ($250), jtodd ($100 + $50), fgravato ($200), bkw918 ($50), marks ($100), Edvina/oej ($100), hkilmer ($100), Cylogistics/reallost1 ($250), kniveton ($50)

Description

I'm placing a $250 bounty on getting Zaptel drivers working under BSD. While the 'hood' is open on this, we'd like to have drivers completed for FreeBSD, NetBSD, and OpenBSD on the x86 platform (other platforms optional).

This needs to be done in a timely fashion. I'd like it completed by 6/30/2004, but once the project is started, we can adjust the deadline if it's not reasonable.

In addition to the Zap drivers, we will require that patches be submitted so that libpri, asterisk, and other parts of the project have clean and proper installations on a per-os basis, as determined by each system's hier(1) man page and ports/package system.
Additional Information In addition, I spoke with Chris Coleman from Daemon News/BSD Mall today, and he's willing to lend the hardware and place an additional $250 bounty on the project.

I would like Mark@Digium to donate/lend the hardware instead, as I believe he can do so more easily than BSD Mall can. I have not yet spoken to Mark about this yet.

Comments by Jtodd



All of the following environments need to be functional with the patches:
  • OpenBSD 3.4 (or -current, if required)
  • FreeBSD 5.2 (or -current, if required)
  • NetBSD 1.6 (or -current, if required)


  • Should work with X100P for calls in/out
  • should work with 2 X100P cards in a system
  • should work with TDM400P for calls in/out

"work" means:
  • DTMF functional for detection/transmission
  • sound quality identical to that of Linux cards
  • no pops/crackles/drops
  • caller name and caller ID functional on inbound calls
  • call recording works correctly
  • flash works correctly
  • other system resources are not adversely effected by use of card

T100P tests
  • Inbound calls with PRI signalling (T1)
  • Outbound calls with PRI signalling (T1)
  • Inbound calls with T1 channelized signalling (T1)
  • Outbound calls with T1 channelized signalling (T1)
  • IP routing with PPP over one or more channels on T1


Load testing
  • all 23 channels on a PRI
  • all 24 channels on a T1
  • should work with two T100P cards in a system or one T100P and one X100P



Questions for the people putting up the dough:
  1. ) Who has a machine that they can offer for development purposes?
  2. ) Who has a T100P card they can offer for development purposes? We probably need two cards; one for the test machine, and one for the load-generating machine.
  3. ) Who has a "real" PRI that can be used for testing purposes?
  4. ) Who can create better test cases than I have above in the 180 seconds I've had to write this?



Oej added:

Should also work as a Zaptel timer source for MeetMe and IAX2 trunking










Created by oej, Last modification by wiz on Wed 13 of Jul, 2005 [23:36 UTC]

Comments Filter

Another contribution.

by onuris on Tuesday 25 of May, 2004 [19:57:51 UTC]
I'll contribute $250 towards the bounty.

Edit

addistional bounty towards OpenBSD support

by Anonymous on Monday 12 of April, 2004 [19:54:37 UTC]
I'll throw in US$200 towards OpenBSD 3.5 support?

I'm a frequent OpenBSD monetary contributor, deichert _at_ wrench _dot_ com

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:

Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver