VCSC Presence works with MOVI 4.2, but not 4.3. But it works with the VCSE

Question

Good evening,
I have run into an issue with a VCSC. For some reason, Presence information doesnt seem to reach any MOVI client registered to the VCSC. The odd part of it is it is just specific to Jabber client 4.3 and greater. When I register the same client to the VCSE, it registers fine.
Has anyone else ran into this? I just blew away the majority of the config and rebuilt it, but the issue still remains.
Aside from just the presence information, all other calling works on the VCSC.
Any help to narrow this one down would be greatly appreciated.
D.

Answer 1

We've had quite similar issue with VCS-C and VCS-E (X7.1) scenario.
VCS-C is the registering clients against the AD, but all clients has to be proxied from the VCS-E to the VCS-C.
VCS-E has no DNS Zone with any matching SearchRule (therefore there is another VCS-E in this scenario).
Presence was also only working if we used JabberVideo client 4.2 and/or clients were directly registered to VCS-C (which is not allowed in our scenario).
After diagnostic log analyzes, we've noticed the difference between working and not working cases:
Working
Contact: IP_ADDRESS_CLIENT:2524;transport=tls>
Non-working
Contact: DOMAIN;gr=urn:uuid:xyz>
After that we've recognized, SIP GRUU function makes the difference.
http://tools.ietf.org/html/rfc5627
It seems that the 4.2 client ignores or breaks the GRUU function offer from VCS and the new clients are ready to deal with it.
In consequence we've deactivated SIP GRUU Mode on VCS-C by entering:
xConfiguration SIP GRUU Mode: Off
Result: we've got also running PresenceStatus for JabberVideo clients >4.2  (mainly tested with Version 4.7).