<Siprec>
Stream both legs of the call to your session-recording server over the SIPREC standard (RFC 7866).
Example
<Response>
<Start>
<Siprec name="audit-trail" connectorName="srs1" track="both_tracks"
statusCallback="https://app.example.com/siprec">
<Parameter name="vendor" value="acme"/>
</Siprec>
</Start>
<Dial><Number>+18005551234</Number></Dial>
<Stop><Siprec/></Stop>
</Response>
Attributes
| Attribute | Default | Behaviour |
|---|---|---|
connectorName |
required |
Names a SIPREC connector configured on your account (portal → Recordings). The connector resolves to your Session Recording Server's SIP URI. An empty, unknown, or disabled connector starts no recording — the verb fails closed. |
name |
unset |
Operator identifier, logged and echoed in callbacks. |
track |
both_tracks |
inbound_track, outbound_track, or both_tracks. |
statusCallback |
unset |
Lifecycle webhook: started, stopped, error. |
statusCallbackMethod |
POST |
HTTP method for lifecycle webhooks. |
Nesting
<Siprec> accepts these nested elements:
Notes
- Nested <Parameter name value> pairs pass through to the SIPREC INVITE and surface on the status callback as Parameter.<name> form fields.
- One active SIPREC session per call: a second <Start><Siprec> stops the prior session before starting the new one. <Stop><Siprec/> ends it; otherwise it ends at hangup.