[Serusers] SER RTP QoS Monitoring

[Atle Samuelsen]

Hi Aisling, 
 A few tought's, see inline :-)

> 1) RTCP
> RTCP stream will contain this information. The problem is that
> sniffers cannot clearly distinguish RTCP packets from other UDP
> packets unless something like an IP address or specific UDP port is
> supplied. I had considered using TCPDUMP but then where do I position
> this in the network when voice is going peer to peer between client
> and I'm not sure how this can work to monitor all calls when I might
> not be aware of the end user IP addresses.
> 
if you use rtpproxy, I think it also does rtpproxy for RTCP so, if you
hack the rtpproxy code, you can proberbly get this info out.

> 2) SIP INFO extension
> This also seem to be an option but most off the shelf phones don't
> seem to support this and this would required modification of a SIP ua.

Hm, true, but FYI, I know Sipura can do some statistics in BYE
messages. :) 

> 3) SNMP
> I thought maybe SNMP might be an option but the SER snmp module no
> longer exists...

Hm, I might be wrong, but look at the fifo module from CVS head, and
just introduce a new module, that get's the same info as the fifo module
can get from Ser, and make a Snmp wrapper :) tough, I dont see the
point, since SER does'nt do media. 

> Does anyone have any comments on the above? Are the statements that I
> made correct or can anyone think of other ways to monitor the voice
> QoS? I am trying to understand how commercial applications have
> accomplished this.

Good Luck!

 -Atle

> 
> Many thanks in advance for advice.
> Aisling.
> 
> >---- Original Message ----
> >From: clona at cyberhouse.no
> >To: ashling.odriscoll at cit.ie
> >Subject: Re: [Serusers] Status of SER SNMP module
> >Date: Sun, 29 Jan 2006 20:30:02 +0100
> >
> >>
> >>Hi Aisling,
> >>
> >>The SNMP module is dead as a killed turtle :( 
> >>
> >>-Atle
> >>* Aisling O'Driscoll <ashling.odriscoll at cit.ie> [060129 20:26]:
> >>> Hello,
> >>> 
> >>> I'm just wondering what the current status of the SER SNMP module
> >is?
> >>> Is it currently supported and is there somewhere I can find
> >>> documentation on it?
> >>> 
> >>> Many thanks,
> >>> Aisling.
> >>> 
> >>> 
> >>> 
> >>> -------------------Legal 
> >Disclaimer---------------------------------------
> >>> 
> >>> The above electronic mail transmission is confidential and
> >intended only for the person to whom it is addressed. Its contents
> >may be protected by legal and/or professional privilege. Should it be
> >received by you in error please contact the sender at the above
> >quoted email address. Any unauthorised form of reproduction of this
> >message is strictly prohibited. The Institute does not guarantee the
> >security of any information electronically transmitted and is not
> >liable if the information contained in this communication is not a
> >proper and complete record of the message as transmitted by the
> >sender nor for any delay in its receipt.
> >>> 
> >>> 
> >>> _______________________________________________
> >>> Serusers mailing list
> >>> serusers at lists.iptel.org
> >>> http://lists.iptel.org/mailman/listinfo/serusers
> 
> 
> 
> 
> -------------------Legal  Disclaimer---------------------------------------
> 
> The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.
> 
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>