Hi Jamie,
The following is the info:
IP address of OCS: 172.20.10.40 (Internal FQDN: ocs2007.corp.company.local)
The below is the info of my EDGE configuration:
IP address of Edge: External: 172.20.10.41 Internal: 172.20.10.42
External Interface Settings:
Access: 172.20.10.41 DNS Name:edge.company.com Port: 5061 (federation) , 443 (Remote)
Web Conferencing: 172.20.10.41 DNS Name:edge.company.com Port: 444
Certificates:
INT: SN: edgeint.corp.company.local
SAN: edge.corp.company.local
SAN: edgeint.corp.company.local
SAN: edgeint
EXT: SN: edge.company.com
SAN: sip.company.com
SAN: edge.company.com
SAN: edge
On the Cisco ASA 5510, we have opened port 443, 444, 5061, 5062.
we have published edge.company.com for DNS entries.
for the client side, according to the even viewer, it's trying to resolve the interal fqdn (ocs2007.corp.company.local) (I put down both internal fqdn and external fqdn in the configuration) and these settings works fine for the office communicator externally and internally. However, i don't see any error message in the event viewer if I put the edge.company.com as both internal and external fqdn but it still doesn't let me join the meeting externally.
on the edge server, in the event log, the most recent errors i found are : (but these have different time stamps, like couple hours earlier)
1. ocs applications module: office communciation server start up is pending.
some configured critical applcations have not yet registered.
resolution: For script only applications ensure that the application is available in the path specified in the MMC, and that no errors are reported by the Office Communications Server Script-Only Applications Service. For non-script only critical applications ensure that they are configured to register on server startup.
2. ocs protocol stack:
Unable to set the Access Edge Server internal DNS name.
DNS name: 'edge.corp.company.local'.
Cause: A DNS name is already set.
Resolution:
Please restart the service in order to apply this change.
3. ocs web conferencing edge server:
Failed to process data received from the client
Over the past 0 minutes Office Communications Server has disconnected clients 1 time(s) as a result of invalid data being received on client connections. The last such client which was disconnected is "75.101.17.64:1203".
Cause: Failed to process data received from the client
Resolution:
Check and make sure that the connection came from a trustworthy client.
On the OCS2007:
At least one attempt to reference stale (non-existent or deleted) security association was detected.
There were 1 messages with signature that referenced stale (non-existent or deleted) security association in the last 0 minutes. The last one was this SIP message:
Instance-Id: 000005E6
Direction: no-direction-info
Source: edgeint.corp.company.local
Message-Type: request
Start-Line: SERVICE sip:bwong@company.com;gruu;opaque=app:conf:focusfactory SIP/2.0
From: <sip:bwong@company.com>;tag=a0e1f229b6;epid=9c1304db48
To: <sip:bwong@company.com;gruu;opaque=app:conf:focusfactory>
CSeq: 1 SERVICE
Call-ID: 75e6231ef617473a8c8fe1da65ce5b6d
Via: SIP/2.0/TLS 10.20.100.42:1826;branch=z9hG4bK73CA7B2F.5644ABE3;branched=FALSE;ms-received-port=1826;ms-received-cid=1200
Record-Route: <sip:edgeint.corp.company.local:1826;transport=tls;maddr=10.20.100.42;lr>;tag=F9BCAE7198D87FD337E8EE25BBA3EA52
Max-Forwards: 69
ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=edgeint.corp.company.local;ms-source-verified-user=verified
Contact: <sip:bwong@company.com:1956;maddr=65.175.48.186;transport=tls;ms-received-cid=3F00>;+sip.instance="<urn:uuid:A6AE7A60-22A0-5FA2-81A8-DE5C9E0D89E2>"
Via: SIP/2.0/TLS 172.20.10.138:1470;received=65.175.48.186;ms-received-port=1956;ms-received-cid=3F00
User-Agent: UCCP/2.0.6362.91
Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="DE6D23F8", targetname="ocs2007.corp.company.local", crand="20332509", cnum="6", response="0100000043005000fb6d66edaf040329"
Content-Type: application/cccp+xml
Content-Length: 2274
Cause: This could be due to users that utilize large number of devices (in excess of configured maximum), or due to connection refresh logic re-balancing remote users to a different director in a bank or a pool, or it could be due to an attacker.
Resolution:
None needed unless the failure count is high (>100). Check if number of allowed devices per user is too low for existing usage scenarios. Check your network for any rogue clients. Restart the server if problem persists.
That's all I have found so far.......
Any thoughts or advice ?
Jamie, thanks you in advance. I am really appreciated.
-Desmond
