Free\busy information not availabe in cross forest federation after migration meeting room from 2010 to 2013 exchange

We have Exchange 2013 in company A and Exchange 2010 + 2013 servers in company B. There is a two-way AD forest trust beetwen forests. We did GAL synchronization with Microsoft Forefront Identity Manager. There is organization sharing configured on both exchange organization in place. Everything worked as expected. Currently we are trying to migrate meeting rooms in company B from exchange 2010 to 2013 mailbox database. Move request was finished with success, meeting room (in comapny B) responds for meeting requests from users from federated company A. But users in company CANNOT see free\busy information about this specific meeting room - error from exchange event log below. Users can see free\busy information about any other meeting rooms from federated organization. Any idea how to fix it?

Process 6744: ProxyWebRequest FederatedCrossForest from S-1-5-21-3929926812-3994860513-325457373-13759 to https://m.companyB.com:443/ews/krks12..companyname.com/exchange.asmx/WSSecurity failed. Caller SIDs: WSSecurity. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: Proxy web request failed.  ---> System.Web.Services.Protocols.SoapException: The specified server version is invalid.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
   --- End of inner exception stack trace ---
. Name of the server where exception originated: companyA_ex_server_name. Make sure that the Active Directory site/forest that contain the user's mailbox has at least one local Exchange 2010 server running the Availability service. Turn up logging for the Availability service and test basic network connectivity.