This page was last edited on October 2, 2019, at 19:20.
Comments or questions about this documentation? Contact us for support!
Geo-location is configured in two places:
You can assign a geo-location tag for each DN (of type Trunk DN, Route Point DN, Extension DN, and Trunk Group DN). The geo-location parameter is configured in the TServer section of these places.
To assign a geo-location tag for a Resource Group (for MCP and Recording Server separately), use the Resource Group Wizard and set the geo-location as part of the Wizard process.
Geo-location is selected for each call depending on the usage model.
SIP Server selects the geo-location with the following order or preference for inbound calls:
For outbound calls, the following order of preference is used:
When a DN is configured to be recorded, the geo-location set at the DN. When more than one DN involved in the call has the geo-location set (for example, both the inbound Trunk DN and the Routing Point DN have the geo-location parameter set), then SIP Server selects the geo-location based on the order of preference listed above.
If record=source is set in the RequestRoutecall extensions, the geo-location of the inbound Trunk DN of the call is selected (if it is configured). If record=destination is set in the RequestRoutecall extensions, the geo-location of the agent (Extension DN) is selected.
When dynamic recording is initiated by the T-lib RequestPrivateService function, either by a third party recording vendor, or by Interaction Workspace, the geo-location is selected based on the recorded DN in the call. Specifically: