Skip to content

Commit 04beff5

Browse files
authored
Update live-events-outputs-concept.md
1 parent 8ef90b9 commit 04beff5

File tree

1 file changed

+17
-15
lines changed

1 file changed

+17
-15
lines changed

articles/media-services/latest/live-events-outputs-concept.md

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -85,41 +85,43 @@ You can either use non-vanity URLs or vanity URLs.
8585

8686
Vanity mode is preferred by large media broadcasters who use hardware broadcast encoders and don't want to re-configure their encoders when they start the Live Event. They want a predictive ingest URL, which does not change over time.
8787

88-
To specify this mode, you set `vanityUrl` to `true` at creation time (default is `false`). You also need to pass your own access token (to avoid a random token in the URL). Set `LiveEventInput.accessToken` to a a unique identifier at creation time. Once the mode is set it cannot be updated.
88+
To specify this mode, you set `vanityUrl` to `true` at creation time (default is `false`). You also need to pass your own access token at creation time. You specify the token value to avoid a random token in the URL. The access token (`LiveEventInput.accessToken`) has to be a valid GUID string (with or without the dashes). Once the mode is set it cannot be updated.
89+
90+
The access token needs to be unique in your data center. If your application needs to use a vanity URL, it is recommended to always create a new GUID instance for your access token (instead of reusing any existing GUID).
8991

9092
### Live ingest URL naming rules
9193

9294
The *random* string below is a 128-bit hex number (which is composed of 32 characters of 0-9 a-f).<br/>
93-
The *access token* below is what you need to specify for fixed URL. It is also 128 bit hex number.<br/>
94-
The *stream name* below indicates the stream name for a specific connection.
95+
The *access token* is what you need to specify for fixed URL. You must set an access token string that is a valid length GUID string. <br/>
96+
The *stream name* indicates the stream name for a specific connection. The stream name value is usually added by the live encoder that you use.
9597

9698
#### Non-vanity URL
9799

98100
##### RTMP
99101

100-
`rtmp://<random 128bit hex string>.channel.media.azure.net:1935/live/<access token>/{stream name}`
101-
`rtmp://<random 128bit hex string>.channel.media.azure.net:1936/live/<access token>/{stream name}`
102-
`rtmps://<random 128bit hex string>.channel.media.azure.net:2935/live/<access token>/{stream name}`
103-
`rtmps://<random 128bit hex string>.channel.media.azure.net:2936/live/<access token>/{stream name}`
102+
`rtmp://<random 128bit hex string>.channel.media.azure.net:1935/live/<access token>/<stream name>`
103+
`rtmp://<random 128bit hex string>.channel.media.azure.net:1936/live/<access token>/<stream name>`
104+
`rtmps://<random 128bit hex string>.channel.media.azure.net:2935/live/<access token>/<stream name>`
105+
`rtmps://<random 128bit hex string>.channel.media.azure.net:2936/live/<access token>/<stream name>`
104106

105107
##### Smooth Streaming
106108

107-
`http://<random 128bit hex string>.channel.media.azure.net/<access token>/ingest.isml/streams({stream name})`
108-
`https://<random 128bit hex string>.channel.media.azure.net/<access token>/ingest.isml/streams({stream name})`
109+
`http://<random 128bit hex string>.channel.media.azure.net/<access token>/ingest.isml/streams(<stream name>)`
110+
`https://<random 128bit hex string>.channel.media.azure.net/<access token>/ingest.isml/streams(<stream name>)`
109111

110112
#### Vanity URL
111113

112114
##### RTMP
113115

114-
`rtmp://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:1935/live/<access token>/{stream name}`
115-
`rtmp://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:1936/live/<access token>/{stream name}`
116-
`rtmps://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:2935/live/<access token>/{stream name}`
117-
`rtmps://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:2936/live/<access token>/{stream name}`
116+
`rtmp://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:1935/live/<access token>/<stream name>`
117+
`rtmp://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:1936/live/<access token>/<stream name>`
118+
`rtmps://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:2935/live/<access token>/<stream name>`
119+
`rtmps://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net:2936/live/<access token>/<stream name>`
118120

119121
##### Smooth Streaming
120122

121-
`http://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net/<access token>/ingest.isml/streams({stream name})`
122-
`https://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net/<access token>/ingest.isml/streams({stream name})`
123+
`http://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net/<access token>/ingest.isml/streams(<stream name>)`
124+
`https://<live event name>-<ams account name>-<region abbrev name>.channel.media.azure.net/<access token>/ingest.isml/streams(<stream name>)`
123125

124126
## Live Event preview URL
125127

0 commit comments

Comments
 (0)