locked
errors post CU9 (May 2019) installation - diagnostic ID 31047 and 24118 RRS feed

  • Question

  • hi,

    we're seeing hundreds of these being logged in SfB Monitoring server.
    We've had these logged in past occasionally, now at least 1 error per minute, various users.
    What is the impact?
    Anyone seeing this post CU9 implementation?

    thanks,

    Failure information
    Request: INVITE Response: 480 
    Diagnostic ID: 31047 Category: Unexpected 
    Component: Unified Communications Web API (UCWA) 
    Reason:
    Invitation received through static registration could not be delivered to application's endpoint.
    Description:
    Invitation received through static registration could not be delivered to application's endpoint.

    information

    From Diagnostic report:

    From user agent: RTCC/6.0.0.0 InboundRouting/6.0.0.0   
    Diagnostic header: 31047; Component="RTCC/6.0.0.0_UCWA/6.0.0.0"; Reason="Invitation received through static registration could not be delivered to application's endpoint."; Source="One-of-FrontEnds.domain.com" 

    # edited, added 24118

    Response code: 403 Diagnostic ID: 24118   
      Request type: INVITE Content type: application/sdp   
      Source: one-of-FrontEnds.domain.com Application: RTCC/6.0.0.0_UCWA/6.0.0.0 iPhoneLync/6.25.4.0004 (iPhone iOS 12.4)   
      From user URI: user1@domain.com To user URI: user2@domain.com   
      From user agent: RTCC/6.0.0.0 UCWA/6.0.0.0 iPhoneLync/6.25.4.0004 (iPhone iOS 12.4)   
      Diagnostic header: 24118; Component="RTCC/6.0.0.0_UCWA/6.0.0.0 iPhoneLync/6.25.4.0004 (iPhone iOS 12.4)"; Reason="Application accepts invitations via static registration only."; Source="one-of-FrontEnds.domain.com" 


    Monday, June 24, 2019 7:32 AM

All replies

  • Hi Ambiguous,

    How many server roles do you have in your topology? And is there any event error reported in the server side?

    Do end users have any function issues now?

    According your description, it seems happened after CU9 update, please check if there is any configuration changed, in addition, take a look at the certificate, make sure the SANs contain all required items.


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Shaw_Lu Friday, June 28, 2019 2:03 AM
    Tuesday, June 25, 2019 2:03 AM
  • Hi,

    Is there any update on this case?

    Please feel free to drop us a note if there is any update.

    Have a nice day!


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, July 2, 2019 6:35 AM
  • Hi,

    we see the sam messages in Monitoring DB since using CU9 - appearently no user interuption is reported. But does somebody know the cause of this behavior?

    best regards

    Niklas

    Thursday, August 22, 2019 1:15 PM
  • I'm thinking this and Diagnostic ID 24118 might be related (Reason="Application accepts invitations via static registration only").
    Check Failure Distribution Report for 24118, session category All.

    I narrowed this down to inability to send IM or call SfB mobile app endpoints.
    That is, user logged only on SfB mobile app, no matter if app is in background or foreground, cannot receive these.
    Mobile user can initiate sessions, but not other way.
    Error seen on other side (SfB desktop app) is "The action couldn’t be completed. Please try again later." 
    But sometimes SfB mobile app works just fine for the same affected user.

    Users are not reporting this but this renders SfB mobile app useless under some unknown circumstances.

    I'm going to try this workaround
    http://www.uccramblings.com/skypelync-mobileapplicationexpirytimeindays/



    Friday, August 30, 2019 10:32 AM
  • Nope, this didn't help.

    It's been only couple of days since implementing but I still can find 24118.
    The only difference I can see all sessions (that actually didn't happen) are Audio, no IM reports so far. 

    Tuesday, September 3, 2019 8:58 AM