Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
9025
Views
25
Helpful
14
Replies

CMS Video Conferencing Error

Go to solution
Laith Ibrahim
Level 1
Level 1

‎08-13-2017 12:55 AM - edited ‎03-18-2019 01:23 PM

Dears,

I have deployed CMS successfully with cucm, and installed all licenses in the server,

but now i get this error when i try ad-hoc call:

Error:ACK received with no session description late media call - ending call

Could anyone please help me?

3 people had this problem
Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Laith Ibrahim
Level 1
Level 1
In response to Alok Jaiswal

‎08-23-2017 05:27 AM

Thank you all for you help,

i finally opened a TAC case and it turns out the subject name was wrong in the sip trunk security profile,

I wasn't able to open a ticket because the contract wasn't activated yet,

Thanks again guys.

View solution in original post

14 Replies 14

Go to solution
Laith Ibrahim
Level 1
Level 1

‎08-13-2017 03:24 AM

I just did a search in google and i found the attached info, i don't exactly know what it means, could anyone explain?

Preview file
12 KB
0 Helpful

Go to solution
Alok Jaiswal
Level 4
Level 4
In response to Laith Ibrahim

‎08-13-2017 04:23 AM

Laith, 

SIP invite message contains as "content-type" header something like this in the SIP signalling.

Content-Type: application/sdp

However the issue you mentioned says if the party sends this header value in "UPPERCASE" it disconnects the call.

You can verify if this is exactly the issue or not, by taking out the log files from the CMS using winscp and look for the above mentioned header.

Regards,

Alok

0 Helpful

Go to solution
Laith Ibrahim
Level 1
Level 1
In response to Alok Jaiswal

‎08-13-2017 11:05 AM

actually i looked at the logs, it was like this:

Aug 13 10:51:32 user.info cms host:server:  INFO : SIP trace: Content-Type: application/sdp

i don't know why is this happening with me here!

i followed the guide exactly but i had no luck of making it to work

I need help!

0 Helpful

Go to solution
Alok Jaiswal
Level 4
Level 4
In response to Laith Ibrahim

‎08-13-2017 03:48 PM

Can you attach the log file, so that we can look at it and suggest ?

Regards,

Alok

0 Helpful

Go to solution
Laith Ibrahim
Level 1
Level 1
In response to Alok Jaiswal

‎08-13-2017 11:23 PM

Here is a log file of the conference i tried to create,

it's not working for me, and i followed also the guide in this video:

https://www.youtube.com/watch?v=FFcGHWb718c

Preview file
34 KB
0 Helpful

Go to solution
Patrick Sparkman
VIP Alumni
VIP Alumni
In response to Laith Ibrahim

‎08-14-2017 08:01 PM

You should SFTP into your CMS and download the "log" file (syslog), the event logs that are available in the web interface are very basic and doesn't include all the information available, but the syslog file contains everything.

0 Helpful

Go to solution
Laith Ibrahim
Level 1
Level 1
In response to Patrick Sparkman

‎08-14-2017 10:38 PM

The syslog attached

syslog_0.zip
0 Helpful

Go to solution
Alok Jaiswal
Level 4
Level 4
In response to Laith Ibrahim

‎08-14-2017 10:51 PM

The file only contains till 13th Aug of logs. Can you  logging on GUI and 

enable sip detailed trace for 10 min s
make a test call, wait it to disconnect. 
Once done, login to winscp and take out the file. And then attach it here.
Thanks
Alok
0 Helpful

Go to solution
Laith Ibrahim
Level 1
Level 1
In response to Alok Jaiswal

‎08-23-2017 12:24 AM

The logs are attached. with a call from these extensions:

6666

6667

2206

cms.sepco-env.local_Wed_Aug_23_07_02_36_2017.tar
0 Helpful

Go to solution
Alok Jaiswal
Level 4
Level 4
In response to Laith Ibrahim

‎08-23-2017 05:23 AM - edited ‎08-23-2017 05:30 AM

Hi,

 

