Call drops: mid-call media failure where both endpoints are internal... RRS feed

  • Question

  • Hi There,

    Does anybody knows what does the following error really means?
    "call terminated on mid-call media failure where both endpoints are internal"

    I have one mediation pool with two servers, and only the second server have this trouble. I have not specified any Trunk configurations so, servers should have pretty common configuration.

    The first question is of course, on which site the problem exists? Between:
     - Mediation server and SIP trunk
     - Mediation server and FEs?


    Monday, September 30, 2013 1:11 PM

All replies

  • Looks like a configuration Problem between Mediation Server and the sip trunk.

    regards Holger Technical Specialist UC

    Monday, September 30, 2013 3:10 PM
  • Would you like to share your thought? As this problem does not appear on the other node of the Mediation pool?


    Monday, September 30, 2013 7:22 PM
  • Hi, Check persistent static route on both nodes. It looks like persistent route is missing. 
    Monday, September 30, 2013 9:23 PM
  • If the problem is configuration based issue, then I assume the problem should be visible pretty much all the time. But this problem hits first and then it comes and goes.


    Tuesday, October 1, 2013 7:43 PM
  • Hi,

    The error you provided is a general message. Please also provide the description of it in the log.

    You can enable logging tool on Mediation and Front End server and reproduce the issue to get trace.


    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.

    In addition, you can try to restart all Mediation services to test the issue.

    Kent Huang
    TechNet Community Support

    • Edited by Kent-Huang Wednesday, October 2, 2013 5:38 AM 12345
    Wednesday, October 2, 2013 5:37 AM
  • Hi Kent,

    Thanks, I'll try to get more logs, but the problem is the problem itself. As you can see, I'm not able to reproduce the problem as I like, it might run nicely the hole day and then suddenly *bang*.

    One thing I made was: I moved the IPs from server A to server B and from server B to server A to see if the problem is in the server. But so far, the problem has been following the IP address, so I feel confident our Operator might have some configurations on their site, or network.


    Thursday, October 3, 2013 12:21 PM