Hi all,
I`ve problems integrate a Tandberg/58 (with F6.3 NTCS).
I can make calls to Communicator clients from Tandberg, and can call to Tandberg using communicator clients... but when OCS MCU (Conference, 2 or more peoples calling Tandberg MCU), i`ve the errors above (collected by SipStack from OCS Logging tool and filtered using snooper).
Anyone have any idea what i need to do? Tandberg are using TLS too, with 5061 port.
Follow the erros and connections strings:
Info about Connection
TL_INFO(TF_PROTOCOL) [0]0920.115C::04/28/2008-22:03:10.444.00278309 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
Instance-Id: 0004A1BB
Direction: incoming
Peer: 10.1.100.31:49154
Message-Type: response
Start-Line: SIP/2.0 200 OK
From: <sip:xx@xx.xxx.xxx;gruu;opaque=app:conf:audio-video:id:BF1E6A0E3F9DA744B387E84F89E37D31>;epid=FCEB0AC7FA;tag=7b1ba68544
To: <sip:tb@xx.xxx.xxx>;epid=TAA005060023424;tag=55913a832bb6ca0d
CSeq: 16 INVITE
Call-ID: b42a95ba-2891-4d09-87f9-ada825852df5
Via: SIP/2.0/TLS 10.1.1.14:5061;branch=z9hG4bK56C26995.E2502384;branched=TRUE;ms-internal-info="dscpdU4j1OyXwt8cVqffvOhCM85JjiUCOEZXleMgAA";received=10.1.1.14
Via: SIP/2.0/TLS 10.1.1.14:3419;branch=z9hG4bK882f7e3f;ms-received-port=3419;ms-received-cid=171700
Contact: <sip:tb@10.1.100.31:5061;transport=tls>;proxy=replace
Record-Route: <sip:xx.xxx.xxx.xx:5061;transport=tls;ms-role-rs-to;ms-role-rs-from;lr;ms-route-sig=fip1Z4Vc4-Zj3HHDgwvtGz-E3RM6DiUCOEKVDwDgAA>;tag=C67087AFEDA5F392CC59F19210411701
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY
Server: TANDBERG/58 (F6.3 NTSC)
Authorization: NTLM qop="auth", realm="SIP Communications Service", targetname="xx.xxx.xxx", opaque="FC9F4239", crand="a4a61886", cnum="136", response="01000000599AAC886E2FB20E186C67C9"
Supported: replaces,100rel,timer,com.microsoft.msrtc.presence,com.microsoft.msrtc.presence,com.microsoft.msrtc.presence,com.microsoft.msrtc.presence,com.microsoft.msrtc.presence,com.microsoft.msrtc.presence,com.microsoft.msrtc.presence
Session-Expires: 500; refresher=uas
Min-SE: 90
Allow-Events: tandberg-dtmf
Content-Type: application/sdp
Content-Length: 203
Message-Body: v=0
o=tandberg 1 1 IN IP4 10.1.100.31
s=-
c=IN IP4 10.1.100.31
b=CT:1000
t=0 0
m=audio 48076 RTP/AVP 0 8
b=TIAS:64000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=sendrecv
m=video 0 RTP/AVP 0
$$end_record
First Error
TL_INFO(TF_PROTOCOL) [0]0920.0B48::04/28/2008-22:03:10.944.002784d6 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
Instance-Id: 0004A1BD
Direction: incoming
Peer: xx.xxx.xxx.xx5063
Message-Type: response
Start-Line: SIP/2.0 500 Internal Server Error
From: <sip:tb@xx.xxx.xxx>;tag=55913a832bb6ca0d;epid=TAA005060023424
To: <sip:xxx@xxx.xxx.xxx;gruu;opaque=app:conf:audio-video:id:BF1E6A0E3F9DA744B387E84F89E37D31>;tag=7b1ba68544;epid=FCEB0AC7FA
CSeq: 501 BYE
Call-ID: b42a95ba-2891-4d09-87f9-ada825852df5
VIA: SIP/2.0/TLS 10.1.1.14:3418;branch=z9hG4bKE8E7516E.37B7132C;branched=FALSE,SIP/2.0/TLS 10.1.100.31:5061;received=10.1.100.31;branch=z9hG4bKf7dabed4c9f2d17e7b261c75b9b4aa0d.1;rport;ms-received-port=49154;ms-received-cid=171100
CONTENT-LENGTH: 0
SERVER: RTCC/3.0.0.0 AV-MCU
Message-Body: –
$$end_record
Second Error
TL_INFO(TF_PROTOCOL) [0]0920.0B48::04/28/2008-22:03:10.944.002785be (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
Instance-Id: 0004A1BD
Direction: outgoing
Peer: 10.1.100.31:49154
Message-Type: response
Start-Line: SIP/2.0 500 Internal Server Error
From: <sip:tb@xxx.xxx.xxx>;tag=55913a832bb6ca0d;epid=TAA005060023424
To: <sip:xxx@xxx.xxx.xx;gruu;opaque=app:conf:audio-video:id:BF1E6A0E3F9DA744B387E84F89E37D31>;tag=7b1ba68544;epid=FCEB0AC7FA
CSeq: 501 BYE
Call-ID: b42a95ba-2891-4d09-87f9-ada825852df5
Authentication-Info: NTLM rspauth="01000000C51300008318F30E186C67C9", srand="61BDBC29", snum="108", opaque="FC9F4239", qop="auth", targetname="xxx.xxx.xxx.com", realm="SIP Communications Service"
Via: SIP/2.0/TLS 10.1.100.31:5061;received=10.1.100.31;branch=z9hG4bKf7dabed4c9f2d17e7b261c75b9b4aa0d.1;rport;ms-received-port=49154;ms-received-cid=171100
CONTENT-LENGTH: 0
SERVER: RTCC/3.0.0.0 AV-MCU
ms-diagnostics: 1011;reason="Ms-Diagnostics header not provided by previous hop";source="sao12.2s.com.br";Domain="xxx.xx.com";PeerServer="xxx.xxx.xxx.com"
Message-Body: –
$$end_record
