-
Office Communications Server 2007 R2, Clients Port List
Ocak 21st, 2010 Yorum yokComponent (Server role or client) Port
Protocol
Notes Front End Servers 5060/5061
TCP\MTLS
Used by Standard Edition Servers and Enterprise pools for all internal SIP communications between servers and between servers and Office Communicator Front End Servers 443
HTTPS
Communication from front-end servers to the Web farm FQDNs (the URLs used by Web Components) Front End Servers 444
HTTPS
Communication between the focus (Office Communications Server component that manages conference state) and the conferencing servers Front End Servers 80
TCP
Communication from front-end servers to the Web farm FQDNs (the URLs used by Web Components) when HTTPS is not used Front End Servers 135
DCOM and RPC
Used when a load balancer is deployed, port 135 is used by the Front End Servers for WMI operations and moving users (a remote DCOM-based database operation) Front End Servers 5062
TCP
Used for incoming SIP listening requests for IM conferencing Front End Servers 5063
TCP
Used for incoming SIP listening requests for A/V conferencing Front End Servers 5064
TCP
Used for incoming SIP listening requests for telephony conferencing Front End Servers 5065
TCP
Used for incoming SIP listening requests for application sharing Front End Servers 5071
TCP
Used for incoming SIP listening requests for Response Group Service Front End Servers 5072
TCP
Used for incoming SIP listening requests for Conferencing Auto Attendant Front End Servers 5073
TCP
Used for incoming SIP listening requests for Conferencing Announcement Server Front End Servers 5074
TCP
Used for incoming SIP listening requests for Outside Voice Control Front End Servers 8057
TLS
Used to listen to direct PSOM connections from Live Meeting client Front End Servers 8404
TLS
Used for internal server communications (remoting over MTLS) for Response Group Service Front End Servers 49152-65335
UDP
Used for media port range Load Balancer for Front End Servers 5060/5061
TCP
MTLS
Used by Standard Edition Servers and Enterprise pools for all internal SIP communications between servers and between servers and Office Communicator Load Balancer for Front End Servers 443
HTTPS
Communication from front-end servers to the Web farm FQDNs (the URLs used by Web Components) Load Balancer for Front End Servers 444
HTTPS
Communication between the focus (Office Communications Server component that manages conference state) and the conferencing servers Load Balancer for Front End Servers 135
DCOM and RPC
Used when a load balancer is deployed, port 135 is used by the Front End Servers for WMI operations and moving users (a remote DCOM-based database operation) Load Balancer for Front End Servers 5065
TCP
Used for incoming SIP listening requests for application sharing Load Balancer for Front End Servers 5069
TCP
Used for Monitoring Server Load Balancer for Front End Servers 5071
TCP
Used for incoming SIP listening requests for Response Group Service Load Balancer for Front End Servers 5072
TCP
Used for incoming SIP listening requests for Conferencing Auto Attendant Load Balancer for Front End Servers 5073
TCP
Used for incoming SIP listening requests for Conferencing Announcement Server Load Balancer for Front End Servers 5074
TCP
Used for incoming SIP listening requests for Outside Voice Control Communicator Web Access Server 80
HTTP
Used if HTTPS is not configured Communicator Web Access Server 88
Used for Kerberos authentication Communicator Web Access Server 137
Used for NetBios Name Service Communicator Web Access Server 138
Used for NetBios for Datagram Service Communicator Web Access Server 139
Used for NetBios for Session Service Communicator Web Access Server 389
Used for LDAP on the DC Communicator Web Access Server 443
HTTPS
HTTP over TLS or SSL Communicator Web Access Server 3268
Used for LDAP on the GC Communicator Web Access Server 5061
TCP/UDP
Used for SIP traffic Group Chat Server 49152-65335
Used for session ports (10 randomly chosen) Group Chat Server 443
HTTP
Group Chat Server 8010
Used for peer server synchronization/WCF ports for the Lookup Server Group Chat Server 8011
Used for peer server synchronization/WCF ports for the Channel Server Group Chat Server 5041
TCP
Used for listening port for channel service Group Chat Server 5061
TCP
Used to communicate to internal servers using SIP/TLS Monitoring Server 135
MSMQ
Monitoring Server 5069
Used when a Front End load balancer is used Archiving Server 135
MSMQ
Director 5060/5061
TCP
Used for internal communications between servers Load Balancer for Director 5060/5061
TCP
Used for internal communications between servers Mediation Server 60000-64000
TCP
Used for media port range Mediation Server 5061
TCP
Used for listening Mediation Server 5060
TCP
Used for gateway listening port and next hop Reverse Proxy 443
TCP
Used for SIP/TLS communications from external users on both the internal and external firewalls for external user access Edge Server 5061
TCP
Used for SIP/MTLS communication for remote user access or federation. Edge Server 5062
TCP
Used for SIP/MTLS authentication of A/V users. Communications flow outbound through the internal firewall. Edge Server 443
TCP
Used for SIP/TLS communication for remote user access, accessing internal Web conferences, and STUN/TCP inbound and outbound media communications for accessing internal media and A/V sessions Edge Server 8057
TCP
Used to listen for PSOM/MTLS communications from the Web Conferencing Server on the internal interface of the Web Conferencing Edge Server Edge Server 3478
UDP
Used for STUN/UDP inbound and outbound media communications Edge Server 50,000-59,999
RTP/TCP
Used for inbound and outbound media transfer through the external firewall. Load Balancer for Consolidated Edge Server 443
TCP
Used for internal ports for SIP/TLS communication for remote user access, accessing internal Web conferences, and STUN/TCP inbound and outbound media communications for accessing internal media and A/V sessions Load Balancer for Consolidated Edge Server 5061
TCP
Used for internal ports for SIP/MTLS communication for remote user access or federation Load Balancer for Consolidated Edge Server 5062
TCP
Used for internal ports for SIP/MTLS authentication of instant messaging communications flowing outbound through the internal firewall Load Balancer for Consolidated Edge Server 3478
UDP
Used for internal ports for STUN/UDP inbound and outbound media communications Load Balancer for Consolidated Edge Server 443
TCP
Used for external ports for SIP/TLS communication for remote user access, accessing internal Web conferences, and STUN/TCP inbound and outbound media communications for accessing internal media and A/V sessions Load Balancer for Consolidated Edge Server 5061
TCP
Used for external ports for SIP/MTLS communication for remote user access or federation Load Balancer for Consolidated Edge Server 3478
TCP
Used for external ports for STUN/UDP inbound and outbound media communications Office Communicator 5060
TCP (SIP)
Used by Office Communicator for SIP communications internally Office Communicator 5061
TCP (SIP)
Used by Office Communicator for SIP communications internally and for SIP/MTLS authentication of A/V users. Communications flow outbound through the internal firewall Office Communicator 443
TCP (HTTP)
Used by Communicator clients connecting from outside the intranet for SIP communications Office Communicator 1024-65535
UDP/TCP
Port range used for inbound and outbound media transfer through the external firewall. Office Communicator 6891-6901
TCP
Port ranged used by Office Communicator for file transfer. Live Meeting 2007 client 443
TCP
Used by Live Meeting 2007 clients connecting from outside the intranet for: SIP traffic sent to the Access Edge Server
PSOM traffic sent to the Web Conferencing Edge Server
Live Meeting 2007 client 8057
TCP
Used for outgoing PSOM traffic sent to the Web Conferencing Server Live Meeting 2007 client 5061
TCP
Used for SIP/TLS communication between Live Meeting and the Front End Servers or the Access Edge Server and for SIP/MTLS authentication of A/V users. Communications flow outbound through the internal firewall Live Meeting 2007 client 1024-65535
UDP/TCP
Port range used for inbound and outbound media transfer through the external firewall Live Meeting 2007 client 6891-6901
TCP
Port ranged used by Live Meeting for file transfer 2007 R2 version of Communicator Mobile 5060
TCP SIP)
Port ranged used by Communicator Mobile for SIP communications internally 2007 R2 version of Communicator Mobile 5061
TCP SIP)
Port ranged used by Communicator Mobile for SIP over TLS communications internally 2007 R2 version of Communicator Mobile 443
TCP (HTTP)
Used by Communicator Mobile for connecting from outside the intranet for SIP communications -
Office Communicator 2007 içerisinde bazı bilgilerin görüntülenmesini engellemek ve GalContacts.db dosyasını düzenlemek
Ekim 28th, 2009 Yorum yokOffice Communicator 2007 içerisinde genelde telefon vs. gibi bazı bilgilerin görüntülenmemesi sorun olabiliyor ama bu durumun birde tam tersini de düşünmek gerekir. Bazı şirketler Office Communicator 2007 tarafında her bilginin de görünüyor olmasından rahatsız olabilirler ve ayrıca network trafiği açısından düşünüldüğünde önemli bir konu olan client tarafında Office Communicator 2007 nin download ettiği GalContacts.db dosyasının da mümkün olduğu kadar küçük olmasını talep edebilmektedirler.
Bu gibi istekleri karşılamak için ise yine OCS 2007 Resource Kit araçlarından absconfig.exe dosyasını kullanabiliriz. Örnek olarak ben Home Phone bölümünün Office Communicator 2007 içinden görünmemesini istediğimi varsayarak gerekli işlemleri aşağıda açıklamaya çalıştım.
1- Öncelikle OCS 2007 Front End veya Standard Edition yüklü makineye OCS 2007 Resource Kit araçlarını aşağıdaki linkten download edip kuruyoruz.
OCS 2007 R2 Resource Kit Download
2- C:\Program Files\Microsoft Office Communications Server 2007\ResKit altındaki absconfig.exe dosyasını açıyoruz ve burada aşağıdaki ekrandaki gibi homePhone için Type of Attribute sütunundaki seçeneği None olarak işaretliyoruz.

