none
Dial-in conferencing not working

    Question

  • I have configured dial-in PSTN conferencing but a call to the conference number does not connect.  Creating a conference and joining it internally works fine.  I keep seeing this error in the event log.

     

    Log Name:      Lync Server

    Source:        LS Audio-Video Conferencing Server

    Date:          2/22/2011 3:32:27 PM

    Event ID:      32083

    Task Category: (1017)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      dci-lync-01.dci.local

    Description:

    The Audio/Video Conferencing Server cannot add Conferencing Announcement Service to a conference.

     

    Audio/Video Conferencing Server Pool: dci-lync-01.dci.local; Conferencing Announcement Service: sip:dci-lync-01.dci.local@dci.local;gruu;opaque=srvr:Microsoft.Rtc.Applications.Cas:mKVVlcQR1F2OtRCDQf151gAA

    Cause: The Audio/Video Conferencing Server is not able to reach the Conferencing Announcement Service. This may be due to network connectivity issues or unavailability of the Conferencing Announcement Service. Conference Announcements in audio/audio-video conferences will be unavailable due to this issue. PSTN dial in users will be impacted, as they will be unable to exercise DTMF controls and other PSTN dial in conferencing functionality while in the conference.

    Resolution:

    Please ensure network connectivity and availability of the Conferencing Announcement Service for the Audio/Video Conferencing Server to be able to function correctly.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="LS Audio-Video Conferencing Server" />

        <EventID Qualifiers="50169">32083</EventID>

        <Level>2</Level>

        <Task>1017</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2011-02-22T22:32:27.000000000Z" />

        <EventRecordID>27663</EventRecordID>

        <Channel>Lync Server</Channel>

        <Computer>dci-lync-01.dci.local</Computer>

        <Security />

      </System>

      <EventData>

        <Data>sip:dci-lync-01.dci.local@dci.local;gruu;opaque=srvr:Microsoft.Rtc.Applications.Cas:mKVVlcQR1F2OtRCDQf151gAA</Data>

        <Data>dci-lync-01.dci.local</Data>

      </EventData>

    </Event>

    Tuesday, February 22, 2011 10:39 PM

