Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Problem with connection by Live Meetung Client... RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Helllo... I have some problem with Live Meeting Client on OCS 2007 Enterprise...

    When I push "Meet now" button on client i see error message "Couldn't connect to meeting"...
    At pwconsole-debug.log I see messages like this:

     Drinks [X-PSOM] Closing the IN channel: source=LS;reconnect=0;reason=conference doesn't exist (bug/race)

    and connection closes.

    I validate WebConferencing server and all is ok... I don't understand why I can't create meeting...

    Any help please...
    Monday, June 23, 2008 8:01 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you configure Meeting policies?

    In Global Settings - Meetings

     

    Monday, June 23, 2008 10:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes all is right... I've enabled Video Conferencing and IP Audio and Video...

    So after a few hours of thinking I've discovered two things:
    1. At Web-Components server I found all my meetings at IIS web folder \\Etc\Place\Null\FileTree
    2. At Front-End Server's Event log I recieve error message:

    A Create Conference request sent to an Mcu was rejected. It will be retried but if this error continues to occur conferencing functionality will be affected.

    Mcu: https://XXXXXXXXXXXXX:444/liveserver/datamcu/ Conference: sip:XXXXXXXXXXXXXX;gruu;opaque=app:conf:focus:id:4A08B2713F1F4148A30D8B8C472BBD20 Error: otherFailure
    Resolution:
    Ensure that the Mcu is functioning correctly.

    At one conference I read that reactivation of Web Conferencing may help but it doesn't...

    So... Any ideas...
    Tuesday, June 24, 2008 5:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Make sure that there is no Firewall in between or on the OCS Server

    Make sure that your proxy settings are not blocking the URLS for OCS (Disable the proxy server settings to test)

     

    Tuesday, June 24, 2008 9:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey... There is only one problem and i resolve it... Just there is no permissions to folder MEETING-METADATA.. I discovered this with logging tool.. Really good thing.. I add RTCComponentUniversalServices with Modify permissions and RTCUniversalGuestAccessGroup with read permissions. Thank you for your help. =))
    Friday, June 27, 2008 1:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi panorik,

    I also have the same problem and cannot find the "MEETING-METADATA" folder? What kind of logging tool did you use?
    My problem is that I am able schedule a meeting and no one can join the meeting. The error message shown is as below...

    "    A Create Conference request sent to an Mcu was rejected. It will be retried but if this error continues to occur conferencing functionality will be affected.

    Mcu: https://xxx.xxx.com:444/liveserver/acpmcu/ Conference: sip:xxx@xxx.com;gruu;opaque=app:conf:focus:id:F1V8651QBJ6XZ9JZP5NCJM1NIE6K3MUU Error: otherFailure
    Resolution:
    Ensure that the Mcu is functioning correctly."

    Can someone help me here? What am I missing?

    thanks in advance,
    Camy72
    Tuesday, October 14, 2008 12:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I tried changing the permissions to "meeting" folder and everything looks good, but still no luck. The funny thing is that it works sometime and fails majority of times.

    The host of the meeting is able to login/join the meeting, but not the attendees/invitees.
    I get the same error shown above...

    Any clues?

    Camy72
    Tuesday, October 14, 2008 4:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The logging tool he is referring to is pobably the Debug Logging Tool included in OCS

    Right click your pool and select logging tool and then New Debug Session

    Select S4 and Sipstack and start the trace (you can also filter per URI)

    Then Analyze the output with the snooper tool (OCS Resource Kit) and look for errors

     

    Tuesday, October 14, 2008 3:21 PM