01-18-2016 01:42 AM - edited 03-17-2019 05:48 PM
Hello,
in Jabber for Windows documentation, I read that Jabber is using Media Port Range for Audio and Video traffic. Question, are these port-ranges source ports or destination ports Jabber is going to use?
Regards
Solved! Go to Solution.
01-18-2016 03:56 AM
Hi,
A port can be source or destination, important to remember is that it is a range that will be used by Jabber. What is used as source and destination is quite random and also depends on which party initiates the call and what range the other party supports. If there is no overlapping range that is supported by both parties, no call can be established.
JH
01-19-2016 10:12 AM
This is untrue. Each client chooses it's own source ports for audio and video. Jabber then reports these to CUCM which passes them along to the far-end during call setup. Jabber does not influence the destination ports of the far-end.
The documentation is referring to the source ports that Jabber will select traffic from.
01-18-2016 03:56 AM
Hi,
A port can be source or destination, important to remember is that it is a range that will be used by Jabber. What is used as source and destination is quite random and also depends on which party initiates the call and what range the other party supports. If there is no overlapping range that is supported by both parties, no call can be established.
JH
01-19-2016 10:12 AM
This is untrue. Each client chooses it's own source ports for audio and video. Jabber then reports these to CUCM which passes them along to the far-end during call setup. Jabber does not influence the destination ports of the far-end.
The documentation is referring to the source ports that Jabber will select traffic from.
01-18-2016 11:50 AM
Cisco Jabber for Windows can use Microsoft Group Policy to apply DSCP values Complete the steps in the following Microsoft support article to create a group policy: http://technet.microsoft.com/en-us/library/cc771283%28v=ws.10%29.aspx
Create separate policies for audio media and video media and signaling with the following attributes:
Attributes |
Audio Policy |
Video Policy |
Signaling Policy |
Application name |
CiscoJabber.exe |
CiscoJabber.exe |
CiscoJabber.exe |
Protocol |
UDP |
UDP |
TCP |
Source Port range |
16384 to 24574 "Low:High" |
24575 to 32766 "Low:High" |
5060 (for SIP) 5061 (for secure SIP) |
DSCP value |
46 |
34 |
24 |
02-27-2018 08:33 AM
Hi All,
I am doing some tests try marking packets on Jabber for Windows, but I have noted that the Policy based QoS not working in Windows 7. I am capturing the trafffic on Sniffer but the DSCP value are showed in 0.
Does anyone know how to achieve it?
02-27-2018 08:43 AM
03-01-2018 02:20 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide