locked
dialing into conferencing - "sorry I can't find a meeting with that number" but yet the user has that ID assigned RRS feed

  • Question

  • via my dial in website 24494 is assigned to the user, but when you try to call it I get  "sorry I can't find a meeting with that number".  I know I can reset the ID and it will work but this is the 3rd user that has had this problem. 

    When I do a debug it shows:

    TL_INFO(TF_PROTOCOL) [2]15F8.1B60::01/24/2013-22:26:51.788.000900a4 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2387.idx(196))[960327338] $$begin_record
    Trace-Correlation-Id: 960327338
    Instance-Id: 8FB48
    Direction: outgoing;source="local"
    Peer: pool:62367
    Message-Type: response
    SIP/2.0 400 pstnMeetingIdNotFound
    Start-Line: SIP/2.0 400 pstnMeetingIdNotFound
    FROM: <sip:RtcApplication-67758190-5c3b-4f6c-b236-a14357c5f097@.com:5072;transport=Tls;ms-opaque=84495afe39ba64b7>;epid=405FA20A16;tag=f310578fdf
    To: <sip:pool@.com;gruu;opaque=srvr:HomeServer:E1afnHoe-VCvSgUhA7OT6gAA>;tag=2711C94508D01F9EE8A863D02A51E2CC
    CALL-ID: 2cfd68ae1e4449d99f9a9b1bb67f710f
    CSEQ: 541 SERVICE
    Via: SIP/2.0/TLS 192.168.205.70:62367;branch=z9hG4bKd82c74c;ms-received-port=62367;ms-received-cid=9C5F00
    Content-Length: 379
    Content-Type: application/cccp+xml
    ms-diagnostics: 3174;reason="An authoritative conference directory was found, but the given id is not currently assigned.";meeting-id="24494";source="LYAPP"
    Message-Body: <response xmlns="urn:ietf:params:xml:ns:cccp" requestId="7" C3PVersion="1" from="sip:pool@.com;gruu;opaque=srvr:HomeServer:E1afnHoe-VCvSgUhA7OT6gAA" to="sip:RtcApplication-67758190-5c3b-4f6c-b236-a14357c5f097@com:5072;transport=Tls;ms-opaque=84495afe39ba64b7" code="failure">\n<resolveConference reason="pstnMeetingIdNotFound"/>\n</response>
    $$end_record

    Thursday, January 24, 2013 11:11 PM

Answers

  • Try to create a new meeting ID through the https://dialin.contoso.com for this user

    regards Holger Technical Specialist UC


    • Edited by Holger Bunkradt Saturday, January 26, 2013 10:11 AM
    • Proposed as answer by Lisa.zheng Monday, February 4, 2013 10:36 AM
    • Marked as answer by Lisa.zheng Tuesday, February 5, 2013 2:20 AM
    Saturday, January 26, 2013 10:10 AM
  • Did you do the migration? If so, you have to renew the conference ID.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Lisa.zheng Monday, February 4, 2013 10:36 AM
    • Marked as answer by Lisa.zheng Tuesday, February 5, 2013 2:20 AM
    Sunday, January 27, 2013 11:39 AM
  • The problem ended up being the order of the certs from the front end server.  The FQDN has to be first in the cert order, since my domain is on a .local, I had dialin, meet ect on a .com, and the .local was not first.  I reorder the cert and it's all good.
    • Marked as answer by JJHaaga Thursday, February 7, 2013 6:03 PM
    Thursday, February 7, 2013 6:03 PM

All replies

  • Try to create a new meeting ID through the https://dialin.contoso.com for this user

    regards Holger Technical Specialist UC


    • Edited by Holger Bunkradt Saturday, January 26, 2013 10:11 AM
    • Proposed as answer by Lisa.zheng Monday, February 4, 2013 10:36 AM
    • Marked as answer by Lisa.zheng Tuesday, February 5, 2013 2:20 AM
    Saturday, January 26, 2013 10:10 AM
  • Did you do the migration? If so, you have to renew the conference ID.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Lisa.zheng Monday, February 4, 2013 10:36 AM
    • Marked as answer by Lisa.zheng Tuesday, February 5, 2013 2:20 AM
    Sunday, January 27, 2013 11:39 AM
  • The problem ended up being the order of the certs from the front end server.  The FQDN has to be first in the cert order, since my domain is on a .local, I had dialin, meet ect on a .com, and the .local was not first.  I reorder the cert and it's all good.
    • Marked as answer by JJHaaga Thursday, February 7, 2013 6:03 PM
    Thursday, February 7, 2013 6:03 PM
  • Hello JJHaaga, which entry did you need to put as the first SAN? dialin.local or the FQDN of the front end or something else?

    Thanks!

    Wednesday, March 5, 2014 6:21 PM
  • The order should not matter.

    As long as the name is include in the cert.

    If you follow the Certificate task  from the Deployment Wizard, all the certificat should be there.


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks.


    Jean-Philippe Breton | Senior Microsoft Consultant | MCTS, MCITP, MCT, Lync MVP

    Wednesday, March 5, 2014 6:50 PM