Difference between revisions of "Linking protocol eSSLv2"
From pubWiki-en
| (10 intermediate revisions by the same user not shown) | |||
| 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.<br> | + | 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. Each PBX „knows” configuration of other systems, thats why internal traffic is directed automatically and does not require configuring. Internal numbers phonesbook contains list of all subscribers in linked PBX’s.<br> |
| − | Main features:<br> | + | '''Main features:'''<br> |
* up to 50 linked PBXs (max 4000 extensions for all system) | * up to 50 linked PBXs (max 4000 extensions for all system) | ||
* eSSL v2 separated signaling: | * eSSL v2 separated signaling: | ||
** through a TCP/IP port number 5529 for XML/PhoneCTI/extension status | ** through a TCP/IP port number 5529 for XML/PhoneCTI/extension status | ||
** acoustic connections that can be implemented by the SIP | ** acoustic connections that can be implemented by the SIP | ||
| + | * chat in PhoneCTI app with subscribers from linked PBX’s | ||
| + | * sending subscriber and PhoneCTI app status betwenn linked PBX’s | ||
| + | * phonebook synchronization between linked systems | ||
| + | ** public phonebook synchronization | ||
| + | ** synchronization of additional exterenal numbers | ||
| + | ** synchronization of internal numbers(from all linked PBXs) in groups | ||
| + | * SMS via main eSSL server(equipped GSM Trunk) | ||
| + | |||
| + | Example network topology in ESSLv2 | ||
| + | *'''star topology''' [[File:essl_star.png|700px]] | ||
| + | *'''full mesh topology''' [[File:essl_full_mesh_en.png|700px]] | ||
Latest revision as of 11:41, 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. Each PBX „knows” configuration of other systems, thats why internal traffic is directed automatically and does not require configuring. Internal numbers phonesbook contains list of all subscribers in linked PBX’s.
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
- chat in PhoneCTI app with subscribers from linked PBX’s
- sending subscriber and PhoneCTI app status betwenn linked PBX’s
- phonebook synchronization between linked systems
- public phonebook synchronization
- synchronization of additional exterenal numbers
- synchronization of internal numbers(from all linked PBXs) in groups
- SMS via main eSSL server(equipped GSM Trunk)
Example network topology in ESSLv2
- star topology
- full mesh topology
