tag:blogger.com,1999:blog-2158853543793456735.post646180552542375363..comments2023-10-02T04:50:01.667-07:00Comments on VoIPNorm's Collaboration Blog: F5 configuration for OCS R2 Enterprise EditionChris Normanhttp://www.blogger.com/profile/07200178774058910421noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2158853543793456735.post-61202901611636851652011-12-12T14:07:24.348-08:002011-12-12T14:07:24.348-08:00We just upgraded from 9 to version 10 and now we a...We just upgraded from 9 to version 10 and now we are not Federated with anyone. Does anyone know a quick fix?Mario Mescinohttp://www.careered.comnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-80032526002774170452009-05-31T10:07:14.569-07:002009-05-31T10:07:14.569-07:00At first glance this document does not talk at per...At first glance this document does not talk at persistence which if incorrectly set will stop your deployment fom working and is also a recommended MSFT setting. You may also find you need this setting in your CWA configuration to stop sessions from disconnecting. So as nice as it is to have the document it still lacks a complete configuration.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-17842514006784531242009-05-31T09:56:31.896-07:002009-05-31T09:56:31.896-07:00Thanks for the link to the new F5 documentation. I...Thanks for the link to the new F5 documentation. It is nice to have the offical documentation from the vendor at last.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-4856355514149919242009-05-29T15:52:59.072-07:002009-05-29T15:52:59.072-07:00F5 has just released an updated version of the OCS...F5 has just released an updated version of the OCS Deployment guide, which now covers R2.<br /><br />Got to http://www.f5.com/pdf/deployment-guides/f5-ocs-r2-dg.pdfAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-77422149108366031892009-05-28T22:25:17.360-07:002009-05-28T22:25:17.360-07:00Hi,
This is the exact configuration we use and th...Hi,<br /><br />This is the exact configuration we use and the reason to use SNAT. No need to have the front ends on the same subnet as the F5 where the F5 is the defualt gateway. Everything is happening at layer 3 and allows a lot more flexibility in your setup. <br /><br />The most important setting in the information above that can be easily missed or incorrectly set is persistence or as MSFT call it affinity. This must be set to source address for everything to function correctly especially port 5061. The F5 can not do deep packet inspection becuase of TLS so setting that port persistence setting to somehting like SIP can cause all sorts of issues.<br /><br />Thanks for the comment and good question, I am sure its a question others have as well.Chris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-20582042512881929672009-05-28T05:03:41.069-07:002009-05-28T05:03:41.069-07:00Great Information Chris. Thanks! I was wondering...Great Information Chris. Thanks! I was wondering if you have seen implementations with BigIP where the FE's have an IP address and then use the loopback adapter (with the BigIP VIP as the address)? BigIP is not setup as the default gateway in this configuration.Anonymousnoreply@blogger.com