locked
Чем больше изучаю тем больше проблем :) RRS feed

  • Вопрос

  • Проблему с сообщениями решил

    но фаилы я не могу отправлять Sad

    вот что пишет:

     Waiting for user1 to accept the file "Текстовый документ.txt" (1 Kb, less than 1 minute with a 28.8 modem). Please wait for a response or Cancel (Alt+Q) the file transfer.

     

     The following message could not be delivered to all recipients:

    The invitation to user1 to send file "H:\Текстовый документ.txt" could not be sent.

     

    Вопрос: Как это жело исправить? есть предложения?

    7 августа 2007 г. 15:39

Ответы

  • Разобрался

    Проблему надо капать в mmc: Microsoft Office Live Communication Server 2005 -> Forest -> Domains -> (Имя домена) -> Live Communicztions server and pools -> (Пул) -> (Сервер) -> Applications

    Правой кнопкой -> Свойства

    14 августа 2007 г. 13:48

Все ответы

  • Вот он мне чем ругается Sad

    Кто в этом что понимает??

     

    Code Snippet

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:26
    Direction: Incoming
    Peer: 10.5.0.11:2925
    Message-Type: Request
    Start-Line: INVITE sip:user1@mifp-lcs.net SIP/2.0
    To:  <sip:user1@mifp-lcs.net>
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID:  6bb06ba1824140928dabab066f155498
    CSeq: 1 INVITE
    Contact:  <sip:psokolov@mifp-lcs.net:13129;maddr=10.5.0.11;transport=tcp>;proxy=replace
    Via:  SIP/2.0/TCP 10.5.0.11:13129
    Max-Forwards:  70
    Content-Length:  115
    Content-Type:  application/sdp
    Other-Headers: User-Agent:  RTC/1.3
    Other-Headers: Roster-Manager:  sip:psokolov@mifp-lcs.net
    Other-Headers: EndPoints:  "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>, <sip:user1@mifp-lcs.net>
    Other-Headers: Supported:  com.microsoft.rtc-multiparty
    Other-Headers: Proxy-Authorization:  NTLM qop="auth", realm="SIP Communications Service", opaque="865815BF", crand="66706b68", cnum="7", targetname="sem-lcs.mifp-lcs.net", response="01000000316230322d9029aa6071392d"
    Message-Body:
    v=0
    o=- 0 0 IN IP4 10.5.0.11
    s=session
    c=IN IP4 10.5.0.11
    t=0 0
    m=message 5060 sip sip:psokolov@mifp-lcs.net
    $$end_record

    $$begin_record
    LogType: diagnostic
    Date: 2007/08/08 15:22:26
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 100 Trying
    SIP-Call-ID: 6bb06ba1824140928dabab066f155498
    SIP-CSeq: 1 INVITE
    Peer: 10.5.0.11:2925
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:26
    Direction: Outgoing
    Origin: Local
    Peer: 10.5.0.11:2925
    Message-Type: Response
    Start-Line: SIP/2.0 100 Trying
    To: <sip:user1@mifp-lcs.net>
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID: 6bb06ba1824140928dabab066f155498
    CSeq: 1 INVITE
    Via: SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Content-Length: 0
    Other-Headers: Authentication-Info: NTLM rspauth="01000000000000002660047E6071392D", srand="5CEBFFCC", snum="9", opaque="865815BF", qop="auth", targetname="sem-lcs.mifp-lcs.net", realm="SIP Communications Service"
    $$end_record

    $$begin_record
    LogType: diagnostic
    Date: 2007/08/08 15:22:26
    Severity: information
    Text: Routed a request on behalf of APIEM
    SIP-Start-Line: INVITE sip:10.5.0.10:2651;transport=tcp;ms-received-cid=400 SIP/2.0
    SIP-Call-ID: 6bb06ba1824140928dabab066f155498
    SIP-CSeq: 1 INVITE
    Peer: 10.5.0.10:2651
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:26
    Direction: Outgoing
    Peer: 10.5.0.10:2651
    Message-Type: Request
    Start-Line: INVITE sip:10.5.0.10:2651;transport=tcp;ms-received-cid=400 SIP/2.0
    To: <sip:user1@mifp-lcs.net>;epid=d2e2fe6451
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID: 6bb06ba1824140928dabab066f155498
    CSeq: 1 INVITE
    Contact: <sip:psokolov@mifp-lcs.net:2925;maddr=10.5.0.11;transport=tcp;ms-received-cid=200>
    Via: SIP/2.0/TCP 10.5.0.11;branch=z9hG4bK64903FBB.B4EFB3D6;branched=FALSE;ms-internal-info="aayv-yXnEStDVyxJWiHrb9PNqaCpUA"
    Via: SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Max-Forwards: 69
    Content-Length: 115
    Content-Type: application/sdp
    Other-Headers: Authentication-Info: NTLM rspauth="010000002D6C637350BED64FC4C9EDBB", srand="C535AA39", snum="8", opaque="3C428A76", qop="auth", targetname="sem-lcs.mifp-lcs.net", realm="SIP Communications Service"
    Other-Headers: Record-Route: <sip:pool01.mifp-lcs.net;transport=tcp;ms-fe=sem-lcs.mifp-lcs.net;lr;ms-route-sig=aavysmfPeq1cjYOMHcpQQPiFx6UzgA>;tag=209AAC767C70039085AE322C1538DCB5
    Other-Headers: User-Agent: RTC/1.3
    Other-Headers: Roster-Manager: sip:psokolov@mifp-lcs.net
    Other-Headers: EndPoints: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>, <sip:user1@mifp-lcs.net>
    Other-Headers: Supported: com.microsoft.rtc-multiparty
    Message-Body:
    v=0
    o=- 0 0 IN IP4 10.5.0.11
    s=session
    c=IN IP4 10.5.0.11
    t=0 0
    m=message 5060 sip sip:psokolov@mifp-lcs.net
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:26
    Direction: Incoming
    Peer: 10.5.0.10:2651
    Message-Type: Response
    Start-Line: SIP/2.0 100 Trying
    To: <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From:  "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID:  6bb06ba1824140928dabab066f155498
    CSeq: 1 INVITE
    Via:  SIP/2.0/TCP 10.5.0.11;branch=z9hG4bK64903FBB.B4EFB3D6;branched=FALSE;ms-internal-info="aayv-yXnEStDVyxJWiHrb9PNqaCpUA"
    Via:  SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Content-Length:  0
    Other-Headers: User-Agent:  RTC/1.3
    Other-Headers: Proxy-Authorization:  NTLM qop="auth", realm="SIP Communications Service", opaque="3C428A76", crand="2c9b1b7a", cnum="7", targetname="sem-lcs.mifp-lcs.net", response="01000000316230328f55f170c4c9edbb"
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:27
    Direction: Incoming
    Peer: 10.5.0.10:2651
    Message-Type: Response
    Start-Line: SIP/2.0 200 OK
    To: <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From:  "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID:  6bb06ba1824140928dabab066f155498
    CSeq: 1 INVITE
    Contact:  <sip:user1@mifp-lcs.net:7087;maddr=10.5.0.10;transport=tcp>;proxy=replace
    Via:  SIP/2.0/TCP 10.5.0.11;branch=z9hG4bK64903FBB.B4EFB3D6;branched=FALSE;ms-internal-info="aayv-yXnEStDVyxJWiHrb9PNqaCpUA"
    Via:  SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Record-Route:  <sip:pool01.mifp-lcs.net;transport=tcp;ms-fe=sem-lcs.mifp-lcs.net;lr;ms-route-sig=aavysmfPeq1cjYOMHcpQQPiFx6UzgA>;tag=209AAC767C70039085AE322C1538DCB5
    Content-Length:  112
    Content-Type:  application/sdp
    Other-Headers: User-Agent:  RTC/1.3
    Other-Headers: Supported:  com.microsoft.rtc-multiparty
    Other-Headers: Proxy-Authorization:  NTLM qop="auth", realm="SIP Communications Service", opaque="3C428A76", crand="46d1eb42", cnum="8", targetname="sem-lcs.mifp-lcs.net", response="010000003162303209086852c4c9edbb"
    Message-Body:
    v=0
    o=- 0 0 IN IP4 10.5.0.10
    s=session
    c=IN IP4 10.5.0.10
    t=0 0
    m=message 5060 sip sip:user1@mifp-lcs.net
    $$end_record

    $$begin_record
    LogType: diagnostic
    Date: 2007/08/08 15:22:27
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 6bb06ba1824140928dabab066f155498
    SIP-CSeq: 1 INVITE
    Peer: 10.5.0.11:2925
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:27
    Direction: Outgoing
    Peer: 10.5.0.11:2925
    Message-Type: Response
    Start-Line: SIP/2.0 200 OK
    To: <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID: 6bb06ba1824140928dabab066f155498
    CSeq: 1 INVITE
    Contact: <sip:user1@mifp-lcs.net:2651;maddr=10.5.0.10;transport=tcp;ms-received-cid=400>
    Via: SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Record-Route: <sip:pool01.mifp-lcs.net;transport=tcp;ms-fe=sem-lcs.mifp-lcs.net;lr;ms-route-sig=aab05pnr2EwIizbbvR8p1tbFx6UzgN>
    Content-Length: 112
    Content-Type: application/sdp
    Other-Headers: Authentication-Info: NTLM rspauth="0100000000000000049365A76071392D", srand="E8B3563E", snum="10", opaque="865815BF", qop="auth", targetname="sem-lcs.mifp-lcs.net", realm="SIP Communications Service"
    Other-Headers: User-Agent: RTC/1.3
    Other-Headers: Supported: com.microsoft.rtc-multiparty
    Message-Body:
    v=0
    o=- 0 0 IN IP4 10.5.0.10
    s=session
    c=IN IP4 10.5.0.10
    t=0 0
    m=message 5060 sip sip:user1@mifp-lcs.net
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:27
    Direction: Incoming
    Peer: 10.5.0.11:2925
    Message-Type: Request
    Start-Line: ACK sip:pool01.mifp-lcs.net;transport=tcp;ms-fe=sem-lcs.mifp-lcs.net;lr;ms-route-sig=aab05pnr2EwIizbbvR8p1tbFx6UzgN SIP/2.0
    To:  <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID:  6bb06ba1824140928dabab066f155498
    CSeq: 1 ACK
    Via:  SIP/2.0/TCP 10.5.0.11:13129
    Route:  <sip:user1@mifp-lcs.net:2651;maddr=10.5.0.10;transport=tcp;ms-received-cid=400>
    Max-Forwards:  70
    Content-Length:  0
    Other-Headers: User-Agent:  RTC/1.3
    Other-Headers: Proxy-Authorization:  NTLM qop="auth", realm="SIP Communications Service", opaque="865815BF", crand="3ab7c543", cnum="8", targetname="sem-lcs.mifp-lcs.net", response="0100000031623032a484626e6071392d"
    $$end_record

    $$begin_record
    LogType: diagnostic
    Date: 2007/08/08 15:22:27
    Severity: information
    Text: Routed a request using signed route headers
    SIP-Start-Line: ACK sip:user1@mifp-lcs.net:2651;maddr=10.5.0.10;transport=tcp;ms-received-cid=400 SIP/2.0
    SIP-Call-ID: 6bb06ba1824140928dabab066f155498
    SIP-CSeq: 1 ACK
    Peer: 10.5.0.10:2651
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:27
    Direction: Outgoing
    Peer: 10.5.0.10:2651
    Message-Type: Request
    Start-Line: ACK sip:user1@mifp-lcs.net:2651;maddr=10.5.0.10;transport=tcp;ms-received-cid=400 SIP/2.0
    To: <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID: 6bb06ba1824140928dabab066f155498
    CSeq: 1 ACK
    Via: SIP/2.0/TCP 10.5.0.11;branch=z9hG4bK226DB55F.D6BC6CB9;branched=FALSE
    Via:  SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Max-Forwards: 70
    Content-Length:  0
    Other-Headers: Authentication-Info: NTLM rspauth="01000000000000005D1C1D3DC4C9EDBB", srand="992BA4A1", snum="9", opaque="3C428A76", qop="auth", targetname="sem-lcs.mifp-lcs.net", realm="SIP Communications Service"
    Other-Headers: User-Agent:  RTC/1.3
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:27
    Direction: Incoming
    Peer: 10.5.0.11:2925
    Message-Type: Request
    Start-Line: MESSAGE sip:pool01.mifp-lcs.net;transport=tcp;ms-fe=sem-lcs.mifp-lcs.net;lr;ms-route-sig=aab05pnr2EwIizbbvR8p1tbFx6UzgN SIP/2.0
    To:  <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID:  6bb06ba1824140928dabab066f155498
    CSeq: 2 MESSAGE
    Contact:  <sip:psokolov@mifp-lcs.net:13129;maddr=10.5.0.11;transport=tcp>;proxy=replace
    Via:  SIP/2.0/TCP 10.5.0.11:13129
    Route:  <sip:user1@mifp-lcs.net:2651;maddr=10.5.0.10;transport=tcp;ms-received-cid=400>
    Max-Forwards:  70
    Content-Length:  211
    Content-Type:  text/x-msmsgsinvite; charset=UTF-8
    Other-Headers: User-Agent:  RTC/1.3
    Other-Headers: Proxy-Authorization:  NTLM qop="auth", realm="SIP Communications Service", opaque="865815BF", crand="07d6af09", cnum="9", targetname="sem-lcs.mifp-lcs.net", response="0100000031623032962a922c6071392d"
    $$end_record

    $$begin_record
    LogType: diagnostic
    Date: 2007/08/08 15:22:27
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 606 Not acceptable
    SIP-Call-ID: 6bb06ba1824140928dabab066f155498
    SIP-CSeq: 2 MESSAGE
    Peer: 10.5.0.11:2925
    $$end_record

    $$begin_record
    LogType: protocol
    Date: 2007/08/08 15:22:27
    Direction: Outgoing
    Origin: Local
    Peer: 10.5.0.11:2925
    Message-Type: Response
    Start-Line: SIP/2.0 606 Not acceptable
    To: <sip:user1@mifp-lcs.net>;epid=d2e2fe6451;tag=2d5bf577552d44a8a425652a3fcd3414
    From: "Пётр А. Соколов" <sip:psokolov@mifp-lcs.net>;tag=450c1b023cb34aed89c82dfcb6c10862;epid=bcc77e98c3
    Call-ID: 6bb06ba1824140928dabab066f155498
    CSeq: 2 MESSAGE
    Via: SIP/2.0/TCP 10.5.0.11:13129;ms-received-port=2925;ms-received-cid=200
    Content-Length: 0
    Other-Headers: Authentication-Info: NTLM rspauth="010000003F270D00156E76376071392D", srand="3CCA99EE", snum="11", opaque="865815BF", qop="auth", targetname="sem-lcs.mifp-lcs.net", realm="SIP Communications Service"
    Other-Headers: ms-diagnostic-info: 209AAC767C70039085AE322C1538DCB5
    Other-Headers: Warning: 309 lcs.microsoft.com "Message contents not allowed by policy"
    $$end_record

     

     

    8 августа 2007 г. 15:34
  • Разобрался

    Проблему надо капать в mmc: Microsoft Office Live Communication Server 2005 -> Forest -> Domains -> (Имя домена) -> Live Communicztions server and pools -> (Пул) -> (Сервер) -> Applications

    Правой кнопкой -> Свойства

    14 августа 2007 г. 13:48