Genesys Engage on-premises: SIP Server Certification Free Sample Questions

In a geographically dispersed HA pair where a network partition is possible, a third-party arbitrator like Solution Control Server (SCS) is critical to prevent a split-brain scenario. The backup SIP Server will consult the arbitrator to confirm the primary server's status. If the arbitrator is also unreachable from the backup site or not configured, the backup server may incorrectly assume the primary is down and promote itself to primary, causing two active primary instances. The other options relate to failover timing and redundancy mode but do not directly address the split-brain arbitration mechanism.

The most robust and automated method is to use a Universal Routing Server (URS) strategy. The strategy can identify calls destined for the high-value cargo department (e.g., based on the dialed number or other data) and attach a T-Library request (Request-Start-Recording) to the call. SIP Server processes this request and instructs Media Server to start recording the media stream. This ensures recording is triggered automatically by the routing logic without relying on manual agent actions or endpoint capabilities.

An Emulated Agent DN acts as a virtual holding point for a call within a routing strategy. It allows the system (typically URS) to take control of a call, perform actions like data dips or treatments, and then decide the next destination (e.g., a real agent, another queue, or an IVR). It is not a real person or endpoint but a logical entity used for advanced call flow control.

The User-to-User header is a standard SIP header specifically designed to carry application data between user agents. Custom headers, conventionally prefixed with X-, are also a common and valid method for passing proprietary information. SIP Server can be configured to map both of these header types into UserData for URS. Via and Contact have specific roles in call routing and signaling path definition. X-Genesys-CallUUID is typically generated by Genesys components, not for incoming custom data. P-Asserted-Identity is used for trusted identity information.

False. Even when SIP Server is configured to act as a T-Server, a T-Server application object must still be created and configured in the Configuration Server. This object represents the T-Server functionality to the rest of the Genesys Framework (like URS and Stat Server), even though the SIP Server process is handling the CTI link. The SIP Server application is then configured with a TServer section that points to this T-Server application object.

The t-invite parameter specifically controls the amount of time SIP Server will wait for a final response (like 200 OK) to an outbound INVITE message sent to an endpoint. In a high-latency scenario, the default value may be too short, causing SIP Server to time out and initiate No Answer Supervision prematurely. Increasing this value gives the remote endpoint more time to respond over the slow link. ringing-timeout applies after a 180 Ringing response is received, and the others relate to different timers.

The gcti-user-data-map option is crucial for multi-site call tracking. It specifies which UserData keys (containing information like call type) should be encoded into a proprietary SIP header (like X-Genesys-GCTI-Data) when SIP Server transfers a call to another site. The receiving SIP Server at the second site then uses the same map to decode the header back into UserData, thus preserving the call context for consistent tracking and reporting across the enterprise.

The 'Barge-in' feature is implemented by creating a three-way conference call between the caller, the agent, and the supervisor. If Media Server is not correctly configured to support conferences, or if conference resources are unavailable, the barge-in attempt will fail. Silent monitoring, on the other hand, typically uses media forking or a passive tap and does not require conference resources, which explains why it would still work.

To block specific SIP headers, you must use two options in conjunction. First, sip-header-filtering-mode must be set to block-list. Second, the sip-headers-to-filter option must be configured with a comma-separated list of the headers to be blocked, such as P-Asserted-Identity,X-Custom-Info. Using only one of these options is insufficient to enable the filtering.

The verbose log level in SIP Server controls the amount of detail in the log files. A setting of 5 is specifically designated for SIP message logging, which directs SIP Server to write the full text of all received and sent SIP messages to the log. This is essential for deep troubleshooting of signaling issues.