Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco 300-820 Exam - Topic 17 Question 66 Discussion

Which complication does a NAT introduce in SDP for a SIP call?
D) The encryption keys advertised in the SDP are only valid for clients not behind a NAT.
A) Additional headers due to NAT encapsulation can cause the packet size to exceed the MTU.
B) When the client is behind a NAT they may be unable to determine the appropriate offset due to time zones.
C) The IP address specified in the connection data field may be an unrouteable internal address.

Cisco 300-820 Exam - Topic 17 Question 66 Discussion

Actual exam question for Cisco's 300-820 exam
Question #: 66
Topic #: 17
[All 300-820 Questions]

Which complication does a NAT introduce in SDP for a SIP call?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Devon
9 months ago
B doesn't really make sense to me, time zones aren't related to NAT.
upvoted 0 times
...
Raymon
10 months ago
Totally agree with C, it's a classic NAT issue.
upvoted 0 times
...
Yolande
10 months ago
Wait, are you saying NAT can make internal addresses unrouteable? That's wild!
upvoted 0 times
...
Beckie
10 months ago
I think A could be a problem too, but C is more common.
upvoted 0 times
...
Susy
10 months ago
C is definitely the right answer. NAT can mess up internal IPs.
upvoted 0 times
...
Rima
10 months ago
I recall that NAT can complicate SIP signaling, especially with the connection data. So, I’m leaning towards option C as the right answer.
upvoted 0 times
...
Ettie
11 months ago
I’m a bit confused about the encryption keys part. I thought NAT didn’t affect them directly, but maybe I’m mixing it up with another topic.
upvoted 0 times
...
Rana
11 months ago
I think option C sounds familiar because we discussed how NAT can lead to unrouteable internal addresses in our practice questions.
upvoted 0 times
...
Shizue
11 months ago
I remember something about NAT causing issues with IP addresses in SIP, but I'm not sure if it's about the connection data field.
upvoted 0 times
...
Veronika
11 months ago
I'm not too confident on this one. The NAT could cause a few different problems with SDP, like packet size or encryption issues. I'll have to review my notes and try to eliminate the wrong answers.
upvoted 0 times
...
Lai
11 months ago
Ah, I see what they're getting at. The NAT will translate the internal IP address in the SDP, so that address won't be valid for the external party. Option C seems like the best answer here.
upvoted 0 times
...
Lyda
11 months ago
Hmm, I'm a bit confused on this one. I know NAT can cause issues with SDP, but I'm not sure which specific complication it introduces. I'll have to think this through carefully.
upvoted 0 times
...
Veronique
11 months ago
This question seems straightforward, I think the answer is C - the IP address in the SDP may be an internal, unrouteable address due to the NAT.
upvoted 0 times
...
Christiane
11 months ago
Okay, let's see... 3000 APs and 7000 IPS licenses. I'm not sure which server size would be the best fit for that. I'll need to think this through carefully.
upvoted 0 times
...
Shawna
11 months ago
I think it's D, but I'm confused because I know both committees have different roles. What if some Ethics Committee members are also patient care providers?
upvoted 0 times
...
Sina
11 months ago
Okay, I've got it - the answer is B, adjusting the policy inheritance settings. That makes sense to me since the dashboard is in a child domain and needs to be visible to the parent.
upvoted 0 times
...
Jolene
11 months ago
Okay, I think I've got a strategy here. The key is finding a cloud provider that can guarantee data location in the required geographic area while still providing global access. I'd go with option C.
upvoted 0 times
...
Alesia
2 years ago
I'm not so sure about option C. I was thinking option A might be the correct answer. The additional headers from NAT encapsulation could cause the packet size to exceed the MTU, leading to fragmentation and other issues.
upvoted 0 times
Theodora
2 years ago
Option A seems to be the consensus choice for the complication introduced by NAT in SDP.
upvoted 0 times
...
Amos
2 years ago
Agreed, the impact on packet size due to NAT encapsulation is a common issue.
upvoted 0 times
...
Jarvis
2 years ago
I think option A is the most likely scenario in this case.
upvoted 0 times
...
Diane
2 years ago
Yes, fragmentation due to packet size exceeding MTU is definitely a concern.
upvoted 0 times
...
Melvin
2 years ago
True, but if the packet size exceeds the MTU, that could lead to further complications.
upvoted 0 times
...
Denny
2 years ago
But option C raises a valid point too. The IP address specified may indeed be unrouteable.
upvoted 0 times
...
Venita
2 years ago
I agree, option A seems plausible. The extra headers from NAT could definitely impact packet size.
upvoted 0 times
...
...
Lenna
2 years ago
Yeah, I agree with Johna. The IP address specified in the connection data field might be an internal, unrouteable address, which could cause problems. That makes the most sense to me.
upvoted 0 times
...
Johna
2 years ago
Okay, so we know that NAT can cause some issues with the IP addresses and ports used in the SDP. I'm leaning towards option C as the correct answer.
upvoted 0 times
...
Vonda
2 years ago
Hmm, this question is tricky. I'm not entirely sure about the complications that NAT can introduce in SDP for a SIP call. Let me think through the options carefully.
upvoted 0 times
...

Save Cancel