Lync 2013 (Oct CU update) Dial-in Webpage not working. This content cannot be displayed in a frame

Question

 today we found an issue with our Lync 2013 deployment while investigating another issue.
ok se we have/had Lync 2013 setup along with IIS ARR. All seems to be working fine.
with the exception of our Dial in page.
no matter what i do it does not work. We have a near identical setup for our other domain & they have no issues. (i copied the Bin folder from the "C:\Program Files\Microsoft Lync Server 2013\Web Components\Dialin Page\Ext" of the working site.
then tracked it down to the "\bin\" folder. which contains the "Micrsoft.RTC.nternal.Conference,dll"
file. If i copy this into our US folder the site works as it should.
So now the kicker....our US file is the newest (5.0.8308.556) where as the other domain is "5.0.8308.301" 
with that said, & with our correct version (.556) of the conference.dll file, this is the page that loads...which we can then click the link & it opens our conference page as it should.
This content cannot be displayed in a frame
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.
What you can try:
Open this content in a new window
So somthing is a miss, & i think it is related to the Oct CU....but have no evidence at the moment.....
any help would be great

Answer 1

yes, IE will shows the warning page, but then lets you click the link.
chrome shows noting. When running Debugger, chrome states:
Refused to display 'https://fepool.company.local/Dialin/Conference.aspx' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'..
the issue is definatley stemming from the new .dll from the CU update. as i compared it against the older version. the newer version is throwing the "X-Frame-options:
SAMEORIGIN"....
I am not sure if that is intended or not.
also i have not been able to find out what the specific purpose of the conferenceproxy.aspx file that the dialin page
uses as its default document. It appears that the page only stands to serve up the Conference.aspx page in the Iframe..
if we swap our default page to be the Conference.aspx all works as expected.