[App_rpt-users] [SPAM-FILTERED-BY-INTTEK] FW: Device usb currently not active
David McGough
kb4fxc at inttek.net
Mon Dec 14 07:36:27 UTC 2009
Hi Paul,
I use the DMK URI boards. I decided that the additional expense was
far outweighed by the ease of use.
But, if you want to roll your own, check out:
http://www.newegg.com/Product/Product.aspx?Item=N82E16829128002&cm_re=usbaudio-_-29-128-002-_-Product
I've got many of these and haven't had any problems....
73, David kb4fxc
On Mon, 14 Dec 2009, Paul wrote:
> Hi again,
>
> This is a follow up to my earlier message.
>
> The JMTek, LLC. fob uses a SSS1623 IC. Not the CM108 that it claims.
>
> A schematic is available at
> http://www.power-on.com.tw/PRODUCT/USB-AUDIO/SSS1623%20product%20spec%20Ver%
> 201.02.pdf
>
> I changed the define statement in chan_usbradio.c to match the JMTek chip
> and I get a blinking light and I can pass tone using the radio tune txvoice
> command.
>
> However, this does not address the COR and PTT requirement. The SSS1623
> chip does have GPIO control pins but on the fob I have they do not appear to
> be brought out to the board.
>
> If you have a fob with a discrete chip on it you may be able to get to these
> pins. But it may also require a new device type be added to chan_usbradio.c
> and usbradio.conf.
>
> Does anyone know a reliable source for the CM108 fobs?
>
> Regards,
> Paul
>
>
>
> -----Original Message-----
> From: Ken [mailto:ke2n at cs.com]
> Sent: Sunday, December 13, 2009 8:21 AM
> To: pjgjunk at comcast.net
> Subject: Re: [App_rpt-users] Device usb currently not active
>
> It took me a while to find this but here are the devices that asterisk
> wants
>
> #define C108_VENDOR_ID 0x0d8c
> #define C108_PRODUCT_ID 0x000c
> #define C108AH_PRODUCT_ID 0x013c
> #define C119_PRODUCT_ID 0x0008
>
> this is found in the file
>
> /usr/src/asterisk/channels/chan_usbradio.c
>
> Ken
>
> -----Original Message-----
> From: Paul <pjgjunk at comcast.net>
> To: app_rpt-users at qrvc.com
> Sent: Sat, Dec 12, 2009 11:54 pm
> Subject: [App_rpt-users] Device usb currently not active
>
> Hi,
>
> (Sorry if you receive this message more than once, the first two
> bounced.)
>
> I am new to asterisk and ROIP. I am trying to set up a test system for
> evaluation. I purchased 2 USB sound adapters that claim to be CM108
> but I
> have NOT tried to modify them yet.
>
> I completed the installation, and connected the USB device when
> instructed.
>
> When I type radio tune I get the following:
>
> test*CLI> radio tune
> Active radio interface is [usb]
> Device String is
> Card is -1
> Output A is currently set to composite.
> Output B is currently set to off.
> Tx Voice Level currently set to 500
> Tx Tone Level currently set to 200
> Rx Squelch currently set to 725
> Usage: radio tune <function>
> rxnoise
> rxvoice
> rxtone
> rxsquelch [newsetting]
> txvoice [newsetting]
> txtone [newsetting]
> auxvoice [newsetting]
> save (settings to tuning file)
> load (tuning settings from EEPROM)
> All [newsetting]'s are values 0-999
>
> When I type radio tune rxnoise I get:
>
> test*CLI> radio tune rxnoise
>
> Device usb currently not active <- Note: device usb not active
> test*CLI> radio active usb Tried this, still not active
>
> test*CLI> radio tune rxnoise
>
> Device usb currently not active How do I make it active?
>
> [root at test asterisk]# lsusb
> Bus 002 Device 001: ID 0000:0000
> Bus 003 Device 001: ID 0000:0000
> Bus 005 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
> Bus 004 Device 002: ID 0c76:1607 JMTek, LLC.
> Bus 004 Device 001: ID 0000:0000
>
> Is this because I have not modified the USB fob?
>
> Or, is it because it is not really a CM108?
>
> Is it possible to tell in software if it is a CM108?
>
>
> Thanks for your help,
>
> Paul
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
>
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
>
More information about the App_rpt-users
mailing list