•
KX-NT500 series IP-PTs support P2P communication over SIP trunks. For information about the required
software version for KX-NT500 IP-PTs, consult your dealer. Other IP-PTs do not support this feature.
•
This PBX supports H.263/H.264 codecs for P2P video communication.
•
P2P communication using the T.38 protocol is supported for calls between IP extensions or IP extensions
and IP trunks. However, only SIP extensions and SIP trunks can be used.
•
A P2P connection cannot be made between an IP extension and SIP trunk if they are connected to different
sites.
In this case, the DSP resources of the PBX will be used to make the connection. For details, see "5.5.4 DSP
Resource Usage". Also, video connections are not possible.
[P2P Groups]
•
Telephones or SIP Trunks must belong to the same P2P group to establish a P2P connection. Telephones
or SIP Trunks at different sites can be assigned to the same P2P group.
•
Calls between IP extensions in different P2P groups are established via the DSP card in "DSP-through
mode". DSP-through mode is where only 1 DSP resource is required, regardless of the codec being used.
If a call is made between sites in a One-look network, 1 DSP resource is required at each PBX.
(
®
5.5.4 DSP Resource Usage)
•
Each PBX in a One-look network is also assigned to a P2P group. This assignment is used when a non-IP
telephone (e.g., an SLT) is on a call with an IP telephone at another branch. If the PBX and the IP telephone
both belong to the same P2P group, the connection is established from the PBX to the IP telephone directly.
Site 2
P2P Group 1
Router
Router
PBX
Site 1
PBX
DSP
SLT
•
Calls between extensions or SIP Trunks in different P2P groups will consume DSP resources, even if both
extensions or SIP Trunks belong to the same PBX (site).
•
To activate P2P communication between IP extensions and IP trunks, set
IP Extension - SIP Trunk
P2P
to enable.
•
The PBX configures P2P group settings for each SIP trunk port, and P2P communication is only allowed
when both parties belong to the same P2P group.
•
In an environment where P2P communication between IP extensions and IP trunks is not allowed due to
provider restrictions, set
IP Extension - SIP Trunk P2P
to disable, or assign different P2P group settings
between callers.
Note
During P2P communication, DTMF signals cannot be detected by the PBX since sound RTP packets are
processed directly between IP extensions and IP trunks. As a result, features that use DTMF detection
(e.g., DISA Call Transfer to Outside User) cannot be used. To use such features, change the settings to
allow for non-P2P calls, to create an environment where DTMF detection is available. Confirm with your
ITSP whether there are services which use DTMF detection and whether P2P communication is possible.
Installation Manual References
4.3.3 DSP S Card (KX-NS0110), DSP M Card (KX-NS0111), DSP L Card (KX-NS0112)
470
Feature Guide
5.2.3 Peer-to-Peer (P2P) Connection
Summary of Contents for KX-NS1000
Page 14: ...14 Feature Guide Table of Contents...
Page 15: ...Section 1 For Your Safety Feature Guide 15...
Page 18: ...18 Feature Guide 1 1 1 For Your Safety...
Page 19: ...Section 2 Call Handling Features Feature Guide 19...
Page 278: ...278 Feature Guide 2 28 2 Outgoing Message OGM...
Page 279: ...Section 3 Unified Messaging System Feature Guide 279...
Page 335: ...Section 4 Network Features Feature Guide 335...
Page 434: ...434 Feature Guide 4 3 6 Network ICD Group...
Page 435: ...Section 5 System Configuration and Administration Features Feature Guide 435...
Page 521: ...Section 6 Appendix Feature Guide 521...
Page 540: ...540 Feature Guide 6 5 4 PCMPR Software File Version 003 2xxxx...
Page 541: ...Feature Guide 541 Notes...