I was tracing the call from 6666 and i see that its actually an Jabber client. And i also see that , as soon as CMS sends out a 200 OK with SDP content, a CANCEL is recieved disconnecting the call from 6666.

 

INVITE

------

Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: incoming SIP TLS data from 10.100.101.250:47938 to 10.100.101.244:5061, size 1000:
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: INVITE sip:001036190002@cms.sepco-env.local:5061 SIP/2.0
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Via: SIP/2.0/TLS 10.100.101.250:5061;branch=z9hG4bK6653a1dfe0d3f
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: From: <sip:6666@10.100.101.250>;tag=878367~6e3bbd62-7ef1-4cea-b9a7-b613b9ff6782-17784016
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: To: <sip:001036190002@cms.sepco-env.local>
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Date: Wed, 23 Aug 2017 06:59:47 GMT
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-ID: a5043900-99d127e3-4b744-fa65640a@10.100.101.250
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Supported: timer,resource-priority,replaces
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Min-SE: 1800
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: User-Agent: Cisco-CSF
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: CSeq: 101 INVITE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Expires: 180
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Allow-Events: presence, kpml
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Supported: X-cisco-srtp-fallback
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Supported: Geolocation
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-Info: <sip:10.100.101.250:5061>;method="NOTIFY;Event=telephone-event;Duration=500"
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-Info: <urn:x-cisco-remotecc:conference>
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Session-ID: 000020cc00105000a00054ee757f2862;remote=00000000000000000000000000000000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Cisco-Guid: 2768517376-0000065536-0000007430-420094874
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: incoming SIP TLS data from 10.100.101.250:47938 to 10.100.101.244:5061, size 306:
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: 6
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Session-Expires: 1800
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: P-Asserted-Identity: <sip:6666@10.100.101.250>
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Remote-Party-ID: <sip:6666@10.100.101.250>;party=calling;screen=yes;privacy=off
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Contact: <sip:6666@10.100.101.250:5061;transport=tls>;video;audio;+u.sip!devicename.ccm.cisco.com="test";bfcp
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Max-Forwards: 70
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Content-Length: 0

 

TRYING

-------
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: outgoing SIP TLS data to 10.100.101.250:47938 from 10.100.101.244:5061, size 463:
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: SIP/2.0 100 Trying
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Via: SIP/2.0/TLS 10.100.101.250:5061;branch=z9hG4bK6653a1dfe0d3f
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-ID: a5043900-99d127e3-4b744-fa65640a@10.100.101.250
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: CSeq: 101 INVITE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Max-Forwards: 70
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: To: <sip:001036190002@cms.sepco-env.local>;tag=4e66ed13623a3a69
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: From: <sip:6666@10.100.101.250>;tag=878367~6e3bbd62-7ef1-4cea-b9a7-b613b9ff6782-17784016
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Allow: INVITE,ACK,CANCEL,OPTIONS,INFO,BYE,UPDATE,REFER,SUBSCRIBE,NOTIFY,MESSAGE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Server: Acano CallBridge
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Content-Length: 0
Aug 23 09:59:47 user.info cms host:server: INFO : call 4: incoming encrypted SIP call from "sip:6666@10.100.101.250" to local URI "sip:001036190002@cms.sepco-env.local:5061"

 

Ringing

-------
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: outgoing SIP TLS data to 10.100.101.250:47938 from 10.100.101.244:5061, size 464:
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: SIP/2.0 180 Ringing
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Via: SIP/2.0/TLS 10.100.101.250:5061;branch=z9hG4bK6653a1dfe0d3f
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-ID: a5043900-99d127e3-4b744-fa65640a@10.100.101.250
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: CSeq: 101 INVITE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Max-Forwards: 70
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: To: <sip:001036190002@cms.sepco-env.local>;tag=4e66ed13623a3a69
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: From: <sip:6666@10.100.101.250>;tag=878367~6e3bbd62-7ef1-4cea-b9a7-b613b9ff6782-17784016
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Allow: INVITE,ACK,CANCEL,OPTIONS,INFO,BYE,UPDATE,REFER,SUBSCRIBE,NOTIFY,MESSAGE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Server: Acano CallBridge
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Content-Length: 0

 

200OK

--------
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: outgoing SIP TLS data to 10.100.101.250:47938 from 10.100.101.244:5061, size 3919:
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: SIP/2.0 200 OK
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Via: SIP/2.0/TLS 10.100.101.250:5061;branch=z9hG4bK6653a1dfe0d3f
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-ID: a5043900-99d127e3-4b744-fa65640a@10.100.101.250
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: CSeq: 101 INVITE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Max-Forwards: 70
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Server: Acano CallBridge
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Contact: <sip:10.100.101.244;transport=tls>;isFocus
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: To: "001036190002" <sip:001036190002@cms.sepco-env.local>;tag=4e66ed13623a3a69
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: From: <sip:6666@10.100.101.250>;tag=878367~6e3bbd62-7ef1-4cea-b9a7-b613b9ff6782-17784016
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Allow: INVITE,ACK,CANCEL,OPTIONS,INFO,BYE,UPDATE,REFER,SUBSCRIBE,NOTIFY,MESSAGE
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Supported: timer
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Require: timer
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Session-Expires: 1800;refresher=uas
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Min-SE: 1800
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Content-Type: application/sdp
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Content-Length: 3273
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: v=0
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: o=Acano 0 0 IN IP4 10.100.101.244
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: s=-
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: c=IN IP4 10.100.101.244
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: b=CT:1953
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: t=0 0
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: m=audio 47532 RTP/AVP 108 107 109 110 9 99 111 100 104 103 0 8 15 102 18 13 118 101
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=sendrecv
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:108 opus/48000/2
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:107 MP4A-LATM/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:107 profile-level-id=24;bitrate=64000;object=23
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:109 G7221/32000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:109 bitrate=48000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:110 G7221/32000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:110 bitrate=32000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:9 G722/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:99 G7221/16000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:99 bitrate=32000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:111 G7221/32000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:111 bitrate=24000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:100 G7221/16000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:100 bitrate=24000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:104 speex/32000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:103 speex/16000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:0 PCMU/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:8 PCMA/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:15 G728/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:102 speex/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:18 G729/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:18 annexb=yes
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:13 CN/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:118 CN/16000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:101 telephone-event/8000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:101 0-15
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: m=video 47534 RTP/AVP 97 116 112 114 96 34 31 100 121
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: b=TIAS:2000000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=content:main
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=sendrecv
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtcp-fb:* nack pli
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtcp-fb:* ccm fir
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:97 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:97 profile-level-id=428014;max-mbps=489600;max-fs=8160;max-cpb=4000;max-dpb=4752;max-fps=6000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:116 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:116 profile-level-id=428014;max-mbps=489600;max-fs=8160;max-cpb=4000;max-dpb=4752;max-fps=6000;packetization-mode=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:112 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:112 profile-level-id=648014;max-mbps=489600;max-fs=8160;max-cpb=4000;max-dpb=4752;max-fps=6000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:114 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:114 profile-level-id=648014;max-mbps=489600;max-fs=8160;max-cpb=4000;max-dpb=4752;max-fps=6000;packetization-mode=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:96 H263-1998/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:96 qcif=1;cif=1;cif4=1;custom=1024,768,1;custom=1280,720,1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:34 H263/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:34 qcif=1;cif=1;cif4=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:31 H261/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:31 qcif=1;cif=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:100 VP8/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtcp-fb:100 nack
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:121 x-rtvc1/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=x-caps:121 263:1920:1080:30.0:2000000:1;4389:1280:720:30.0:2000000:1;8455:640:480:30.0:2000000:1;10345:352:288:30.0:2000000:1;12912:176:144:30.0:2000000:1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=label:11
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: m=video 47536 RTP/AVP 97 116 112 114 96 34 100 121
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: b=TIAS:2000000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=content:slides
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=sendrecv
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtcp-fb:* nack pli
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtcp-fb:* ccm fir
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:97 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:97 profile-level-id=428014;max-mbps=270000;max-fs=9000;max-cpb=4000;max-dpb=4752;max-fps=3000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:116 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:116 profile-level-id=428014;max-mbps=270000;max-fs=9000;max-cpb=4000;max-dpb=4752;max-fps=3000;packetization-mode=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:112 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:112 profile-level-id=648014;max-mbps=270000;max-fs=9000;max-cpb=4000;max-dpb=4752;max-fps=3000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:114 H264/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:114 profile-level-id=648014;max-mbps=270000;max-fs=9000;max-cpb=4000;max-dpb=4752;max-fps=3000;packetization-mode=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:96 H263-1998/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:96 qcif=1;cif=1;cif4=1;custom=1024,768,1;custom=1280,720,1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:34 H263/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=fmtp:34 qcif=1;cif=1;cif4=1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:100 VP8/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtcp-fb:100 nack
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=rtpmap:121 x-rtvc1/90000
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=x-caps:121 263:1920:1080:30.0:2000000:1;4389:1280:720:30.0:2000000:1;8455:640:480:30.0:2000000:1;10345:352:288:30.0:2000000:1;12912:176:144:30.0:2000000:1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=label:12
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: m=application 47538 UDP/BFCP *
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: c=IN IP4 10.100.101.244
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=floorctrl:s-only
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=confid:1
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=userid:4
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=floorid:2 mstrm:12
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: m=application 47529 UDP/UDT/IX *
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=ixmap:0 ping
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: a=ixmap:2 xccp

 

