locked
Dialin conference Join Error from Sip Trunk RRS feed

  • Question

  • Hi all,

    we have installed s4b standard CU5 on windows server 2016. Only one server with all roles installed.

    everything works fine with dialin conference with s4b clients and web, but when we try to join in the conference with a PSTN number connected to s4b via TRUNK SIP we are able to listen the initial voice that ask conference ID (so trunk sip is working fine) but when we are connecting to conference the leader see for 1 second 2 users in the conference and after that a voice tell that "cannot join to the conference  at the moment retry later..."

    On logging via snooper we see a 503 error.

    we have already disable and enable dialin conferencing feature removing and installing the feature without result.

    Any suggestion how to troubleshoot this problem?

    Thanks

    Tuesday, October 10, 2017 6:18 AM

All replies

  • Hi Michele__74,

    1.Could you find some error event logs in the SFB server?

    2.Please check the normalization rule for dial-in number.

    Please try to following ways.

    Disable PSTN Conferencing in topology builder, publish topology and run the deployment wizard on the server.

    Then re-enable PSTN conferencing, publish topology, and re-run the deployment wizard again.


    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, October 11, 2017 2:31 AM
  • Hi Leon-Lu,

    thanks for your support.

    I have already tried to disable conference -> publish -> deploy wizard --> restart --> enable conference -> deploy wizard --> patch CU5 --> restart

    without success.

    no normalization rules for dialin conference

    the error  the we see in EventViewer below:

    User failed to join the conference.

     

    Microsoft.Rtc.Collaboration.ConferenceFailureException:The operation failed due to a response from the server. For more information, examine the properties on the exception and inner exception.

       at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()

       at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)

       at Microsoft.LiveServer.Caa.CaaCall.EndTransfer(IAsyncResult asyncResult, Boolean& retry, Exception& caught)

    Detected at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)

       at System.Environment.get_StackTrace()

       at Microsoft.Rtc.Collaboration.ConferenceFailureException..ctor(String message, Exception innerException)

       at Microsoft.Rtc.Collaboration.Conferencing.SendCommandAsyncResult.CreateConferenceFailureException(ConferenceCommandResponse commandResponse, Exception innerException)

       at Microsoft.Rtc.Collaboration.Conferencing.SendCommandAsyncResult.ProcessCccpResponse(SipMessageData messageData, responsetype response, Boolean& isPendingResponse)

       at Microsoft.Rtc.Collaboration.Conferencing.SendCommandAsyncResult.ProcessStatusMessage(SipMessageData statusMessageData, responsetype response)

       at Microsoft.Rtc.Collaboration.Conferencing.StatusMessageReceivedWorkItem.Process()

       at Microsoft.Rtc.Signaling.AsyncWorkitemQueue.ProcessItems()

       at Microsoft.Rtc.Signaling.QueueWorkItemState.ExecuteWrappedMethod(WaitCallback method, Object state)

       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

       at System.Threading.ThreadPoolWorkQueue.Dispatch()

    Cause: Administration issues.

    Resolution:

    Verify that Conferencing Attendant is installed in a supported topology and the dependant Front End servers are functioning correctly.

    Thanks

    Michele

    Wednesday, October 11, 2017 7:25 AM
  • Hi Michele,

     

    You should create a dial plans(include set of normalization rules) for the dian-in conferencing.

    To configure dial-in conferencing, you create dial plans and dial-in conferencing access numbers. You also specify the dial-in regions that associate a dial-in conferencing access number with its dial plans. More specifically:

    1. Dial plans are sets of normalization rules that specify the number and pattern of digits in a phone number, and translate the phone number into the standard E.164 format required for call routing.
    2. Dial-in conferencing access numbers are the numbers participants call to join a conference.
    3. Every dial-in conferencing access number must be associated with at least one dial plan.
    4. Every dial plan is associated with a conferencing region

    There is a link about planning for dial-in conferencing for your reference.

    https://technet.microsoft.com/en-us/library/mt297725.aspx


    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, October 12, 2017 1:34 AM
  • Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.

    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, October 16, 2017 8:52 AM
  • Hi

    I haven't tried yet.

    I will do next week sorry.

    I will reply as soon I have verified.

    thanks again

    Tuesday, October 17, 2017 10:44 AM
  • Ok, waiting for your update.

    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, October 18, 2017 9:13 AM
  • Hi,

    I have done al test following your suggestion but nothing change, and all configurations are ok, any other suggestion about this error pls?

    thx

    Michele

    Thursday, October 19, 2017 8:00 PM
  • Hi Michele__74,

     

    Thanks for your reply.

    Based on you error and description, I find a similar case, the problem may cause by the issue was with the certificate on the FE server, you could refer to the following link

     

    https://ccolonbackslash.com/2015/01/14/lync-2010-standard-33060-events-pstn-dial-in-fails-sip2-0-503-service-unavailable-dial-in-caller-joins-then-immediately-disconnected/

     

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, October 23, 2017 9:05 AM
  • thanks but this is not my case we use SHA.

    Monday, October 23, 2017 12:57 PM
  • Hi Michele__74,

    Thanks for your reply.

    According the above Error message, we did some research and most of articles point to the certificate issue, but it seems not our point. So could you please check if there is any other related Event error on your server side and client side.

    Also I suggest that you could check if CAA (Skype for Business Server Conferencing Attendant) and CAS (Skype for Business Server Conferencing Announcement) have been installed and started up in service management.

    Then please use “netstat -an” on the Skype for business server to check if 5072 and 5073 ports are listening. Also try to telnet these ports to see if they can reach.

    Another way, please also check the SIP trunk configuration (transport, port…) and compare them with Skype for business topology.

    Thanks for your understanding and patience!


    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, October 25, 2017 8:53 AM
  • Thanks I have open a MS support case.

    I keep you update.

    Wednesday, October 25, 2017 1:32 PM
  • OK, waitting for your update

    Best Regards,

    Leon-Lu
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, October 26, 2017 1:10 AM
  • Hi Michele,

    Do you have any update? I've same your issue. Our server not listen 5072/5073 port. Although disable and re-enable PSTN conferencing.

    Our SFB server version: SFB 2015, CU5

    Thanks,

    Cuong

    Sunday, February 25, 2018 9:05 AM
  • Hello

    Any updates? have the same issue


    /Andreas

    Wednesday, March 20, 2019 12:35 PM