Answered by:
pc-to-pc call

Question
-
We are just finalizing test of a hosted OCS setup (HMC deployment guide), and everything works, just not anything related to SIP tunnelling between external clients. Our configuration is as follows:
- 1 backend (CD,QoE, SQL)
- 1 application (OCS roles)
- 1 frontend (Edge, two nics)
Published with a Cisco PIX 515 firewall and Squirt for reverse proxy. We can chat, expand groups, see ABS, do live meeting (w/wo video, voice), share desktop, everything works - just not two features: pc-to-pc call and send file. Pc-to-pc call only works if they are on the same side of an external line (SIP not traversing firewal), but if one of the MOC users are behind another ADSL (router) - we cannot get voice to connect. I guess is has something to do with media relay or SIP/TURN/STUN. I even tried putting the external MOCs on a WAN connection with not firewall, but does not work.
Where do I start looking. I used a Network Monitor but my MOC clients only do TURN and TCP protocols - no SIP/STUN.
Any clues?Monday, October 12, 2009 8:13 AM
Answers
-
First of all your naming of OCS roles in incorrect
1 Backend (this is your SQL)
1 Front-End (this is your pool)
1 EDGE Server (this is your DMZ server)
You can read this whitepaper on designing the OCS DMZ Server
http://www.microsoft.com/downloads/details.aspx?FamilyID=e4a8d703-e41a-47d9-b9dd-2799f894af92&DisplayLang=en
Are you using OCS 2007? or OCS 2007 R2?
OCS 2007 requires a public IP Address!
- Belgian Unified Communications Community : http://www.pro-exchange.be -- Marked as answer by Gavin-ZhangModerator Friday, October 23, 2009 8:35 AM
Monday, October 12, 2009 10:02 AM -
You can find some additional details on the communications process in this blog article:
http://www.shudnow.net/2009/08/29/office-communications-server-2007-r2-audiomedia-negotiation/
Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS- Marked as answer by Gavin-ZhangModerator Friday, October 23, 2009 8:35 AM
Monday, October 12, 2009 10:55 AMModerator
All replies
-
First of all your naming of OCS roles in incorrect
1 Backend (this is your SQL)
1 Front-End (this is your pool)
1 EDGE Server (this is your DMZ server)
You can read this whitepaper on designing the OCS DMZ Server
http://www.microsoft.com/downloads/details.aspx?FamilyID=e4a8d703-e41a-47d9-b9dd-2799f894af92&DisplayLang=en
Are you using OCS 2007? or OCS 2007 R2?
OCS 2007 requires a public IP Address!
- Belgian Unified Communications Community : http://www.pro-exchange.be -- Marked as answer by Gavin-ZhangModerator Friday, October 23, 2009 8:35 AM
Monday, October 12, 2009 10:02 AM -
Hi - thank you for the clarification.
We are running Windows 2003 R2 64bit, with OCS 2007 R2 (due to support for NAT). I got a hint to see about routing between the internal interface and external interface on the EDGE, but I cannot see how routing should be configured to solve this matter.
I will read the whitepaper as there maybe some solvements here, but we did follow the HMC deployment step by step, I do believe this is a strange matter.Monday, October 12, 2009 10:12 AM -
You can find some additional details on the communications process in this blog article:
http://www.shudnow.net/2009/08/29/office-communications-server-2007-r2-audiomedia-negotiation/
Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS- Marked as answer by Gavin-ZhangModerator Friday, October 23, 2009 8:35 AM
Monday, October 12, 2009 10:55 AMModerator -
Hi
Any update for your issue?
Regards!Monday, October 19, 2009 6:44 AMModerator