CHAPTER16 Services
Mediant 4000 SBC | User's Manual
You can configure the format of the recording metadata (i.e., based on RFC 7865 or "legacy")
that is generated by the device. For more information, see Configuring Format of SIPRec
Metadata on page203.
The SRS can respond with 'a=recvonly' for immediate recording or 'a=inactive' if recording is not
yet needed, and send re-INVITE at any later time with the desired RTP/SRTP mode change. If a re-
INVITE is received in the original call (e.g. when a call is on hold), the device sends another re-
INVITE with two 'm=' lines to the SRS with the updated RTP/SRTP data. If the recorded leg uses
SRTP, the device can send the media streams to the SRS as SRTP; otherwise, the media streams
are sent as RTP to the SRS.
Below is an example of an INVITE sent by the device to an SRS. The example shows legacy- and
RFC 7865-based metadata (only one of these is generated in real-life scenarios):
INVITE sip:VSRP@1.9.64.253 SIP/2.0
Via: SIP/2.0/UDP 192.168.241.44:5060;branch=z9hG4bKac505782914
Max-Forwards: 10
From: <sip:192.168.241.44>;tag=1c505764207
To: <sip:VSRP@1.9.64.253>
Call-ID: 505763097241201011157@192.168.241.44
CSeq: 1 INVITE
Contact: <sip:192.168.241.44:5060>;src
Supported: replaces,resource-priority
Allow:
REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SU
BSCRIBE,UPDATE
Require: siprec
User-Agent: Device /7.20A.252.011
Content-Type: multipart/mixed;boundary=boundary_ac1fffff85b
Content-Length: 1832
--boundary_ac1fffff85b
Content-Type: application/sdp
v=0
o=AudioCodesGW 921244928 921244893 IN IP4 10.33.8.70
s=SBC-Call
c=IN IP4 10.33.8.70
t=0 0
m=audio 6020 RTP/AVP 8 96
c=IN IP4 10.33.8.70
a=ptime:20
a=sendonly
a=label:1
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
m=audio 6030 RTP/AVP 8 96
c=IN IP4 10.33.8.70
a=ptime:20
a=sendonly
a=label:2
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
--boundary_ac1fffff85b
Content-Type: application/rs-metadata
Content-Disposition: recording-session
- 198 -