This Application Note is a configuration guide for the Ribbon Core Session Border Controller (SBC) 5XX0 and 7XX0 series, and SBC SWe versions when connecting to Skype for Business 2015 (Skype 2015) and Virgin Media SIP Trunk.
This configuration guide supports features described on the Microsoft Technet https://technet.microsoft.com/ website.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between Ribbbon SBC 5XX0, Skype for Business 2015 and Virgin Media SIP Trunk.
Audience
This technical document is intended for telecommunication engineers, who are configuring both the Ribbon SBC and third-party product. Navigating the third-party as well as the Ribbon SBC Command Line Interface (CLI) is required. Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP are also necessary to complete the configuration and any needed troubleshooting.
This configuration guide is offered as a convenience to Ribbon customers. The specifications and information regarding the product in this guide are subject to change without notice. All statements, information, and recommendations in this guide are believed to be accurate, but are presented without warranty of any kind, express or implied, and are provided "AS IS." Users must take full responsibility for the application of the specifications and information in this guide.
The following equipment and software were used for the sample configuration provided:
Requirements
Equipment | Software Version | |
---|---|---|
Ribbon | Ribbon SBC 5200 | V06.01.00-R002 |
EMA | V06.01.00-R002 | |
SonusDB | V06.01.00-R002 | |
OS | V03.03.00-R001 | |
BIOS | V02.06.00 | |
BMC | V03.14.00 | |
Third-party Equipment | Microsoft Skype for Business 2015 (Skype 2015) Mediation Server | 6.0.9319.0 |
Microsoft Skype for Business 2016 Client | 16.0.8827.2131 | |
VentaFax | 4.0.7577.44455 | |
Cisco SPA-3102 | 5.2.13(GW002) | |
Minicom 8000 |
Reference Configuration
The following reference configuration shows connectivity between Virgin Media SIP Trunk, Skype 2015, and Ribbon SBC 5XX0.
Reference Configuration Topology
For any questions regarding this document or the content herein, contact your maintenance and support provider.
Third-Party Product Features
The testing was executed with the Virgin Media test plan. The following features were tested:
The following new configurations are included in this section:
Select Topology Builder > Shared Components > PSTN Gateways
Define a new IP/PSTN Gateway
Define FQDN
Define Root Trunk
Select Control Panel > Voice Routing > Voice Policy
Edit Voice Policy
Select Control Panel > Voice Routing > PSTN Usage
View PSTN Usage
Select Control Panel > Voice Routing > Route
Edit Voice Route
Select Control Panel > Voice Routing > Trunk Configuration
Edit Trunk Configuration
Test Results
Interoperability | Test Scenario | Setup / Result Information | Result | Comment |
---|---|---|---|---|
IOP1 | Vendors eSBC response to SIP OPTIONS messages from SBC | No calls are required for this test. SIP trace to be captured for approx 60 seconds and checked for correct signaling. For each eSBC, the SBC will periodically send an OPTIONS request to the vendors eSBC to check if its SIP stack is reachable. If a SIP response 200 OK is received from the IP-PBX, the SIP trunk will be placed (or remain) in an In-Service state e.g. OPTIONS sip:ping@<ip-pbx_IP_Addr>:5060 SIP/2.0 | Pass | |
IOP2 | SBC response to SIP OPTIONS messages from vendor eSBC | No calls are required for this test. SIP trace to be captured for approx 60 seconds (depending on agreement) and checked for correct signaling. Vendors eSBC setup for Solution IP.Addr Mode Check that the eSBC can simultaneously send SIP OPTIONS messages to both the solution SBC addresses. | Pass | |
IOP4 | Basic test call from IP-PBX to PSTN line through SBC-A (using SBC-A IPV4 ip address). | IP-PBX line initiates call, Call is answered, IP-PBX line terminates call. Vendors eSBC setup for Solution IP.Addr Mode Check the wireshark trace and confirm that G.711 A law codec with 10 or 20ms packetisation is being used. | Pass | |
IOP5 | Basic test call from IP-PBX to PSTN line through SBC-B (using SBC-B IPV4 ip address) Vendor to configure eSBC so that it used secondary SBC (SBC_B) for this test. | IP-PBX line initiates call, Call is answered, IP-PBX line terminates call. Vendors eSBC setup for Solution IP.Addr Mode Check the wireshark trace and confirm that G.711 A law codec with 10ms or 20ms packetisation is being used. | Pass | |
IOP7b | Called Number format - vendors eSBC to soft switch number normalization - Global Dial Plan Test eSBC capability to send the called number in one of the following Global number formats (user part of Request & To URIs) 0yyyyyyyyyy (where y refers to any number, calling party = national) | SBC to be configured for Global calling plan. IP-PBX line initiates call to PSTN line, Call is answered. Configure the eSBC to present the called number in the user part of the Request & To URIs to be sent in one of the following formats 0yyyyyyyyyy (where y refers to any number, calling party = national) | Pass | |
IOP8b | Calling Number format - vendors eSBC to soft switch number normalization - Global Dial Plan Test eSBC capability to send calling number in one of the following Global number formats (user part of FROM & PAI URIs) 0yyyyyyyyyy (where y refers to any number, calling party = national) | SBC to be configured for Global calling plan. IP-PBX line initiates call to PSTN line, Call is answered. Configure the eSBC to present the calling number in the user part of the From & PAI URIs to be sent in one of the following formats 0yyyyyyyyyy (where y refers to any number, calling party = national) | Pass with Caveat | This is a Pass with Caveat. The PAI header on the trusted side for the 2nd Invite is not being normalized. This is a known issue since the upgrade of our SBC and there is a case currently open with Ribbon (180115-660221). As far as Ribbon is concerned this is ok. |
IOP9b | Called Number format - soft switch to eSBC number normalization - Global Dial Plan Test eSBC capability of accepting the called number in one of the following Global number formats (user part of Request & To URIs) +44yyyyyyyyy (where y refers to any number, calling party = national) | SBC to be configured for Global calling plan. PSTN line initiates call to IP-PBX line, Call is answered. Configure the eSBC to accept the called number in the user part of the Request & To URIs in one of the following formats +44yyyyyyyyy (where y refers to any number, calling party = national) Also check to see that the INVITE contains Session-Expires header and that it is syntactically correct. Check for Supported Header and ensure 'timer' is supported. Ensure response in 200 OK is compatible with INVITE and check for Required Header and if it contains 'timer'. | Pass | |
IOP10b | Calling Number format - soft switch to eSBC number normalization - Global Dial Plan Test eSBC capability of accepting the calling number in one of the following Global number formats (user part of FROM & PAI URIs) +44yyyyyyyyy (where y refers to any number, calling party = national) | SBC to be configured for Global calling plan. PSTN line initiates call to IP-PBX line, Call is answered. Configure the eSBC to accept the calling number in the user part of the Request & To URIs in one of the following formats +44yyyyyyyyy (where y refers to any number, calling party = national) | Pass | |
IOP11 | Emergency Call Handling -IP-PBX Line to PSTN - UK Emergency call 999 | Call made from IP-PBX line to the Emergency services using 999. Call answered. | Pass | |
IOP12 | Emergency Call Handling -IP-PBX Line to PSTN - UK Emergency call 112 | Call made from IP-PBX line to the Emergency services using 112. Call answered, | Pass | |
IOP13 | Emergency Call Handling -IP-PBX Line to PSTN - UK Emergency call 18000 - Text Direct | Call made from IP-PBX line using a text direct set to the Emergency services using 18000. Call answered. | Pass |
|
IOP14 | IP-PBX Line to PSTN - call answer - Originator disconnect | Call made from IP-PBX line to PSTN line, Answer Call. | Pass | |
IOP15 | PSTN calls SIP #1, SIP #1 conferences in SIP #2 | Call made from IP-PBX line to PSTN line, Answer Call. | Pass | |
IOP16 | IP-PBX Line to PSTN - Busy subscriber | Call made from IP-PBX line to a busy PSTN line (without divert on busy) | Pass | |
IOP17 | IP-PBX Line to PSTN - No answer timeout test | Call made from IP-PBX line to a PSTN line (without divert on no answer) | Pass | Cancel message is coming from Skype for business and there is no option to change the timer for this on Skype for business. |
IOP18 | IP-PBX Line to PSTN - Subscriber not reachable Vendor to call 01189111111 | Call made from IP-PBX line to an invalid number. | Pass | |
IOP19 | PSTN Line to IP-PBX - call answer - Originator disconnect. | Call made from a PSTN line to an IP-PBX line, Answer Call. | Pass | . |
IOP20 | PSTN Line to IP-PBX - call answer - Terminator disconnect | Call made from a PSTN line to an IP-PBX line, Answer Call. | Pass | |
IOP21 | PSTN Line to IP-PBX - busy subscriber | Call made from PSTN line to a busy IP-PBX line (without divert on busy) | NoExec | Skype for business 2015/Lync does not support Busy because there it all the time activated call waiting on all lines so they cannot be busy, if voice mail is activated, calls are forwarded there after some timeout. |
IOP22 | PSTN Line to IP-PBX - No answer timeout test, Invoked by PBX | Call made from a PSTN line to an IP-PBX line (without divert on no answer) Wait for the IP-PBX to return no answer timeout response | Fail | SfB doesn't have the option for no answer, the call can be forwarded after xx (max 60) seconds towards different number or it will be terminated in VM. UM can be disabled for the particular user and in this case SfB will return 480 but this is normally not default behavior of SfB. |
IOP23 | PSTN Line to IP-PBX - subscriber not reachable | Call made from a PSTN line to an invalid number/unprogrammed DDI on the IP-PBX. | Pass | |
IOP24 | Verify CLIP service on IP-PBX line (incoming call from PSTN) | Call made from PSTN line to IP-PBX line. PSTN line is set to allow CLI presentation. | Pass | |
IOP25 | Verify CLIR service on IP-PBX line (incoming call from PSTN) | Call made from PSTN line to IP-PBX line. PSTN line is set to restrict CLI presentation. | Pass | |
IOP26 | Verify CLIP service on PSTN line (outgoing call from IP-PBX, From) | Ensure number used in From header is agreed with Virgin Media and entered into the soft switch database for screening purposes. Call made from an IP-PBX line to a PSTN line. Ensure that the eSBC allows presentation of its CLI using privacy-header (Privacy: none or privacy-header not present) Ensure that the expected CLI is presented to the PSTN line. | Pass | |
IOP27 | Verify CLIP service on PSTN line (outgoing call from IP-PBX, PAI/PPI) Vendor to ensure PAI number is different to that from which the call originates | Ensure number used in PAI/PPI header is agreed with Virgin Media and entered into the soft switch database for screening purposes. Call made from an IP-PBX line to a PSTN line. Ensure that the expected CLI is presented to the PSTN line. | Pass | |
IOP28 | Verify CLIR service on PSTN line (outgoing call from IP-PBX) | Ensure number used in From/PAI header is agreed with Virgin Media and entered into the soft switch database for screening purposes. Call made from an IP-PBX line to a PSTN line. Ensure that the eSBC restricts presentation of its CLI using privacy-header (Privacy: id or Privacy: user or Privacy: user;id) Ensure that CLI is NOT presented to the PSTN line. | Pass | |
IOP29 | Verify Call Forward Immediate (unconditional) on a IP-PBX line (Incoming call from PSTN, call forward terminates within IP-PBX) | Call made from a PSTN line to an IP-PBX line with call forward to a line within the same IP-PBX, Answer Call. Does the IP-PBX have configuration settings to send SIP status 181 messages to the soft switch? | Pass | |
IOP30 | Verify Call Forward Immediate (unconditional) on a IP-PBX line (Incoming call from PSTN, call forward terminates PSTN) | Call made from a PSTN line to an IP-PBX line with call forward to a line in the PSTN, Answer Call. | Pass | |
IOP31 | Verify Call Forward Busy on IP-PBX line (Incoming call from PSTN, call forward terminates within IP-PBX) | Call made from a PSTN line to an IP-PBX line with Call Forward Busy (or equivalent) to a line within the IP-PBX, Answer Call. | Pass | Skype for business 2015/Lync does not support Busy because there it all the time activated call waiting on all lines so they cannot be busy, if voice mail is activated, calls are forwarded there after some timeout. |
IOP32 | Verify Call Forward No-answer on IP-PBX line (Incoming call from PSTN, call forward terminates within IP-PBX) | Call made from a PSTN line to an IP-PBX line with Call Forward No-answer (or equivalent) to a line within the IP-PBX, Answer Call. | Pass | |
IOP33 | Verify Call Hold Service on IP-PBX (Incoming call from PSTN) | Call made from a PSTN line to an IP-PBX line with Call Hold, Answer call. | Pass | |
IOP34 | Verify 3-party conference service on IP-PBX (Incoming call from PSTN, 3rd party within IP-PBX) | Call made from a PSTN line to an IP-PBX line with 3-party conference, Answer call. | Pass | When conference is created, it means that all users are connected to same room and it isn’t treated as a normal basic call even if there is just one user, all others have been released, this last user has to cancel the call manually and it will not be disconnected automatically from the Skype server. |
IOP35 | Verify 3-party conference service on IP-PBX (Incoming call from PSTN, 3rd party PSTN) | Call made from a PSTN line to an IP-PBX line with 3-party conference, Answer call. | Pass | When conference is created, it means that all users are connected to same room and it isn’t treated as a normal basic call even if there is just one user, all others have been released, this last user has to cancel the call manually and it will not be disconnected automatically from the Skype server. |
IOP36 | Verify do-not-disturb service on IP-PBX line (Incoming call from PSTN) | Does not ring Record the SIP status received from IP-PBX | Pass with Caveat | In normal scenario when UM is active for specifed user and the status of that user is set to DND, the call will be forwarded to VM. |
IOP37 | Verify Call park service on IP-PBX line (Incoming call from PSTN) | Call made from a PSTN line to IP-PBX line A with Call Park (or equivalent) feature active, Answer call. | Pass | |
IOP38 | Verify Call Waiting on an IP-PBX line, involving a PSTN line | Call made from PSTN line A to an IP-PBX line with Call Waiting active, Answer call. | Pass | |
IOP39 | Verify DTMF transmission from/to IP-PBX - Inband | Configure the IP-PBX/eSBC to send DTMF transmission in-band. Call made from IP-PBX line to a PSTN line, Answer call. Was the received DTMF tone reflective the length of time the key was pressed? | Pass | |
IOP40 | Verify DTMF transmission from/to IP-PBX - RFC 2833 - telephone-event | Configure the IP-PBX/eSBC to send DTMF transmission using RFC 2833 - telephone-event. Call made from IP-PBX line to a PSTN line, Answer call. Was the received DTMF tone reflective the length of time the key was pressed? | Pass | |
IOP41 | T.38 Fax transmission mode - PSTN to IP-PBX origination | Configure the ATA/IP-PBX/eSBC such that Fax transmission is sent using T.38 Version 0 Fax transmission mode. Ensure Wireshark trace shows that T.38 Fax Transmission is used. Check that the fax is transmitted and received as expected. | Pass | |
IOP42 | T.38 Fax transmission mode - IP-PBX to PSTN origination | Configure the ATA/IP-PBX/eSBC such that Fax transmission is sent using T.38 Version 0 Fax transmission mode. Ensure Wireshark trace shows that T.38 Fax Transmission is used. Check that the fax is transmitted and received as expected. | Pass | |
IOP43 | In-band G.711 Fax transmission mode - PSTN to IP-PBX origination | Configure the ATA/IP-PBX/eSBC such that Fax transmission is sent using in-band G.711 Fax transmission mode. Ensure Wireshark trace shows that in-band G.711 Fax Transmission is used. Check that the fax is transmitted and received as expected. | Pass | |
IOP44 | In-band G.711 Fax transmission mode - IP-PBX to PSTN origination | Configure the ATA/IP-PBX/eSBC such that Fax transmission is sent using in-band G.711 Fax transmission mode. Ensure Wireshark trace shows that in-band G.711 Fax Transmission is used. Check that the fax is transmitted and received as expected. | Pass with Caveat | Fax successful. The Caveat is regarding initial T.38 signal which is not used. |
IOP45 | Test of Call in progress audit function (response to in-call OPTIONS from soft switch to eSBC) & session refresh & response to UPDATE messages. | Call made from an IP-PBX line to a PSTN line, Answer call. Check wireshark trace to ensure that in-call OPTIONS are sent by the soft switch and that the eSBC responds with status 200OK. | Pass | |
IOP46 | Test of 4 simultaneous calls, 2 inbound, 2 outbound calls Vendor to configure eSBC for Round robin to ensure calls go to both Primary and secondary SBC | Configure the eSBC such that successive calls route to alternate SBCs (round robin, cyclic etc). | Pass | |
IOP47 | Test of eSBC endpoint restart-recovery | Restart the eSBC and ensure that, after recovery, inbound and outbound calls are successful. | Pass | |
IOP48 | Test of eSBC loss of Ethernet link and reconnection | Remove the Ethernet link between the eSBC and CE router. Leave in this condition for at least 3 minutes. Reconnect the Ethernet link and ensure that after approx 2 minutes inbound and outbound calls are successful. | Pass | |
IOP49 | Test of Primary SBC loss | ** Contact MSL engineer to carry out the following ** Call made from IP-PBX line to a PSTN Line. ** Contact MSL engineer to carry out the following ** | Pass |
Conclusion
These Application Notes describe the configuration steps required for Ribbon SBC 5XX0 to successfully interoperate with Skype for Business 2015 and Virgin Media SIP Trunk. All feature and serviceability with the exception of test case IOP21 (Busy subscriber) were completed with the exceptions/observations noted in Test Results. Three test cases (IOP 3, 6, and 50) from the Virgin Media test plan were not performed because they are no longer relevant to the tests being conducted.
Select Control Panel > Voice Routing > Trunk Configuration
Edit Trunk Configuration