Partager via

Presence issue with OCS R1 Pool and R2 MOC Client

  • Article

Symptoms

R2 MOC Client issue with status showing incorrectly - showing as offline/online, not accurate.

Cause

Checking the Communicator UCCAPILOG.log from a customer’s R2 MOC Client I found the following:
- SIP/2.0 409 Conflict
- ms-diagnostics: 2044;reason="Publication version out of date";source="<OCS Server or Pool FQDN>"
This lead me to think to have the customer check and verify that the OCS Server and Client were on the build or on the latest CU.
Customer informed MSFT that, "We are in an environment that is unsupported. We have R2 ocs clients and R1 servers. We have known about this. It was something the vendor who setup our system did. "
Unfortunately, this is an supported configuration and troubleshooting will need to stop until they either move the MOC Clients to R1 or move their OCS Servers to R1.

Resolution

This is a unsupported configuration.  A solution can be realized by either:
a - use R1 MOC Client with their existing OCS R1 deployment
b - upgrade current OCS R1 deployment to R2 if they want to use R2 MOC Client

 

 

Example R2 MOC Client UCCAPILOG

04/22/2010|15:26:20.663 151C:5C4 INFO :: Data Received - xxx.xxx.xxx.xxx:5061 (To Local Address: xxx.xxx.xxx.xxx:3579) 1634 bytes:

04/22/2010|15:26:20.663 151C:5C4 INFO :: SIP/2.0 409 Conflict

Proxy-Authentication-Info

: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFFE06FF196D1F37D1D3EBD918113499FC5", srand="657320AF", snum="10", opaque="7CBBD7DB", qop="auth", targetname="sip/OCS-Front-Server-FQDN", realm="SIP Communications Service"

Content-Length

: 835

From

: "First Name Last Name (Services - 6)"<sip:user@domain.com>;tag=50f8ba1127;epid=c785eb6576

To

: <sip:user@domain.com>;tag=314E45B93DFA34E75449474258A78FE0

Call-ID

: 7bc7bc54f0354c2fac115aae93e6bb9c

CSeq

: 1 SERVICE

Via

: SIP/2.0/TLS xxx.xxx.xxx.xxx:3579;received=xxx.xxx.xxx.xxx;ms-received-port=3579;ms-received-cid=29C3DD00

ms-diagnostics

: 2044;reason="Publication version out of date";source="OCS-Front-Server-FQDN"

Content-Type

: application/msrtc-fault+xml

<Fault>

<Faultcode>Client.BadCall.WrongDelta</Faultcode>

<details>

<operation index="1" version="0" curVersion="1" >

<device xmlns="https://schemas.microsoft.com/2006/09/sip/device" endpointId="AD2D8E0D-8E0B-5CF7-A833-486B3B4CCC59" gruu="sip:bruce.d.reid@domsvcs.com;opaque=user:epid:DY4trQuO91yoM0hrO0zMWQAA;gruu" ><capabilities preferred="false" uri="sip:bruce.d.reid@domsvcs.com" ><text capture="true" render="true" publish="false" ></text><gifInk capture="false" render="true" publish="false" ></gifInk><isfInk capture="false" render="true" publish="false" ></isfInk><applicationSharing capture="true" render="true" publish="false" ></applicationSharing><breakthrough capture="false" render="false" publish="true" ></breakthrough></capabilities><machineName >OJRB67FMG1</machineName></device></operation>

</details>

</Fault>

04/22/2010|15:26:20.663 151C:5C4 INFO :: End of Data Received - xxx.xxx.xxx.xxx:5061 (To Local Address: xxx.xxx.xxx.xxx:3579) 1634 bytes