CANCEL FROM CSF

------------------
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: incoming SIP TLS data from 10.100.101.250:47938 to 10.100.101.244:5061, size 433:
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: CANCEL sip:001036190002@cms.sepco-env.local:5061 SIP/2.0
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Via: SIP/2.0/TLS 10.100.101.250:5061;branch=z9hG4bK6653a1dfe0d3f
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: From: <sip:6666@10.100.101.250>;tag=878367~6e3bbd62-7ef1-4cea-b9a7-b613b9ff6782-17784016
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: To: <sip:001036190002@cms.sepco-env.local>
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Date: Wed, 23 Aug 2017 06:59:47 GMT
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Call-ID: a5043900-99d127e3-4b744-fa65640a@10.100.101.250
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: User-Agent: Cisco-CSF
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: CSeq: 101 CANCEL
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Max-Forwards: 70
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: Content-Length: 0
Aug 23 09:59:47 user.info cms host:server: INFO : SIP trace: connection 4: outgoing SIP TLS data to 10.100.101.250:47938 from 10.100.101.244:5061, size 477:

 

By the way what is the ip's 10.100.101.250 & 10.100.101.244 ? 

 

Can you attach the Jabber client PRT as well ? Also is this issue happens with all clients or just with Jabber clients ? What version of Jabber are you running ? Did you tried enabling Early offer for the CMS ?

 

From the logs ,

Aug 23 09:59:47 user.err cms host:server: ERROR : ACK received with no session description late media call - ending call
Aug 23 09:59:47 user.info cms host:server: INFO : call 4: ending; local SIP teardown with reason 27 (late media) - not connected after 0:00

Regards,

Alok

0 Helpful

Go to solution
Laith Ibrahim
Level 1
Level 1
In response to Alok Jaiswal

‎08-23-2017 05:27 AM

Thank you all for you help,

i finally opened a TAC case and it turns out the subject name was wrong in the sip trunk security profile,

I wasn't able to open a ticket because the contract wasn't activated yet,

Thanks again guys.

Go to solution
Alok Jaiswal
Level 4
Level 4
In response to Laith Ibrahim

‎08-23-2017 04:33 PM

Thanks for posting the solution. Certificate errors can be verified in the CUCM SDL traces or wireshark as well.

 

Regards,

Alok

0 Helpful

Go to solution
carlo alberto michelotti
Level 1
Level 1

‎11-24-2017 01:13 AM

thanks for post the solution!
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents