MENU
An end user at a remote site is trying to initiate an Ad Hoc conference call to an end user at the main site. The conference bridge is configured to support G.711. The remote user's phone only supports G.729. The remote end user receives an error message on the phone: "Cannot Complete Conference Call." What is the cause of the issue?
Suggested Answer: D
Get Premium 350-801 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
GI
Gilma
10 months ago
Nah, it's gotta be the transcoder that's the problem.
ON
Onita
10 months ago
Wait, why can't the bridge just handle both codecs?
SA
Sabra
11 months ago
Missing Media Termination Point could also be the culprit.
RE
Reiko
11 months ago
I agree, they need a transcoder for that.
GL
Glennis
11 months ago
It's definitely a codec mismatch issue. G.711 vs G.729.
RO
Rory
11 months ago
I’m leaning towards the transcoder being the issue. If the remote phone only supports G.729, it needs something to convert that to G.711 for the bridge.
NE
Nettie
11 months ago
I'm not entirely sure, but I feel like the error could also be related to the conference feature not being assigned to the remote phone.
AM
Amira
12 months ago
I think I saw a similar question where a Media Termination Point was involved. Could that be the missing piece here?
LA
Lanie
12 months ago
I remember something about codec compatibility being crucial for conference calls. G.711 and G.729 might not work together without a transcoder.
LA
Lavera
1 year ago
Ah, I see. The remote phone doesn't support the codec used by the conference bridge, so it can't join the call. The transcoder resource is probably missing to convert between the two codecs.
HA
Hannah
1 year ago
Okay, I think the key here is that the remote phone and conference bridge have different codecs. The question is asking what the cause of the issue is, so I'll need to figure out how that mismatch would prevent the call from completing.
MA
Marvel
1 year ago
Hmm, the question mentions the remote phone only supports G.729 but the conference bridge is set to G.711. That's probably the issue, right?
RO
Rosendo
1 year ago
This one seems tricky. I'll need to think through the different codec requirements and how that might impact the conference call.
CO
Corazon
1 year ago
Wait, did someone say 'ad hoc'? That's my favorite kind of conference call - the one where everything falls apart the moment you press 'Join'.
LE
Levi
1 year ago
D) The transcoder resource is missing.
VA
Valentin
1 year ago
C) A Media Termination Point is missing.
JU
Judy
1 year ago
B) A software conference bridge is not assigned.
KR
Kris
1 year ago
A) The remote phone does not have the conference feature assigned.
CA
Caitlin
1 year ago
Exactly, without the transcoder, the call cannot be completed due to the codec mismatch.
BE
Bettyann
1 year ago
I'd bet my last dollar that the answer is D. The transcoder resource is missing. How else are you gonna get those two codecs to play nice together? This is like Codec Compatibility 101.
MA
Matthew
1 year ago
So, the transcoder resource is missing to convert the codec for the conference call to work.
PE
Peggie
1 year ago
Classic case of incompatible codecs. The remote user's phone can't handle the conference bridge's codec, so the call fails. Gotta love those good old audio compatibility problems.
GE
German
1 year ago
C) A Media Termination Point is missing.
IZ
Izetta
1 year ago
B) A software conference bridge is not assigned.
AL
Alyce
1 year ago
A) The remote phone does not have the conference feature assigned.
LA
Latanya
1 year ago
Yeah, the remote user's phone only supports G.729, but the conference bridge is configured for G.711.
DU
Dulce
1 year ago
Hmm, the issue seems to be with the codec mismatch. The conference bridge is set to G.711, but the remote phone only supports G.729. Looks like we need to find a transcoder resource to bridge the gap.
AD
Adela
1 year ago
That's why the remote user is getting an error message.
JU
Jutta
1 year ago
That's why the remote user is getting the error message.
IV
Ivette
1 year ago
The remote phone only supports G.729, but the conference bridge is set to G.711.
JU
Junita
1 year ago
The remote phone only supports G.729, but the conference bridge is set to G.711.
NI
Nikita
1 year ago
We need to find a transcoder resource to bridge the gap.
AD
Adelina
1 year ago
We need to find a transcoder resource to bridge the gap.
LA
Laura
1 year ago
I think the issue is with the codec mismatch.