Use this configuration information to connect a Ribbon Session Border Controller (SBC) with a Cisco Unified Communication Manager (CUCM) system and a PlusNet SIP trunk.
This configuration information is applicable to the Ribbon SBC SWe, SBC 5XX0 series and SBC 7XX0 series.
For more information about the Ribbon SBC, refer to your Ribbon SBC product documentation http://ribboncommunications.com/.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between a Ribbon Core SBC and Cisco Unified Communication Manager (CUCM).
This technical document is intended for telecommunication engineers that configure the Ribbon SBC Core aspects of the PlusNet SIP trunk group with the Cisco Unified Communication Manager (CUCM). This configuration requires access to a third-party server and the Ribbon SBC Web browser user interface, Embedded Management Application (EMA). Engineers require a basic understanding of IP routing, SIP, RTP, and TLS to configure and troubleshoot this solution.
The following table lists the equipment and software used to complete the tests that a PlusNet SIP trunk requires to connect with Ribbon software.
Equipment
Equipment | Software Version | |
---|---|---|
Ribbon Communications | Ribbon SBC SWe | V08.01.00-R000 |
Third-party Equipment | Cisco Unified Communication Manager (CUCM) | 12.0.1.21900-7 |
Cisco 7841 | sip78xx.11-7-1-17 | |
Fax Machine VentaFax | 7.6.243.616 |
The following topology illustrates the network connection between the Microsoft Skype for Business 2015, Virgin Media network and the Ribbon SBC Core.
Topology
For issues with connectivity or configuration between Ribbon SBC, PlusNet SIP trunk, and Cisco Unified Communication Manager (CUCM), contact Ribbon Support in either of the following ways:
We tested the following features between Cisco Unified Communication Manager (CUCM) and PlusNet:
The following new configurations are included in this section:
Select System > Security > SIP Trunk Security Profile
SIP Trunk Security Profile
Select Device > Device Settings > SIP Profile
SIP Profile
SIP Profile1
SIP Profile2
SIP Profile3
Select Device > Trunk > Add New
SIP Trunk
SIP Trunk1
SIP Trunk2
SIP Trunk3
Select Call Routing > Route/Hunt > Route Group > Add New
Route Group
Select Call Routing > Route/Hunt > Route List > Add New
Route List
Select Call Routing > Route/Hunt > Route Pattern > Add New
Route Pattern
Route Pattern1
The follow configuration applies to the SWe, 5xxx and 7xxx series Core SBC. It is included in the Cisco Unified Communication Manager and PlusNet SIP trunk configuration.
The following table provides information about the tests that Ribbon performed to complete all scenarios that PlusNet needs for their customers.
Interoperability Compliance Test Results
Test Number | Test Scenario | Setup / Test Results | Status | Comment |
---|---|---|---|---|
4.1 | Registration and authentication (registration mode) | The PBX is able to execute the correct resolution oft he DNS SRV record. | Pass | |
4.3 | Basic call | With the basic call tests, the standard call scenarios and the CLIP/CLIR features are tested.
| Pass | |
4.3.1 | Normal call | Outgoing call from PBX to PSTN
| Pass | |
4.3.1.1 | Normal call | The geographic number in the PAI header corresponds to the location 11 of the user | Pass | Is it possible to configure several PAI per SIP trunk? Yes |
4.3.1.2 | Normal call | Display of A-number in B-party CLIP (national PSTN) | Pass | |
4.3.1.3 | Normal call | Display of A-number in B-party CLIP (international PSTN) | Pass | |
4.3.1.4 | Normal call | Display of A-number in B-party CLIP (mobile) | Pass | |
4.3.1.5 | Normal call | Call to mobile | Pass | |
4.3.1.6 | Normal call | Suppression of A-number => CUR | Pass | |
4.3.1.7 | Normal call | Outgoing call from analog extension | Pass | |
4.3.1.8 | Normal call | Outgoing call (> 5 min.) => PSTN | Pass | Hold connection for 5 minutes => RTP still correct? Yes |
4.3.2 | Normal call | Incoming call from PSTN (national) => PBX
| Pass | |
4.3.2.1 | Normal call | Display of A-number => CLIP | Pass | |
4.3.2.2 | Normal call | Incoming call from mobile => PBX | Pass | |
4.3.2.3 | Normal call | Suppression of A-number => CLIR | Pass | |
4.3.3 | Normal call | Two simultaneous outgoing/incoming calls | Pass | |
4.3.4 | Normal call | Enabled feature DND (do not disturb) | Pass | |
4.3.5 | Normal call | Test call with codec G.711 | Pass | |
4.3.6 | Normal call | Test call with codec G.722 (only SIP <=> SIP) | Fail | PlusNet did not support G.722 |
4.3.7 | Normal call | Test call with codec G.729 | Pass | |
4.3.2.8 | Clip No Screening | Outgoing call from PBX to PSTN
| Pass | |
4.3.2.8.1 | Clip No Screening | Despite Clip No Screening the geographic number in the PAI header corresponds to the location of the user | Pass | Is it possible to configure several PAI per SIP trunk? Yes |
4.3.2.8.2 | Clip No Screening | Display of A-number (NoSClip) at B-party (PSTN) | Pass | |
4.3.2.8.3 | Clip No Screening | Display of A-number (NoSClip) at B-party (international PSTN; depending on the destination carrier, the NoSClip telephone number may not be displayed in this case) | Pass | |
4.3.2.8.3 | Clip No Screening | Call made from a PSTN line to an IP-PBX line with call forward to a line within the same IP-PBX, Answer Call.
| Pass | Does the IP-PBX have configuration settings to send SIP status 181 messages to the soft switch? Yes |
4.3.2.8.4 | Clip No Screening | Display of A-number (NoSClip) at B-party (mobile) | Pass | |
4.3.3.9 | Special call situations | Outgoing call PBX => PSTN
| Pass | |
4.3.3.10 | Special call situations | Outgoing call PBX=> PSTN
| Pass | |
4.3.3.11 | Special call situations | Outgoing call PBX => PSTN
| Pass | |
4.3.3.12 | Special call situations | Outgoing call PBX=> PSTN
| Pass | |
4.3.3.13 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.3.14 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.3.15 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.3.16 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.4.17 | Call clearing | Incoming / outgoing call; clearing after established call. Correct clearing on both sides
| Pass | |
4.3.4.18 | Call clearing | Interrupting the network connection of the SIP terminal device during a call
| Pass | |
4.4.19 | Hold | PBX => PSTN and PSTN => PBX
| Pass | |
4.4.19.1 | Hold | Putting an external call on hold in the PBX | Pass | |
4.4.19.2 | Hold | If applicable, MoH (music on hold) at A-party (PSTN) | Pass | |
4.4.19.3 | Hold | HOLD RETRIEVE: retrieving the external call | Pass | |
4.4.19.4 | Hold | Clearing the connection of the A-party while it is put on hold | Pass | |
4.4.20 | Hold | PBX => PSTN and PSTN => PBX
| Pass | |
4.4.20.1 | Hold | Putting an external call on hold in the PSTN | Pass | |
4.4.20.2 | Hold | If applicable, MoH (music on hold) at A-party (PBX) | Pass | |
4.4.20.3 | Hold | HOLD RETRIEVE: retrieving the external call | Pass | |
4.4.20.4 | Hold | Clearing the connection of the A-party while it is put on hold | Pass | |
4.5.21 | Call transfer | Internal call is transferred to external party: internal => PBX => external | Pass | |
4.5.21.1 | Call transfer | Call transfer from PBX party => PSTN party with announcement (attendant | Pass | |
4.5.21.2 | Call transfer | Call transfer from PBX party => PSTN party without announcement (blind transfer) | Pass | |
4.5.21.3 | Call transfer | Call transfer from PBX party => PSTN party without announcement (blind transfer)
| Pass | |
4.5.21.4 | Call transfer | Call transfer from PBX party => PSTN party without announcement (blind transfer)
| Pass | |
4.5.22 | Call transfer | Transferred call from external party to PBX: PSTN => PBX | Pass | |
4.5.22.1 | Call transfer | Call transfer from PSTN => PBX party with announcement (attendant transfer) | Pass | |
4.5.22.2 | Call transfer | Call transfer from PSTN => PBX party without announcement (blind transfer) | Pass | |
4.5.22.3 | Call transfer | Call transfer from PSTN => PBX party without announcement (blind transfer)
| Pass | |
4.5.22.4 | Call transfer | Call transfer from PSTN => PBX party without announcement (blind transfer)
| Pass | |
4.5.23 | Call transfer | Call from external party transferred to another external party: external => PBX => external | Pass | |
4.5.23.1 | Call transfer | PSTN => PBX party => PSTN with announcement (attendant transfer) | Pass | |
4.5.23.2 | Call transfer | PSTN => PBX party => PSTN without announcement (blind transfer) | Pass | |
4.5.23.3 | Call transfer | PSTN => PBX party => PSTN without announcement (blind transfer)
| Pass | |
4.5.23.4 | Call transfer | PSTN => PBX party => PSTN without announcement (blind transfer)
| Pass | |
4.6.24 | Call diversion | PBX party CFU to external party (PSTN) | Pass | |
4.6.24.1 | Call diversion | Internal call (CFU) => PSTN | Pass | |
4.6.24.2 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.24.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.24.4 | Call diversion | External => PBX party (CFU) => PSTN | Pass | |
4.6.24.5 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.24.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.25 | Call diversion | PBX party CFNR to external party | Pass | |
4.6.25.1 | Call diversion | Internal call (CFNR) => PSTN | Pass | |
4.6.25.2 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.25.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.25.4 | Call diversion | External => PBX party (CFNR) => PSTN | Pass | |
4.6.25.5 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.25.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.26 | Call diversion | PBX party CFB to external party | Pass | |
4.6.26.1 | Call diversion | Internal call (CFB) => PSTN | Pass | |
4.6.26.2 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.26.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.26.4 | Call diversion | External => PBX party (CFB) => PSTN | Pass | |
4.6.26.5 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.26.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.27 | Call diversion | External party (PSTN, mobile, etc.) CFU to PBX party: | Pass | |
4.6.27.1 | Call diversion | External (CFU) => PBX party | Pass | |
4.6.27.2 | Call diversion | PBX party busy, rejects call, does not answer | Pass | |
4.6.27.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.27.4 | Call diversion | External (CFNR) => PBX party | Pass | |
4.6.27.5 | Call diversion | PBX party busy, rejects call, does not answer | Pass | |
4.6.27.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.28 | Call diversion | External party (PSTN, mobile, etc.) CFB to PBX party: | Pass | |
4.6.28.1 | Call diversion | PBX party busy, rejects call, does not answer | Pass | |
4.6.28.2 | Call diversion | A-party clears in ring phase | Pass | |
4.6.29 | Call diversion | Call deflection: diversion during the ring phase | Pass | |
4.6.29.1.1 | Call diversion | Internal call PBX party CD => PBX party | Pass | |
4.6.29.1.2 | Call diversion | PBX party busy | Pass | |
4.6.29.1.3 | Call diversion | PBX party does not answer | Pass | |
4.6.29.1.4 | Call diversion | A-party clears in ring phase | Pass | |
4.6.29.2.1 | Call diversion | External call to PBX party CD => PBX party | Pass | |
4.6.29.2.2 | Call diversion | PBX party busy | Pass | |
4.6.29.2.3 | Call diversion | PBX party does not answer | Pass | |
4.6.29.2.4 | Call diversion | A-party clears in ring phase | Pass | |
4.6.29.3.1 | Call diversion | External call to PBX party CD => external PSTN party | Pass | |
4.6.29.3.2 | Call diversion | PSTN party busy | Pass | |
4.6.29.3.3 | Call diversion | PSTN party does not answer | Pass | |
4.6.29.3.4 | Call diversion | A-party clears in ring phase | Pass | |
4.7.30 | Call waiting | Incoming call during active internal call | Pass | |
4.7.30.1 | Call waiting | Call waiting tone | Pass | |
4.7.30.2 | Call waiting | Display of number of waiting party | Pass | |
4.7.30.3 | Call waiting | Acceptance of waiting call | Pass | |
4.7.30.4 | Call waiting | Putting the waiting call on hold | Pass | |
4.7.30.5 | Call waiting | Retrieve of waiting call | Pass | |
4.7.30.6 | Call waiting | Holding the 2nd call | Pass | |
4.7.30.7 | Call waiting | Terminating the active call | Pass | |
4.7.30.8 | Call waiting | Disregarding the waiting call | Pass | |
4.7.30.9 | Call waiting | Rejecting the waiting call | Pass | |
4.8.31 | 3-party conference | Establishing a conference according to the operating instructions of the PBX Internal - internal - external | Pass | |
4.8.31.1 | 3-party conference | Selecting a party (internal or external); 3rd party is put on hold
| Pass | |
4.8.32 | 3-party conference | Establishing a conference according to the operating instructions of the PBX | Pass | |
4.8.32.1 | 3-party conference | Selecting a party (external); 3rd party is put on hold
| Pass | |
4.9.33 | Pick up | Picking up a call from another extension of the PBX | Pass | |
4.10.34 | Call list | Entries in the call list
| Pass | |
4.10.35 | Call list | Call-back from call list
| Pass | |
4.11.36 | DTMF | DTMF support (G.711)
| Pass | |
4.11.37 | DTMF | DTMF support (G.729) | Pass | |
4.12.38 | Fax | Fax reception (G.711 only) | Pass | |
4.12.38.1 | Fax | Network-side T.38 re-invite rejected by PBX (response 488) or only G.711 codec is confirmed
| Pass | |
4.12.39 | Fax | Fax sending (G.711 only) | Pass | |
4.12.39.1 | Fax | Network-side T.38 re-invite rejected by PBX (response 488) or only G.711 codec is confirmed
| Pass | |
4.12.40 | Fax | Fax reception via T.38 | Pass | |
4.12.40.1 | Fax | Re-invite to T.38 by PBX or network
| Pass | |
4.12.41 | Fax | Fax sending via T.38 (not possible in conjunction with the encryption option) | Pass | |
4.12.41.1 | Fax | Re-invite to T.38 by PBX or network
| Pass | |
5.42 | Redundancy | Test of redundancy:
| Pass | |
5.42.1 | Redundancy | 1. Register all available PBX systems the Plusnet SBC. | Pass |
Ribbon successfully completed configuration and testing for the Ribbon SBC Core to interoperate with a Cisco Unified Communication Manager (CUCM) system and a PlusNet SIP trunk. All feature and serviceability issues were completed with the noted exceptions and observations.
Use this configuration information to connect a Ribbon Session Border Controller (SBC) with a Cisco Unified Communication Manager (CUCM) system and a PlusNet SIP trunk.
This configuration information is applicable to the Ribbon SBC SWe, SBC 5XX0 series and SBC 7XX0 series.
For more information about the Ribbon SBC, refer to your Ribbon SBC product documentation http://ribboncommunications.com/.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between a Ribbon Core SBC and Cisco Unified Communication Manager (CUCM).
This technical document is intended for telecommunication engineers that configure the Ribbon SBC Core aspects of the PlusNet SIP trunk group with the Cisco Unified Communication Manager (CUCM). This configuration requires access to a third-party server and the Ribbon SBC Web browser user interface, Embedded Management Application (EMA). Engineers require a basic understanding of IP routing, SIP, RTP, and TLS to configure and troubleshoot this solution.
The following table lists the equipment and software used to complete the tests that a PlusNet SIP trunk requires to connect with Ribbon software.
Equipment
Equipment | Software Version | |
---|---|---|
Ribbon Communications | Ribbon SBC SWe | V08.01.00-R000 |
Third-party Equipment | Cisco Unified Communication Manager (CUCM) | 12.0.1.21900-7 |
Cisco 7841 | sip78xx.11-7-1-17 | |
Fax Machine VentaFax | 7.6.243.616 |
The following topology illustrates the network connection between the Microsoft Skype for Business 2015, Virgin Media network and the Ribbon SBC Core.
Topology
For issues with connectivity or configuration between Ribbon SBC, PlusNet SIP trunk, and Cisco Unified Communication Manager (CUCM), contact Ribbon Support in either of the following ways:
We tested the following features between Cisco Unified Communication Manager (CUCM) and PlusNet:
The following new configurations are included in this section:
Select System > Security > SIP Trunk Security Profile
SIP Trunk Security Profile
Select Device > Device Settings > SIP Profile
SIP Profile
SIP Profile1
SIP Profile2
SIP Profile3
Select Device > Trunk > Add New
SIP Trunk
SIP Trunk1
SIP Trunk2
SIP Trunk3
Select Call Routing > Route/Hunt > Route Group > Add New
Route Group
Select Call Routing > Route/Hunt > Route List > Add New
Route List
Select Call Routing > Route/Hunt > Route Pattern > Add New
Route Pattern
Route Pattern1
The follow configuration applies to the SWe, 5xxx and 7xxx series Core SBC. It is included in the Cisco Unified Communication Manager and PlusNet SIP trunk configuration.
The following table provides information about the tests that Ribbon performed to complete all scenarios that PlusNet needs for their customers.
Interoperability Compliance Test Results
Test Number | Test Scenario | Setup / Test Results | Status | Comment |
---|---|---|---|---|
4.1 | Registration and authentication (registration mode) | The PBX is able to execute the correct resolution oft he DNS SRV record. | Pass | |
4.3 | Basic call | With the basic call tests, the standard call scenarios and the CLIP/CLIR features are tested.
| Pass | |
4.3.1 | Normal call | Outgoing call from PBX to PSTN
| Pass | |
4.3.1.1 | Normal call | The geographic number in the PAI header corresponds to the location 11 of the user | Pass | Is it possible to configure several PAI per SIP trunk? Yes |
4.3.1.2 | Normal call | Display of A-number in B-party CLIP (national PSTN) | Pass | |
4.3.1.3 | Normal call | Display of A-number in B-party CLIP (international PSTN) | Pass | |
4.3.1.4 | Normal call | Display of A-number in B-party CLIP (mobile) | Pass | |
4.3.1.5 | Normal call | Call to mobile | Pass | |
4.3.1.6 | Normal call | Suppression of A-number => CUR | Pass | |
4.3.1.7 | Normal call | Outgoing call from analog extension | Pass | |
4.3.1.8 | Normal call | Outgoing call (> 5 min.) => PSTN | Pass | Hold connection for 5 minutes => RTP still correct? Yes |
4.3.2 | Normal call | Incoming call from PSTN (national) => PBX
| Pass | |
4.3.2.1 | Normal call | Display of A-number => CLIP | Pass | |
4.3.2.2 | Normal call | Incoming call from mobile => PBX | Pass | |
4.3.2.3 | Normal call | Suppression of A-number => CLIR | Pass | |
4.3.3 | Normal call | Two simultaneous outgoing/incoming calls | Pass | |
4.3.4 | Normal call | Enabled feature DND (do not disturb) | Pass | |
4.3.5 | Normal call | Test call with codec G.711 | Pass | |
4.3.6 | Normal call | Test call with codec G.722 (only SIP <=> SIP) | Fail | PlusNet did not support G.722 |
4.3.7 | Normal call | Test call with codec G.729 | Pass | |
4.3.2.8 | Clip No Screening | Outgoing call from PBX to PSTN
| Pass | |
4.3.2.8.1 | Clip No Screening | Despite Clip No Screening the geographic number in the PAI header corresponds to the location of the user | Pass | Is it possible to configure several PAI per SIP trunk? Yes |
4.3.2.8.2 | Clip No Screening | Display of A-number (NoSClip) at B-party (PSTN) | Pass | |
4.3.2.8.3 | Clip No Screening | Display of A-number (NoSClip) at B-party (international PSTN; depending on the destination carrier, the NoSClip telephone number may not be displayed in this case) | Pass | |
4.3.2.8.3 | Clip No Screening | Call made from a PSTN line to an IP-PBX line with call forward to a line within the same IP-PBX, Answer Call.
| Pass | Does the IP-PBX have configuration settings to send SIP status 181 messages to the soft switch? Yes |
4.3.2.8.4 | Clip No Screening | Display of A-number (NoSClip) at B-party (mobile) | Pass | |
4.3.3.9 | Special call situations | Outgoing call PBX => PSTN
| Pass | |
4.3.3.10 | Special call situations | Outgoing call PBX=> PSTN
| Pass | |
4.3.3.11 | Special call situations | Outgoing call PBX => PSTN
| Pass | |
4.3.3.12 | Special call situations | Outgoing call PBX=> PSTN
| Pass | |
4.3.3.13 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.3.14 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.3.15 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.3.16 | Special call situations | Incoming call PSTN => PBX
| Pass | |
4.3.4.17 | Call clearing | Incoming / outgoing call; clearing after established call. Correct clearing on both sides
| Pass | |
4.3.4.18 | Call clearing | Interrupting the network connection of the SIP terminal device during a call
| Pass | |
4.4.19 | Hold | PBX => PSTN and PSTN => PBX
| Pass | |
4.4.19.1 | Hold | Putting an external call on hold in the PBX | Pass | |
4.4.19.2 | Hold | If applicable, MoH (music on hold) at A-party (PSTN) | Pass | |
4.4.19.3 | Hold | HOLD RETRIEVE: retrieving the external call | Pass | |
4.4.19.4 | Hold | Clearing the connection of the A-party while it is put on hold | Pass | |
4.4.20 | Hold | PBX => PSTN and PSTN => PBX
| Pass | |
4.4.20.1 | Hold | Putting an external call on hold in the PSTN | Pass | |
4.4.20.2 | Hold | If applicable, MoH (music on hold) at A-party (PBX) | Pass | |
4.4.20.3 | Hold | HOLD RETRIEVE: retrieving the external call | Pass | |
4.4.20.4 | Hold | Clearing the connection of the A-party while it is put on hold | Pass | |
4.5.21 | Call transfer | Internal call is transferred to external party: internal => PBX => external | Pass | |
4.5.21.1 | Call transfer | Call transfer from PBX party => PSTN party with announcement (attendant | Pass | |
4.5.21.2 | Call transfer | Call transfer from PBX party => PSTN party without announcement (blind transfer) | Pass | |
4.5.21.3 | Call transfer | Call transfer from PBX party => PSTN party without announcement (blind transfer)
| Pass | |
4.5.21.4 | Call transfer | Call transfer from PBX party => PSTN party without announcement (blind transfer)
| Pass | |
4.5.22 | Call transfer | Transferred call from external party to PBX: PSTN => PBX | Pass | |
4.5.22.1 | Call transfer | Call transfer from PSTN => PBX party with announcement (attendant transfer) | Pass | |
4.5.22.2 | Call transfer | Call transfer from PSTN => PBX party without announcement (blind transfer) | Pass | |
4.5.22.3 | Call transfer | Call transfer from PSTN => PBX party without announcement (blind transfer)
| Pass | |
4.5.22.4 | Call transfer | Call transfer from PSTN => PBX party without announcement (blind transfer)
| Pass | |
4.5.23 | Call transfer | Call from external party transferred to another external party: external => PBX => external | Pass | |
4.5.23.1 | Call transfer | PSTN => PBX party => PSTN with announcement (attendant transfer) | Pass | |
4.5.23.2 | Call transfer | PSTN => PBX party => PSTN without announcement (blind transfer) | Pass | |
4.5.23.3 | Call transfer | PSTN => PBX party => PSTN without announcement (blind transfer)
| Pass | |
4.5.23.4 | Call transfer | PSTN => PBX party => PSTN without announcement (blind transfer)
| Pass | |
4.6.24 | Call diversion | PBX party CFU to external party (PSTN) | Pass | |
4.6.24.1 | Call diversion | Internal call (CFU) => PSTN | Pass | |
4.6.24.2 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.24.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.24.4 | Call diversion | External => PBX party (CFU) => PSTN | Pass | |
4.6.24.5 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.24.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.25 | Call diversion | PBX party CFNR to external party | Pass | |
4.6.25.1 | Call diversion | Internal call (CFNR) => PSTN | Pass | |
4.6.25.2 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.25.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.25.4 | Call diversion | External => PBX party (CFNR) => PSTN | Pass | |
4.6.25.5 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.25.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.26 | Call diversion | PBX party CFB to external party | Pass | |
4.6.26.1 | Call diversion | Internal call (CFB) => PSTN | Pass | |
4.6.26.2 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.26.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.26.4 | Call diversion | External => PBX party (CFB) => PSTN | Pass | |
4.6.26.5 | Call diversion | PSTN party busy, rejects call, does not answer | Pass | |
4.6.26.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.27 | Call diversion | External party (PSTN, mobile, etc.) CFU to PBX party: | Pass | |
4.6.27.1 | Call diversion | External (CFU) => PBX party | Pass | |
4.6.27.2 | Call diversion | PBX party busy, rejects call, does not answer | Pass | |
4.6.27.3 | Call diversion | A-party clears in ring phase | Pass | |
4.6.27.4 | Call diversion | External (CFNR) => PBX party | Pass | |
4.6.27.5 | Call diversion | PBX party busy, rejects call, does not answer | Pass | |
4.6.27.6 | Call diversion | A-party clears in ring phase | Pass | |
4.6.28 | Call diversion | External party (PSTN, mobile, etc.) CFB to PBX party: | Pass | |
4.6.28.1 | Call diversion | PBX party busy, rejects call, does not answer | Pass | |
4.6.28.2 | Call diversion | A-party clears in ring phase | Pass | |
4.6.29 | Call diversion | Call deflection: diversion during the ring phase | Pass | |
4.6.29.1.1 | Call diversion | Internal call PBX party CD => PBX party | Pass | |
4.6.29.1.2 | Call diversion | PBX party busy | Pass | |
4.6.29.1.3 | Call diversion | PBX party does not answer | Pass | |
4.6.29.1.4 | Call diversion | A-party clears in ring phase | Pass | |
4.6.29.2.1 | Call diversion | External call to PBX party CD => PBX party | Pass | |
4.6.29.2.2 | Call diversion | PBX party busy | Pass | |
4.6.29.2.3 | Call diversion | PBX party does not answer | Pass | |
4.6.29.2.4 | Call diversion | A-party clears in ring phase | Pass | |
4.6.29.3.1 | Call diversion | External call to PBX party CD => external PSTN party | Pass | |
4.6.29.3.2 | Call diversion | PSTN party busy | Pass | |
4.6.29.3.3 | Call diversion | PSTN party does not answer | Pass | |
4.6.29.3.4 | Call diversion | A-party clears in ring phase | Pass | |
4.7.30 | Call waiting | Incoming call during active internal call | Pass | |
4.7.30.1 | Call waiting | Call waiting tone | Pass | |
4.7.30.2 | Call waiting | Display of number of waiting party | Pass | |
4.7.30.3 | Call waiting | Acceptance of waiting call | Pass | |
4.7.30.4 | Call waiting | Putting the waiting call on hold | Pass | |
4.7.30.5 | Call waiting | Retrieve of waiting call | Pass | |
4.7.30.6 | Call waiting | Holding the 2nd call | Pass | |
4.7.30.7 | Call waiting | Terminating the active call | Pass | |
4.7.30.8 | Call waiting | Disregarding the waiting call | Pass | |
4.7.30.9 | Call waiting | Rejecting the waiting call | Pass | |
4.8.31 | 3-party conference | Establishing a conference according to the operating instructions of the PBX Internal - internal - external | Pass | |
4.8.31.1 | 3-party conference | Selecting a party (internal or external); 3rd party is put on hold
| Pass | |
4.8.32 | 3-party conference | Establishing a conference according to the operating instructions of the PBX | Pass | |
4.8.32.1 | 3-party conference | Selecting a party (external); 3rd party is put on hold
| Pass | |
4.9.33 | Pick up | Picking up a call from another extension of the PBX | Pass | |
4.10.34 | Call list | Entries in the call list
| Pass | |
4.10.35 | Call list | Call-back from call list
| Pass | |
4.11.36 | DTMF | DTMF support (G.711)
| Pass | |
4.11.37 | DTMF | DTMF support (G.729) | Pass | |
4.12.38 | Fax | Fax reception (G.711 only) | Pass | |
4.12.38.1 | Fax | Network-side T.38 re-invite rejected by PBX (response 488) or only G.711 codec is confirmed
| Pass | |
4.12.39 | Fax | Fax sending (G.711 only) | Pass | |
4.12.39.1 | Fax | Network-side T.38 re-invite rejected by PBX (response 488) or only G.711 codec is confirmed
| Pass | |
4.12.40 | Fax | Fax reception via T.38 | Pass | |
4.12.40.1 | Fax | Re-invite to T.38 by PBX or network
| Pass | |
4.12.41 | Fax | Fax sending via T.38 (not possible in conjunction with the encryption option) | Pass | |
4.12.41.1 | Fax | Re-invite to T.38 by PBX or network
| Pass | |
5.42 | Redundancy | Test of redundancy:
| Pass | |
5.42.1 | Redundancy | 1. Register all available PBX systems the Plusnet SBC. | Pass |
Ribbon successfully completed configuration and testing for the Ribbon SBC Core to interoperate with a Cisco Unified Communication Manager (CUCM) system and a PlusNet SIP trunk. All feature and serviceability issues were completed with the noted exceptions and observations.