Setup Reference Guide for KX-NS Series
(Tested with NS700 Ver8.03)
"Call2Teams” SIP Extension
Panasonic
Version 1.0 (BCBU-CNS) 24.August, 2020
Introduction
This document is a reference for configuring "Call2Teams" integration and SIP Extension onto KX-NS Series systems and includes the settings required for Microsoft Teams. Call2Teams is a service that bridges between your PBX service and Microsoft Teams on Office 365. The service is designed to connect to your PBX using the standard 'SIP Registration' method, the same way as a Panasonic Mobile Softphone via Media Relay Gateway (MRG). In practice, there may be changes required to your PBX or network to create a successful connection. This document sets out the process you can run through to configure and validate your PBX connection so that Call2Teams can connect successfully.
Audience for this document
This document is provided for customers to understand and configure their PBX for access by the Call2Teams service. It is expected the customer will be able to call upon the following resources and experience:
- Networking and firewall configuration
- PBX configuration and management
- SIP device configuration (phone/softphone)
- Microsoft Teams basic configuration (PowerShell skills are not required)
Customers often need to involve the organization or person that maintains and configures their phone system.
Attention
This document was created based on the results of test environment accounts. Panasonic cannot guarantee SIP Extension operation in all environments, however as a result of completing this Inter-Operability Test Panasonic will provide technical support for any issues experienced an assist as far as possible in providing a resolution. Please obtain relevant information from Qunifi/Call2Teams, and Microsoft Teams before configuration of Call2Teams integration and SIP Extension.
Panasonic will not be held liable for any information provided in this guidance document. Information used in this document is for interoperability testing. Information and Specifications in this document are subject to change without notice.
Network Topology
The network topology illustrates the connection between various components for Call2Teams integration. It shows the flow from the Internet, connecting to Call2Teams and Microsoft Office 365. The PBX (Panasonic KX-NS Series) connects to Call2Teams via SIP Registration, Media, and Signaling protocols. The PBX is also connected to the PSTN via a SIP Carrier. The Media Relay Gateway (MRG) Function is integral to the PBX. The system supports different endpoints, including a standard Digital Phone (e.g., Extension 101), a Teams SIP Phone (e.g., Extension 102), and another Teams SIP Phone (e.g., Extension 303). Microsoft Teams integrates with Microsoft Office 365, enabling MS Direct Routing and MS Phone System functionalities.
Environment
- Call2Teams: One-Click 2nd Gen
- Panasonic PBX: KX-NS700 ver:8.03
- Microsoft Teams: 1.300.19565
- Microsoft Office 365 E5 Trial
Note
Specific notes or disclaimers related to the environment setup.
(1) Enabling Remote Access to PBX
Call2Teams connects to your phone system from the Internet. You should configure access to your phone system to connect to the PBX. This document provides guidelines for your IT admin to configure the firewall.
1.1 Connection topology
The PBX is typically on an internal network, with a firewall or router performing Network Address Translation (NAT) between the public internet address and internal network addresses. This allows specific traffic types from the internet to be redirected to the PBX, enabling internet devices to communicate with it.
1.1.1 PBX behind firewall
PBXs behind a firewall require specific redirections for internet-based devices to traverse the firewall. Typically, two sets of redirections are needed:
- SIP Signaling: Standard is Protocol = UDP, Port = 5060. A different port may be used for SIP Extension via MRG at the WAN port (e.g., WAN SIP 35963 forwards to PBX LAN SIP 5060).
- MEDIA: PBXs use Protocol = UDP, Port range = 16000-16511 (dependent on installed DSP cards).
1.2 Firewall Rules
To restrict public access to the PBX, configure firewall rules. For signaling, allow traffic from Call2Teams SBC IP addresses on the specified ports using the chosen transport protocol (UDP for UDP, TCP for TCP or TLS).
The following SBCs are assigned to this service: 3.11.215.246:10380, 34.200.40.117:13370. If filtering SIP signaling traffic based on source IP addresses, add all listed IPs to the appropriate whitelist. Media traffic may originate from additional IP addresses.
(2) Configuring PBX to Remote SIP Extension
2.1 Creating SIP accounts on PBX
- Login as "INSTALLER".
- Navigate to [System Property] and select [Site].
2.1.3 [Media Relay] Tab – [Common]
Configure the following settings:
- NAT - External IP Address/FQDN: Enter the assigned public IP address (e.g., 10.0.0.1).
- NAT - SIP Proxy server Port No: Enter the port number (e.g., 35963).
When using DDNS
- NAT - External IP Address/FQDN: Enter the DDNS hostname (e.g., call2test.pbx.jp).
- DNS Interval Time (min): Leave at 10.
- NAT - SIP Proxy server Port No: Enter the port number (e.g., 35963).
Click [Apply]. No system reset is needed.
2.1.5 Move over [V-SIPEXT32] and then select [Port Property]
Navigate to the SIP Extension Port Property settings.
2.1.6 [Main] Tab
- Extension Number: Enter the desired extension number (e.g., 303).
- Password: Enter a strong password (e.g., PaSsWoRd34567890).
The following table shows example configurations:
No. | Shelf | Slot | Port | Extension Number (SIP Username) | Password | Connection Type | SIP Phone IP Address Method | Current MWI |
---|---|---|---|---|---|---|---|---|
1 | Virtual | 6 | 1 | 301 | PaSsWoRd12345678 | OUS | 0.0.0.0 | Unsolicited |
2 | Virtual | 6 | 2 | 302 | PaSsWoRd23456789 | OUS | 0.0.0.0 | Unsolicited |
3 | Virtual | 6 | 3 | 303 | PaSsWoRd34567890 | OUS | 0.0.0.0 | Unsolicited |
4 | Virtual | 6 | 4 | 304 | PaSsWoRd12345678 | OUS | 0.0.0.0 | Unsolicited |
5 | Virtual | 6 | 5 | 310 | PaSsWoRd34567890 | OUS | 0.0.0.0 | Unsolicited |
2.1.7 [Location/P2P] Tab
- Phone Location: Select "Remote + Local".
- Panasonic SIP Phone only: Select "No".
Click [OK] to apply the changes.
(3) Call2Teams Configuration to Work with Panasonic PBX
Once the PBX is enabled for remote access and SIP credentials are created, the Call2Teams service needs to be configured to connect to the PBX. This involves two areas: Service-level configuration for user connection and Per-user configuration for device registration.
After registration, you will receive an Invitation email; click the [Accept Invitation] button.
3.1 Access to Call2Teams Portal
Visit: https://admin.call2teams.com/portal/
- Login: o365_admin@customerdomain.onmicrosoft.com (Example)
- Password: Enter your o365 password.
Click [Sign in].
3.2 Configure the connection to your PBX
In the Call2Teams portal, navigate to the Services tab for overall configuration. Select the appropriate PBX template (e.g., "Panasonic KX-NS and NSX Series"). If your PBX is not listed, choose 'Custom' or 'Not listed'.
3.3 Services PBX
Go to the [PBX] Tab.
Select [Panasonic KX-NS and NSX Series] from the pull-down menu.
3.4 How to complete the PBX configuration form
Fill in the following PBX settings:
- Service Name: Customer PBX-1 (For Example) *Reference only
- Country & State/Province: Select Japan (For Example). This ensures optimal server location for call quality and availability.
- SIP Domain: Enter the PBX local IP address (e.g., 192.168.10.101). Do not include a port number.
- SIP Proxy: Enter the IP address or public hostname to reach the PBX (e.g., call2test.pbx.jp:35963 or Assigned public IP address: 35963). A port number can be appended with a colon.
- Authentication Type: Leave "Registration".
- Calling Policy: Manage Teams Calling Policy.
- Teams Voicemail: Leave "Allow Voicemail".
- Music On Hold: Teams Hold Music (Default) or PBX Hold Music (If needed).
- Expiry (seconds): Leave "BLANK" (Default).
- Protocol: Leave "UDP" (Default).
- Propagate Refer: Leave "Teams handles transfers" (Default).
- Suppress Contact Data Param: Leave "Yes" (Default). Set to 'No' for single-organization PBXs with a single public IP if it hinders function.
- Encrypt Media: Leave "No" (Default).
- Override Codecs: Leave PCMA(G.711), PCMU(G.711), G729. You can reorder these to set preference.
- Outside line prefix: Leave "BLANK". This prepends a prefix for dialing outside lines, simplifying dialing for Teams users.
- E164 Number Format: Select "Localized" (For Example). Teams uses E164 format (+country code).
- E164 Number Translation: For Japan (dialing country code 81):
- Outbound International Prefix: Enter "010" (For Example).
- Outbound National Prefix: Enter "0" (For Example).
- Inbound International Prefix: Leave "BLANK".
- Inbound National Prefix: Leave "BLANK".
Click [Add PBX].
3.5 Additional configuration topics
3.5.1 Dialing Limitations
Be aware of Teams dialing rules:
- Numbers beginning with '0' are converted to full E164 numbers. Consider changing extension numbers that start with '0'.
- Many PBXs use feature codes starting with '*'. While most work in Teams, *11, *12, and *13 do not. Microsoft may reserve other star codes for future features. If using blocked codes, change them on the PBX.
3.6 Services Teams Sync Enable
Go to the [Teams] Tab. Check the Microsoft Office 365 domain and ensure the Sync Now checkmark is green. After enabling the service, data will sync between Call2teams and Microsoft Office 365.
For Microsoft Office 365 management, refer to Appendix (7) Microsoft Office 365 Admin Center “Free trial edition”.
(4) Creating Call2Teams Users (Teams and PBX SIP accounts)
User settings are configured in the Call2Teams service 'Users' tab to map Microsoft Teams users to SIP device credentials. A unique phone number (DID or extension) is required for each user. The country code is derived from the Office 365 user's country setting. SIP Usernames should not include the '@' symbol.
4.1 Creating Users (Teams and PBX SIP accounts) on Call2Teams
Go to [Users] and click [Add User].
4.2 Add User
Teams
- Select a User: Select the user from the list (e.g., oonishikiyoshi).
- Phone Number (Japan): Enter the phone number (e.g., +81 92 4331504).
Custom PBX
- SIP Username: Enter the username (e.g., 303).
- Auth Username: Enter the username (e.g., 303).
- Password: Enter the password (e.g., PaSsWoRd).
Click [Add].
4.3 Check Users Registration
Click [Sync Now]. Remember to click Sync again after user configuration to perform Office 365 configuration for those users.
4.4 SIP Registration indicators and error messages
The Users tab displays SIP registration status. A green indicator means normal operation. A red indicator shows an error, with a brief explanation on hover. Common messages and advice include:
Message | Advice |
---|---|
Unable to resolve URI | Either the SIP Proxy (if specified) or SIP Domain is incorrect. |
No response received after xx seconds | The PBX did not respond. Check the firewall and the SIP Proxy/Realm. Specify a port in the SIP Proxy if required. |
Authentication Failure | Usually means that the SIP Username, SIP Auth Username (if specified) or SIP Password are incorrect. |
Declined | |
Forbidden | It could be that the SIP Realm is incorrect if the PBX checks this. |
Invalid password | (Covered by Authentication Failure) |
Not found | (Covered by Authentication Failure) |
Proxy Authentication Required | (Covered by Authentication Failure) |
Unauthorized | (Covered by Authentication Failure) |
User unknown | (Covered by Authentication Failure) |
(5) How to use the Call2Teams with PBX
5.1 Teams with Call2Teams outgoing calls to PBX Extension and national line
Click [Calls] - [Dial a Number].
Extension Call:
Press [PBX Extension Number] and Click [Call]. You can also dial using the on-screen keypad.
National call:
Press [0 + National Number] and Click [Call]. Note: The '0' is typically the PBX CO line access number.
5.2 Teams with Call2Teams to international calls (+sign)
For international calls, long press [0/+] to bring up the '+' symbol, then enter the [International Number] and Click [Call].
To disconnect, click the Hung-up [?] button.
5.3 Teams with Call2Teams Incoming calls from PBX
Incoming calls appear as a pop-up window with Caller ID on your Teams interface. Click "Accept with Audio" to answer. To disconnect, click the Hung-up [?] button.
(6) Configure additional PBX option / Trouble Shooting
(1) Disconnection issue
Reason behind: Status un-match due to 183(SDP) reply for outgoing call.
Countermeasure: Enable System Option 10-7 (Requires login as Sales Company Mode).
(2) Become a call back state when talking
Reason behind: Issue related to "Override Codecs on Call2Teams" and PBX supported codecs.
Countermeasure: Choose supported codecs for PBX on Call2Teams. Supported codecs include PCMA (G.711), PCMU (G.711), and G.729.
Issue outline / Scenario (Override Codecs: Default, Leave blank)
- Making a call from Teams to a PBX extension or CO line.
- A pop-up window appears, resembling a call back on your Teams.
Important: Never press the "Accept with [?] Audio" button in this scenario, as it can cause voice issues for up to 30 minutes and continue sending RTP voice packets to the PBX (DSP), preventing normal use.
- Press "Decline Call" [?] button.
- Disconnect the call by the called party first, then hang up by Teams. CO calls may not disconnect properly if handled solely by Teams.
Note: This issue does not occur with incoming calls at Teams.
To avoid this issue, ensure the codecs selected in the Call2Teams portal match the PBX supported codecs.
Appendix (7) Microsoft Office 365 Admin Center “Free trial edition”
Preparation:
- Prepare an active personal email address (e.g., panasonic.test001@gmail.com).
- Obtain a Microsoft Office 365 E5 “Free trial” (includes a Microsoft Phone system).
- Consider the office 365 domain for testing (e.g., "bcbuo365".onmicrosoft.com).
7.1 Create a Microsoft office 365 E5 trial environment for Call2Teams Test
7.1.1 Access to Microsoft Office E5 Portal
Go to the Microsoft 365 E5 portal and click [Free trial].
7.1.2 How to Setup
Follow these steps to configure the Office 365 settings:
- 7.1.2.1 Personal email address
- 7.1.2.2 Register User Information
- 7.1.2.3 Create Admin User
Make domain for test (e.g., bcbuo365.onmicrosoft.com).
7.1.3 Sign in to Microsoft Office 365
Enter your personal email address as the admin and click [Sign in]. Then, sign in as the Microsoft Office 365 Admin user using your admin credentials. An initial Admin user needs to be registered.
7.1.4 Microsoft Office Home
Click [Admin] to access the Microsoft 365 Admin Center.
7.2 Microsoft 365 Admin Center (Home)
7.2.1 Add User
- Click [User] – [Add users] for Teams User.
- Enter [Surname], [Name], [Display name], and [Password]. Click [Next].
- Assign product licenses: Enable [Office 365 E5].
- Set options.
- Review and complete the user addition.
The following shows example user details:
Active User | Display Name | User Name | License |
---|---|---|---|
Oonishikiyoshi (Admin User) Sync: EXT303 | Oonishikiyoshi | oonishik365@bcbuo365.onmicrosoft.com | Office 365 E5 |
Panasonic.Call2Teams (General User) Sync: EXT310 | Panasonic.Call2Teams | Panasonic.Call2Teams@bcbuo365.onmicrosoft.com | Office 365 E5 |
7.3 Confirm Custom domain
- Click [Setup a custom domain].
- Confirm the Default domain and click [Management].
7.3.3 Confirm Domain Name (Default) and Status
Verify that the domain status is "Healthy".