3- Appy Changes ‘a basıp bir süre bekliyoruz ve aşağıdaki mesaj belirdiğinde OK ‘e basarak absconfig.exe ‘yi kapatıyoruz.
“UR regeneration process has been triggered – you may have to wait for 5 minutes for it to actually complete.You can check the event viewer entry for OCS User Replicator (Event ID: 30024) to verify that UR synchronization completed. You can then force sync the ABS files for the new settings by running abserver.exe -syncNow from the ABS install directory or the setting will take affect during the scheduled ABS sync time.”
Daha sonra event log içerisinde aşağıdaki event ‘in düşmesini bekliyoruz.
Type: Information
Event id: 30028
Category: (1009)
Source: OCS User Replicator4- C:\Program Files\Microsoft Office Communications Server 2007\Server\Core altındaki abserver.exe ‘yi kullanarak komut satırında “abserver -syncNow” (tırnak işaretsiz) komutunu çalıştırıyoruz ve event viewer da aşağıdaki event ‘i görmek için bir süre bekliyoruz.
Type: Information
Event id: 21004
Category: (1008)
Source: OCS Address Book Server5- Yaptığımız işlemlerin hemen etkisini görmek için bir client makinede Office Communicator 2007 ‘dan sign-out olup kapatıyoruz (Exit), daha sonra C:\Documents and Settings\<UserName>\Local Settings\Application Data\Microsoft\Communicator (eğer işletim sistemi Windows Vista ve Windows Server 2008 ise C:\Users\<UserName>\AppData\Local\Microsoft\Communicator) altındaki tüm dosyaları siliyoruz ve Office Communicator 2007 ile yeniden Office Communicator 2007 yi başlatıp sign-in oluyoruz ve Title bölümünün kullanıcılarda görünüp görünmediğini ve GalContacts.db dosyasının küçülüp küçülmediğini kontrol ediyoruz, tabiki çok az sayıda kullanıcı bulunan bir domain içerisinde bu dosyanın çok fazla küçülmeyeceğini de unutmamalıyız.
Not : Hızlı bir test ile sonuçları görmek için kesinlikle Office Communicator 2007 uygulamasını kapatıp yeniden başlatmamız gerekiyor, sadece sign-out ve sign-in bu durumda yeterli olmuyor.


