discuss.channel.rtc.session: fields, relations and API
The discuss.channel.rtc.session model ("Mail RTC session") is a persistent model declared by the Discuss module, then extended by 1 other module. It exposes 14 fields, 9 of them declared directly on the model; 1 field from other models points to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.
Model identity
- Technical name
discuss.channel.rtc.session- Label
- Mail RTC session
- Type
- Persistent (models.Model)
- SQL table
discuss_channel_rtc_session- Origin module
- Discuss (
mail) - Extended by
- im_livechat
- Display field (_rec_name)
channel_member_id- Inherits from (mixins)
- bus.listener.mixin
Model fields
9 own fields, 0 inherited from mixins and 5 automatic ORM fields. Click a name to get a direct link to that field.
14 of 14 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| channel_id | Channel | many2one | read-only related: |
| channel_member_id | Channel Member | many2one | required |
| guest_id | Guest | many2one | related: |
| is_camera_on | Is sending user video | boolean | |
| is_deaf | Has disabled incoming sound | boolean | |
| is_muted | Is microphone muted | boolean | |
| is_screen_sharing_on | Is sharing the screen | boolean | |
| partner_id | Partner | many2one | related: |
| write_date | Last Updated On | datetime | |
| create_date | Created on | datetime | read-onlyautomatic |
| create_uid | Created by | many2one | read-onlyautomatic |
| display_name | Display Name | char | read-onlycomputedautomatic |
| id | ID | integer | read-onlyautomatic |
| write_uid | Last Updated by | many2one | read-onlyautomatic |
Relations
Models linked from this model
- discuss.channel: channel_id
- discuss.channel.member: channel_member_id
- mail.guest: guest_id
- res.partner: partner_id
Fields of other models pointing here
- discuss.channel.member: rtc_inviting_session_id
Reading this model through the API
Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.
curl -X POST "https://your-instance.odoo.com/json/2/discuss.channel.rtc.session/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["channel_member_id","channel_id","guest_id","partner_id","is_camera_on"],"limit":5}'import requests
BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}
res = requests.post(
f"{BASE_URL}/discuss.channel.rtc.session/search_read",
headers=headers,
json={"domain": [], "fields": ["channel_member_id","channel_id","guest_id","partner_id","is_camera_on"], "limit": 5},
)
res.raise_for_status()
print(res.json())- External API access requires Odoo's Custom plan.
- XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
- The access rights and record rules of the key's user apply.
Cite this tool
Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.
<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/discuss-channel-rtc-session">discuss.channel.rtc.session (Odoo 19.0)</a>Sources
Data verified on September 23, 2026 · Odoo 19.0 Community
Have an Odoo project, or want to put your ERP to work with AI? Let's talk
Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.