Difference between revisions of "Linking protocol eSSLv2"
From pubWiki-en
| Line 1: | Line 1: | ||
{{Warning|Essl v2 protocol introduced with version 6.40 is not compatible with the previous version eSSL v1 (do not work together, equally). Therefore, all PBXs in the system must be linked eSSL v1 or eSSL v2.}} | {{Warning|Essl v2 protocol introduced with version 6.40 is not compatible with the previous version eSSL v1 (do not work together, equally). Therefore, all PBXs in the system must be linked eSSL v1 or eSSL v2.}} | ||
| − | Linking PBX’s with usage of eSSLv2 (extended Smart Slican Link) protocol allows to connect Slican PBX’s in one system with joint internal numeration. Protocol uses TCP protocol to exchange informations between PBX’s and SIP signalling for make a calls. | + | Linking PBX’s with usage of eSSLv2 (extended Smart Slican Link) protocol allows to connect Slican PBX’s in one system with joint internal numeration. Protocol uses TCP protocol to exchange informations between PBX’s and SIP signalling for make a calls.<br> |
| + | Main features:<br> | ||
| + | * up to 50 linked PBXs (max 4000 extensions for all system) | ||
| + | * eSSL v2 separated signaling: | ||
| + | ** through a TCP/IP port number 5529 for XML/PhoneCTI/extension status | ||
| + | ** acoustic connections that can be implemented by the SIP | ||
Revision as of 08:32, 3 August 2015
|
Linking PBX’s with usage of eSSLv2 (extended Smart Slican Link) protocol allows to connect Slican PBX’s in one system with joint internal numeration. Protocol uses TCP protocol to exchange informations between PBX’s and SIP signalling for make a calls.
Main features:
- up to 50 linked PBXs (max 4000 extensions for all system)
- eSSL v2 separated signaling:
- through a TCP/IP port number 5529 for XML/PhoneCTI/extension status
- acoustic connections that can be implemented by the SIP
