Skip to content

Commit 54018a9

Browse files
committed
test restructuring of SIP calling section
1 parent 1fb264f commit 54018a9

File tree

2 files changed

+16
-22
lines changed

2 files changed

+16
-22
lines changed

fern/advanced/calls/sip.mdx

Lines changed: 13 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -4,25 +4,21 @@ subtitle: You can make SIP calls to Vapi Assistants.
44
slug: advanced/calls/sip
55
---
66

7-
<Accordion title="1. Create an Assistant.">
8-
9-
## 1. Create an Assistant
7+
<Steps>
8+
<Step title="Create an Assistant">
109

1110
We'll create an assistant with `POST /assistant` endpoint. This is no different than creating an assistant for other transports.
1211

1312
```json
1413
{
1514
"name": "My SIP Assistant",
16-
"firstMessage": "Hello {{first_name}}, you've reached me over SIP. How can I help you today?"
15+
"firstMessage": "Hello {{first_name}}, you've reached me over SIP."
1716
}
1817

1918
```
19+
</Step>
2020

21-
</Accordion>
22-
23-
<Accordion title="2. Create a SIP Phone Number.">
24-
25-
## 2. Create A SIP Phone Number
21+
<Step title="Create a SIP Phone Number">
2622

2723
We'll create a SIP phone number with `POST /phone-number` endpoint.
2824

@@ -37,37 +33,33 @@ We'll create a SIP phone number with `POST /phone-number` endpoint.
3733

3834
`sipUri` is the SIP URI of the phone number. It must be in the format `sip:username@sip.vapi.ai`. You are free to choose any username you like.
3935

40-
</Accordion>
41-
36+
</Step>
4237

4338

44-
<Accordion title="3. Start a SIP call.">
4539

46-
## 3. Start a SIP call.
40+
<Step title="Start a SIP call">
4741

4842
You can use any SIP softphone to test the Assistant. Examples include [Zoiper](https://www.zoiper.com/) or [Linphone](https://www.linphone.org/).
4943

5044
You just need to dial `sip:your_unique_user_name@sip.vapi.ai` and the Assistant will answer your call.
5145

5246
There is no authentication or SIP registration required.
5347

54-
</Accordion>
48+
</Step>
5549

56-
<Accordion title="4. Send SIP Headers to Fill Template Variables.">
50+
<Step title="Send SIP Headers to Fill Template Variables">
5751

58-
## 4. Send SIP Headers to Fill Template Variables.
5952

6053
To fill your template variables, you can send custom SIP headers.
6154

6255
For example, to fill the `first_name` variable, you can send a SIP header `x-first_name: John`.
6356

6457
The header name is case insensitive. So, `X-First_Name`, `x-first_name`, and `X-FIRST_NAME` are all the same.
6558

66-
</Accordion>
59+
</Step>
6760

68-
<Accordion title="5. Use a Custom Assistant For Each Call.">
61+
<Step title="Use a Custom Assistant For Each Call">
6962

70-
## 5. Use a Custom Assistant For Each Call.
7163

7264
You can use a custom assistant for SIP calls same as phone calls.
7365

@@ -83,5 +75,6 @@ Set the `assistantId` to `null` and the `serverUrl` to the URL of your server wh
8375

8476
Now, every time you make a call to this phone number, the server will receive a `assistant-request` event.
8577

86-
</Accordion>
78+
</Step>
8779

80+
</Steps>

fern/assistants/background-messages.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ As a developer you may run into scenarios where a user action, such as pressing
4343
</Steps>
4444

4545
<Card title="Practical Use Cases">
46-
- Silent logging of user activities. - Contextual updates in conversations triggered by background
47-
processes. - Non-intrusive user experience enhancements through additional information provision.
46+
- Silent logging of user activities.
47+
- Contextual updates in conversations triggered by background processes.
48+
- Non-intrusive user experience enhancements through additional information provision.
4849
</Card>

0 commit comments

Comments
 (0)