[cisco-voip] bandwidth restrictions for MRA clients - necessary or not?

Fri Apr 8 08:54:19 EDT 2016

Thanks Daniel. This is fantastic information. 

----- Original Message -----

From: daniel at ohnesorge.me 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: cisco-voip at puck.nether.net 
Sent: Wednesday, April 6, 2016 6:29:27 PM 
Subject: Re: [cisco-voip] bandwidth restrictions for MRA clients - necessary or not? 

Lelio, 

Jabber has been using something call CPVE for a while; Cisco Precision Video Engine. CPVE comes from the Tandberg acquisition and was mainly used in Tandberg Movi (later Jabber Video). CPVE indeed starts at a low quality bitrate and then assesses the network using RTCP and other technologies to up-scale and down-scale as needed. 

You stated your requirement in your initial email - " i'd like to make sure we have the best video quality while on-campus". While it's fine to assume that over 3G/4G video may be disabled or perhaps a low bandwidth, what about MRA clients using home or cafe WiFi? If said WiFi has a fast bandwidth e.g. 50 Mbps and your Jabber MRA device calls an on-prem video device, you have no control over the bandwidth. 

The idea behind Device Mobility is quite simple, for your case you could do it like this; 

- Create a Device Pool named Internet_DP 
- Create Internet_RG region and assign Internet_RG to Internet_DP (Internet_RG has region relationships to your on-campus regions limiting the bandwidth e.g. 512 Kbps max video) 
- Create a Physical Location Internet_PL and Device Mobility Group Internet_DMG and assign both to Internet_DP 
- Create a Device Mobility Info (basically a subnet) called Internet_DMI and give it the IP of your Expressway-C with subnet mask of 32 e.g. 10.10.10.100/32 
- Associate Internet_DP with the Internet_DMI 
- Enable Device Mobility from CallManager Service Parameters (enabled Device Mobility for all phones) or enable on a per-phone basis via BAT or individually 

What happens now is that anytime a BOT/TCT/TAB/CSF/78XX/88XX phone registers via Expressway, it's registration IP will always be the IP of Expressway-C. CUCM realizes this and essentially changes the DP to Internet_DP where you have defined your lower bandwidth region relationships. Once that device comes back to the corporate network it will no longer have a registration IP of the Expressway-C, rather a normal DHCP IP and will of course use the normal Device Pool which you configured which may have a maximum BW of 10 Mbps. 

Hope this helps! 

On 2016-04-07 00:05, Lelio Fulgenzi wrote: 

I honestly don't know. 
I'm new to the whole Jabber world, as well as to video codecs and bit rates. 
I could be worrying about something that I don't need to be, i.e. a 10 minute Jabber video call will never use more than X megabytes of data. 
Then again, it's only a matter of time until clients will want to use the quality that comes with a mobile phone front facing camera to have a HD video call from anywhere. 
--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 
519‐824‐4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 
----- Original Message -----

From: "Dennis Heim" <Dennis.Heim at wwt.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, cisco-voip at puck.nether.net 
Sent: Wednesday, April 6, 2016 10:00:11 AM 
Subject: RE: [cisco-voip] bandwidth restrictions for MRA clients - necessary or not? 

Can many mobile jabber devices with cellular connectivity do more than 360p? 

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi 
Sent: Wednesday, April 06, 2016 9:53 AM 
To: cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] bandwidth restrictions for MRA clients - necessary or not? 

Thanks Eric. 

I had a similar discussion with a Cisco engineer. Basically, let Jabber figure things out. Which is all fine and dandy, until you read that Canada pays some of the highest fees for mobile data in the world. lol. 

There are not many unlimited data plans available, and a simple 10 minute video call at 10mbps (using 5mbps for calc) could probably use up 3gb of data traffic. 

But then, I don't want to impact quality for Jabber clients on wifi connections. 

I'm guessing that I might go with leaving device mobility out of the picture for now and ensuring video calling is disabled while on mobile networks. 

----- Original Message -----

From: "Eric Pedersen" < PedersenE at bennettjones.com > 
To: "Lelio Fulgenzi" < lelio at uoguelph.ca >, cisco-voip at puck.nether.net 
Sent: Monday, April 4, 2016 11:00:36 AM 
Subject: RE: [cisco-voip] bandwidth restrictions for MRA clients - necessary or not? 

Jabber apparently monitors packet loss and sets the video rate accordingly, which is why the quality starts out really low and them improves with the call. I don't think any of the phones do that, but I believe the 8845 maximum bandwidth is 2mpbs. 

From: cisco-voip [ mailto:cisco-voip-bounces at puck.nether.net ] On Behalf Of Lelio Fulgenzi 
Sent: 04 April 2016 7:40 AM 
To: cisco-voip at puck.nether.net 
Subject: [cisco-voip] bandwidth restrictions for MRA clients - necessary or not? 

quick question... how are people restricting the video/audio bandwidth for Jabber MRA clients or physical phone MRA clients for that matter? 

we have not had to use locations or enabled mobility (i think that's the IP Address based feature) since we have high speed, low latency WAN links to our locations. 

is it even a problem that I need to consider? 

i'd like to make sure we have the best video quality while on-campus (including those connected via high speed WAN links), so i've set the default bw to 10mbps. 

i'm wondering how that will impact MRA clients. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 

519 ‐ 824 ‐ 4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

The contents of this message may contain confidential and/or privileged subject matter. If this message has been received in error, please contact the sender and delete all copies. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish us to communicate with you by e-mail, please notify us at your earliest convenience. In the absence of such notification, your consent is assumed. Should you choose to allow us to communicate by e-mail, we will not take any additional security measures (such as encryption) unless specifically requested. 

If you no longer wish to receive commercial messages, you can unsubscribe by accessing this link: http://www.bennettjones.com/unsubscribe 

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160408/be720911/attachment.html>