We have persistent problem where ST users cannot see presence of buddies in an external OCS/Lync community, but they can see our presence, start a chat, and only then can we reply. We have now got hold of a trace.log from another Sametime setup that does talk correctly to the same OCS/Lync community, and can find 3 differences in the trace log from them and ours. The two logs are listed below (working from them, failing from us) and the differences I see are highlighted. Can anyone maybe point to ways we can configure our Gateway differently, in order to get an identical (or working) result, since OCS people are saying it's our problem.
Working one - In Message:
SUBSCRIBE sips:ashaull@be4nj01ucf02dmsw0.ims.research.att.com:5061;transport=tcp SIP/2.0
Content-Length: 0
Contact: <sips:imgw.ibm.com:5061;transport=tcp>
Via: SIP/2.0/TLS imgw.ibm.com:5061;branch=z9hG4bK460469184837169;rport
Via: SIP/2.0/TLS y03wcxim227.ahe.boulder.ibm.com:5065;rport=5065;ibmsid=RTCGWServer02.1437807304245.0_612344_635092;branch=z9hG4bK460469184837169;received=170.225.31.227
Expires: 3600
Accept: application/pidf+xml
CSeq: 2 SUBSCRIBE
Max-Forwards: 69
Call-ID: 39376421626496994@y03wcxim227.ahe.boulder.ibm.com
To: sips:ashaull@ucfed2k13.uclabs.com
From: sips:sdelor69@iespc.ibm.com;tag=9856321530912381_RTCGWServer02.1437807304245.0_612344_635092
Event: presence
Nonworking one - In Message:
SUBSCRIBE sip:ashaull@ucfed2k13.uclabs.com SIP/2.0 - we are missing the "transport-tcp"
Content-Length: 0
Via: SIP/2.0/TLS 172.24.41.56:5061;rport;ibmsid=local.1438072143906_4_5;branch=z9hG4bK727042121562228 - our address is IP, not FQDN
Contact: sip:gateway.stfed.uclabs.com:5061 - we are missing the "transport-tcp"
Expires: 3600
Accept: application/pidf+xml
CSeq: 2 SUBSCRIBE
Max-Forwards: 70
Call-ID: 41267173058116147@172.24.41.56
To: sip:ashaull@ucfed2k13.uclabs.com
From: sip:zk@stfed.uclabs.com;tag=8535510285613371_local.1438072143906_4_5
Event: presence
ms-asserted-verification-level: ms-source-verified-user=verified