3CX Media Server error

[Ricardo Santos]

Hi everyone!

I have some doubts about informations in 3CX Media Server.log.

Someone can help me to understand the information listed below:

15:45:24.797|00000ec8|Trace|MSEndPoint.cpp(2811): 5:[MS505002] C:684563.4: Failed to receive incoming stream from 127.0.0.1:20710 WSAError=10054

15:45:23.167|00000edc|Trace|RTPReceiver.cpp(414): 5:MediaProxy:VRTP receiver was removed for [email protected]:5482(C:684687.5) on socket (8468)

15:45:23.167|00000edc| Warn|RTPReceiver.cpp(440): 5:MediaProxy:VRTP receiver for [email protected]:5482(C:684687.1) has no assigned socket


Best regards !

 

[ChrisC_3CX]

The fact that you see log entries that seem to suggest there's a problem does not necessarily mean that is the case. Especially if these log entries are categorized as "Trace" or "Warnings" as in this case.

The question is, why are you looking at the logs in the first place, are you experiencing any issues with the 3CX PBX? If you are facing an issue of some sort please do let us know what that is so that we can try and help.

 

[Ricardo Santos]

Hi , thanks for the return, I had a problem days ago about the audio quality in calls when a started someting like 650 simultaneous calls. The major doubt is the RTP ports and the distribution.

 

[ChrisC_3CX]

Hi , thanks for the return, I had a problem days ago about the audio quality

Is this something that has happened before or was it a one time thing?

when a started someting like 650 simultaneous calls

So the audio quality issue started while you had 650+ calls on the system?

To get a better idea of your setup, what are the specifications of the 3CX PBX host machine, how many sim calls is your license and how many extensions are configured on it?

 

[Ricardo Santos]

License 1024 channels, / Version 16.0.9 / OS Windows / Xeon 64 processors 1.5TB Disk 393GB Ram.The machine is not the gap.

 

[ChrisC_3CX]

There should be more than enough internal and external ports for 650 sim calls.

Is this something that happens frequently enough to allow you to collect data for investigation? If yes you could try digging deeper by capturing the traffic during the time the issue occurs and then analyzing the RTP traffic of an affected call to confirm if the issue is originating from the PBX or not. You can find more information on how to do this in our training material here(slide 10-12): https://www.3cx.com/3cxacademy/videos/advanced/basic-troubleshooting/

Alternatively, it might be worth contacting one of our 3CX Partners to have them look into this or submit a 3CX Support Ticket so that our team can look into it.

If it does not occur frequently enough to be deemed disruptive. , I'd actually suggest waiting for 3CX V18 for Windows as it might resolve the issue altogether provided of course it is the PBX that is at fault here.

 

[Ricardo Santos]

Thanks so much for the cooperation!

Best Regards.

 

[ChrisC_3CX]

You're welcome! Do let us know what you find if you get to the bottom of this!

 

[Ricardo Santos]

Ok ! I'll report if I get it \o/