> For the complete documentation index, see [llms.txt](https://docs.omnitalk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnitalk.io/commons/call-flow.md).

# Call Flow

videocall과 audiocall의 흐름을 sequence diagram으로 보여줍니다. Caller는 발신자를 의미하고 Callee는 수신자를 의미합니다. 자세한 내용은 각 플랫폼별 문서를 참조 바랍니다.

### Caller와 Callee가 미리 Session을 생성한 상태에서 offerCall을 호출할 때

<figure><img src="/files/PsyPCZtaMHgr8Ym4BSiP" alt=""><figcaption></figcaption></figure>

### Caller가 offerCall 호출 이후에 Callee가 Session을 생성할 때

<figure><img src="/files/sWX0dlKXcNXbVKYYMR6q" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omnitalk.io/commons/call-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
