QoS - LYNC

Hi
In a deployment with QoS configured on switches, we are going to do QoS on wireless as well (for LYNC optimization)
Right now we use flexConnect on ver. 7.4.. Looking on the new AVC feature, it already have a profile for LYNC (when doing central switching).
Can someone clarify the following:
- If going to use Central switching instead of flexConnect, to implement a AVC LYNC-profile, then we will have to config QoS on switches to prioritize CAPWAP ?
- Would it be better to keep flex connect and do some "old" QoS on WLC (Does QoS on WLC always require central switching) ?
- Anyone have done QoS for LYNC on WLC ?
Regards
Kasper

Hi
QoS in Lync is a tricky one. Normally you would have a Generic QoS profile on the Lync Server. However, to better optimize QoS for the client, you would have to configure Policy based QoS on the laptops. This can be done through the local computer group policy. Normally, the DSCP value for voice is 46, while that for video is 34.
The big question is how you can do this on all laptops in your domain. If you can find a way to push it through the domain group policy, then that would ease your pain. I would also recommend that you configure your AP switch port to trust dscp.
A noteworthy point is that QoS becomes ineffective in a poor wireless environment. Hence you would have to make sure that your wireless LAN set up was properly done. Prioritizing CAPWAP will no major effect for LYNC.

Similar Messages

What are the ports required for the Audio, Video and A/V conferencing when the following end points are enabled for QoS in Lync 2013 server?

Hi All,
What are the ports required for the Audio, Video and A/V conferencing when the following clients are enabled for QoS in Lync 2013 server?
Client Type
Port range and Protocol required for Audio
Port range and Protocol required for
Video
Port range and Protocol required for
A/Vconferencing
Windows Desktop Client
Windows mobile App
Iphone
Ipad
Andriod phone
Andriod Tablet
MAC desktop client
Please advise. Many Thanks.

Out of the box, 1024-65535 for all of the client ports. :)
https://technet.microsoft.com/en-us/library/gg398833.aspx
You'll want to tune your client ports a bit
https://technet.microsoft.com/en-us/library/jj204760.aspx as seen here, and then the client ports would use those ranges which is easier to set QoS markings. I'm not sure the mobile clients respect that setting.
Elan's got the best writeup for Windows clients here:
http://www.shudnow.net/2013/02/16/enabling-qos-for-lync-server-2013-and-various-clients-part-1/
However, the marking of the packets is the tricky part. Windows can do it via Group Policy, but for the other clients you'll need to have the network specifically prioritize ports regardless of DSCP markings. You have to do it based on ports
as the traffic could be peer to peer.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

QoS application for Lync for Mac 2011 clients

Hi guys,
I'm deploying Lync 2013 at a customer site. We'll be applying QoS by enforcing static port ranges within Lync (CsConferencingConfiguration), and applying ACLs on the network equipment and dropping the various Lync modalities into the relevant QoS queue,
pretty standard.
Quick question. What's the expected behaviour for the Lync for Mac 2011 client. Will it honour the port ranges as defined on the Lync server conferencing configuration? Can't seem to find the answer anywhere online or in the forums.
2nd question - does anyone know what the meaning of the following command:
Set-CsMediaConfiguration -EnableQoS $True
According to the TechNet
article titled Enabling QoS for devices that are not based on Windows, it sounds like this command has some role to play in enabling QoS for non-Windows devices... just wondering if that includes Mac OS. Again, information is sketchy
on this.
Cheers, James.
James Frost

One way you can check is simply by running a WireShark capture on a Windows endpoint. Either run a capture on the Mediation server to sniff a PSTN call, or as RTP traffic is point to point in a two-party call you can just call a Windows PC from the
Mac. Look for the DSCP section in the Internet Protocol area as shown in this non-Lync article:
http://conceptsfortheroad.com/2012/06/how-to-verify-dscp-value-in-not-being-stripped/
Or play with this filter "ip.dsfield.dscp == 46" to see if something is being sent at all.
Hopefully someone has done a deep dive and will chime in, but I'd love to see your results!
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Steps to enable lync 2013 QOS for audio

Experts,
I am on the way to enable lync 2013 QOS for audio only. We have already decided the ports ranges and make sure that its not override.
I just want to now, what will be happen to existing users using eEnterprise voice during i will lock the ports in servers and clients with GPO.
What is user impact during the implementation. I can't see any TechNet article for same. Do we have some recommended steps to follow to avoid any issue to existing users ??
Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

