AudioCodes Mediant 500 E-SBC, Руководство пользователя

Страница: 196 / 920

User's Manual 196 Document #: LTRT-10437
Mediant 500 E-SBC
Parameter Description
Peer IP Group ID
CLI: peer-ip-group-id
[SIPRecRouting_PeerIPGroupID]
Defines the peer IP Group that is participating in
the call.
Caller
CLI: caller
[SIPRecRouting_Caller]
Defines which calls to record according to which
party is the caller.

[0] Both (default) = Caller can be peer or
recorded side

[1] Recorded Party

[2] Peer Party
Recording Server (SRS) IP Group ID
CLI: srs-ip-group-id
[SIPRecRouting_SRSIPGroupID]
Defines the IP Group of the recording server
(SRS).
Note: The SIP Interface used for communicating
with the SRS is according to the SRD assigned to
the SRS IP Group (in the IP Group table). If two
SIP Interfaces are associated with the SRD - one
for "SBC" and one for "GW &IP2IP" – the device
uses the "SBC" SIP Interface. If no SBC SIP
Interface type is configured, the device uses the
“GW & IP2IP” interface.
15.2.3 Configuring SIP User Part for SRS
You can configure the SIP user part of the Request-URI for the recording server (SRS).
The device inserts this user part in the SIP To header of the INVITE message sent to the
SRS.

To configure the SIP user part for SRS:
1. Open the SIP Recording page ( Configuration tab > VoIP menu > Services > SIP
Recording ).
2. In the 'Recording Server (SRS) Destination Username' field, enter a user part value
(string of up to 50 characters).
3. Click Submit , and then save ("burn") your settings to flash memory.
15.2.4 Interworking SIP-based Media Recording with Third-Party
Vendors
The device can interwork the SIP-based Media Recording feature with third-party vendors,
as described in the following subsections.
15.2.4.1 Genesys
The device's SIP-based media recording can interwork with Genesys' equipment. Genesys
sends its proprietary X-Genesys-CallUUID header (which identifies the session) in the first
SIP message, typically in the INVITE and the first 18x response. If the device receives a
SIP message with Genesys SIP header, it adds the header's information to AudioCodes'
proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server,
as shown below:
<ac:GenesysUUID
xmlns="urn:ietf:params:xml:ns:Genesys">4BOKLLA3VH66JF112M1CC9VHKS1
4F0KP</ac:GenesysUUID>
No configuration is required for this support.