01-23-2013 06:14 AM - edited 03-18-2019 12:28 AM
Solved! Go to Solution.
02-03-2013 10:42 PM
Thanks Teck : this is mactching ddts allright!
So moving to TCNC5.1.6 or even TCNC6.0.0 (just released) would fix this.
01-23-2013 12:23 PM
Where did you do the network capture?
You can do a tcpdump on the endpoint, that would be the best place to check on it.
Remember that there might be switches or routers which strip away the marks, even if you believe different for now :-)
Did you check if there are any bugs / limitations with the TCNC software and the older
software version? (which btw, is deferred:
So I would recommend to upgrade to TC5 or TC4.2.6
Please remember to rate helpful responses and identify
01-24-2013 12:03 AM
Dear Martin
Thanks for your respone.
The link what you sent is only for SW TC. We are using TCNC. Also there is nothing mentioned about the QoS DCSP issue.
Profile42 is and my pc is connected to the same switch.
used port span port mirror configuration on switch to capture packet.
Reason why I am not suspecting switch or other devices are not striping away the marks.
VCS is connected to other switch, but still I am getting any paket sourced from VCS with DCSP value is 0x1a AF31.
Also for RTP video stream I can see packet sourced from Profile42 is marked as configured ie AF41.
Only for the signalling packet sourced from Profile42 is marked as 0x00, eventhough Profile42 is configured signaling QoS value is 26.
Any other configuration required ? Am I missing any additonal configuration? or Upgrade sw will resolve issue ?
Rgds
Rajesh
01-24-2013 12:37 AM
Hello,
as Martin indicated, an easy way to see "what comes out" of the codec is to run tcpdump from the codec. For this you need to have root access to the codec. Here's an example on EX90 running TE6 release.
[dderidde-ex90-home:~] $ tcpdump tcp port 5060 -vv
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
09:27:19.295420 IP (tos 0x68, ttl 64, id 23001, offset 0, flags [DF], proto TCP (6), length 1300)
ams-dderidde-8916.cisco.com.47557 > vcs-sjc-101.cisco.com.5060: Flags [.], cksum 0x0495 (correct), seq 715707297:715708545, ack 2729772177, win 1233, options [nop,nop,TS val 154314297 ecr 2193209578], length 1248
TOS is set to 0x68.
xConfiguration Network 1 QoS Diffserv Signalling: 26
When I set it back to 9, the TOS changes too.
xconfiguration Network 1 qos Diffserv Signalling: 0
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
09:35:58.892761 IP (tos 0x0, ttl 64, id 31993, offset 0, flags [DF], proto TCP (6), length 1300)
ams-dderidde-8916.cisco.com.41733 > vcs-sjc-101.cisco.com.5060: Flags [.], cksum 0xae5a (correct), seq 1999530794:1999532042, ack 2497347384, win 483, options [nop,nop,TS val 154833894 ecr 2193708619], length 1248
I am unaware of any known issues in this area, but again, Martin's point about deferred images and upgrading the unit seems to be a logical step to do first!
01-24-2013 02:48 AM
Dear Danny
Thanks a lot.
Our Profile42 is using C20 codec. This is without encryption license and there is no console.
There is COM1 port in Profile42. I cant connect with normal console cable, may be I need Y type console cable.
I will try to get tcp dump using telnet and update you on the same.
Rgds
Rajesh
01-29-2013 05:28 AM
Dear Danny
Somhow Profile42 I could not run winscp
I took tcpdump from Profile 52
version TC4.2.1.265253
Call made between P52 and P42
P52 IP is 10.49.229.202 and P42:10.49.0.51
VCS IP:10.49.73.11
Attached tcpdump and QoS configuration on P52.
Here also, SIP signaling packet initiated bt P52 QoS DSCP value shows 0x00
But VCS sourced IP DSCP value is perfect as configured in VCS.
Pls. suggest
01-29-2013 12:44 PM
Hello,
the traces reveal IMHO there's a software bug in TC4.2.1 code when it comes to DSCP marking. I looked at our database and could not identify a matching ddts at this point, however, as I tested later release, there it worked. So it got changed/fixed somewhere in the code. Let me ask around.
02-03-2013 08:24 PM
Dear Danny
Any update on the sw bug issue? Were you able to confirm it is becoz of bug issue?
Also, if I have TCNC software shall I upgrade to TC software without purchasing encryption license? Endpoint is under cisco warranty.
Waiting for your response.
Rgds
Rajesh Kumar
02-03-2013 09:10 PM
Hello,
I looked around for known issues in this area, but could not find any defects. Any chance to get the Profile upgraded to a more recent version?!
02-03-2013 09:33 PM
This should be CSCtr28274. Fixed in TC5 release.
02-03-2013 10:42 PM
Thanks Teck : this is mactching ddts allright!
So moving to TCNC5.1.6 or even TCNC6.0.0 (just released) would fix this.
02-04-2013 03:52 AM
Dear Danny
Thanks a lot.
If I have TCNC software shall I upgrade to TC software without purchasing encryption license? Endpoint is under cisco warranty.
Rgds
Rajesh
02-04-2013 04:28 AM
For TC5 you will need a new release key which you need to obtain from licensing. There must have been a reason for you to run TCNC software in the first place, no? If the country the unit is installed at allows encryption AND you can get licencing to provide you new key for that release, I can see no problem. This is something you need to work out woth software licensing...
02-06-2013 04:40 AM
Dear Danny
Thanks, Profile52 shipped with TC sw and P42 with TCNC SW. I will check with licnesing team.
Rgds
Rajesh
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