While you configure QoS nothing will happen with existing users or even existing calls. All that happens when you set a port range for Audio in the Lync is the next calls after the user picks up the change (client refreshes policies every 8 hours or
on log out/in) will us that port range.
If you have already decided on the port range you simply need to create the corresponding GPOs for both Server and Client as you mention. There is no harm in doing it mid-day unless you had defined ports before/specific firewall rules across the environment
for those ports - but that doesn't sound like the scenario here.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

QoS values to match Lync-calls

A customer of ours is tuning QoS for Lync for better voice-quality. The wired network works fine, but on the wireless it looks like there are some “drops” from time to time.
The Lync-calls are tagged with AF41.
There are 4 types of QoS on the WLC. At the moment SSID is configured as Silver, but should it be Gold (instead of Silver) to match AF41?
Based on this document, Gold is AF41. Is that correct?
Is there anything else we could adjust and will they benefit from that QoS change?
Thank you!

Prior to configuration optimization, you need to ensure you have sufficient wireless coverage (20% overlap) & preferably clients are connecting in 5GHz band. This design guide cover most of topics (Voice, QoS, Multicast,etc) & read it thoroughly to see whether your wireless deployment adheres to those recommendation.
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob73dg/emob73.html
With respect to QoS here is my suggestions.
1. QoS profile to configured Platinum with 802.1p=6 (this will allow proper voice packets comes with 802.11e UP of 6 passthrough without capping the QoS value)
http://mrncciew.com/2012/12/02/understanding-wireless-qos-part-3/
2. WMM (under WLAN -> QoS ) to be set as "Required" to avoid non-WMM traffic get prioratised.
http://mrncciew.com/2013/07/30/wmm-qos-profile/
3. If all local mode APs, you need to configure the QoS trust boundaries as below
- AP connected switchport : DSCP
- WLC connected switchoport : CoS
- inter switch trunks : DSCP
4. Makesure WLC management interface is not on native vlan (in otherwords on a tagged vlan) in order to proper QoS functionality.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080c01d2c.shtml
5. If you are using AVC, better you mark up this traffic as EF, so your wired network will properly treat this traffic as Voice. Otherwiese this traffic will treat as video & will not get required priority within your network.
Additionally make sure priority queue "priority-queue out interface config" enabled for your access layer switchports. Below QoS guide help you to verify your switch QoS configuration, see whether you configured in inline with this guide recommendation
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampuscat3xxxaag.html
HTH
Rasika
**** Pls rate all useful responses ****

How to set up Qos for Microsoft Lyncs 2013 in cisco Switches and Router

Hi
as i am new to Qos part , please send the complete qos configuration command has to apply in my cisco 2960s switchs as well as 4506 chassis(L3 mode act as my router).
as i know from microsoft, DSCP 46 and 34 should give highest priory
please send the completed configuration for priorities this DSCP
thanks
Sujish

Hi,there,
The rule setting should be same as in Exchange 2010,you can configure it via outlook or OWA if you have full access permission. I also believe it should be something related to Repliation,would you please check the event log to see if the
AD and Exchange replication has completed.
In some cases, replication can take longer depending on how many AD sites and Exchange servers in the environment:
http://support.microsoft.com/kb/148381
http://support.microsoft.com/kb/158989
Hope these useful!
Regards,
Sharon
Sharon Shen
TechNet Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

QoS / Native VLAN Issue - Please HELP! :)

I've purchased 10 Cisco Aironet 2600 AP’s (AIR-SAP2602I-E-K9 standalone rather than controller based).
I’ve configured the WAP’s (or the first WAP I’m going to configure and then pull the configuration from and push to the others) with 2 SSID’s. One providing access to our DATA VLAN (1000 – which I’ve set as native on the WAP) and one providing access to guest VLAN (1234). I’ve configured the connecting DELL switchport as a trunk and set the native VLAN to 1000 (DATA) and allowed trunk traffic for VLAN’s 1000 and 1234. Everything works fine, when connecting to the DATA SSID you get a DATA IP and when you connect to the GUEST SSID you lease a GUEST IP.
The problem starts when I create a QoS policy on the WAP (for Lync traffic DSCP 40 / CS5) and try to attach it to my VLAN’s. It won’t let me attach the policy to VLAN 1000 as it’s the native VLAN. If I change VLAN 1000 on the WAP to NOT be the native VLAN I can attach the policies however wireless clients can no longer attach to either SSID properly as they fail to lease an IP address and instead get a 169.x.x.x address.
I'm sure I'm missing something basic here so please forgive my ignorance.
This is driving me insane!
Thanks to anyone that provides assistance. Running config below and example of the error...
User Access Verification
Username: admin
Password:
LATHQWAP01#show run
Building configuration...
Current configuration : 3621 bytes
! Last configuration change at 02:37:59 UTC Mon Mar 1 1993 by admin
version 15.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname LATHQWAP01
logging rate-limit console 9
aaa new-model
aaa authentication login default local
aaa authorization exec default local
aaa session-id common
no ip routing
dot11 syslog
dot11 vlan-name Data vlan 1000
dot11 vlan-name Guest vlan 1234
dot11 ssid LatitudeCorp
   vlan 1000
   authentication open
   authentication key-management wpa version 2
   wpa-psk ascii
dot11 ssid LatitudeGuest
   vlan 1234
   authentication open
   authentication key-management wpa version 2
   guest-mode
   wpa-psk ascii
crypto pki token default removal timeout 0
username admin privilege 15 password!
class-map match-all _class_Lync0
match ip dscp cs5
policy-map Lync
class _class_Lync0
set cos 6
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption vlan 1234 mode ciphers aes-ccm
encryption vlan 1000 mode ciphers aes-ccm
ssid LatitudeCorp
ssid LatitudeGuest
antenna gain 0
stbc
station-role root
interface Dot11Radio0.1000
encapsulation dot1Q 1000 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.1234
encapsulation dot1Q 1234
no ip route-cache
bridge-group 255
bridge-group 255 subscriber-loop-control
bridge-group 255 spanning-disabled
bridge-group 255 block-unknown-source
no bridge-group 255 source-learning
no bridge-group 255 unicast-flooding
service-policy input Lync
service-policy output Lync
interface Dot11Radio1
no ip address
no ip route-cache
encryption vlan 1234 mode ciphers aes-ccm
encryption vlan 1000 mode ciphers aes-ccm
ssid LatitudeCorp
ssid LatitudeGuest
antenna gain 0
no dfs band block
stbc
channel dfs
station-role root
interface Dot11Radio1.1000
encapsulation dot1Q 1000 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio1.1234
encapsulation dot1Q 1234
no ip route-cache
bridge-group 255
bridge-group 255 subscriber-loop-control
bridge-group 255 spanning-disabled
bridge-group 255 block-unknown-source
no bridge-group 255 source-learning
no bridge-group 255 unicast-flooding
service-policy input Lync
service-policy output Lync
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface GigabitEthernet0.1000
encapsulation dot1Q 1000 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface GigabitEthernet0.1234
encapsulation dot1Q 1234
no ip route-cache
bridge-group 255
bridge-group 255 spanning-disabled
no bridge-group 255 source-learning
service-policy input Lync
service-policy output Lync
interface BVI1
ip address 10.10.1.190 255.255.254.0
no ip route-cache
ip default-gateway 10.10.1.202
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
bridge 1 route ip
line con 0
line vty 0 4
transport input all
end
LATHQWAP01#conf
Configuring from terminal, memory, or network [terminal]? t
Enter configuration commands, one per line. End with CNTL/Z.
LATHQWAP01(config)#int dot11radio1.1000
LATHQWAP01(config-subif)#ser
LATHQWAP01(config-subif)#service-policy in
LATHQWAP01(config-subif)#service-policy input Lync
set cos is not supported on native vlan interface
LATHQWAP01(config-subif)#

Hey Scott,
Thank you (again) for your assistance.
So I' ve done as instructed and reconfigured the WAP. I've added an additional VLAN (1200 our VOIP VLAN) and made this the native VLAN - so 1000 and 1234 are now tagged. I've configure the BVI interface with a VOIP IP address for management and can connect quite happily. I've configured the connecting Dell switchport as a trunk and to allow trunk vlans 1000 (my DATA SSID), 1200(native) and 1234 (MY GUEST SSID). I'm now back to the issue where when a wireless client attempts to connect to either of my SSID's (Guest or DATA) they are not getting a IP address / cannot connect.
Any ideas guys? Forgive my ignorance - this is a learning curve and one i'm enjoying.
LATHQWAP01#show run
Building configuration...
Current configuration : 4426 bytes
! Last configuration change at 20:33:19 UTC Mon Mar 1 1993 by Cisco
version 15.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname LATHQWAP01
logging rate-limit console 9
enable secret 5
no aaa new-model
no ip source-route
no ip cef
dot11 syslog
dot11 vlan-name DATA vlan 1000
dot11 vlan-name GUEST vlan 1234
dot11 vlan-name VOICE vlan 1200
dot11 ssid LatitudeCorp
   vlan 1000
   authentication open
   authentication key-management wpa version 2
   mobility network-id 1000
   wpa-psk ascii
dot11 ssid LatitudeGuest
   vlan 1234
   authentication open
   authentication key-management wpa version 2
   mbssid guest-mode
   mobility network-id 1234
   wpa-psk ascii
   no ids mfp client
dot11 phone
username CISCO password
class-map match-all _class_Lync0
match ip dscp cs5
policy-map Lync
class _class_Lync0
set cos 6
bridge irb
interface Dot11Radio0
no ip address
encryption vlan 1000 mode ciphers aes-ccm
encryption vlan 1234 mode ciphers aes-ccm
ssid LatitudeCorp
ssid LatitudeGuest
antenna gain 0
stbc
mbssid
station-role root
interface Dot11Radio0.1000
encapsulation dot1Q 1000
bridge-group 255
bridge-group 255 subscriber-loop-control
bridge-group 255 spanning-disabled
bridge-group 255 block-unknown-source
no bridge-group 255 source-learning
no bridge-group 255 unicast-flooding
service-policy input Lync
service-policy output Lync
interface Dot11Radio0.1200
encapsulation dot1Q 1200 native
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.1234
encapsulation dot1Q 1234
bridge-group 254
bridge-group 254 subscriber-loop-control
bridge-group 254 spanning-disabled
bridge-group 254 block-unknown-source
no bridge-group 254 source-learning
no bridge-group 254 unicast-flooding
service-policy input Lync
service-policy output Lync
interface Dot11Radio1
no ip address
encryption vlan 1000 mode ciphers aes-ccm
encryption vlan 1234 mode ciphers aes-ccm
ssid LatitudeCorp
ssid LatitudeGuest
antenna gain 0
peakdetect
no dfs band block
stbc
mbssid
channel dfs
station-role root
interface Dot11Radio1.1000
encapsulation dot1Q 1000
bridge-group 255
bridge-group 255 subscriber-loop-control
bridge-group 255 spanning-disabled
bridge-group 255 block-unknown-source
no bridge-group 255 source-learning
no bridge-group 255 unicast-flooding
service-policy input Lync
service-policy output Lync
interface Dot11Radio1.1200
encapsulation dot1Q 1200 native
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio1.1234
encapsulation dot1Q 1234
bridge-group 254
bridge-group 254 subscriber-loop-control
bridge-group 254 spanning-disabled
bridge-group 254 block-unknown-source
no bridge-group 254 source-learning
no bridge-group 254 unicast-flooding
service-policy input Lync
service-policy output Lync
interface GigabitEthernet0
no ip address
duplex full
speed auto
interface GigabitEthernet0.1000
encapsulation dot1Q 1000
bridge-group 255
bridge-group 255 spanning-disabled
no bridge-group 255 source-learning
service-policy input Lync
service-policy output Lync
interface GigabitEthernet0.1200
encapsulation dot1Q 1200 native
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface GigabitEthernet0.1234
encapsulation dot1Q 1234
bridge-group 254
bridge-group 254 spanning-disabled
no bridge-group 254 source-learning
service-policy input Lync
service-policy output Lync
interface BVI1
mac-address 881d.fc46.c865
ip address 10.10. 255.255.254.0
ip default-gateway 10.10.
ip forward-protocol nd
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
bridge 1 route ip
line con 0
line vty 0 4
login local
transport input all
sntp server ntp2c.mcc.ac.uk
sntp broadcast client
end
LATHQWAP01#

Any roadmap to have to Lync client for Blackberry 10?

...with full feature support of course (phone, video, presence,...).
I know there are still some challenges like at current time with BB10 OS (like you must keep you app in an active frame), but these limitations will soon go away with the new OS version (http://devblog.blackberry.com/2013/05/blackberry-jam-headless-invoke/?CPID=E10C020,
new Background Services framework which allows developers to bundle a separate process with their application to run in the background without a UI)
The Lync for Mac version still lacks of some critical phone features not being implemented (delegate support, team-call group members, wireless QoS tagging 802.11e,...)

Hi,
There is currently no Lync client available for Blackberry (RIM) devices. Sorry to say I also did not find any roadmap about lync for Blackberry 10.
Kent Huang
TechNet Community Support

QOS configuration - Is there a way to prevent marking SIP signaling as media

I have configured QOS for Lync 2013 per all the documenation, blogs, etc.
While reviewing network captures to make sure it is working, I noticed something: normal SIP signaling traffic from the Lync servers to port 5067 uses random source ports, and when those source ports fall into the ranges defined for media, gets marked
as if it was media traffic. This is over-prioritizing: marking SIP signaling traffic with a higher DSCP than is warranted.
Any way to prevent this?

The two main methods are marking source ports or marking anything coming from the service executables with a DSCP value. Sometimes SIP signaling traffic will fall into the source range, and it will always come from the service executable. You
can't force only signaling to use a set range source ports, so there's not too much you can do. That being said, SIP signaling traffic is generally negligible compared to the media traffic so I generally just let it be.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Cisco Aironet AIR-SAP2602I-E-K9 - Setting QoS from CLI...

Hey guys,
I've created a QoS policy from within the GUI. However when trying to apply the policy to all incoming and outgoing interfaces of the VLAN concerned (1000 / CORP) from within the GUI I'm not convinced it is working. I select the policy against each interface and hit "apply" and then it defaults back to no policy being selected. Looking at show run I can see the policy is created although I'm not convinced it has been applied to the interfaces? Could somebody please take a quick glance at the config below and indicate whether the policy has been applied to the interfaces for VLAN 1000. Pretty sure it hasn't.
User Access Verification
Username: admin
Password:
LATHQWAP#show run
Building configuration...
Current configuration : 3456 bytes
! Last configuration change at 00:38:43 UTC Thu Mar 4 1993 by admin
version 15.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname LATHQWAP
logging rate-limit console 9
aaa new-model
aaa authentication login default local
aaa authorization exec default local
aaa session-id common
no ip routing
dot11 syslog
dot11 vlan-name Data vlan 1000
dot11 vlan-name Guest vlan 1234
dot11 ssid Corp
   vlan 1000
   authentication open
   authentication key-management wpa version 2
   wpa-psk ascii 7
dot11 ssid Guest
   vlan 1234
   authentication open
   authentication key-management wpa version 2
   guest-mode
   wpa-psk ascii 7
crypto pki token default removal timeout 0
username admin privilege 15 password 7
class-map match-all _class_Lync0
match ip dscp cs5
policy-map Lync
class _class_Lync0
set cos 6
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption vlan 1234 mode ciphers aes-ccm
encryption vlan 1000 mode ciphers aes-ccm
ssid Corp
ssid Guest
antenna gain 0
stbc
station-role root
interface Dot11Radio0.1000
encapsulation dot1Q 1000 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.1234
encapsulation dot1Q 1234
no ip route-cache
bridge-group 255
bridge-group 255 subscriber-loop-control
bridge-group 255 spanning-disabled
bridge-group 255 block-unknown-source
no bridge-group 255 source-learning
no bridge-group 255 unicast-flooding
interface Dot11Radio1
no ip address
no ip route-cache
encryption vlan 1234 mode ciphers aes-ccm
encryption vlan 1000 mode ciphers aes-ccm
ssid Corp
ssid Guest
antenna gain 0
no dfs band block
stbc
channel dfs
station-role root
interface Dot11Radio1.1000
encapsulation dot1Q 1000 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio1.1234
encapsulation dot1Q 1234
no ip route-cache
bridge-group 255
bridge-group 255 subscriber-loop-control
bridge-group 255 spanning-disabled
bridge-group 255 block-unknown-source
no bridge-group 255 source-learning
no bridge-group 255 unicast-flooding
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface GigabitEthernet0.1000
encapsulation dot1Q 1000 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface GigabitEthernet0.1234
encapsulation dot1Q 1234
no ip route-cache
bridge-group 255
bridge-group 255 spanning-disabled
no bridge-group 255 source-learning
interface BVI1
ip address 10.10. 255.255.254.0
no ip route-cache
ip default-gateway 10.10.
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
bridge 1 route ip
line con 0
line vty 0 4
transport input all
end
Thank you to anyone taking the time to assist. Greatly appreciated - very new Cisco wireless tech.
Cheers.

