EVDO and VoIP for remote audio transmission


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News EVDO and VoIP for remote audio transmission
# 1  
Old 08-29-2008
EVDO and VoIP for remote audio transmission

08-29-2008 08:00 AM
A cellular plan using an EVDO modem can provide a connection with bandwidth of approximately 3Mbps to the client and 1.5Mbps up to the provider (comparable to DSL) for a much lower cost than alternatives such as satellite. For applications requiring high-quality audio transmission from remote locations, such as the radio remotes we do at the radio station where I work, a Linux laptop with an EVDO modem and VoIP software offers an inexpensive and reliable solution. Here's what you need to get started.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Slackware

Problems with audio recording in Audacity 2.0.5. Slackware64 14.1; Intel HD Audio.

I'm trying to record audio using Audacity 2.0.5 installed from SlackBuilds. My system is 64-bit Slackware 14.1 and a sound card is Intel HD Audio. I didn't change my sound system to OSS. (Default sound system in Slackware 14.1 is ALSA, isn't it?) First, I set Internal Microphone slider in KMix... (2 Replies)
Discussion started by: qzxcvbnm
2 Replies

2. UNIX for Dummies Questions & Answers

File transmission logs in UNIX

Can any one give a explaination with examples on how to understand file transmission log files in Unix for inbound and outbound traffic. (1 Reply)
Discussion started by: ITDev01
1 Replies

3. Slackware

X terminal: Redirecting remote sound to my local audio device

Hello everybody, I'm testing some aspects of X Terminal implementation and it's going great. I can use remote applications on my local slow workstation at remote's processor speed by redirecting the remote DISPLAY variable to "my_local_ip:0.0"; but i'm having troubles to get remote audio and... (2 Replies)
Discussion started by: semash!
2 Replies

4. Shell Programming and Scripting

curl into a shell script (variable transmission): need help

Hey I'm writting a little shell script, and I started using curl with it today. I would like to login into a website using curl (--data argument). This part is working, curl sent me the webpage that we see when we log in this website. Problem: This is a temporary page. When I log in this... (0 Replies)
Discussion started by: Link_
0 Replies

5. Ubuntu

Connecting internet through EVDO?

i have tried to install vlc in ubuntu. Couldn' find package error. is internet mandatory to install packages. i have tried to internet through evdo but im not able to connect. i have started a thread but no reply. here is the link Connect Script failed - Ubuntu Forums how can i... (0 Replies)
Discussion started by: laknar
0 Replies

6. UNIX for Advanced & Expert Users

Geeting the error during file transmission

I am facing the following issue during file transmission from one of our application to SFTP server.Here the fact is that i am geeting the error message but the file transmission is happening properly.The message i get is as follows: sftp> cd inbox sftp> ... (3 Replies)
Discussion started by: bimal3099
3 Replies

7. Shell Programming and Scripting

COMP-3 File transmission

Guys, i need to transfer a file which contains both display and comp-3 fields from unix to mainframe. Cyberfusion , FTP doesn't work since they treat display and comp-3 fields same. Any Solution in this regard will be appreciated. Thanks, Sharif.S (3 Replies)
Discussion started by: sharifhere
3 Replies

8. UNIX for Dummies Questions & Answers

lftp transmission error help

We have installed lftp version 3.4.7. When trying to send a file it loops on sending. It appears that the lftp sends about 130k then attempts to verify transmission (with a head command maybe). The receiver is pulling the data immediatly behind the firewall and does not appear to be answering... (0 Replies)
Discussion started by: Iversog
0 Replies

9. Programming

direct transmission of files via TCP/IP

Hi, is it possible to write files via write() to a socket and read it on the other side via read(), without going through buffers? Iif not via write() and read() are there other possibilities? thanks darkspace (5 Replies)
Discussion started by: darkspace
5 Replies
Login or Register to Ask a Question
AUSCOPE(1)						      General Commands Manual							AUSCOPE(1)

NAME
auscope - Network Audio System Protocol Filter SYNOPSIS
auscope [ option ] ... DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio server. auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or, you can invoke auscope as perl auscope [ option ] ... assuming the Perl executable is in your path. To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati- cally biased by 8000. The output port defaults to 0 and the input port defaults to 1. ARGUMENTS
-i<input-port> Specify the port that auscope will use to take requests from clients. -o<output-port> Determines the port that auscope will use to connect to the audio server. -h<audio server name> Determines the desktop machine name that auscope will use to find the audio server. -v<print-level> Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater output detail. EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect to the audio server on port 8000. Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the audio server via the TCP/IP network host tcphost and port 8001: auscope -i1 -o0 -hmcxterm auplay -audio tcp/tcphost:8001 dial.snd In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the network host tcphost, while displaying its graphical interface on another server labmcx: auscope -i1 -o0 -hmcxterm -v1 autool -audio tcp/tcphost:8001 -display labmcx:0.0 SEE ALSO
nas(1), perl(1) COPYRIGHT
Copyright 1994 Network Computing Devices, Inc. AUTHOR
Greg Renda, Network Computing Devices, Inc. 1.9.3 AUSCOPE(1)