Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

TC7.2.1 Problems with SIP calls

Hi, we got the following problem concerning sip calls:

here's the log:

Software Version VCS: Plattform X7.2.3 | Labor X8.2.1

 

______________________________________________________________________________

        Not Working Call with TC 7.2.1
______________________________________________________________________________

SIPMSG:
 |INVITE sip:9209901105@xyz.com SIP/2.0
 Via: SIP/2.0/TCP xx.xxx.60.133:57597;branch=z9hG4bK38f566387dbd719702049ddcb2590ebe.1;rport
 Call-ID: 4832bd6a60d9d3d43670c55c573667ec
 CSeq: 101 INVITE
 Contact: <sip:201101102@xyz.com:57597;gr=urn:uuid:6c856033-4cbd-5b15-bb13-0715c4a694cd;ob>
 From: "201101102_C40_ServiceDesk" <sip:201101102@xyz.com>;tag=d25377890df67530
 To: <sip:9209901105@xyz.com>
 Max-Forwards: 70
 Route: <sip:xx.xxx.1.51;lr>
 Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY
 User-Agent: TANDBERG/521 (TC7.2.1.cb31c3d)
 Proxy-Authorization: Digest nonce="bb1d830b2d64949caaadfb732cd7ca77414a991699854e8971970a68fe06", realm="tplabvcsc01.xyz.com", qop=auth, opaque="AwAAAMSaxlh37+YNQULdXHDdMkXYHVQ1", username="", uri="sip:xyz.com", response="51f225da16a3ac710e86c1b1b5815438", algorithm=MD5, nc=00000008, cnonce="21c839c8313e8f7f7477786cb40c5ee6"
 Supported: replaces,100rel,timer,gruu,path,outbound
 Session-Expires: 1800
 Content-Type: application/sdp
 Content-Length: 2842
 
 v=0
 o=tandberg 6 2 IN IP4 xx.xxx.60.133
 s=-
 c=IN IP4 xx.xxx.60.133
 b=AS:6000
 t=0 0
 m=audio 16424 RTP/AVP 107 108 109 110 104 105 9 15 18 8 0 101
 b=TIAS:128000
 a=rtpmap:107 MP4A-LATM/90000
 a=fmtp:107 profile-level-id=25;object=23;bitrate=128000
 a=rtpmap:108 MP4A-LATM/90000
 a=fmtp:108 profile-level-id=24;object=23;bitrate=64000
 a=rtpmap:109 MP4A-LATM/90000
 a=fmtp:109 profile-level-id=24;object=23;bitrate=56000
 a=rtpmap:110 MP4A-LATM/90000
 a=fmtp:110 profile-level-id=24;object=23;bitrate=48000
 a=rtpmap:104 G7221/16000
 a=fmtp:104 bitrate=32000
 a=rtpmap:105 G7221/16000
 a=fmtp:105 bitrate=24000
 a=rtpmap:9 G722/8000
 a=rtpmap:15 G728/8000
 a=rtpmap:18 G729/8000
 a=fmtp:18 annexb=yes
 a=rtpmap:8 PCMA/8000
 a=rtpmap:0 PCMU/8000
 a=rtpmap:101 telephone-event/8000
 a=fmtp:101 0-15
 a=sendrecv
 m=video 16426 RTP/AVP 97 126 96 34 31
 b=TIAS:6000000
 a=rtpmap:97 H264/90000
 a=fmtp:97 packetization-mode=0;profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9000;max-smbps=245000;max-fps=6000;max-rcmd-nalu-size=3456000
 a=rtpmap:126 H264/90000
 a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9000;max-smbps=245000;max-fps=6000;max-rcmd-nalu-size=3456000
 a=rtpmap:96 H263-1998/90000
 a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
 a=rtpmap:34 H263/90000
 a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
 a=rtpmap:31 H261/90000
 a=fmtp:31 cif=1;qcif=1;maxbr=20000
 a=label:11
 a=answer:full
 a=content:main
 a=rtcp-fb:* nack pli
 a=rtcp-fb:* ccm fir
 a=rtcp-fb:* ccm tmmbr
 a=sendrecv
 m=application 28300 UDP/BFCP *
 a=setup:actpass
 a=confid:1
 a=userid:6
 a=floorid:2 mstrm:12
 a=floorctrl:c-s
 a=connection:new
 m=video 16428 RTP/AVP 97 126 96 34 31
 b=TIAS:6000000
 a=rtpmap:97 H264/90000
 a=fmtp:97 packetization-mode=0;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560
 a=rtpmap:126 H264/90000
 a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560
 a=rtpmap:96 H263-1998/90000
 a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
 a=rtpmap:34 H263/90000
 a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
 a=rtpmap:31 H261/90000
 a=fmtp:31 cif=1;qcif=1;maxbr=20000
 a=label:12
 a=content:slides
 a=rtcp-fb:* nack pli
 a=rtcp-fb:* ccm fir
 a=rtcp-fb:* ccm tmmbr
 a=sendrecv
 m=application 16430 RTP/AVP 100
 a=rtpmap:100 H224/4800
 a=sendrecv
 m=application 29789 UDP/UDT/IX *
 a=ixmap:0 ping
 a=ixmap:2 xccp
 |
________________________________________________________________________________________________

        Working Call with TC 7.1.4
________________________________________________________________________________________________


 SIPMSG:
 |INVITE sip:9209901105@xyz.com SIP/2.0
 Via: SIP/2.0/TCP xx.xxx.60.133:37491;branch=z9hG4bKe3dfed840a299516919a79e4a54cd707.1;rport
 Call-ID: 480ec504782c0ad894929e882a696e74
 CSeq: 100 INVITE
 Contact: <sip:201101102@xyz.com;gr=urn:uuid:6c856033-4cbd-5b15-bb13-0715c4a694cd;ob>
 From: "201101102_C40_ServiceDesk" <sip:201101102@xyz.com>;tag=3ab87b1c0d8b4d9d
 To: <sip:9209901105@xyz.com>
 Max-Forwards: 70
 Route: <sip:xx.xxx.1.51;lr>
 Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY
 User-Agent: TANDBERG/520 (TC7.1.4.908e4a9)
 Supported: replaces,100rel,timer,gruu,path,outbound
 Session-Expires: 1800
 Content-Type: application/sdp
 Content-Length: 2842
 
 v=0
 o=tandberg 3 2 IN IP4 xx.xxx.60.133
 s=-
 c=IN IP4 xx.xxx.60.133
 b=AS:6000
 t=0 0
 m=audio 16394 RTP/AVP 107 108 109 110 104 105 9 15 18 8 0 101
 b=TIAS:128000
 a=rtpmap:107 MP4A-LATM/90000
 a=fmtp:107 profile-level-id=25;object=23;bitrate=128000
 a=rtpmap:108 MP4A-LATM/90000
 a=fmtp:108 profile-level-id=24;object=23;bitrate=64000
 a=rtpmap:109 MP4A-LATM/90000
 a=fmtp:109 profile-level-id=24;object=23;bitrate=56000
 a=rtpmap:110 MP4A-LATM/90000
 a=fmtp:110 profile-level-id=24;object=23;bitrate=48000
 a=rtpmap:104 G7221/16000
 a=fmtp:104 bitrate=32000
 a=rtpmap:105 G7221/16000
 a=fmtp:105 bitrate=24000
 a=rtpmap:9 G722/8000
 a=rtpmap:15 G728/8000
 a=rtpmap:18 G729/8000
 a=fmtp:18 annexb=yes
 a=rtpmap:8 PCMA/8000
 a=rtpmap:0 PCMU/8000
 a=rtpmap:101 telephone-event/8000
 a=fmtp:101 0-15
 a=sendrecv
 m=video 16396 RTP/AVP 97 126 96 34 31
 b=TIAS:6000000
 a=rtpmap:97 H264/90000
 a=fmtp:97 packetization-mode=0;profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9000;max-smbps=245000;max-fps=6000;max-rcmd-nalu-size=3456000
 a=rtpmap:126 H264/90000
 a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9000;max-smbps=245000;max-fps=6000;max-rcmd-nalu-size=3456000
 a=rtpmap:96 H263-1998/90000
 a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
 a=rtpmap:34 H263/90000
 a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
 a=rtpmap:31 H261/90000
 a=fmtp:31 cif=1;qcif=1;maxbr=20000
 a=label:11
 a=answer:full
 a=content:main
 a=rtcp-fb:* nack pli
 a=rtcp-fb:* ccm fir
 a=rtcp-fb:* ccm tmmbr
 a=sendrecv
 m=application 29489 UDP/BFCP *
 a=setup:actpass
 a=confid:1
 a=userid:3
 a=floorid:2 mstrm:12
 a=floorctrl:c-s
 a=connection:new
 m=video 16398 RTP/AVP 97 126 96 34 31
 b=TIAS:6000000
 a=rtpmap:97 H264/90000
 a=fmtp:97 packetization-mode=0;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560
 a=rtpmap:126 H264/90000
 a=fmtp:126 packetization-mode=1;profile-level-id=428016;max-br=5000;max-mbps=108000;max-fs=3840;max-smbps=108000;max-fps=6000;max-rcmd-nalu-size=1474560
 a=rtpmap:96 H263-1998/90000
 a=fmtp:96 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000
 a=rtpmap:34 H263/90000
 a=fmtp:34 cif4=1;cif=1;qcif=1;maxbr=20000
 a=rtpmap:31 H261/90000
 a=fmtp:31 cif=1;qcif=1;maxbr=20000
 a=label:12
 a=content:slides
 a=rtcp-fb:* nack pli
 a=rtcp-fb:* ccm fir
 a=rtcp-fb:* ccm tmmbr
 a=sendrecv
 m=application 16400 RTP/AVP 100
 a=rtpmap:100 H224/4800
 a=sendrecv
 m=application 31127 UDP/UDT/IX *
 a=ixmap:0 ping
 a=ixmap:2 xccp

 

Another problem, shown in the diagnostics on a MX200-Device, reports NTP issues. I already tried to choose another NTP-Server but this doesnt solve the problem and with TC7.1.4 it's working. In addition the time and the date is wrong on the display but correct on the Touch-device.

Furthermore an error is reported dealing with the OSD-Settings.

 

You got any advice?

Thanks for helping.
 |

1 ACCEPTED SOLUTION

Accepted Solutions
VIP Super Bronze

So what is the problem? You

So what is the problem? You have only showed us an INVITE. What is your system setup? What is the response to the INVITE? We need full diagnostics logs. Is this registred to VCS-C? Where is the VCS-C diagnostics logs

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
16 REPLIES
VIP Super Bronze

So what is the problem? You

So what is the problem? You have only showed us an INVITE. What is your system setup? What is the response to the INVITE? We need full diagnostics logs. Is this registred to VCS-C? Where is the VCS-C diagnostics logs

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Oh, sorry; forgot about the

Oh, sorry; forgot about the important stuff.

First, i'm not allowed to post the full VCS-C log. But that was the error shown in the VCS-C: tvcs: Event="Authentication Failed" Service="SIP" Src-ip="10.XXX.XX.XX" Src-port="57597" Detail="User not found" Protocol="TCP" Method="INVITE" Level="1" UTCTime="2014-10-21 12:35:09,450" 

The system is, as mentioned above, registered to the VCS-C v. 8.2.1.

I tried to call an EX-90 registred to the CUCM from a C-40-Codec registered to the VCS-C. Both using TC7.2.1. The call couldn't be established. No further message on the display.

After i downgraded the C-40-Codec to TC7.1.4 (no config changes made). It worked again.

 

Thanks for your help

VIP Purple

What is the authentication

What is the authentication policy for the VCS zone that this endpoint is registered to?

What is Src-ip="10.XXX.XX.XX", is that CUCM or the C40?

Sounds like you have authentication setup somewhere on the VCS and the account you're trying to authenticate with can't be found.

Regarding the NTP issue, there is a bug (CSCuo59424) where the codec will report an issue after restart, but will go away in time if a valid NTP server is present, this might be what you're seeing.

New Member

Thanks for your answer.The

Thanks for your answer.

The source-IP is the C-40 codec.

VCS-C autentication policy is set to treat as autenticated.

 

Thanks for the info about the NTP-issue, I will try to figure it out.

