Unity QOS

[mwadam]

Jeff, hopefully you will chime in on this.

This topic has been discussed before, but not from this perspective.

The TSP on CCM by default marks SCCP packets at AF31(dscp 26). Unity also marks any SCCP packets at AF31(dscp 26). My question is; short of using a switch or a router in the network to remark the SCCP packets in either direction from AF31(dscp 26) to CS3(dscp 24), is there a method on CCM for the TSP based SCCP and Unity for SCCP that will allow changing of the markings? One would assume that there is a system parameter, although I cannot find one, or possibly a registry setting that would allow this.

Thanks!!!

Adam

[Chris Deren]

Adam,

The default SCCP markings on CM is in fact CS3 since CallManager 4.0. Unity 4.2 and below is AF31 and cannot be changed, until Unity 5.0 where this is a configurable parameter in the UTIM, also the default was changed to CS3.

Chris

[mwadam]

Chris,

Thanks for the reply.

I am using Unity 4.05 with TSP 8.01b on CCM. Sniffer traces show AF31 both ways. My understanding is that the TSP has not been changed yet to reflect CS3. As I am sure you suspect, Unity 5.0 is not an option in this scenario. Have to determine if is is possible to make the change in CCM/Unity 4.05.

Adam

[eschulz]

The configurable QoS for Unity is really a feature of the 8.2(1) wave driver and for SCCP it is not specific to Unity 5.0. The QoS settings are stored in the registry as dword keys "Call Signaling QoS" and "Media Signaling QoS" under:

Software\\Active Voice\\Miu\\1.0\\Initialization

UTIM in Unity 5.0 simply provides a safe user interface for adjusting these values. However, if you run TSP 8.2(1) on an earlier version of Unity you could manual create and set these keys. Of course, manually tweaking the registry on your Unity server is a do-at-your-own-risk activity.

Regards,

Eric

[mwadam]

Eric,

Thanks for the info! I was actually in the process of upgrading the TSP to 8.2.1 just to see if anything had changed. Since I am working on equipment in my lab, I will give the registry option a try and see whether it will work or not, and update afterwards.

Thanks again!!!

Adam

[mwadam]

Eric,

The new TSP 8.21 definately changes SCCP to CS3. However, even after adding the new registry dwords I could not manipulate the settings. I tried hex values of 68 and 1a for Af31 and decimal of 26, restarted the Unity services, but SCCP was still CS3 in the sniffer traces. Maybe these new dwords are not compatible with 4.05?

Regardless, this is great information!

Thanks!!!

Adam

[navinger · Accepted solution]

Hi Adam,

It had been my understanding that in all versions of Unity prior to 5.0(1), the Unity QoS settings are hard-coded. As Eric said, in Unity 5.0, the Unity Manage Integrations tool, UTIM, has been enhanced so that you can change the QoS settings.

But let's try an experiment since you're in a lab setting. In Unity 5.0, when you change the QoS via UTIM, it sets those registry keys to a value from 0 to 20 (decimal)according to the chart below. So try manually entering a value from 0 to 20, restart the Unity services after changing the registry, and see what happens.

QoS Index Symbolic Name 6-bit DSCP Value

0 AF11 DSCP 001010

1 AF12 DSCP 001100

2 AF13 DSCP 001110

3 AF21 DSCP 010010

4 AF22 DSCP 010100

5 AF23 DSCP 010110

6 AF31 DSCP 011010

7 AF32 DSCP 011100

8 AF33 DSCP 011110

9 AF41 DSCP 100010

10 AF42 DSCP 100100

11 AF43 DSCP 100110

12 CS1(precedence 1) DSCP 001000

13 CS2(precedence 2) DSCP 010000

14 CS3(precedence 3) DSCP 011000

15 CS4(precedence 4) DSCP 100000

16 CS5(precedence 5) DSCP 101000

17 CS6(precedence 6) DSCP 110000

18 CS7(precedence 7) DSCP 111000

19 Default DSCP 000000

20 EF DSCP 101110

Nancy

[mwadam]

Nancy,

Thank you very much for the information! This was great!

Here are the results of my testing:

Using Unity 4.05 and TSP versions 8.21 and 8.13 I was able to add the registry entries and change the decimal values to reflect any marking I desired based on your chart.

Using Unity 4.05 and TSP versions 8.12, 8.11, and 8.01b I could not change the markings regardless of the registry settings.

This really helps me out a lot. I truely appreciate it!!!

Adam