Sorted this myself. It wouldn't apply to the VLAN because VLAN 1000 was the native VLAN.

Lync to PSTN quality Issues, no issues to be found in reports

We have a lync 2013 install recently completed however we are experiencing voice quality issues. It appears to be specifically calls between Lync clients and PSTN and additionally the issues are only heard on the PSTN side (Lync side sounds great). This
is regardless if it was a PSTN initiated or Lync initiated call.Reports of quality issues are given as "sounding watery", "Robotic", "Fading in and out", and "Momentary loss of sound". It it VERY consistent.
Our Lync to Lync calls are perfect (internally and federated), or if its not good quality it is easily diagnosed.
We are running 2 lync edge servers, two front end. currently only have 40 users. We have a 40mb internet circuit. QOS is enabled on the edge router\core switch and we have had the QOS investigated and does not appear to be the issue (I read another forum
post indicating QOS causing issues and we contracted a firm to verify QOS). We are using Intelepeer as a SIP trunk and it terminates to an Audiocodes Mediant 1000. The Mediant 1000 connects directly to the internet.
When we look at the call statistics there are no issues to be found. We have opened tickets with Intelepeer and they do not show any issues either.
I am starting to feel a bit lost as to where to look for help. Please let me know what additional info you need and I will be grateful and happy to give more info.

Assuming you are not encrypting traffic between Mediation and gateway, you can use Wireshark to capture the traffic of the “internal” leg. Later you can “decode” and listen the actual call which will be the flow Lync <-> Mediation <-> Gateway.
If the quality is good, mirror switchport and Wireshark the traffic between Gateway and IntelePeer. This way you can identify the leg that introduces the issue. Just a place to start...
Drago
http://www.lynclog.com

Setting up a Test Voice VLAN for Lync 2013

I want to set up a second voice vlan to be a test vlan.
In the current situation the customer has voice and data running on vlan1. The customer insist on taking incremental steps to improve QoS. I have advocated separated vlans for voice and data. They just want to move everything (phase 1) to a different
vlan. They want to see how getting all traffic of vlan 1 will improve there performance. Again, I recommended the best practice, they want to try this approach first.
I am conducting a pilot test with just one cx600 IP phone. and a single switchport. I created a new vlan99 using VTP. I configured the switchports on the Cisco 2960-x switch as follows.
#switchport mode access
#switchport access vlan 99
The phone gets its correct vlan id, and pulls its IP from the correct dhcp scope. However the phone displays "connecting with the lync server" for a long time, then "connecting to download its certificates". This takes a long time then fails.
If I change the switchport back to vlan1 it works fine. What can be the problem? Does the vlan99 need to be defined on the lync server? How many vlans can be supported by Lync 2013?
Thank you,
gigiu

Did you set the VLAN Configuration for Lync Phone Edition?
You can check the following links:
http://blog.schertz.name/2011/01/manual-vlan-configuration-for-lync-phone-edition/
http://www.bricomp.com/blogs/post.cfm/dedicated-voice-vlan-for-lync-devices
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Lisa Zheng
TechNet Community Support

Question about QoS in Wireless

Hi,
I've spent some time reading about QoS in Wireless but can't get my head around a few things. QoS is a confusing subject.
In the WLANs -> Edit WLAN you can set a QoS profile, from Bronze to Platinum, as shown in the picture.
1) Does this level tag ALL traffic on the WLAN to Platinum if the client does not tag the traffic itself to other values? In other words, is Platinum the default level?
2) I've read that this setting is the maximum level of QoS permitted on the WLAN, in that case I should set it to Platinum if I have VOIP traffic and regular DATA traffic on the same WLAN? For instance Lync/Skype?
3) How does this relate to AVC profiles? I've prioritized certain apps (lync gets DSCP 46) and down-prioritized others (youtube gets DSCP 10), will the values I've defined be tagged with Platinum since I set the WLAN QoS profile to Platinum? Or will they retain their original value as I defined in AVC Profiles.
4) Which clients are not WMM compatible? It seems almost all regular computers support WMM.
Can someone confirm the following QoS is true for the wired infrastructure: WLC ports are mls qos trust cos and AP ports are mls qos trust dscp. But what about trunks between switches and the uplink to your ISP? trust dscp?
Will be thankful if someone can shed some light on this.

1) Does this level tag ALL traffic on the WLAN to Platinum if the client does not tag the traffic itself to other values? In other words, is Platinum the default level?
NO
2) I've read that this setting is the maximum level of QoS permitted on the WLAN, in that case I should set it to Platinum if I have VOIP traffic and regular DATA traffic on the same WLAN? For instance Lync/Skype?
Yes, this is max level allowed. you should tag to platinum if you have VOIP clients. i dont think skype sends data with priority voice. not sure about lync.
3) How does this relate to AVC profiles? I've prioritized certain apps (lync gets DSCP 46) and down-prioritized others (youtube gets DSCP 10), will the values I've defined be tagged with Platinum since I set the WLAN QoS profile to Platinum? Or will they retain their original value as I defined in AVC Profiles.
wlan setting takes precedence over AVC if i recall correctly
4) Which clients are not WMM compatible? It seems almost all regular computers support WMM.
yes all modern clients are WMM compatible. you need WMM compatibility for 11n/ 11ac rates
Can someone confirm the following QoS is true for the wired infrastructure: WLC ports are mls qos trust cos and AP ports are mls qos trust dscp. But what about trunks between switches and the uplink to your ISP? trust dscp?
trunks are usually trust cos and access ports are usually trust dscp. you need to make sure end to end qos is configured properly.

Lync 2013 Multi-tenant Hosting Pack third-party solutions available for features listed as "Via Thirdparty"

Hi,
Who are all the third party vendors that can integrate with Lync 2013 Multi-tenant hosting pack V2 features that are supported Via 3rd party.
1) Call park
2) Outgoing DID manipulation
3) E-911
3) Dialplans & Policies
4) Support for Analog devices (e.g. FAX)
5) Response groups
6) Network QoS - DSCP
7) Phone number management
8) IM/P & Voice with Skype.
9)Inteoperability with on-premises video conferencing systems
Regards,
SR

Hi,
Base on my understanding, as it is the Mutli-Tenant environment, in internal DNS server, there is no need to add the DNS A record
lyncdiscoverinternal. However, you can try to add the DNS record in internal DNS server to test the issue as well.
Also, please make sure you have updated both Lync Server 2013 and Exchange 2013 to the latest version. If not, update it and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync Client uses wrong RTP Ports for calls from/to RGS with Agent Anonymity

We have QoS implemented and client ports for audio, video und application defined by Set-CsConferencingConfiguration. We also use firewalls in our LAN between the different VLANs for Clients, Servers and Gateways/SBC. Only RTP from the client with the defined
ports are allowed by the firewall. Media ByPass is enabled.
In all normal cases, the right ports will be used and marked by GPO with the right DSCP value. But if an agent get a call from a RGS which has agent anonymity enabled, the client uses a port in the range 1024-65535 for audio. Also if you make a call on behalf
of the RGS, the client use a random port between 1024-65535. As soon, as the source of the call is in another VLAN (e.g. a call from PSTN which comes in over a SBC in e separate VLAN), the firewall between the two VLANs block the RTP traffic.
We see the deny on the firewall log and in the SBC log we see, the reinvite for the media by pass with the IP of the agent and a not valid port. We also see, that no RTP from the client/agent will arrive the SBC and no RTP from the SBC will arrive the client/agent.
So the call will be disconnected, as soon as an agent wants accept the call.
Is there an additional setting to make sure, the Lync client always use the valid RTP port range?
This behavior exist in Lync 2010 and Lync 2013 clients.

Hi Holger,
Thanks for reply!
Sure! I set all AudioPorts on all Services, but the problem are not the ports used by the server, the problem are the ports used by the client. We set the client ports to 49152 with a count of 40. The client (2013 and also 2010) use these ports correctly in all
cases exept for call from/on behalf of an RGS with Agent Anonymity.
If we disable the RGS agent anonymity, restart the client of the agent, then the client uses also the correct source ports for RTP.
I've checked this behaviour now on 3 customer installations, our own productive installation and in our lab.
Because until now only one of our customers have firewalls between the internal VLANs, only this single customer have the issues...
Regards,
Stephan

QoS - LYNC

Similar Messages

Maybe you are looking for