New Member

I'm hitting exactly the same

I'm hitting exactly the same issue here.  Did you get a resolution to the problem in the end?  I've ensured that the subzone is set to Treat as Authenticated and also added the device to the VCS-C/configured this within the endpoint but still no joy in making calls from the endpoint.  I have the issue with TC7.2.0, 7.2.1, and 7.3.2 versions of code against VCS X8.5.0 and X8.5.1.

Many thanks

David.

New Member

Same problem with other

Same problem with other devices

-> trying to direct call a CTS1300@CUCM from a EX90@VCS-C v.7.2.3@TC7.2.1

VCS-C reports 404 not found 

 

any ideas?

VIP Super Bronze

George,Have you checked your

George,

Have you checked your search history to see if this call showed "found". You can also set your diagnostics log to debug and do another test call..attach logs here

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
VIP Purple

Looking at the SIP invites,

Looking at the SIP invites, the only thing that stands out and is different between the two, is the following line in the non-working call:

Proxy-Authorization: Digest nonce="bb1d830b2d64949caaadfb732cd7ca77414a991699854e8971970a68fe06", realm="tplabvcsc01.xyz.com", qop=auth, opaque="AwAAAMSaxlh37+YNQULdXHDdMkXYHVQ1", username="", uri="sip:xyz.com", response="51f225da16a3ac710e86c1b1b5815438", algorithm=MD5, nc=00000008, cnonce="21c839c8313e8f7f7477786cb40c5ee6"

The codec has to provide authentication to the VCS, and it's sending a blank username, which will result in the Event="Authentication Failed" and Detail="User not found" you're seeing in the VCS logs.  Esspecially if the subzone the endpoint is registered to or has to go through is expecting to check credentials, the endpoint must provide something or the call will fail.  What is the authentication setting for the subzone this endpoint is registered to, and any other zone or subzone the call travels through?  What happens if you created an account on the VCS (Configuration > Authentication > Local database) and entered the account information into the endpoint (Configuration > SIP > Authentication)?

New Member

The setttings in the subzones

The setttings in the subzones are set to "Treat as authenticated" so it shouldn't even check the credentials. In the Search history the call is not appearing. The search is not starting, the call fails before applying any Search rules or Transforms.

I will check the credential thing, but as stated before the endpoint should not check credentials so this is no real option.

New Member

What i can see is that the

What i can see is that the SIP Authentication Settings apply to the Proxy Authentication Header. Then the credentials are added to the local database the call works. Seems logical to me but why does the VCS check the credentials in a zone that is set to "Treat as authenticated" or to "Do not check credentials"? This seems to be a bug in VCS X8.2.2 and X8.2.1...

VIP Purple

Sounds like it's time to open

Sounds like it's time to open a TAC case and have someone take a look for you, of it is a bug, they'll find it. 

New Member

Yes the TAC Case was opened

Yes the TAC Case was opened shortly after this thread. But they also did not find any conclusion until now... They say it has to be a config thing on VCS, which sounds strange to me as we did not change anything and it worked before... I reported what we found out here and will report here what they say.

New Member

Hello, I've a customer

Hello,

 

I've a customer reporting the same problem with SX10 and v7.2.1. About 3-4 hours after registration on the VCS the authentication starts to fail:

SIP Profile 1 Registration 1 Reason: "403 Forbidden"

Is this a know bug? Is there a workaround available?

I've checked NTP and it is correctly configured and in sync.

I suppose most of the customer install this version for the Shellshock fix for endpoints directly connected to the Internet..

 

rgds, Geert.

Hi, we are still having those

Hi,

 

we are still having those issues. But - for us - turning the listenport on seems to be an workaround but it's realy strange because the listenport shouldn't have anything to do with this.

Could you please test this and report back?

Thanks.

 

New Member

Okay, thx for the feedback. I

Okay, thx for the feedback. I've asked to turn the SIP listenport to 'on'.

I'll keep you informed.

New Member

Turning on the Listenport is

Turning on the Listenport is not an option because the endpoint is directly located on the Internet and vulnerable to SIP attacks.

986
Views
5
Helpful
16
Replies
CreatePlease login to create content