> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/voice-and-media/editing-custom-sip-bye-headers-format.md).

# Editing Custom SIP BYE headers format

The custom SIP BYE headers field is formatted similarly to [Text CDR records](/telecom-references/cdr-and-statistics/text-call-detail-records.md). For example, the following content:

```
X-Test: This is a test.
P-RTP-Stat: PL=@{Stat:Rtp:Rx:Error:LostPackets}, DU=@{CallDuration}
```

Would put the following SIP headers in the BYE packet:

```
X-Test: This is a test.
P-RTP-Stat: PL=0, DU=12
```

For a call which lasted 12 seconds and had no packet loss.

For **P-RTP-Stat** SIP BYE headers, it is recommended to use the following content in release 2.9 and later:

```
P-RTP-Stat: PS=@{Stat:Rtp:Tx:IPPackets}, OS=@{Stat:Rtp:Tx:IPBytes}, PR=@{Stat:Rtp:Rx:IPPackets}, OR=@{Stat:Rtp:Rx:IPBytes}, PL=@{Stat:Rtp:Rx:Error:LostPackets}, JI=@{Stat:Rtcp:Jitter}, LA=@{Stat:Rtcp:RoundTripDelay}, DU=@{CallDuration}
```

The following link provides the statistics format: [Call statistics format](/telecom-references/voice-and-media/call-statistics-format.md).

Here is the list of fields specific to SIP BYE headers:

| Field name        | Description                    |
| ----------------- | ------------------------------ |
| @{CallDuration}   | Call duration, in seconds      |
| @{CallDurationMs} | Call duration, in milliseconds |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/voice-and-media/editing-custom-sip-bye-headers-format.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.