You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/call-automation/custom-context.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ As a prerequisite, we recommend you to read these articles to make the most of t
32
32
For all the code samples, `client` is CallAutomationClient object that can be created as shown and `callConnection` is the CallConnection object obtained from Answer or CreateCall response. You can also obtain it from callback events received by your application.
33
33
34
34
-----
35
-
# Technical parameters
35
+
##Technical parameters
36
36
Call Automation supports up to 5 custom SIP headers and 1000 custom VOIP headers. Additionally, developers can include a dedicated User-To-User header as part of SIP headers list.
37
37
38
38
The custom SIP header key must start with a mandatory ‘X-MS-Custom-’ prefix. The maximum length of a SIP header key is 64 chars, including the X-MS-Custom prefix. The maximum length of SIP header value is 256 chars. The same limitations apply when configuring the SIP headers on your SBC.
@@ -41,7 +41,7 @@ The maximum length of a VOIP header key is 64 chars. These headers can be sent w
41
41
42
42
-----
43
43
44
-
# Adding custom context when inviting a participant
44
+
##Adding custom context when inviting a participant
45
45
46
46
### [csharp](#tab/csharp)
47
47
@@ -126,7 +126,7 @@ result = call_connection_client.add_participant(
126
126
```
127
127
128
128
-----
129
-
# Adding custom context during call transfer
129
+
##Adding custom context during call transfer
130
130
131
131
### [csharp](#tab/csharp)
132
132
@@ -219,7 +219,7 @@ result = call_connection_client.transfer_call_to_participant(
219
219
Transfer of a VoIP call to a phone number is currently not supported.
220
220
221
221
-----
222
-
# Reading custom context from an incoming call event
222
+
##Reading custom context from an incoming call event
- For a sample payload of the incoming call, refer to this [guide](../../../event-grid/communication-services-voice-video-events.md#microsoftcommunicationincomingcall).
0 commit comments