All replies

  • The first event will repeat 5x, then it is followed by;

     

    Log Name:      Lync Server

    Source:        LS Audio-Video Conferencing Server

    Date:          2/22/2011 3:33:48 PM

    Event ID:      32084

    Task Category: (1017)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      dci-lync-01.dci.local

    Description:

    The Audio/Video Conferencing Server cannot add Conferencing Announcement Service to a conference.

     

    Conferencing Announcement Service failing: sip:dci-lync-01.dci.local@dci.local;gruu;opaque=srvr:Microsoft.Rtc.Applications.Cas:mKVVlcQR1F2OtRCDQf151gAA

    Cause: The Audio/Video Conferencing Server is not able to reach the Conferencing Announcement Service. This may be due to network connectivity issues or unavailability of the Conferencing Announcement Service. Conference Announcements in audio/audio-video conferences will be unavailable due to this issue. PSTN dial in users will be impacted, as they will be unable to exercise DTMF controls and other PSTN dial in conferencing functionality while in the conference.

    Resolution:

    Resolution=Please ensure network connectivity and availability of the Conferencing Announcement Service for the Audio/Video Conferencing Server to be able to function correctly. For additional information to troubleshoot the issue, please look at the events AVMCU_E_CAS_UNREACHABLE (Event ID: 32083).

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="LS Audio-Video Conferencing Server" />

        <EventID Qualifiers="50169">32084</EventID>

        <Level>2</Level>

        <Task>1017</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2011-02-22T22:33:48.000000000Z" />

        <EventRecordID>27665</EventRecordID>

        <Channel>Lync Server</Channel>

        <Computer>dci-lync-01.dci.local</Computer>

        <Security />

      </System>

      <EventData>

        <Data>sip:dci-lync-01.dci.local@dci.local;gruu;opaque=srvr:Microsoft.Rtc.Applications.Cas:mKVVlcQR1F2OtRCDQf151gAA</Data>

      </EventData>

    </Event>

    Tuesday, February 22, 2011 10:42 PM
  • Experiencing the exact same issue. Was this ever resolved?

    M Tipler

    Tuesday, November 19, 2013 11:11 AM
  • Shell Test-CsDialInConferencing command output is below - obviously failed...

    PS C:\Users\m.tipler> Test-CsDialInConferencing -UserSipAddress sip:m.tipler@company.com -UserCredential $cred -TargetFqdn xxxxlnc01.corp. company.com.com –verbose

     

    VERBOSE: Reading Registrar port from topology process started.

    VERBOSE: Reading Registrar port '5061' from topology process successfully

    finished.

    VERBOSE: Workflow Instance Id 'a2991d79-9283-480e-b034-4880390051ad', started.

    VERBOSE: Command line executed is 'Test-CsDialInConferencing -UserSipAddress

    sip:m.tipler@ company.com.com -UserCredential $cred -TargetFqdn

    xxxxlnc01.corp. company.com.com -verbose'.

     

     

    Target Fqdn   : xxxlnc01.corp. company.com

    Result        : Failure

    Latency       : 00:00:00.2061271

    Error Message : Could not establish audio call with the access number 6199.

     

     

    Diagnosis     :

     

     

    VERBOSE: Workflow

    'Microsoft.Rtc.SyntheticTransactions.Workflows.STCAAAVWorkflow' started.

    Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STCAAAVWorkflow'

    completed in '2.33E-05' seconds.

    An exception 'Could not establish audio call with the access number 6199.

    ' occurred during Workflow

    Microsoft.Rtc.SyntheticTransactions.Workflows.STCAAAVWorkflow execution.

    Exception Call Stack:    at

    Microsoft.Rtc.SyntheticTransactions.Activities.InviteCAAAVActivity.InternalExec

    ute(ActivityExecutionContext executionContext)

       at

    Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Ex

    ecute(ActivityExecutionContext executionContext)

       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity,

    ActivityExecutionContext executionContext)

       at

    System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRunti

    me workflowCoreRuntime)

       at System.Workflow.Runtime.Scheduler.Run()

     

    'RegisterActivity2' sequence activity started.

    'RegisterActivity2' sequence activity completed in '1.87E-05' seconds.

    'Register' activity started.

    Sending Registration request:

     Target Fqdn      = xxxxlnc01.corp. company.com.com

     User Sip Address = sip:m.tipler@ company.com.com

     Registrar Port = 5061.

    Authentication Type 'IWA' is selected.

    Registration Request hit against sip/xxxxLNC01.corp. company.com.

    'Register' activity completed in '0.2061271' seconds.

    'InviteCAAAV' activity started.

    Requesting presence data for user sip:m.tipler@ company.com.

    Requesting provisioning data for user sip:m.tipler@ company.com.

    Successfully received provisioning data for user

    sip:m.tipler@ company.com.

    User is configured with a phone number TEL:+6257.

    Meeting policy assigned to the user allows PSTN conferencing.

    PSTN Id for the newly created conference is 53844.

    PSTN conferencing access number to test not provided as a parameter. Getting

    access numbers to test from conference information.

    Synthetic transaction will only test access numbers in user's region.

    Default region assigned to the user is Conferencing.

    Access number 6199 belongs to user's region.

    Establishing call with Access Number 6199.

    Establishing call with Access Number

    sip:6199;ms-skip-rnl;phone-context=user-default@ company.com;user=phone.

    Audio Video Flow is now Established.

    'UnRegister' activity started.

    'UnRegister' activity completed in '0.2166602' seconds.

    VERBOSE: Workflow Instance ID 'a2991d79-9283-480e-b034-4880390051ad' completed.

    VERBOSE: Workflow run-time (sec): 7.368.


    M Tipler

    Tuesday, November 19, 2013 1:34 PM
  • Apologies - I should mention that we are using 2013 and not 2010. I've responded to this post because it is the exact same issue we're experiencing but with 2013.

    Kind regards.


    M Tipler

    Tuesday, November 19, 2013 1:38 PM
  • Hi,

    Have either of you recently performed any CU upgrades?

    Please restart the Lync Server Audio/Video Conferencing service and see if the problem persists.

    Kind regards
    Ben

    Tuesday, November 19, 2013 1:43 PM
  • Hello Ben!

    Thank you for your response.

    Updates were applied about 2 weeks ago. However, this still wasn't working prior to the application of the updates. I feel restarting the AV service would be in vain - we've been trying to get the conference service working for weeks and the system has had multiple restarts in that time.


    M Tipler

    Tuesday, November 19, 2013 3:46 PM
  • Hi, is your Lync-PSTN integration working fine? Do you receive PSTN call to some of your EV user correctly?
    Regards
    Luca


    Luca Vitali | Centro Computer UC Specialist | Twitter: @Luca_Vitali

    Tuesday, November 19, 2013 3:55 PM
  • Ah ok no worries.

    Providing that your PSTN conectivity is fine as Luca has queried, can you confirm that each of the options listed in the Dialin Conferencing Checklist have been adhered to? Rather than me regurgitate them, they're listed at the below link. If there are any you need clarification on, or you identify a particular problem then please shout. Alternately if you've already been through this let us know and we'll look deeper.

    http://technet.microsoft.com/en-us/library/gg412726.aspx

    Kind regards
    Ben

    Tuesday, November 19, 2013 4:02 PM
  • Hey gents!

    Thanks for your assistance but I've now got this working! :)

    I did the following...

    Disabled the conference service > published > re-enabled the conference service > published > recreated the conference dial-in account 6xxx > about 5 minutes later it’s working like a dream!


    M Tipler

    • Proposed as answer by Mattyt123321 Tuesday, November 19, 2013 5:08 PM
    Tuesday, November 19, 2013 5:07 PM
  • For best and affordable but high standard audio conference service Reliance Mind Bridge can be your best possible solution for business purposes as well.
    Monday, September 26, 2016 10:36 AM