Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Avaya Exam 71201X Topic 4 Question 41 Discussion

Actual exam question for Avaya's 71201X exam
Question #: 41
Topic #: 4
[All 71201X Questions]

You are creating an OPTIM trunk between Avaya Aura Session Manager (SM) and Avaya Aura Communication Manager (CM) to separate the SIP traffic for your Advanced SIP Telephone (AST) users.

How would you create a second SIP Trunk between SM and CM, when you already have an existing SIP trunk between these two entities for regular traffic?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Thurman
2 months ago
C is the correct answer, no doubt. Anything else would just be a convoluted mess. Hey, at least they didn't ask about configuring a 'Rube Goldberg' machine, right?
upvoted 0 times
Lore
29 days ago
It's all about maintaining efficiency and organization in the network setup.
upvoted 0 times
...
Clare
1 months ago
Agreed, it's important to keep the OPTIM traffic separate from regular traffic.
upvoted 0 times
...
Iluminada
1 months ago
Exactly, creating a new SIP Entity and using an alternate TLS port is the way to go.
upvoted 0 times
...
Bettina
1 months ago
C is the correct answer, no doubt. Anything else would just be a convoluted mess. Hey, at least they didn't ask about configuring a 'Rube Goldberg' machine, right?
upvoted 0 times
...
...
Joanna
2 months ago
Wow, this is a tricky one. I'm going to go with C as well. Gotta keep that OPTIM traffic nice and tidy!
upvoted 0 times
Jesus
20 days ago
A) A second link should not be created as OPTIM traffic must be sent down the existing SIP link.
upvoted 0 times
...
Natalie
21 days ago
B) Specify a new Entity Link on the existing CM SIP Entity but using UDP instead of TLS as the Transport Protocol.
upvoted 0 times
...
Nu
1 months ago
C) Create an additional SIP Entity, SIP Entity Link and CM Signaling/Trunk Group using an alternate TLS port (such as 5062).
upvoted 0 times
...
...
Selma
2 months ago
I agree, C is the way to go. Trying to reuse the existing link with a different protocol doesn't seem like a good idea.
upvoted 0 times
Thomasena
1 months ago
C) Create an additional SIP Entity, SIP Entity Link and CM Signaling/Trunk Group using an alternate TLS port (such as 5062).
upvoted 0 times
...
Micheline
1 months ago
B) Specify a new Entity Link on the existing CM SIP Entity but using UDP instead of TLS as the Transport Protocol.
upvoted 0 times
...
Franklyn
1 months ago
A) A second link should not be created as OPTIM traffic must be sent down the existing SIP link.
upvoted 0 times
...
...
Mitsue
2 months ago
I'm not sure about option C. I think option B could also work by specifying a new Entity Link with UDP instead of TLS for the OPTIM traffic.
upvoted 0 times
...
Dortha
2 months ago
Option C seems like the best choice here. Creating a separate SIP Entity and Trunk Group using an alternate TLS port is the way to go to keep the OPTIM traffic separate.
upvoted 0 times
Levi
1 months ago
A) A second link should not be created as OPTIM traffic must be sent down the existing SIP link.
upvoted 0 times
...
Whitney
2 months ago
C) Create an additional SIP Entity, SIP Entity Link and CM Signaling/Trunk Group using an alternate TLS port (such as 5062).
upvoted 0 times
...
Larue
2 months ago
B) Specify a new Entity Link on the existing CM SIP Entity but using UDP instead of TLS as the Transport Protocol.
upvoted 0 times
...
...
Florinda
3 months ago
I agree with Fletcher. Option C seems like the most logical solution to keep the SIP traffic separate for AST users.
upvoted 0 times
...
Fletcher
3 months ago
I think option C is the best choice because it allows us to create a separate SIP trunk for OPTIM traffic using an alternate TLS port.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77