Difference between revisions of "Linking protocol eSSLv2"
From pubWiki-en
| Line 11: | Line 11: | ||
* sending subscriber and PhoneCTI app status betwenn linked PBX’s | * sending subscriber and PhoneCTI app status betwenn linked PBX’s | ||
Example network topology in ESSLv2 | Example network topology in ESSLv2 | ||
| − | *'''star topology''' [[ | + | *'''star topology''' [[File:essl_star.png]] |
| − | *'''full mesh topology''' [[ | + | *'''full mesh topology''' [[File:essl_full_mesh.png|700px]] |
Revision as of 08:40, 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
- public phnebook synchronization
- chat in PhoneCTI app with subscribers from linked PBX’s
- sending subscriber and PhoneCTI app status betwenn linked PBX’s
Example network topology in ESSLv2
- star topology
- full mesh topology
