--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To post to this group, send email to ns-3-...@googlegroups.com.
To unsubscribe from this group, send email to ns-3-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ns-3-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
I'v found this work:
Hi All!I found an interesting discussion here about VoIP.I have implemented also VoIP for my scenario and the attributes like ontime,oftime,data rate and packet size are covering the properties of VoIP traffic.But I have another concern which about VoIP. To analyse the behaviour of VoIP it should be two-way traffic. So I tried to have two streams opposed each other with dedicated timing and socket configuration. But it does not work.I need to know why we cannot have two flows of onoff application?
--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/groups/opt_out.
Hi everyone,Well, after some reading and studying, I implemented a simple VoIP application. At a first glance, this application has only one main difference against the NS-3 default ones that I have seen in this list (PacketSync, UdpClient).My application has client and server sides. First the client sends a request to server asking for VoIP traffic. On the other hand, the server waits for clients requests and sends the packets when it detects a request. In the NS-3 default applications the server starts sending packets without the request of the client.The VoIP traffic is modeled in a simple manner, I mean, the server sends packets of fixed size in fixed intervals. There is not any kind of VAD or silence suppression. There are two variables to be set by the user: packetSize and packetInterval.I'm going to set these parameters basing on the Cisco reference indicated by Konstantinos [1]. I have chosen the codec G.729. This codec allows the packet size to be equal to 10, 20, 30, 40, 50 or 60 bytes. For each one of these size packets we have an appropriate packet interval.So far, so good. However, now we have to take a look in the headers. The VoIP application has a packet with size:packetSize + RTP(SeqTsHeader) + UDP + IP + P2P20 + 12 + 8 + 20 + 2 = 62 bytesFor 20 bytes of payload we have 42 bytes of headers! This can be improved if we use packets with 60 bytes of payload. However, in both cases this is a lot of overhead.From [1], one can see that the bandwidth is calculated in this way:The required bandwidth for a G.729 call (8 Kbps codec bit rate) with cRTP, MP and the default 20 bytes of voice payload is:Total packet size (bytes) = (MP header of 6 bytes) + ( compressed IP/UDP/RTP header of 2 bytes) + (voice payload of 20 bytes) = 28 bytesTotal packet size (bits) = (28 bytes) * 8 bits per byte = 224 bitsPPS = (8 Kbps codec bit rate) / (160 bits) = 50 ppsNote: 160 bits = 20 bytes (default voice payload) * 8 bits per byteBandwidth per call = voice packet size (224 bits) * 50 pps = 11.2 KbpsSo, using compressed IP/UDP/RTP, 40 bytes become 2 bytes. In this sense, the 42 bytes of headers become 4 bytes (P2P + cRTP) and the total packet size 24 bytes. I don't know if NS-3 has support to header compression. Then, to make this true in the NS-3 VoIP application, I'm going to discount the overhead in the payload size, as I saw in UdpClient.
There are 38 bytes to be removed in the payload. In this context, the packetSize options are reduced to 40, 50 and 60 bytes. For now, I'm going to use a payload of 60 bytes. In the code:
This looks very good, see comments below and inline.One addition that I would recommend is the use of requested time from the client.That is, the client asks for a VoIP session of 'x' seconds and with some sort of flag will not ask for a new session until the first is finished.That way you can implement a more realistic scenario, that you have calls generated with different time periods.
Otherwise, the application would not be much different from current CBR applications (on/off configured with the packet sizes you suggest) where the server starts sending data to clients after random time.
There are 38 bytes to be removed in the payload. In this context, the packetSize options are reduced to 40, 50 and 60 bytes. For now, I'm going to use a payload of 60 bytes. In the code:Have to make sure that the user will not be able to use "m_packetSize < 38" otherwise this would cause errors
--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/groups/opt_out.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.
Dizhi,
Could you please help me?
Best regards
Leticia
On 26 mayo, 16:35, Leticia <leticia.si...@gmail.com> wrote:
> Hi Dizhi,
>
> Thank you for your answer!
>
> I am modifying the lena-simple-epc example of LENA, I have only one
> eNB and my idea is generate traffic from one UE to another UE and then
> studying the QoS and QoE.
>
> Best,
>
> Leticia
>
> On 26 mayo, 11:04, Dizhi Zhou <dizhi.z...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi Leticla,
>
> > What is your topology? eNB -- UE OR UE -- UE
>
> > Best,
> > Dizhi
>
> > On Friday, May 25, 2012 5:19:11 PM UTC-3, Leticia wrote:
>
> > > Hello, I'm new at NS3-LENA.
> > > I want to implement different kind of traffic in a LTE network with
> > > only one eNB, for example: video streaming, web browsing, FTP and
> > > VoIP.
> > > I found that the ON OFF applications can model the VoIP Traffic but
> > > I dont know how to configure the ONOFF applications to achieve that
> > > the traffic flows from one UE to another UE and how can I see the
> > > packets of the applications, can I see it from Pdcp traces for
> > > example?
>
> > > Can anybody help me?
>
> > > Thank you
>
> > > Leticia