# RTTP Message Codes

This page explains how [RTTP](../liberator/liberator-rttp.md) messages are shown in log files, and lists the meanings of the RTTP message codes that appear in log entries.

## Message Direction

`<` Signifies an **incoming** message.

`>` Signifies an **outgoing** message.

## Message Information

Example message info: `380U0009`

| Segment | Description |
| --- | --- |
| `38` | Message type. This is a Blank Response (object being requested from an active DataSource). |
| `0U` | Sequence number. This is used by the client so that it knows that it hasn’t missed any messages. |
| `0009` | Object number. |

## Example Communication

### Incoming message

```
<<< 09 Jun 09:21:45.72
```

Message details:

```
0GYy7KP1XH_zFX2uTHoTeT REQUEST /FILTER2/TT/EventService/Containers/Log%3Fsort%3DEventTime:number

ascending%3Bmode%3Dlive%3BcacheBuster%3D1273489184126;
ctrid=4,ctrstart=0,ctrend=26,EventTime,EventType,OrderInfo
```

Here, a client with the session id = "0GYy7KP1XH_zFX2uTHoTeT" is making a’REQUEST' for: "_/FILTER2/TT/EventService/Containers/Log...._ "

### Outgoing message

```
>>> 09 Jun 09:21:45.72
```

Message details:

```
380U0009 /FILTER2/TT/EventService/Containers/Log%3Fsort%3DEventTime:number:ascending%3Bmode%3Dlive%3BcacheBuster%3D1273489184126
```

As there is a `38` in the message information,this is a 'Blank Response' (object being requested from an active datasrc).

This is the first message for _/FILTER2/TT/EventService/Containers/Log_. The object number will be 0009 for this object

### Outgoing message

Message details

```
7U0V0009 /FILTER2/META/PLACEHOLDER;200;000A size=1 order=000A:0
```

1. Container image (7U)
2. Container constituent message /FILTER2/META/PLACEHOLDER;200;000A 
   * constituent subject is /FILTER2/META/PLACEHOLDER
   * constituent object type is 200 (unknown at this point)
   * constituent object number is 000A
3. The overall size of the container is 1 (size=1)
4. /FILTER2/META/PLACEHOLDER(000A) is in position 0 (order=000A:0)
5. Status OK(6V) for /FILTER2/TT/EventService/Containers/Log (0009) 6V0W0009 rN=0 rO=All+peers+providing

## Initial response codes

| Short Code | RTTP v2 | RTTP v1 | Description |
| --- | --- | --- | --- |
| RESP_UNKNOWN | 38 | 200 | BlankResponse (object being requested from an active DataSource) |
| DIRECTORY_RESP | 3S | 220 | Directory object |
| PAGE_RESP | 3T | 221 | Page object |
| RECORD_RESP | 3U | 222 | Record object (type 1 fields only) |
| CONT_RESP | 3a | 228 | Container object |
| PERM_RESP | 3c | 230 | Permissions Object |

## Status messages

| Short Code | RTTP v2 | RTTP v1 | Description |
| --- | --- | --- | --- |
| STATUS_OK | 6V | 415 | Object Status OK |
| STATUS_STALE | 6W | 416 | Object Status Stale. Some required sources are down |
| STATUS_LIMITED | 6X | 417 | Object Status Limited. Some optional sources are down |
| STATUS_REMOVED | 6Y | 418 | Object Status Removed. Subscription removed |
| STATUS_INFO | 6Z | 419 | Object Status Info. Message only |

## Updates

| Short Code | RTTP v2 | RTTP v1 | Description  |
| --- | --- | --- | --- |
| DIR_UPD | 6a | 420 | Directory update |
| REC1_UPD | 6c | 422 | Record type 1 update |
| REC2_UPD | 6f | 425 | Record type 2 update |
| REC3_UPD | 6g | 426 | Record type 3 update |
| CONT_UPD | 6i | 428 | Container update |
| PERM_UPD | 6k | 430 | Permissions Update |

## Images

| Short Code | RTTP v2 | RTTP v1 | Description  |
| --- | --- | --- | --- |
| REC1_IMG | 7O | 472 | Record type 1 cache/image data |
| REC2_IMG | 7R | 475 | Record type 2 cache/image data |
| REC3_IMG | 7S | 476 | Record type 3 cache/image data |
| CONT_IMG | 7U | 478 | Container cache/image data |
| PERM_IMG | 72 | 450 | Permissions cache/image data |