December 7, 2011 – 6:58 pm | 16 Comments

3CX is pleased to announce a new release of 3CX Phone System 10, build 22686. Service Pack 5 fixes numerous 3CX Wallboard issues and also adds a new and important caller ID feature. To download …

Read the full story »
Releases

3CX Product Releases

VoIP How To

Technical tips to run your VoIP PBX more efficiently

Events

3CX Trainings and Webinars around the world

Docs & FAQ

3CX Documentation how to and FAQ

Phone configuration

3CX, Aastra, Cisco, Yealink, Grandstream, Polycom configs

Home » Docs & FAQ

What to do when Media Server reports “Binding Failed”

Submitted by on January 12, 2010 – 6:24 pmNo Comment

If the Media Server needs to allocate a port for media transmission, and cannot bind, it will generate a log message such as:

MediaServerReporting:InitEndPoint [MS003003] C:179.1: RTCP socket 10.0.0.173:7023 binding failed with error code 10048

This is due to some other application already binding to some ports in the 7000-7499 range. Typically it is the Microsoft DNS server doing this. To check which ports are bound at any point in time, you can run the following command from the DOS prompt:

netstat -ano -p UDP

Microsoft Windows allows you to define which port ranges will NOT be returned to any application/service that requests a random port number, via the following registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts

To ensure correct functionality, you should add the following ranges, without removing whatever the value already contains:

  • 3478-3478  – STUN / Firewall Checker
  • 5000-5000 – MyPhone Interface
  • 5060-5090 – SIP Port for 3CX PhoneSystem and Tunnel Ports
  • 5480-5490 – Management Console, FAX Server, Other 3CX Components
  • 7000-7499 – range of RTP ports for Local Connections
  • 9000-9049 – range of RTP ports for External Connections
  • 10000-10500 – range of RTP ports for Fax (10000-10001) and Tunnel Connections
  • 40000-41000 – Conference, IVR, Parking Orbits

If the value already contained “1433-1434”, the end result would look something like this (click on image to enlarge):

For more specific instructions regarding this registry entry, refer to: http://support.microsoft.com/kb/812873/

Comments are closed.