An engineer received this requirement from a service provider: Diversion header should match the network DID "123456@company.com" for Call Forward and transfer scenarios back to PSTN.
Which SIP profile configuration satisfies this request?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
This question is related to configuring SIP profiles on Cisco Unified Communication Manager (CUCM) to modify the Diversion header in SIP messages.
The Diversion header is used to indicate the diversion path of a call, and it can be used for call forwarding or call transfer scenarios. In this case, the service provider requires the Diversion header to match the network DID "123456@company.com" for such scenarios when calls are forwarded or transferred back to the PSTN.
To achieve this, we need to create a SIP profile and configure it to modify the Diversion header in SIP messages. The correct SIP profile configuration depends on whether the modification needs to be applied to the request or response messages, and whether it needs to modify the SIP or SDP header.
Option A modifies the Diversion header in both request and response messages by matching the pattern "sip:(.*>)" and replacing it with "123456@company.com>". This option modifies the SIP header.
Option B modifies the Diversion header in both request and response messages by matching the pattern "sip:(.*>)" and replacing it with "123456@company.com>". However, it modifies the SDP header instead of the SIP header. This option is incorrect because it does not meet the requirement specified by the service provider.
Option C modifies the Diversion header in response messages with a 200 status code by matching the pattern "sip:(.*>)" and replacing it with "123456@company.com>". This option modifies the SDP header.
Option D modifies the Diversion header in response messages with a 200 status code by matching the pattern "sip:(.*>)" and replacing it with "123456@company.com>". This option modifies the SIP header.
Therefore, the correct answer is option A. It modifies the Diversion header in both request and response messages, and it modifies the SIP header to match the requirement specified by the service provider.