GEOP-SIP Genesys Engage on-premises: SIP Server Certification Practice Questions

The t-options parameter controls the timer for SIP OPTIONS keep-alive messages. A positive integer value sets the frequency (in seconds) for sending these messages. If a gateway does not respond to OPTIONS requests, setting t-options to 0 on the relevant DN or Trunk object will disable this keep-alive mechanism, preventing SIP Server from incorrectly marking the gateway out of service based on the lack of a response.

The dnis-map option is specifically designed for this purpose. By configuring dnis-map with a value like To, you instruct SIP Server to extract the DNIS value from the user part of the To header URI instead of the Request-URI. This value is then populated in the DNIS attribute of the EventRouteRequest, making it directly accessible to the URS strategy without complex header-to-UserData mapping.

Implementing multi-site supervision requires careful planning. 1) Media Forking: The most efficient way to capture the agent's audio is to fork the RTP stream at the edge device (SBC/gateway) closest to them, avoiding hairpinning media across the WAN. 2) Codec Selection: The forked media stream sent to the supervisor will consume WAN bandwidth, so selecting a low-bandwidth codec (like G.729) is crucial. 3) Legal Compliance: Cross-border call monitoring is subject to complex and varied legal requirements (e.g., GDPR, two-party consent laws), which is a critical non-technical consideration.

For a simple, single-site deployment, the Standalone Mode where SIP Server also performs the T-Server function is the most straightforward. This reduces the number of server components to install and manage, as a separate T-Server application is not needed. It combines SIP signaling and CTI link management into a single process, making it ideal for smaller environments without complex redundancy or distribution needs.

When the number of concurrent calls on a trunk governed by a Class of Service restriction reaches the max-calls limit, SIP Server will reject any new call attempts for that trunk. The standard SIP response for this condition is 503 Service Unavailable, indicating that the server is temporarily unable to process the request due to overloading. This immediate rejection prevents the call from proceeding and signals the 'all circuits busy' condition.

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.