discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] RAW source


From: Activecat
Subject: Re: [Discuss-gnuradio] RAW source
Date: Tue, 24 Jun 2014 13:05:40 +0800



On Thu, Jun 19, 2014 at 9:32 PM, Sara Chérif <address@hidden> wrote:
Sorry , I forgot to say that some packets coming from Twinkle are SIP & ARP packets not only RTP.
Hence , I think I need to receive RAW packets in GNU Radio ( as I have different type of packets:  RTP , ARP , SIP packets)

Note that :
I use 4 laps & 2 USRPs.
1st & 4th lap has twinkle softphone & I will make a call between them.
2nd lap has an OFDM TX implemented by Gnuradio.
3rd lap has an OFDM RX implemented by Gnuradio.
First and 2nd laps are connected by Ethernet cable.
3rd & 4th laps are connected by Ethernet cable.
One USRP is connected to the 2nd lap , the other USRP is connected to the 3rd lap.
2nd lap(GNUradio ,ofdm tx)  will receive the packets from 1st lap(Twinkle) using RAW socket (as I think ) .
2nd lap will send the packets to the 3rd lap by the USRPs.
3rd lap ( Gnuradio , ofdm rx)  will send real time voice packets to 4th lap (Twinkle) using RAW socket(as I think).

If I want only to make a call & send and receive the voip real time packets , Do I have then to write a specific block as this mentioned decoder ?

Thanks in Advance.



Hi Sara,

After few rounds of communications, apparently you are interested to intercept the VoIP session at OSI layer 5 or above (eg. RTP session), and you try to use gnuradio (with USRPs) to accomplish that.
Probably this is because your area of interest is actually those RTP and VoIP stuffs.
I have few highlights:

1).  To accomplish this, one of the right ways is to make your PC becomes one of the VoIP endpoints. 
In this case you listen to the speaker and speak to microphone attached to your PC.  At the other end of the session is a SIP phone.
With this, you really dig into the RTP and VoIP stuffs.
You need neither gnuradio nor USRP.  In this case the wireless link is trivial in your setup.

2).  In this case you need ASIO [1] or something similar, and start working from the low level.
But as ASIO may not sound as an easy topic, you are looking for tools like gnuradio to abstract the low level stuff.
Yes gnuradio has built-in blocks that abstract ASIO, but that abstraction doesn't mean to let you work at RTP layer.

3).  In this case the gnuradio is not the right tool for your purpose.  You had chosen the tool without first qualifying it.
Your setup above (with the 4 laps) couldn't actually force gnuradio to intercept the VoIP session at RTP layer.
This is a wrong design.


Let's be honest about your area of interest.
Anyway I could be wrong.

1. http://www.boost.org/doc/libs/1_55_0/doc/html/boost_asio.html

reply via email to

[Prev in Thread] Current Thread [Next in Thread]