MENU
Alter a new SIP trunk is configured from a third-party SIP trunk provider, the call does not seem to work. A troubles hooting tool and a tiace log from the Cisco Unified Border Element shows that there is communication with the provider and that it is sending out SDP information in the 2XX response. Why is the call not working?
Suggested Answer: B
Get Premium 300-815 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
26 comments · newest first
NO
Noelia
10 months ago
Wait, why would the SIP provider expect anything different?
FI
Fidelia
10 months ago
I agree, early offer makes sense here.
RE
Reiko
11 months ago
I think it’s definitely about the early offer expectation.
DO
Dominque
11 months ago
Could be a delayed offer situation too, not sure.
HI
Hildred
11 months ago
Sounds like a licensing issue with the Cisco Border Element.
BE
Beata
11 months ago
I don't think it's about PDVM resources since the logs show communication. It must be something with how the offer is being handled.
MA
Marva
11 months ago
The SDP info in the response makes me think it could be related to the offer type. I feel like the provider might need a delayed offer, but I can't recall the specifics.
DA
Daren
12 months ago
I think I saw a practice question about licensing for SIP trunks. If the border element isn't licensed, that could definitely cause issues.
LA
Lacresha
12 months ago
I remember something about early and delayed offers, but I'm not sure which one the provider expects in this case.
TA
Tarra
1 year ago
This looks like a classic SIP trunk configuration issue. I'm going to start by verifying the Cisco Unified Border Element's settings and then cross-check them against the SIP provider's requirements.
NO
Norah
1 year ago
Okay, I've got a few ideas here. The key seems to be understanding the SIP provider's expectations for the offer/answer process. I'll make sure to thoroughly analyze the trace log and consider each of the answer choices.
CO
Cornell
1 year ago
Hmm, the question mentions that the SDP information is being sent in the 2XX response, so I'm thinking it might be an issue with the offer/answer negotiation. I'll need to double-check the SIP provider's requirements.
VA
Valentine
1 year ago
This seems like a tricky one. I'll need to carefully review the information provided in the question and the trace log to determine the issue.
CR
Craig
1 year ago
I think the Cisco Unified Border Element must be licensed for third-party SIP trunks to make the call work.
OT
Otis
1 year ago
I believe the SIP provider expects a delayed offer, that could be causing the issue.
DE
Deeann
1 year ago
Wait, the Cisco Unified Border Element doesn't have any PDVM resources? What is this, the Stone Age? Option A is clearly the answer here.
JA
Jacki
1 year ago
User1: Yeah, it seems like the Cisco Unified Border Element needs those PDVM resources.
AV
Avery
1 year ago
I agree with Valentin, it could be the reason why the call is not going through.
MI
Michel
1 year ago
The SIP provider must be using some ancient technology if it expects a delayed offer. Option B is the way to go, my friend.
VA
Valentin
1 year ago
I think the call is not working because the Cisco Unified Border Element does not have any PDVM resources.
MA
Margo
1 year ago
Haha, the Cisco Unified Border Element probably needs a license for third-party SIP trunks. What, did they think it was a free-for-all?
SA
Samira
1 year ago
B) The SIP provider expects a delayed offer.
DI
Dierdre
1 year ago
A) The Cisco Unified Border Element must be licensed for third-party SIP trunks.
RA
Ramonita
1 year ago
The issue seems to be with the SDP negotiation. I'm guessing the provider expects an early offer, so option C is the correct answer.
CA
Carin
1 year ago
That makes sense, the SDP negotiation must be the issue then.
MA
Margurite
1 year ago
I think the SIP provider expects an early offer, so option C is the correct answer.