Hi ,
I am meeting a strange problem. I can not login OC server. The following is the log information.
While if I restart the machine of domain controler and oc server. Then everything will be OK. But mabye after one or two hour. I meet the same issue again.
I also notice that
1. If I let one user is online. And restart the oc server. When the server is restarted. The user will be automaticlly relogin successfully.
2. If I let one user is online. And wait for one night. And check again. The user is offline. And can not login. Need to restart both servers.
3. If I restart the both servers, I can login with all users. but after one or two hours. I sign out any one user, then i can not login the user again . But the other users are still online. And can send message each other.
Unavailable authorization authority causing errors.
There were 1 failures because the authority was unavailable in the last 0 minutes. The last one was this SIP message:
Instance-Id: 00000040
Direction: no-direction-info
Message-Type: request
Start-Line: REGISTER sip:oc.sm.com SIP/2.0
From: <sip:octester@oc.sm.com>;tag=3421451032;epid=666eacfd90
To: <sip:octester@oc.sm.com>
CSeq: 2 REGISTER
Call-ID: a2f7c8b7e9534cb7b13ff93461252299
Contact: <sip:16.173.232.125:1748;transport=tls;ms-opaque=ce5ca9ea79;ms-received-cid=300>;methods="INVITE, MESSAGE, INFO, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";+sip.instance="<urn:uuid:854A8E6C-BC74-5F05-A02E-5E7DB4C05BB4>"
Via: SIP/2.0/TLS 16.173.232.125:1748;ms-received-port=1748;ms-received-cid=300
Max-Forwards: 70
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Authorization: Kerberos qop="auth", realm="SIP Communications Service", targetname="sip/ocserver.oc.sm.com", gssapi-data="YIIEpwYJKoZIhvcSAQICAQBuggSWMIIEkqADAgEFoQMCAQ6iBwMFAAAAAACjggPBYYIDvTCCA7mgAwIBBaELGwlPQy5TTS5DT02iJDAioAMCAQKhGzAZGwNzaXAbEm9jc2VydmVyLm9jLnNtLmNvbaOCA30wggN5oAMCARehAwIBAqKCA2sEggNnzNyZWKdwlRuvj/6t1s4YfQpHN51WXIDWIV37viyxuBotFuurFI/1618cQGR33NNZSPkW+5WxeFoZuE31y2qFfeoJkQJs10PbsvSvuejoHPuDJ3ZNxf/NU2A1V+SLDn0Jr4UdLj4pdXR0gNcGN/yB2qWDqNigWvp3WEwzKxIn8KpGg+69l48ZoE4oWdofP9wVQRQbEBGV/dIs0WtAEH6+JSls/QhZCyxsLofumaaXeXSdvw+lO23FsujE8/co4pFzCaPzU+Cu0gqtn+MtlDWwh3Y1lK/WSw3L8GqeJUVyhBlPwYwkFom5rpDGLjOadeUtlmbDQ66J5xwosoz3DZTioMxVdtbmyO4WOwJOAohCEPgvMxOYbD16b7RgBU0DJlxlHR/9/GqqXxKX3ia4IIREAZQnLp6T53Yflev2yx/HZNSB4lWL7xmTJG7Cr2QQhOSb94wC/CNCq+bj4B9m/ClUmTzsZ8qLooZxTr0NFFS+dAKAjMwEy1OlFf8KESnMlI4E76J0KEbczzPLougcsoVAJowV8GnPnXDzRwtx1GtWKHfeODTYL/xGtCtemk8f/hlgk0W0NnkaZZWMXqtHgMG+8V/tDW+pw7YvAtqsGjigi3VhMQwwl89atZrO9qUfNhHilqItYmONc0bo1Qq/VKiery2KDU3eoxmDn4/1/SICKTKCy5jzHQ8OTLqSEIPOTdo/5GHVsPJ1zxio6IKLTBRXXfyWNQSyVRj+AY+bAg28a/gFWyBvSXCU38WRoBWp59VM2a5cpttUhBEtvqSeD1qg9W1D7doW8zW12dScrKwO/Zgzk4uTPErX66PTapuddiaLSpuCPmtkk7qhIKaHllFo4uRas9+PQoYZS/YJ1yUL/AZhT56N3j0eGhwImnGBq20yduiyv13zwKaCSjEg/sY9oWOclJPFyIsxaUQVO9YPS4m1hGFJ8fepKBTLpr8XW2anH+x1+Bwake9mNXVI8XQT3O0HwU5IMq3XW2vWDMPdCWVzIdWYuhE/oqrQEW8GDezfL1L+cEDNcba8oL6+LlP2FA60BLaQl0Gq4l7Vu5notFvFUmfYcZX4WTuiv/aPaMV9/aEMzWq3lMAQr/YAPqNBPDdSHUS+LWn63D/Cg5dYbOYWdE/F6QiF1zikAkv6bLS8flBjtIH6AaSBtzCBtKADAgEXooGsBIGp7Pjl7CxdO8BtJhyV/yCzPJ5ZHXvE4zczvM/Ccc8fnR5DbfRZSvTUSdWdSLhvE5+/Pv265m4Lz2/n+gbT2RXHa7CKSjakp/33bvEdWP7d3qcKJIFvKspxur8TSpWf3UI/hqWEPxGoMkjScVwIEYfIbOXzm45T8ESeD86mOIhAXSZlC6bSDxZ6eZa7PD1JiWCoZs1TGJmJGo2pPF60Gzwd1xJojcAo+zrVDA==", version=3
Supported: gruu-10, adhoclist, msrtc-event-categories
Supported: ms-forking
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Content-Length: 0
Cause: This could be because of problems with the local security provider or because of network connectivity issues to domain controllers.
Resolution:
Check DC/GC connectivity. If problem persists, restart the server.
The log in the validation tool provided by OCS.
Maximum hops: 2
Failed to register user: User sip:administrator@oc.sm.com @ Server
Failed registration response: [
SIP/2.0 503 Service unavailable
FROM: <sip:administrator@oc.sm.com>;epid=epid00;tag=72d37161
TO: <sip:administrator@oc.sm.com>;tag=F3CC60BFFD9AAE49AD967725C72C618B
CSEQ: 2 REGISTER
CALL-ID: 3a59aa48f1c841f98a7f10ff94be32d1
VIA: SIP/2.0/TLS 16.173.232.125:2069;branch=z9hG4bKfe75d0aa;ms-received-port=2069;ms-received-cid=500
CONTENT-LENGTH: 0
ms-diagnostics: 1;reason="Service Unavailable";source="ocserver.oc.sm.com";ErrorType="Server Could not contact the DC for authentication"
]
Suggested Resolution: Use the maximum hop count to determine the server that generated this error. For example, if the maximum hop value is 2, then it is likely that this error was generated by a server that is 1 (immediate target) or 2 hops away. If the target server supplied and the home server for the user are different check the trust relationship between them. If the target server is an access edge server then check whether the internal supported domain list contains the domain of this user. In addition, check the forest-level domain supported list and make sure the user domain is present. Finally, run the dbanalyze tool on the home server to check whether the user is homed and configured correctly.
