locked
OCS IM Multiparty Error RRS feed

  • Question

  •  

    Hi all,

     

    i have a strange problem when i am trying to make a multiparty IM Session.

    I have a mixed environment with one LCS and one OCS server, but i don't know if this matters in this case.

    All the users which i try to invite to the multiparty IM session are on the ocs pool.

     

    I can also communicate with each of this users seperate in a peer to peer session.

    But i try to invite a third user i get the error 504 in ocs client.

    In the application event log i get:

     

    A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f8). More information is contained in the following technical data:
     
    RequestUri:   sip:First.Last@domain.at;gruu;opaque=app:conf:chat:id:40AC85885D8B0B4EADEDCCCEEA24F8FA
    From:         sip:First.Last@domain.at;tag=f26f7f8576
    To:           sip:First.Last@domain.at;gruu;opaque=app:conf:chat:id:40AC85885D8B0B4EADEDCCCEEA24F8FA;tag=6B23A6EC0407A2BB9D9D6F0B06B5AD44
    Call-ID:      29f1ece5c0434c96959f43e3c6b3f0d2
    Content-type: application/sdp;call-type=im

    v=0
    o=- 0 0 IN IP4 9.1.4.107
    s=session
    c=IN IP4 9.1.4.107
    t=0 0
    m=message 5060 sip null
    a=accept-types:text/rtf application/x-ms-ink image/gif multipart/alternative application/ms-imdn+xml


    Response Data:

    504  Server time-out
    ms-diagnostics:  1007;reason="Temporarily cannot route";source="ocsserver.domain.local.at";ErrorType="Connect Attempt Failure";WinsockFailureDescription="The peer actively refused the connection attempt";WinsockFailureCode="274D(WSAECONNREFUSED)";Peer="ocsserver.domain.local.at"

     

    Thank you for helping

    Kind regards

    Harry

    Friday, August 22, 2008 10:09 AM

Answers

  • Problem was with frond end OCS 2007 server IM conferencing IP address option. The Server has two IP Addresses, because in a mixed environment with LCS 2005, the Pool Name and the Hostname from OCS Server can not be resolvable to the same ip address. As soon as i but the IM conferncing option to listen an ALL ip addresses (Port 5062) the error gone away.

    Monday, August 25, 2008 6:00 AM