SIP Trunk Compatibility Report NEC is pleased to verify that: Broadsoft / Broadcloud service Has successfully met the standards for SIP Trunk compatibility With the NEC products listed below. SL1100 / SL1000 Platforms NEC Enterprise Solutions has performed Interoperability Testing with the Switch (es) and Provider/Service listed above on the date specified. Please always refer to the appropriate SIP Trunk Compatibility Report Index and the latest edition of a specific Compatibility Report on BusinessNet before considering connection. If a Provider is no longer mentioned in the Index then the Compatibility Report has been withdrawn and connection will no longer be supported by NEC Enterprise Solutions. Test Completion Date: 9 th December 2016 Test Location: Name of Provider: Service Name Website: System Tested: Software Version: SIP Connection Mode: Test Plan Version: Tekvizion Broadsoft Broadcloud www.broadsoft.com SV9100 V5.00.50 (when tested) Carrier Mode (DNS) 5.0 Please refer to the following page(s) for further Information and Configuration Notes. Page 1 of 15
SIP Configuration Notes Broadsoft / Broadcloud service Use the specific configuration guide below as an example to configure an SV9100 PBX for connection to the service described above via SIP trunks. Recommended Software Versions SL1x00: CCPU Version 6.11 / PC Pro Version 6.00.01 Network Configuration If Public IP addresses are assigned to the SL1x00 VoIPDB and VoIP Gateways, then there should be no network configuration required. If there is one public IP address assigned, and NAT is used, it is necessary to configure Port Forwarding on the router and we recommend that SIP ALG is disabled: Port 5060 should be forwarded to the VoIPDB IP address as per command 10-12-09. If using multiple SIP Carriers then port 5062 should be used for the second profile in command 84-14-06. Broadcloud has not been tested in this mode. SIP Carrier does not need to change their port as 5060 is still correct. Port 10020 10147 should be forwarded to the VoIP Gateway IP addresses as per command 84-26-01 (Maximum assuming 32VOIPDB installed) NAT Router should be enabled in PRG10-29-21 and the Public IP address should be entered into PRG10-12-07. System Programming The following items should be changed all other items are considered irrelevant and as such left as default. Screenshots are for example purposes only and will have been taken from the PBX under test but will apply to the other PBXs listed on the cover of the Compatibility Report. Any differences in programming will be documented where necessary. 10-12-02 IP Address Must be in a different network range to IPLE IP Address (10-12-09) Must not be set as 0.0.0.0 10-12-01 Default Set according to customers network Gateway Subnet requirements Mask Advanced Items + VoIP + General Settings + IP Addressing + CCPU IP Network Setup 10-12-03 Default Set according to customers network Gateway requirements 10-29-21 NAT Router Set USED if using NAPT (Port forwarding on Router) 10-12-07 NAPT Router IP Enter the Public IP Address of the Local Network Address connection if NAT is required 10-12-09 IPLE/VOIPDB IP Set according to customers network Address requirements 10-12-10 IPLE/VOIPDB Set according to customers network Subnet Mask requirements Page 2 of 15
Advanced Items + VoIP 84-26-01 VoIP Set according to customers network + General Settings + IP Gateway IP SL1x00 requirements. The VoIP Gateway Addressing + VoIP Resource IP Address Address requires 1 x static IP address for the DSP resources. (32 or 64 DSP Resource options available) Page 3 of 15
Licensing The SL1x00 system requires a SIP Trunk license per Channel required. Maximum SIP Trunks supported is 32. As Per the next example please enable the correct amount of Trunks that matches the licenses applied. Advanced Items + 10-40-01 IP Trunk Enable this setting VoIP + SIP Networking + SIP IP Trunk Assignment Availability 10-40-02 IP Trunk Port Count Drop down and select the correct number of SIP Trunks required. Page 4 of 15
Advanced Items + VoIP + SIP 14-01-01 Trunk Name Label as required Networking + SIP Trunk Incoming 14-05 Trunk Group Allocate SIP Trunks to their own SIP Trunk group and assign all unused Trunks to group 25 Call Type 14-18-05 SIP Profile Set to Profile 1 or alternative profile if multiple SIP Carriers are required. 22-02 Incoming Call Trunk Setup Set to DID Advanced Items + VoIP + SIP 84-14-06 SIP Trunk Port Set to 5060 or as requested by the SIP provider Networking + 84-14-07 Session timer Set to 0 Profile 1 + SIP Profile 1 - Trunk General Settings + SIP Profile 1 - Trunk Basic Settings value 84-14-08 Minimum session timer value Set as 1800 Page 5 of 15
84-13-28 Audio Capability Priority Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Trunk General Settings + SIP Profile 1 - CODEC Settings 84-13-31 DTMF Set as 101 Payload Size 84-13-32 DTMF Set to RFC2833 Relay Mode 84-13-49 RTP Filter Set to disabled Set to customer s requirements (G.711 or G.729) Page 6 of 15
Broadcloud SIP Service supports Trunk call divert (trunk to trunk forwarding) with caller ID pass-through. Please make sure that only the required Trunks and Extensions are enabled for this service and toll restriction programming is in place to prevent toll fraud when enabled. Transfer CLI of HELD call is not supported on SL1x00 systems but is on the SV9100 Advanced Items + VoIP 14-01-13 Trunk To Enable for each line required + SIP Networking + Profile 1 + SIP Profile 1 - Trunk General Settings + SIP Profile 1 - Trunk Call Divert + SIP Profile 1 - Trunk to Trunk Settings Trunk Transfer 14-01-24 Trunk to Trunk Outgoing ID Through Mode 84-14-17 Call Forward Moved Temporarily Enable if required. This is only supported on direct trunk to trunk forwards not with external transferred call. Leave set as Disabled as not supported with the Broadcloud service Page 7 of 15
Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Trunk General Settings + SIP Profile 1 - Trunk Call Divert + SIP Profile 1 - Trunk to Trunk COS 20-11-12 Call Forward Off Premise Enable for the required class of service. We recommend using a new COS for the required extensions. Page 8 of 15
21-03 Trunk Group Routing For Trunks Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Trunk General Settings + SIP Profile 1 - Trunk Call Divert + SIP Profile 1 - Trunk to Trunk Outgoing Route Set to the required Trunk Group as the outgoing route for Trunk to Trunk calls. Advanced Items + VoIP + SIP Networking + 84-39-05 Option 5: Outgoing INVITE Message P- Set to Mode 3:Use P-Asserted-Identity Header Using User ID Information Profile 1 + SIP Profile 1 - Trunk General Settings + SIP Profile 1 - Trunk Message Customization Asserted-Identity/P- Preferred-Identity Usage 84-39-09 Option 9: Outgoing Call INVITE Message Set to Mode 1:Both the same. Page 9 of 15
Advanced Items + VoIP + SIP Networking + 10-28-01 Domain Name The BroadCloud Domain Name can be found on the Broadcloud MySite Trunk Profile 1 + SIP Profile 1 Group Configuration Page under the - Carrier Mode Trunk Group Settings section. Enter the (Domain Name) + SIP second part of the Domain as the Profile 1 - System Domain name (i.e customer.test.com) Information Setup test.com 10-28-02 Host Name The BroadCloud Domain Name can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. Enter the first part of the Domain as the Host name (i.e customer.test.com) customer 10-28-05 Domain Set to Domain Name Assignment Page 10 of 15
10-29-01 Outbound Default Enable Proxy 10-29-02 Inbound Default Enable Proxy 10-29-05 Registration Mode Set to Manual 10-29-08 DNS Mode Set to ON Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Carrier Mode (Domain Name) + SIP Profile 1 - Server Setup 10-29-09 DNS IP Address Enter a valid DNS Address for example 8.8.8.8 10-29-11 Registrar Domain The BroadCloud Outbound Proxy Name can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. 10-29-12 Proxy Domain Name The BroadCloud Outbound Proxy can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. Enter the second part of the Domain as the Proxy Domain name (i.e test.sipconnect.com) sipconnect.com 10-29-13 Proxy Host Name The BroadCloud Outbound Proxy can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. Enter the first part of the Domain as the Proxy host name (i.e test.sipconnect.com) test 10-29-14 Sip Carrier Choice Set to carrier choice B 10-29-15 Registration Expiry Set to 3600 Time 10-29-16 Register Sub Mode Disable setting 10-29-21 NAT Router Set USED if using NAPT (Port forwarding on Router) 10-12-07 NAPT Router IP Enter the public IP Address of your Address local network connection Page 11 of 15
10-36-01 Registration Enable ID 00 10-36-02 User ID Enter User ID as provided by BroadCloud. The BroadCloud username can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. 10-36-03 Authentication User ID Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Carrier Mode (Domain Name) + SIP Profile 1 - Primary Authentication Information 10-36-04 Authentication Password Enter Authenticated User ID as provided by BroadCloud. The BroadCloud username can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. Enter Authenticated Password as provided by BroadCloud. The BroadCloud password can be found on the Broadcloud MySite Trunk Group Configuration Page under the Trunk Group Settings section. Page 12 of 15
Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Carrier Mode (Domain Name) + SIP Profile 1 - Multiple Authentication Information 10-36-01 Registration Enable ID 01 to 31 if required for additional accounts assigned to user ID 00 (primary account) 10-36-02 User ID Enter additional User ID as required 10-36-03 Authentication User ID 10-36-04 Authentication Password Enter additional Authentication User ID as required Enter additional Authenticated Password as required Page 13 of 15
21-19 SIP Trunk CPN Number Advanced Items + VoIP + SIP Networking + Profile 1 + SIP Profile 1 - Carrier Mode (Domain Name) + SIP Profile 1 - Calling Party Number for Extensions Enter the full number including the area code for example Comments / Known Limitations DDIs can be configured if required, using the same procedure as for ISDN trunks If using Trunk to Trunk diverting then you can enable command 14-01-24 for each Trunk Port so that the calling party s CLI is passed through to the forwarding destination. Calling Party CLIP will be sent in the P=Asserted Identity Header in the Invite of the outbound call to the forwarding destination. SIP calls are sent en bloc. This means that the External Call Interdigit timer (PRG21-01-03) must expire before the call is set up. This can be reduced, but will have an impact on ISDN trunks also. The user can dial # to indicate end of dialling instead if required. The SIP trunk is registered to the SIP server and the expiration time is 3600 which is matched by the PBX configuration, SIP Server reply 200 OK with expires=60, PBX does send reregistration every 30 seconds. T.38 Fax is supported by both Broadsoft and the SL1x00 but there is currently an issue as the Broadcloud service requires a re-invite with digest information when t.38 is negotiated, this will be supported in a future release. Fax over IP has been tested successfully using G711 and this can be used as an alternative to T.38. Please set 15-03-03 to SPECIAL for the analogue extension port that has the fax connected. Tests were performed on the SV9100 PABX using software version 5.00.50 but is also compatible with the SL1x00 platform. Screen shots taken from the SL1100 PC Pro version 6.00.01 that is similar to the SL1000 PC Pro configuration screens. Page 14 of 15
NEC Enterprise Solutions cannot be held responsible for any regulatory non-compliance resulting from the use of this service. Document History Version Date 5.0 18 th January 2017 Description SIP Compatibility released for the SL1100 & SL1000 platforms based on the SV9100 test results. 5.1 25 th January 2017 Certification updated with additional comments by Broadcloud regarding the domain name and authentication requirements. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT SHALL NEC ENTERPRISE SOLUTIONS BE LIABLE FOR PERSONAL INJURY OR ANY INCIDENTAL, SPECIAL, DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION OR ANY OTHER COMMERCIAL DAMAGES OR LOSSES ARISING OUT OF OR RELATED TO YOUR USE OF THIS REPORT, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY (CONTRACT, TORT OR OTHERWISE) AND EVEN IF NEC ENTERPRISE SOLUTIONS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, DUE TO THE POSSIBILTY OF PROVIDERS MAKING SYSTEM CHANGES WHICH PROCEED THE COMPATIBILITY TESTING DETAILED IN THIS REPORT. IN NO EVENT SHALL NEC ENTERPRISE SOLUTIONS TOTAL LIABILITY TO YOU FOR ALL DAMAGES (OTHER THAN AS MAY BE REQUIRED BY APPLICABLE LAW IN CASES INVOLVING PERSONAL INJURY) EXCEED THE AMOUNT OF SEVENTY FIVE POUNDS ( 75). THE FOREGOING LIMITATIONS WILL APPLY EVEN IF THE ABOVE STATED REMEDY FAILS OF ITS ESSENTIAL PURPOSE. Page 15 of 15