Skip to content

Commit 81a8092

Browse files
Merge pull request #265069 from boris-bazilevskiy/doc-update-feb24
clarify SBC status description
2 parents 0b06edf + 32ef63d commit 81a8092

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/communication-services/concepts/telephony/direct-routing-provisioning.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -35,22 +35,25 @@ The health of an SBC connection now exposed in Azure portal. It takes in account
3535
### Possible values of each health indicator
3636

3737
TLS Status - Status of the TLS connections of a Trunk:
38-
- Unknown - Indicates an unknown status.
38+
- Unknown - Indicates that SBC hasn't attempted a TLS handshake in the last 15 minutes.
3939
- Active - Indicates that TLS connection is established.
4040
- CertExpiring - Indicates that SBC certificate is expiring.
4141
- CertExpired - Indicates that SBC certificate is expired.
4242

4343
SIP OPTIONS (Ping) - Status of SIP OPTIONS messages exchange:
44-
- Unknown - Indicates an unknown status.
44+
- Unknown - Indicates that SBC hasn't sent any SIP options.
4545
- Active - Indicates that OPTIONS are being sent and received.
46-
- Expired - Indicates that status is expired.
46+
- Expired - Indicates that SBC was sending SIP OPTIONS, but we haven't received any OPTIONS messages in the last 15 minutes.
4747
- Error - Indicates an error in OPTIONS exchange.
4848

4949
Status - The overall health status of a Trunk:
5050
- Unknown - Indicates an unknown health status.
5151
- Online - Indicates that SBC connection is healthy.
5252
- Warning - Indicates TLS or Ping is expired.
5353

54+
> [!NOTE]
55+
>If you've just configured a new trunk, it can take up to 15 minutes to update the status.
56+
5457
> [!IMPORTANT]
5558
> Before placing or receiving calls, make sure that SBC status is *Online*
5659

0 commit comments

Comments
 (0)