MS-721 · Question #53
Your company has a Microsoft Teams Phone deployment that uses Direct Routing and a single carrier. You deploy a new Session Border Controller (SBC) that shows as healthy in the Microsoft Teams admin c
The correct answer is B. The Refer on the SBC is misconfigured.. Call transfer in SIP is accomplished with the REFER method. If the SBC's handling of SIP REFER is misconfigured - for example, the SBC is not correctly forwarding or generating REFER requests - the transfer will fail even though the original call succeeded. The SIP ladder in such
Question
Exhibit
Options
- AThe SSL certificate of the SBC is incorrect.
- BThe Refer on the SBC is misconfigured.
- CNOTIFY is enabled in the SIP options of the SBC.
- DThe carrier rejects the format of the forwarded FROM number.
How the community answered
(28 responses)- A7% (2)
- B75% (21)
- C14% (4)
- D4% (1)
Explanation
Call transfer in SIP is accomplished with the REFER method. If the SBC's handling of SIP REFER is misconfigured - for example, the SBC is not correctly forwarding or generating REFER requests - the transfer will fail even though the original call succeeded. The SIP ladder in such a scenario would show the REFER being sent but not properly processed. An incorrect SSL certificate (A) would prevent the SBC from appearing healthy in the admin center. A correctly configured initial call rules out NOTIFY issues (C) as the transfer-blocking cause. If the carrier rejected the FROM number format (D), the original outbound call would also have failed, which did not occur.
Topics
Community Discussion
No community discussion yet for this question.