Page History
...
Caption | ||||
---|---|---|---|---|
| ||||
For details about devices that support Teams voice services, refer to the Yealink Teams client products page for the latest feature descriptions and specifications for available models.
...
Caption | ||||
---|---|---|---|---|
| ||||
Anchor | ||||
---|---|---|---|---|
|
Spacevars | ||
---|---|---|
|
...
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|
Anchor | ||||
---|---|---|---|---|
|
...
Caption | ||||
---|---|---|---|---|
| ||||
Spacevars | ||
---|---|---|
|
...
Caption | ||||
---|---|---|---|---|
| ||||
Note | ||||
---|---|---|---|---|
| ||||
Please note that a WAN outage has the potential to sever the connection not only between the on-premises Yealink Teams clients and Phone System, but also the connection between the on-premises Yealink Teams clients and the |
...
Caption | ||||
---|---|---|---|---|
| ||||
Note | ||
---|---|---|
| ||
The Yealink client device does not present the user with an indication that Phone System is unavailable to process a call establishment request from the Teams Client UI. If the user observes a condition that suggests Phone System is unavailable (e.g. a timeout on a call attempt, etc.):
|
...
Caption | ||||
---|---|---|---|---|
| ||||
SBC Configuration
Access the WebUI, and click the Settings tab.Anchor Step 1 Step 1 In the left navigation page, access SIP > Local Registrars Table.
Click
to add a row.In the Create SIP Local Registrar dialog box, type the desired identifier name and maximum number of registering clients for your new SIP local registrar instance. For our example deployment, the entered name is LocalReg .
Info title Registrar Provisioning Reference Information For details on SIP local registrar configuration, refer to Creating and Modifying SIP Local Registrars.
Click OK.
Caption 0 Figure 1 Newly Created Example SIP Local Registrar Instance "LocalReg", to Which Yealink Devices Will Register as SIP Endpoints
In the left navigation page, access SIP > Local/Pass-thru Auth Tables
Click ( ) to add a local pass-through authorization table.
In the Description dialog box, type the desired Local Pass-through Authorization Table name. For our example deployment, the name specified is Local registration table .
Click OK.
Caption 0 Figure 1 Newly Created Example Local Pass-through Authorization Table instance "Local Registration table", that will shortly define acceptable credentials for successful registration Info title Local Pass-through Authorization Tables Provisioning Reference Information For details on Local Pass-through Authorization Tables configuration, refer to Managing Local Pass-through Authorization Tables.
In the left navigation page, access SIP > Local/Pass-thru Auth Tables, and select (click) the new Local Pass-through Authorization Table just created. In example deployment, the entered name is Local registration table . The table displays under the tabs, with the note: -- Table is empty --Anchor Client Authorization Client Authorization
Click the Create Local Pass-through Authorization Entry ( ) iconAnchor Step 123 Authorization Step 123 Authorization Specify the following values for fields:
Caption 0 Table 1 Local Pass-through Authorization Entry Attributes Field
Required Entry
Type of Address of Record
Local, to signify the SBC is the registrant of record.
Address of Record URI
Specify the acceptable Address of Record (AOR) URI from a potential valid registering endpoint. In the example deployment, one such AOR URI is sip:30001 .
User Name
Specify the acceptable user name from the registering endpoint. In the example deployment, one acceptable User Name is 30001 .
Enter Password
Specify the password the registering endpoint must submit for successful registration.
Confirm Password
Type the same password as entered above for confirmation.
Info title Local Pass-through Authorization Table Entries Provisioning Reference Information For details on Local Pass-through Authorization Table Entry configuration, refer to Creating and Modifying Entries to Local Pass-through Authorization Tables.
Click OK.
Caption 0 Figure 1 Highlighted Example New Local Pass-through Authorization Entry
Repeat steps 1, 2, and 3 for each remaining possible valid registering endpoints. In the example deployment, steps 2 and 3 are repeated for Yealink device 30003 .Pagebreak Note title Use of Local Pass-through Authorization Table is Strongly Recommended Ribbon and Yealink strongly recommend the use of the optional Local Passthrough Authorization Table, especially for Azure-based SBC deployments. The use of the Local Passthrough Authorization Table deters the fraudulent use of your enterprise's SIP trunking services by unauthorized users.
Optional Step for encrypted SIP signaling: Create the TLS profile to define the cryptographic parameters for the SIP signaling between the subtended Yealink devices and the SBC.Anchor TLS Profile TLS Profile - In the WebUI, click the Settings tab.
In the left navigation pane, go to Security > TLS Profiles.
- Click the CreateTLS Profile ( ) icon at the top of the TLS Profile page.
Configure the parameters shown below. Leave all other parameters as default.
Caption 0 Table 1 New TLS Profile Entry Attributes for Registered Yealink SIP Clients ↔ SBC Communication Field
Required Entry
Description
Specify a descriptive name for the entry. A sample name may be Yealink SIP Client SBC Signaling
TLS Protocol
Set the administrative state to TLS 1.0 - 1.2
Mutual Authentication
Specify the authentication as Disabled.
Client Cipher List
Select a cipher value (this value must be supported by the subtended registered Yealink clients). See above for guidelines. Ribbon recommends TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384.
Validate Server FQDN Specify the validation as Disabled.
All other fields Please leave all default values as-is for basic SIP signaling encryption purposes. Click OK , and confirm the presence of the new TLS Profile entry.
Note title Use of Signaling and Media Encryption Strongly Recommended for Azure-based SBC Deployments While optional, Ribbon Communications and Yealink strongly recommend the use of TLS and SRTP for secure encrypted communication between the Yealink devices and the SBC, especially when the latter is deployed in the Azure public cloud. For more information, please refer above.
Info title TLS Profile Provisioning Reference Information For more information about creating new TLS Profile entries, refer to Managing TLS Profiles.
Access the WebUI, click the Settings tab.Anchor Step 2 Step 2
In the left navigation pane, go to Call Routing > Call Routing Table.Anchor new call route table new call route table Click ( ).
Enter a descriptive name in the Description text field; for this deployment example, the value is From Local SIP EP
Click OK.
Caption 0 Figure 1 Highlighted Example New Call Routing Table for Registered SIP Client-Initiated Call Processing Info title Call Routing Table Provisioning Reference Information For more information about creating call routing tables, refer to Managing Call Routing Tables.
In the WebUI, click the Settings tab.Anchor Transformation Table Transformation Table In the left navigation pane, go to Call Routing -> Transformation .
Click the Create (
) icon.In the Description dialog box, enter the desired Transformation Table name identifier for calling to the PSTN. For our example deployment, the entered name is from SIP to IMS .
Click OK .
Caption 0 Figure 1 Highlighted New Transformation Table for Registered SIP Clients to Call the PSTN Info title Transformation Table Provisioning Reference Information For details on Transformation Table configuration, refer to Managing Transformation Tables.
Anchor Transformation Table Entry Transformation Table Entry
In the left navigation page, go to Transformation, and select (click) the new Transformation Table just created. In example deployment, the entered name is from SIP to IMS . The table displays under the tabs, with the note: -- Table is empty --Pagebreak Click the Create ( ) icon
Type or select the following values to specify the passthrough of dialed digits from the subtended registered Yealink Survivability (SIP) client to the PSTN:
Caption 0 Table 1 New Transformation Table Entry Attributes for Registered SIP Clients to Reach the PSTN Field
Required Entry
Description
Specify a descriptive name for the entry. In the example deployment, the entered name is SIP to PSTN .
Admin State
Set the administrative state to Enabled.
Type (Input Field)
Specify the type for input as Called Address/Number.
Value (Input Field)
Specify an asterisk (.*) to indicate acceptance of any digits.
Type (Output Field)
Specify the type for output as Called Address/Number.
Value (Output Field)
Specify the value of output as \1 to indicate that digits received will be passed through to the outbound route without any change made.
Info title Transformation Table Entries and Digit Manipulation Provisioning Reference Information For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, please reference Creating Call Routing Logic with Regular Expressions.
Click OK .
Caption 0 Figure 1 Highlighted New Transformation Table Entry for Registered SIP Clients to Call the PSTN
In the WebUI, click the Settings tab.Anchor Transformation Table 2 Transformation Table 2 In the left navigation pane, go to Call Routing > Transformation.
Click the Create ( ) icon.
In the Description dialog box, enter the desired Transformation Table name identifier for intra-office calling. For our example deployment, the entered name is from SIP to SIP .
Click OK.
Caption 0 Figure 1 Highlighted New Transformation Table for Registered SIP Clients to Call Other SIP Clients in the Office Info title Transformation Table Provisioning Reference Information For details on Transformation Table configuration, refer to Managing Transformation Tables .
In the left navigation page, go to Transformation , and select (click) the new Transformation Table just created for intra-office calling. In example deployment, the entered name is from SIP to SIP . The table will appear under the tabs, with a note stating – Table is empty --Anchor Transformation Table Entry 2 Transformation Table Entry 2 Click the Create ( ) icon
Enter or select the following values into the pop-up window, to specify the pass through of dialed digits from the subtended registered Yealink Survivability (SIP) client to another subtended registered Yealink Survivability (SIP) client.
Caption 0 Table 1 Transformation Table Entry Attributes for Intra-Office Calling Field
Required Entry
Description
Please use a descriptive name for the entry. In the example deployment, the entered name is SIP to SIP .
Admin State
Enabled
Type (Input Field)
Called Address/Number
Value (Input Field)
Please enter a regular expression to confirm a private dial plan number that conforms to the private dial plan assigned to the registered SIP clients. In the example deployment, the entered expression is ^(3\d{4})$, signifying the called digits must be 5 characters in length, and must start with a 3.
Type (Output Field)
Called Address/Number
Value (Output Field)
\1 , signifying matching digits received will be passed through to the outbound route without change.
Info title Transformation Table Entries and Digit Manipulation Provisioning Reference Information For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, please reference Creating Call Routing Logic with Regular Expressions.
Click OK .
Caption 0 Figure 1 Highlighted New Transformation Table Entry for Registered SIP Clients to Call Other Registered SIP Clients
In the WebUI, click the Settings tab.Anchor anchorname100 anchorname100 In the left navigation pane, go to Call Routing > Call Routing Table and select the newly created Call Routing Table; for our example deployment, the newly created table is From Local SIP EP .
Click the Create Routing Entry ( ) icon to create the route for calling into the PSTN.
Enter the following values into the pop-up window:
Caption 0 Table 1 Call Routing Entry Attributes for Calling from Registered Yealink Devices to the PSTN Field
Required Entry
Description Enter an informative name in the text field; for our example deployment, the value is to IMS Admin State
Select Enabled Number/Name Transformation Table
Select the newly created Transformation Table instance to which calls from a subtended registered Yealink device will be routed to the PSTN. For the example deployment , the value is from SIP to IMS .
Destination Type Select Normal Destination Signaling Groups Select the PSTN-related Signaling Group. For the example deployment , the value is IMS All other fields Please leave all default values as-is for basic configuration purposes. Info title Call Routing Table Entry Provisioning Reference Information For details on call routing table entry configuration including modification of fields with default values, refer to Creating and Modifying Entries to Call Routing Tables.
Click OK .
Caption 0 Figure 1 Example Call Routing Entry Attributes for Calling from Registered Yealink Devices to the PSTN
Click the Create Routing Entry (
) icon once again to create the route entry for intra-office calling.Type or choose the following values:
Caption 0 Table 1 Call Routing Entry Attributes for Calling from Registered Yealink Devices to Other Registered Yealink Devices Field
Required Entry
Description Type a descriptive name in the text field; for the example deployment, the value is SIP TO SIP. Admin State
Select Enabled Number/Name Transformation Table
Select the newly created Transformation Table instance to which calls from a subtended registered Yealink device will be routed when attempting to reach another subtended registered Yealink device. For the example deployment , the value is from SIP to SIP .
Destination Type Select Registrar Table Destination Signaling Groups Select the newly created SIP Local Registrar-related Signaling Group to which the subtended registered Yealink devices are associated. For the example deployment , the value is LocalReg All other fields Leave all other default values as-is for basic configuration purposes. Click OK.
Caption 0 Figure 1 Example Call Routing Entry Attributes for Calling from Registered Yealink Devices to Other Registered Yealink Devices
Review and confirm the two new Call Routing Table entries in the newly created Call Routing Table.
Caption 0 Figure 1 New Priority Call Routing Table Entry
Access the WebUI, click the Settings tab.Anchor Step 3 Step 3 In the left navigation pane, go to Signaling Groups.
From the top menu bar, click Create Signaling Group and select SIP Signaling Group (note: for the
, select Add SIP SG )Spacevars 0 series3 Create the SIP Signaling Group using the following configuration:
Caption 0 Table 1 SIP Signaling Group Attribute Values for Registered Yealink Devices Field
Required Entry
Description Enter an informative name in the Description text field; for the example deployment , the value is LocalReg . Admin State Select Enabled Call Routing Table Select the recently created Call Routing Table Instance that will define routing for calls that originate from the subtended registered Yealink devices. For the example deployment, the value is from Local SIP EP . SIP Mode Select the Local Registrar value. Registrar Select the recently created SIP Local Registrar instance to which subtended Yealink devices will advertise their presence. For the example deployment , the value is LocalReg . Challenge Request Select Enable Local/Pass-thru Auth Table Select the recently created Local Pass-through Authorization Table that defines the credentials the subtended Yealink devices must present to the SBC to be successfully recognized (registered). For the example deployment , the value is Local registration table . Media List ID (Optional Step for for encrypted media)
If you specified a new TLS Profile ID , please select the Media List ID value associated with Phone System Signaling Group for SRTP communication with the registered subtended Yealink client devices. The value to be selected should be MS Teams Media List , originally created through the use of the Teams DR-related easy configuration wizard during the SBC setup . The contains SRTP cryptographic settings that can be used for
↔ subtended registered Yealink client device encrypted media exchange.Spacevars 0 product NOTE: For details on Media List ID configuration including the setup of attributes related to media encryption, please refer to Managing Media Lists and Managing SDES-SRTP Profiles .
Listen Port
Click the (
) icon to create a new instance of the SIP Listen Port, and update as follows:Option 1: For unencrypted
↔ subtended registered Yealink client device communication, please enter the Port value as 5060, the Protocol value as UDP, and the TLS Profile ID as N/A.Spacevars 0 product Option 2: For encrypted ↔ subtended registered Yealink client device communication (you must have specified a new TLS Profile ID entry earlier), please enter the Port value as 5061, the Protocol value as TLS, and the TLS Profile ID as the new entry created earlier (e.g. Yealink SIP Client SBC Signaling ) .
Federated IP/FQDN
Click the ( For our example deployment , the IP/FQDN is entered as XXX .0.0.0 , with the Netmask/Prefix as 255.0.0.0 , meaning the signaling group will accept communication with any host (i.e. Yealink device) that presents a host IP of anywhere from XXX.0.0.1 → XXX.255.255.254
) icon to create a new instance of the Federated IP/FQDN, and specify as follows to identify the networking IP addresses of your Yealink Teams client devices, supplied by the enterprise IT administrator.All other fields Please leave all default values as-is for basic configuration purposes. Info title Signaling Group Provisioning Reference Information For details on Signaling Group configuration attributes described above including modification of fields with default values, refer to Creating and Modifying SIP Signaling Groups.
Click OK . The new SIP Signaling Group (in the example deployment , named LocalReg ) may be expanded to present the following sample attributes.
Caption 0 Figure 1 Example SIP Signaling Group Configuration for Connection to Registered Yealink Teams Devices; Key User-Supplied values Highlighted
In the WebUI, click the Settings tab.Anchor Step 4 Step 4
In the left navigation pane, Call Routing -> Transformation .Anchor Transformation Table 3 Transformation Table 3 Click the Create (
) icon.In the Description dialog box, enter the desired Transformation Table name identifier for calls received from the PSTN and destined for a subtended Yealink device. For our example deployment, the entered name is from IMS to SIP .
Click OK .
Caption 0 Figure 1 Highlighted New Transformation Table for PSTN Call Routing to Registered Yealink Devices Info title Transformation Table Provisioning Reference Information For details on Transformation Table configuration, refer to Managing Transformation Tables.
In the left navigation page, go to Transformation , and select (click) the new Transformation Table just created. In example deployment, the entered name is from IMS to SIP . The table will appear under the tabs, with a note stating – Table is empty --Anchor Transformation Entry 3 Transformation Entry 3
Click the Create ( ) iconAnchor New 1 2 3 New 1 2 3 Enter or select the following values into the pop-up window, to specify the modification of dialed digits from the PSTN to reach a subtended registered Yealink Survivability (SIP) client:
Caption 0 Table 1 New Transformation Table Entry Attributes for a PSTN Call to Reach a Specific Registered Yealink Device Field
Required Entry
Description
Please use a descriptive name for the entry. In the example deployment, the entered name is Entry ID 1
Admin State
Enabled
Type (Input Field)
Called Address/Number
Value (Input Field)
Please enter a regular expression to define the Teams Phone Number assigned to the Yealink device with the survivability. In the example deployment, the entered expression is \+86XXXX604392, the Teams Phone Number assigned to the Yealink device that also carries the SIP phone number 30001 (latter used in the Survivability UI).
Type (Output Field)
Called Address/Number Value (Output Field)
Enter a regular expression to replace the Teams Phone Number dialed by the PSTN user to the assigned to the SIP phone number assigned to the Yealink device with the survivability. In the example deployment, the entered expression is 30001 , the Teams Phone Number assigned to the Yealink device that also carries the Teams Phone Number +86XXXX604392 (latter used in the Teams client UI).
Info title Transformation Table Entries and Digit Manipulation Provisioning Reference Information For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, please reference Creating Call Routing Logic with Regular Expressions.
Click OK.
Caption 0 Figure 1 New Transformation Table Entry for PSTN Calls to Reach Registered Yealink Device Repeat steps 1, 2 & 3 for each remaining possible registered Yealink device with both the Teams client and the Survivability (SIP) client. In the example deployment, steps 1, 2, and 3 are repeated for the Yealink device with the SIP phone number 30003 .
Caption 0 Figure 1 Completed Example New Transformation Table for PSTN Calls to Reach Registered Yealink Devices
In the left navigation pane, go to Call Routing > Call Routing Table and select the Call Routing Table originally created through the use of the Easy Configuration wizard (refer to Using the Easy Configuration Wizard) template for processing calls originating from the PSTN . For our example deployment, the table requiring the new entry is From IMS .Anchor updated route entry 100 updated route entry 100 Click the Create Routing Entry (
) icon.Enter the following values into the pop-up window:
Caption 0 Table 1 Key Call Routing Entry Attribute Values That Must be Explicitly Submitted by User Field
Required Entry
Description Enter an informative name in the text field; for our example deployment, the value is from IMS TO SIP Admin State
Select Enabled Number/Name Transformation Table
Select the newly created Transformation Table instance to which calls from the PSTN will be routed during survivability scenarios (i.e. when Phone System is unavailable). For the example deployment , the value is from IMS to SIP .
Destination Type Select Registrar Table Destination Signaling Groups Select the newly created SIP Local Registrar-related Signaling Group to which the subtended Yealink devices are associated. For the example deployment , the value is LocalReg All other fields Leave all default values as-is for basic configuration purposes. Caption 0 Figure 1 Call Route Entry Attributes for Example Teams Survivability-Related Call Route Entry Info title Call Routing Table Entry Provisioning Reference Information For details on call routing table entry configuration including modification of fields with default values, refer to Creating and Modifying Entries to Call Routing Tables.
Click OK and review the new Call Routing Table Entry related to survivability in the updated PSTN-related Call Routing Table from the left navigation pane.
Caption 0 Figure 1 Newly Created Teams Survivability Call Routing Entry in PSTN-Originated Call Routing Table
Access the WebUI, click the Monitor tab. Confirm the new SIP Signaling Group instance associated with the new SIP Local Registrar instance is active. For our example deployment , the new SIP Signaling Group instance is LocalReg .Anchor Step 5 Step 5 Caption 0 Figure 1 Example SIP Signaling Group Linked to Registered Yealink Devices Shows Active
Update Yealink Teams Client Devices to Register with the
Spacevars | ||||
---|---|---|---|---|
|
...
Caption | ||||
---|---|---|---|---|
| ||||
SBC Confirmation
...
In the left navigation page, access SIP > Local Registrars Table.
Confirm the SIP Local Registrar instance created to support survivability appears in the main body of the WebUI. For our example deployment, the the SIP Local Registrar instance is identified as LocalReg .
From the SIP Local Registrar instance presented in step 2, click Registered Users.
Caption 0 Figure 1 Registered Yealink Phones with Example SIP Local Registrar Confirm the presence of the Yealink device. For the example deployment, the correct user name (phone number) is 30001 and is clearly visible in the first row of the table.
Info title SIP Local Registrar Registered Users Reference Information For details surrounding the information available on the registered users, refer to Managing SIP Local Registrars.
...
Access a Yealink device's Survivability (SIP) UI. In the example deployment , one such device is the 30001 client.
Caption 0 Figure 1 Yealink Device Survivability (SIP) UI Place a call from the UI to the PSTN, and confirm two-way audio. Note the following indicators in the UI:
The green handset icon indicating a live call;
The Talking text indicating a live audio path.
Caption 0 Figure 1 Yealink Device Displaying Active Call in Survivability Mode with PSTN Client via the SBC
From the SBC, Confirm Call Completion to the PSTN Without Transiting Phone System
Access the WebUI, and click the Monitor tab.
Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are LocalReg (the signaling group to which the Yealink devices are registered), IMS (the PSTN-related signaling group), and Microsoft Teams.
Review the channel states for each signaling group, and confirm correct operation:
One channel is seized ( blue ) in the PSTN-related signaling group (for our example deployment, the IMS signaling group). Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device (e.g. call direction is outgoing, call originator has the same phone number as the Yealink device, called party number is the dialed PSTN number, etc.).
One channel is seized ( blue ) in the SIP local registrar-related signaling group (for our example deployment, the LocalReg signaling group). Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device.
All channels remain idle ( light green ) in Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group).
Caption 0 Figure 1 SBC Displaying (from the Monitor) an Active Call Between Yealink Client (in Survivability Mode) with PSTN Client via the SIP Trunk Info title Signaling Group Information Available From Monitor Reference Information For details surrounding the information available in the monitor related to signaling groups, refer to Monitoring Real Time Status . Note pop-ups must be enabled in your Internet browser to allow channel details to be presented.
Anchor | ||||
---|---|---|---|---|
|
Place Call from Yealink Device Survivability UI To Another Yealink Device Survivability UI
Access one SBC subtended Yealink device's Survivability (SIP) UI. In the example deployment, one such device is the 30001 client.
Caption 0 Figure 1 Yealink Device Survivability (SIP) UI Place a call from the Survivability (SIP) UI to a second Yealink device, using the SIP phone number to the second Yealink device. For the example deployment, the SIP phone number assigned to the second Yealink device is 30003.
Note title Please use SIP Phone Number to Reach Yealink Device's Survivability (SIP) UI Please dial from first Yealink device the SIP phone number associated with the second Yealink device, as opposed to the phone number associated with the Teams (SIP) client. By using the SIP phone number, the test confirms that the transformation and routing table entries associated with the SIP local registrar-related signaling group (for our example deployment , the LocalReg signaling group) have been correctly provisioned for intra-office dialing when Phone System is unavailable.
Answer the call from the Survivability (SIP) UI on the second Yealink device, and confirm two-way audio. Note the following indicators in the UI:
The green handset icon indicating a live call;
The Talking text indicating a live audio path.
Caption 0 Figure 1 Yealink Device Displaying Active Call in Survivability Mode with PSTN Client via the SBC
From the SBC, Confirm Call Completion Via the SIP Local Registrar
Access the WebUI, and click the Monitor tab.
Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are LocalReg (the signaling group to which the Yealink devices are registered), IMS (the PSTN-related signaling group), and Microsoft Teams .
Review the channel states for each signaling group, and confirm correct operation:
Two channels are seized and in connected state (channels will be blue ) in the SIP local registrar-related signaling group (for our example deployment, the LocalReg signaling group). Double-click either seized channels to ensure consistency between the channel details and the call placed from one Yealink device to the other.
All channels remain idle ( represented by the light green ) in the Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group) as well as the PSTN-related signaling group (for our example deployment, the IMS signaling group).
Pagebreak Caption 0 Figure 1 SBC Displaying (from the Monitor) an Active Call Between Yealink Client (in Survivability Mode) with PSTN Client via the SIP Trunk Info title Signaling Group Information Available From Monitor Reference Information For details surrounding the information available in the monitor related to signaling groups, refer to Monitoring Real Time Status.
...
Access the Yealink device's Teams UI.
Caption 0 Figure 1 Yealink Device Teams UI Place a call from the Teams UI to the PSTN, and confirm two-way audio. Note the active call indicators in the display.
Caption 0 Figure 1 Yealink Phone Displaying Active Call (in Teams Mode) with PSTN Client via the SBC
Pagebreak
From the SBC, Confirm Call Completion to the PSTN via Phone System
Access the WebUI, and click the Monitor tab.
Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are LocalReg (the signaling group to which the Yealink devices are registered), IMS (the PSTN-related signaling group), and Microsoft Teams .
Review the channel states for each signaling group, and confirm correct operation:
One channel is seized ( blue ) in the PSTN-related signaling group (for our example deployment, the IMS signaling group). Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device (e.g. call direction is outgoing, call originator has the same phone number as the Yealink device, called party number is the dialed PSTN number, etc.).
One channel is seized ( blue ) in the Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group). Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device.
All channels remain idle ( light green ) in the SIP local registrar-related signaling group (for our example deployment, the LocalReg signaling group).
Caption 0 Figure 1 SBC Displaying (from the Monitor) an Active Call Between Yealink Client (in Teams Mode of Operation) with PSTN Client via the SIP Trunk
Anchor | ||||
---|---|---|---|---|
|
...
In the left navigation pane, go to Signaling Groups
From the main display, select the check box next to the Teams Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group) and click the Out of Service ( ) icon.
Confirm that the Phone System-related signaling group is out of service, through the Down indication in the Service Status field.
Caption 0 Figure 1 Example Teams Phone System-Related SIP Signaling Group in Out of Service State Info title SIP Signaling Group Operations Reference Information For details on SIP Signaling Group operation including enablement and disablement, refer to Creating and Modifying SIP Signaling Groups.
...
Access the Yealink device's Survivability (SIP) UI.
Caption 0 Figure 1 Yealink Device Survivability (SIP) UI Prior to Incoming Call Place a call from the PSTN to the Yealink device, using the Teams phone number assigned to the Yealink device. For the example deployment, the Teams phone number assigned to the Yealink device with the 30003 SIP-related number is +86XXXX604393.
Note title Please use Teams Phone Number to Reach Yealink Device's Survivability (SIP) UI Please dial from the PSTN the phone number required to reach the Teams client on the Yealink device, as opposed to the phone number associated with the Survivability (SIP) client. By using the Teams client phone number, the test confirms that the transformation table entries associated with the PSTN signaling group (for our example deployment, the IMS signaling group) have been correctly provisioned for survivability routing.
Confirm an incoming call is presented in the Survivability (SIP) UI. Note the alerting indication.
Caption 0 Figure 1 Yealink Device Displaying Incoming Call from PSTN Client Access the SBC's WebUI, and click the Monitor tab.
Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are LocalReg (the signaling group to which the Yealink devices are registered), IMS (the PSTN-related signaling group), and Microsoft Teams .
Review the channel states for each signaling group, and confirm correct operation:
The PSTN-related signaling group (for our example deployment, the IMS signaling group) presents an alerting indication ( magenta ) in a single channel. Double-click the seized channel to ensure consistency between the channel details and the call placed from the PSTN (e.g. call direction is incoming, called digits are the Teams client number of the 30003 endpoint, calling party number is the PSTN endpoint, etc.).
The SIP local registrar-related signaling group (for our example deployment, the LocalReg signaling group) presents an alerting indication ( magenta ) in a single channel. Double-click the seized channel to ensure consistency between the channel details and the call placed from the PSTN (e.g. call direction is incoming, called digits are the Teams client number of the 30003 endpoint, calling party number is the PSTN endpoint, etc.).
All channels remain out of service ( gray ) in the Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group).
Caption 0 Figure 1 SBC displaying (from the Monitor) a call attempt from the PSTN to a Yealink device, Using a Teams client #
Answer Call and Confirm Connection
From the Yealink device's survivability (SIP) UI, answer the call and confirm two-way audio. Note the following indicators in the UI:
The green handset icon indicating a live call;
The Talking text indicating a live audio path.
Caption 0 Figure 1 Yealink Device Displaying Active Call in Survivability Mode with PSTN Client
Access the SBC's WebUI, and click the Monitor tab.
Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are LocalReg (the signaling group to which the Yealink devices are registered), IMS (the PSTN-related signaling group), and Microsoft Teams .
Review the channel states for each signaling group, and confirm correct operation:
The PSTN-related signaling group (for our example deployment, the IMS signaling group) presents a connected indication ( blue ) in the channel that previously presented the alerting indication. Double-click the seized channel to ensure consistency between the channel details and the call placed from the PSTN (e.g. call direction is incoming, called digits are the Teams client number of the 30003 endpoint, calling party number is the PSTN endpoint, etc.).
The SIP local registrar-related signaling group (for our example deployment, the LocalReg signaling group) presents a connected indication ( blue ) in the channel that previously presented the alerting indication. Double-click the seized channel to ensure consistency between the channel details and the call placed from the PSTN (e.g. call direction is incoming, called digits are the Teams client number of the 30003 endpoint, calling party number is the PSTN endpoint, etc.).
All channels remain out of service ( gray ) in the Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group).
Caption 0 Figure 1 SBC displaying the connected call from the PSTN to a Yealink device, Using a Teams client #
Anchor | ||||
---|---|---|---|---|
|
...
Access the Yealink device's Teams UI.
Caption 0 Figure 1 Yealink Device Teams UI Place a call from the PSTN to the Yealink device, using the Teams phone number assigned to the Yealink device. For the example deployment, the Teams phone number assigned to the Yealink device with the 30003 SIP-related number is +86XXXX604393.
Note title Please use Teams Phone Number to Reach Yealink Device's Survivability (SIP) UI Please dial from the PSTN the phone number required to reach the Teams client on the Yealink device, as opposed to the phone number associated with the Survivability (SIP) client. By using the Teams client phone number, the test confirms that the routing table entries associated with the PSTN signaling group (for our example deployment, the IMS signaling group) have been correctly provisioned to prioritize call routing to Phone System when the latter is available for processing calls.
Confirm an incoming call is presented in the Teams UI. Note the alerting indication.
Caption 0 Figure 1 Yealink Device Displaying Incoming Call from PSTN Client in Teams UI Answer the call, and confirm two-way audio.
Caption 0 Figure 1 Yealink Phone Displaying Active Call (in Teams Mode) with PSTN Client via the SBC
From the SBC, Confirm Call Completion via Phone System
...
Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are LocalReg (the signaling group to which the Yealink devices are registered), IMS (the PSTN-related signaling group), and Microsoft Teams.
Review the channel states for each signaling group, and confirm correct operation:
One channel is seized ( blue ) in the PSTN-related signaling group (for our example deployment, the IMS signaling group). Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device (e.g. call direction is incoming, called party number has the same phone number as the Yealink device, calling party number is the PSTN number from which you made the call, etc.).
One channel is seized ( blue ) in the Phone System-related signaling group (for our example deployment, the Microsoft Teams signaling group). Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device.
All channels remain idle ( light green ) in the SIP local registrar-related signaling group (for our example deployment, the LocalReg signaling group).
Caption 0 Figure 1 SBC Displaying (from the Monitor) an Active Call Between Yealink Client (in Teams Mode of Operation) with PSTN Client via the SIP Trunk
Success
If all test cases are successfully completed, Teams client survivability is correctly provisioned and operational. If any test cases fail, please revisit all prerequisites and provisioning.
...