An end used at a remote site is trying initiate an ad hoc conference call to an end user at the main site the conference bridge is configured to support G.711 remote user phone only support G.729…

The error message "cannot complete conference call" suggests a resource or compatibility issue after initiation, not a lack of the conference feature on the phone itself, which would likely manifest as an inability to even attempt the conference.

While a Media Termination Point (MTP) can be involved in media operations, the specific issue described is a codec mismatch for a conference bridge. A transcoder is the precise media resource designed to resolve codec incompatibility.

The problem describes a scenario where a remote phone uses G.729, but the conference bridge only supports G.711. For these two endpoints to communicate through the conference bridge, a transcoder is required to convert the audio streams between G.729 and G.711 codecs. Without an available transcoder resource, the codec incompatibility prevents the conference call from being completed, resulting in the error message.

The problem statement explicitly mentions that "the conference bridge is configured to support G.711," implying that a conference bridge is assigned. The issue is not the lack of a bridge, but the codec mismatch with the existing one.