Joining a tel conference in R2 from pstn just disconects the call RRS feed

  • Question

  • Hi

    So i create a live meeting or tel conference from my outlook.
    And if i just use communicator and livemeeting as clients everything works just fine.

    But if i try to join from pstn the lovely lady just says that she cant connect to my conference right now and that i should try later.
    No difference if i authenticate or not...

    The log file on the mediation server shows nothing red and says everything is fine in the vallidation.

    But the logfile on OCSR2 front end server says this

    TL_INFO(TF_PROTOCOL) [1]1414.1534::07/14/2009-13:38:12.292.0000ffd0 (UserServices,HttpInterface::TraceMessage:HttpTransport.cpp(656))$$$$START-MESSAGE$$$$

    TraceSeqNum: 294 Incoming Message { Unknown => Local }

    <?xml version="1.0" encoding="utf-8"?>

    <response xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" requestId="278411"

    C3PVersion="1" from="https://ocsr2.demosthlm02.local:444/liveserver/avmcu/" to="https://OCSR2.demosthlm02.local:444/LiveServer/Focus" code="failure" xmlns="urn:ietf:params:xml:ns:cccp">

    <addUser reason="otherFailure">

    <diagnostics-info xmlns="http://schemas.microsoft.com/rtc/2005/08/cccpextensions" />

    <conferenceKeys confEntity="sip:Tommy.Clarke@demo.atea.com;gruu;opaque=app:conf:focus:id:3814A82809A34ED0958CFDB60957BDF" />

    <user entity="sip:Mathias.Huber@demo.atea.com" xmlns="urn:ietf:params:xml:ns:conference-info">

    <display-text>Mathias Huber</display-text>




    <endpoint p6:endpoint-uri="sip:OCSR2MED.demosthlm02.local@demo.atea.com;gruu;opaque=srvr:MediationServer:XBjgnih8aUukTq_BS6r28gAA;grid=840d4e91321f485a9cba66d426208021" entity="{5d649f80-81bc-424a-a72c-240e5a1d43b0}" p6:session-type="audio-video" xmlns:p6="http://schemas.microsoft.com/rtc/2005/08/confinfoextensions">






    <media id="1">











    <separator xmlns="urn:ietf:params:xml:ns:conference-info-separator" />




    <info xmlns="http://schemas.microsoft.com/rtc/2005/08/cccpextensions" />

    <connection-info xmlns="http://schemas.microsoft.com/rtc/2005/08/cccpextensions">















    Tuesday, July 14, 2009 1:48 PM

All replies

  • Tuesday, July 14, 2009 1:59 PM
  • Tommy.

    It's a long-shot but take a look at this article: http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=69; it could be a certificate related issue.

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Tuesday, July 14, 2009 2:26 PM
  • Thanks for your replys.
    Iwe checked the certificate and it looks abit strange so it might be that, BUT the strange thing is that it works like the first time after a restart of the server, and then it stops working again but it only works for the first one to call in....

    The policy looks correct so it should not be that..

    Wednesday, July 15, 2009 12:22 PM
  • How are you connected? what type of PBX, and Gateway do you have?.

    Have you tested 3 way conferencing with moc, PSTN, moc?

    and have you tested 3 way conferencing with MOC, PSTN, PSTN?

    Based on the fact you can get in right after a reboot sounds a little odd, and also makes me thing of Anti-virus or Firewall type problems.
    Wednesday, July 15, 2009 12:43 PM
  • Tommy,

    That behavior is EXACTLY the same as what I saw as well in a recent deployment.  Double-check that the signing algorithm is not using MD5 or SHA2 but is using SHA1 on your certificate.

    I also noticed that users connecting directly from OCS (using the link in an email invite from a scheduled confrerence) could join conferences but anyone dialing using the CA number would fail to join.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, July 15, 2009 1:42 PM