Hi Guys
I saw this post on a forum while investigating other issues and had to note it down for you and for my own reference! Finally a definitive answer easily understood to a question I have had for ages regarding determining wireless performance
SNR (Signal-to-Noise Ratio) is a ratio based value that evaluates
your signal based on the noise being seen. So let's look at the
components of the SNR and they see how to determine it. SNR is
comprised of 2 values and is measured as a positive value between 0db
and 120db and the closer it is to 120db the better: Signal Value and
Noise Value typically these are expressed in decibels (db).
So we will look at the Signal (Also known as RSSI) first this value is
measured in decibels from 0 (zero) to -120 (minus 120) now when looking
at this value the closer to 0 (zero) the stronger the signal is which
means it's better, typically voice networks require a -65db or better
signal level while a data network needs -80db or better. Normal range
in a network would be -45db to -87db depending on power levels and
design; since the Signal is affected by the APs transmit power &
antenna aswell as the clients antenna.
Great stuff, found the post here:
https://supportforums.cisco.com/discussion/10954591/snr-and-rssi-values
Also worth pointing out as per his post that the 7925g handsets can actually be used to perform site surveys! Another handy trick!
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7925g/7_0/english/administration/guide/7925wrnt.html#wp1117827
For more information
Collaboration Edge Deployment Guide
https://ciscocollab.wordpress.com/2014/01/29/deploying-collaboration-edge/
Default login to tandberg is admin password is TANDBERG
Default login to tandberg is admin password is TANDBERG
Match Incoming calls based on SIP URI!!! (Or SIP Host or SIP Ip address, super useful!) match incoming dial-peer on sip address
Hi Guys!
You can now match incoming calls based on the SIP Address sending to you
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube_fund/configuration/xe-3s/asr1000/cube_fund-xe-3s-asr1000-book/voi-inbnd-dp-match-uri.html
This could be incredibly useful in a situation where you don't know what numbers the provider might be sending but you need a way to distingush a provider call from another call.
See below some example configuration:
voice class uri ACMESIPTRUNK sip
host ipv4:70.30.1.1
host ipv4:70.40.1.1
dial-peer voice 2 voip
corlist incoming INCOMINGFROMATTTOCUCM
description ### Incoming calls from AT&T SIP Trunk ###
session protocol sipv2
incoming uri via ACMESIPTRUNK
voice-class codec 1
dtmf-relay cisco-rtp sip-kpml sip-notify
This will make this dial-peer voice 2 be the incoming dial-peer for any calls from host 70.30.1.1 and 70.40.1.1
You can now match incoming calls based on the SIP Address sending to you
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube_fund/configuration/xe-3s/asr1000/cube_fund-xe-3s-asr1000-book/voi-inbnd-dp-match-uri.html
This could be incredibly useful in a situation where you don't know what numbers the provider might be sending but you need a way to distingush a provider call from another call.
See below some example configuration:
voice class uri ACMESIPTRUNK sip
host ipv4:70.30.1.1
host ipv4:70.40.1.1
dial-peer voice 2 voip
corlist incoming INCOMINGFROMATTTOCUCM
description ### Incoming calls from AT&T SIP Trunk ###
session protocol sipv2
incoming uri via ACMESIPTRUNK
voice-class codec 1
dtmf-relay cisco-rtp sip-kpml sip-notify
This will make this dial-peer voice 2 be the incoming dial-peer for any calls from host 70.30.1.1 and 70.40.1.1
New Cisco Switches: 40 gig uplinks, Support for Nbase - a new standard to deliver 2.5 and 5gbps over CAT 5e and the new Wave2 802.11AC
Hi Guys!
Wow It's been a while since i've done a "new product" post! There has been so much slideware stuff being bounced around these days (COUGH *SDN COUGH COUGH) it's nice to see some honest to goodness, "solving a REAL problem, right NOW!" type products like new switches and new access points.
802.11AC Wave 2 is almost upon us, promising speeds of up to 6.8 Gigabit per second and a new method of allocating bandwidth so that CSCA (carrier Sense Collision Avoidance) algorithims traditionally used in the shared media of wireless can be avoided.
While our existing 802.11AC Wave 1 access points can get away with a 1 gig connection (because although the physical radio rate is slightly higher, the actual data rate is less than 1 gig) with these access points obviously that is no longer going to be an option.
I know what your thinking: "OK time to go and pull out all my Cat5E cable I guess then and replace it all, that will be super cost effective! Hey Boss! Know how we just got all that cabling put in when we moved into this office? Yeah it's redundant now we need to run all new cabling."
The disruption to the office, the cost and the justification for the above scenario will be difficult for quite a few customers.
So, Cisco and other concerned internet citizens banded together to introduce a standard (awaiting approval from the IEEE) called NBase. (note: their is a competing standard being proposed by another smaller networking vendor alliance. It is difficult to predict which standard will emerge at this point)
NBase allows you to use Cat5E and Cat6 cable all the way to 100m (the original spec) with speeds of either 2.5gigabit per second or 5 gigabit per second!
This is going to be a great stop-gap measure for a lot of people!
Let's take a look at some of the switches/devices they introduced to support this:
Like the 3850X these models support NBase technology, Universal POE and in certain models 10 gigabit uplinks, all in a completely silent and fanless switch!
What's more, the new models can be used as instant access switches, allowing you to centralize the configuration on your 6800 switches. Depending on what your network topology looks like, this could be a huge boon!
I hope you found this interesting and are as excited as I am to see if the products live up to the hype!
Wow It's been a while since i've done a "new product" post! There has been so much slideware stuff being bounced around these days (COUGH *SDN COUGH COUGH) it's nice to see some honest to goodness, "solving a REAL problem, right NOW!" type products like new switches and new access points.
802.11AC Wave 2 is almost upon us, promising speeds of up to 6.8 Gigabit per second and a new method of allocating bandwidth so that CSCA (carrier Sense Collision Avoidance) algorithims traditionally used in the shared media of wireless can be avoided.
While our existing 802.11AC Wave 1 access points can get away with a 1 gig connection (because although the physical radio rate is slightly higher, the actual data rate is less than 1 gig) with these access points obviously that is no longer going to be an option.
I know what your thinking: "OK time to go and pull out all my Cat5E cable I guess then and replace it all, that will be super cost effective! Hey Boss! Know how we just got all that cabling put in when we moved into this office? Yeah it's redundant now we need to run all new cabling."
The disruption to the office, the cost and the justification for the above scenario will be difficult for quite a few customers.
So, Cisco and other concerned internet citizens banded together to introduce a standard (awaiting approval from the IEEE) called NBase. (note: their is a competing standard being proposed by another smaller networking vendor alliance. It is difficult to predict which standard will emerge at this point)
NBase allows you to use Cat5E and Cat6 cable all the way to 100m (the original spec) with speeds of either 2.5gigabit per second or 5 gigabit per second!
This is going to be a great stop-gap measure for a lot of people!
Let's take a look at some of the switches/devices they introduced to support this:
The first switch we should look at is the great 3850. The 3850 has had Converged wireless access for a while now (which allows us to use it as both a switch and a wireless controller) as well as great stacking capabilities and bandwidth and Universal POE, allowing up to 60 watts of power per port!
The new models of the 3850 introduce support for NBASE multi-gigabit. 12 of 24 ports on the 24 port model can accept NBase connections or 24 of 48 ports on the 48 port model. To support this potentially massive amount of bandwidth, the switch now supports 40 gig uplink modules!
The 4500E chassis switch (which makes sense for a lot of people) hasn't been forgotten either with it's OWN 48 port linecard with 12 of the ports being multigigabit capable. It now also supports Converged Wired and Wireless like the 3850, so for those companies a little too big for a stack of 3850's but who want the converged wireless this is perfect!
Before we go on to the 3560 let's talk about the new linecard for the 6500/6800 and the other improvements introduced for this platform.
The new line card for the 6500 is shown below
As you can see it offers 32 x 10 gig ports! Double the amount previously offered. an odd ommision in this announcement is any mention of any linecards that are going to support NBase for the actual 6500/6800 itself! Which I find a bit strange.
Another key takeaway from this picture is the doubling of supported Instant Access switches, Instant Access is essentially the catalyst version of FEX from the Nexus platform, where by you manage your switches from a central control plane (the 6800 itself)
This leads us into the 3560-CX and 2960-CX
What's more, the new models can be used as instant access switches, allowing you to centralize the configuration on your 6800 switches. Depending on what your network topology looks like, this could be a huge boon!
I hope you found this interesting and are as excited as I am to see if the products live up to the hype!
Tips for dealing with Finesse
Consider this a dynamic article where I will put hints and tips for issues I encounter when dealing with Finesse
- When administrating Finesse, always use the URL that contains the hostname and not the IP address. This makes life a LOT easier. Otherwise you will get errors such as:
"
- Don't underestimate the HTTPS aspect, the cert's being non trusted is quite a pain for the users, although once they trust them in their browser they are fine, anyone else logging into the PC will get an invalid cert. Cisco has a few methods to resolve this like having your own CA and using properly signed certificates.
- When administrating Finesse, always use the URL that contains the hostname and not the IP address. This makes life a LOT easier. Otherwise you will get errors such as:
"
An error occurred while retrieving settings. To try again, refresh the page."
- Don't underestimate the HTTPS aspect, the cert's being non trusted is quite a pain for the users, although once they trust them in their browser they are fine, anyone else logging into the PC will get an invalid cert. Cisco has a few methods to resolve this like having your own CA and using properly signed certificates.
and other various timeout issues!
Subscribe to:
Posts (Atom)