10-22-2014 02:33 AM - edited 03-18-2019 03:33 AM
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.
|
Solved! Go to Solution.
11-24-2014 02:57 AM
Okay, thx for the feedback. I've asked to turn the SIP listenport to 'on'.
I'll keep you informed.
11-28-2014 02:34 AM
Turning on the Listenport is not an option because the endpoint is directly located on the Internet and vulnerable to SIP attacks.
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: