[cisco-voip] lync moc desktop p2p & p2m video calls , conferencing

[Matt Slaga (AM)]

On #3, yes, it will enable FEC for packet loss, however it also uses RTCP to determine bandwidth, jitter and delay to adjust audio and video as part of RT's adjustable codec.  FEC only kicks in though if there is high bandwidth and high loss though.  FEC takes two voice segments, say segment 1 and 2, and puts it into a single packet.  The next packet will include segments 2 and 3, next 3 and 4 and so on.  It ends up using more bandwidth overall which is why it is used for high bandwidth high loss situations.



From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: Tuesday, May 10, 2011 2:09 PM
To: Tony Edwards
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] lync moc desktop p2p & p2m video calls , conferencing



Are you doing a pilot of both M$ and Ci$co?  Comparing the two?

1.  M$ can do  the same stuff that CM does.  It does not have to be configured together to get it working.

2.  I think it depends on what your planing to end up with.  are you planning on integrating the two?

3.  Not really sure.  Someone told me (YMMV) that MS just pushes more packets if it starts loosing packets.  Can fill up pipes if its having issues getting the packets through.  Don't know if it's true or not.

4.  & 5.  I don't know.

Scott
On Tue, May 10, 2011 at 3:16 AM, Tony Edwards <tonyedwards.rs<http://tonyedwards.rs>@gmail.com<http://gmail.com>> wrote:

hi guys,

can some one please guide me on the below queries?

i am planning to run a pilot with a lync2010 server with 10 odd lync moc clients on 10 user windows7 computers with an aim to
turn on a desktop video p2p and p2m ( conference) streams both with in lan environment as well as between 2 x wan site , separated by a 512k frame relay pipe.

in isolation i do have a ccm running with 10 sites with 100 sccp end points and lync platform will be totally separate to begin with while i trial desktop to desktop video.

so that being the aim , i am not sure on how to address following 4 aspects.

1. can my 10 pilot lync moc clients do p2p or p2m desktop video sessions with rt audio and rt video codecs with out going via ccm cluster or with out the help of ccm at all.

2. just like ccm's sccp end points which will have a dn # , should my lync moc clients too need to have dn # or lync moc can audio & video call each other via their sip addresses or user names ?

3.from qos perspective , what tcp & udp ports should i have to mark and classify for rt audio or rt video signalling and payloads ? from my very limited understanding on lync so far , moc clients when they talk to lync server via sip , they do open up peer to peer sort of 1024 to 65534 sort of huge port range. which i gather , can we locked in to smaller range via in-band signalling. so as you can see here , i am totally confused on best possible qos templates to protect and give some sort of priority (perhaps IP Prec 2 or AF21)  lync desktop video p2p and p2p sessions.
4. i do gather that , lync do offer cac , similar to ccm. if that is the case , how much bw shall i have to configure for 2 x desktop video sessions ?

5. lastly , i was just checking nbar class maps on my is router and i spotted match protocol rtp audio and rtp video and rtp payload , but nbar match options does not offer rt audio or rt video to cover microsoft lync protocol matching. so , i am just wondering , are they both same or not. if they are not same , then perhaps , the bets i could do it is match tcp and udp port ranges of rt audio and rt video traffic streams.

thank you a lot.

tony

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110511/8e682ff2/attachment.html>