Acano solution. Acano Server & VM Release Release Notes. June Az

Size: px
Start display at page:

Download "Acano solution. Acano Server & VM Release Release Notes. June Az"

Transcription

1 Acano solution Acano Server & VM Release Release Notes June Az

2 Contents 1 Introduction Name change from cospaces to spaces New Features/Changes in R New Features for Lync meetings Dual Homed Conferencing RDP transmission Multiple video encoder support Improved TURN server Using TLS Multi-tenancy XMPP multi-domains Tenanted dial plans Forwarding rules Outbound dial plan rules Tenant call limits H.323 Gateway changes Change to h323_gateway sip_proxy command and Outbound Dial Plan rule H323 Gateway Certificates H.323 Gateway address handling for older gatekeepers and endpoints Support for multiple CDR Receivers Changes to voice prompts Customizing the text shown in invitations Screen layout control using DTMF Additional custom layouts Locking and unlocking a meeting lobby Support for XMPP resiliency Example of deploying XMPP resiliency Identifying issues within an XMPP cluster SIP and Lync call traversal To configure the SIP/Lync call traversal Certificate based login from clients Miscellaneous improvements Summary of additional MMP commands Additional MMP commands for TURN server Additional MMP commands to support XMPP multi-domains Additional MMP commands for the H.323 Gateway Addition of ciphers to tls Additional MMP commands to support XMPP resiliency in multi-server deployments Additional MMP commands to support SIP Edge Summary of API Additions & Changes Affecting Tenants Determining type of Lync call Acano Solution: Acano Server R Release Notes Az Page 2

3 Overriding port number for TCP media on TURN server Support for multiple CDR receivers Improvements to screen layout handling via the API Locking and unlocking a meeting lobby Customizing the text within invitations Media traversal changes Improved error diagnostics Certificate based authentication Notes on Installing and Upgrading to R R1.8 Deployments Deployments using a single host server Deployments using a single split server hosted on a Core server and an Edge server Deployments for scalability and resilience Upgrading to Release R Downgrading Resolved Issues Resolved in R Resolved in R Resolved in R Resolved in R Resolved in R Resolved in R Resolved in R Resolved in R1.8.7 but limited release Resolved in R Resolved in R Resolved in R R1.8.4 not released Resolved in R Resolved in R Resolved in R Resolved in R1.8.0 (formerly released as RC4) Known Limitations Acano Solution: Acano Server R Release Notes Az Page 3

4 1 Introduction This release note describes the new features, improvements and changes in Release 1.8 of the Acano solution software for both Acano Server and virtualized deployments. Note about beta features: This release contains features that are provided for beta testing only and not intended for a production environment. The beta features are: - firewall traversal for SIP and Lync devices, - XMPP resiliency, - certificate based login from clients. Acano does not guarantee that a beta feature will become a fully supported feature in the future. Beta features are subject to change based on feedback, and functionality may change or be removed in the future Throughout this document the term Lync refers to Lync 2010, Lync 2013 and Skype for Business. When functionality exists only for a specific version then this will be highlighted. Before upgrading to R1.8, you are advised to take a configuration backup using the backup snapshot <filename> command, and save the backup safely on a different device. See the MMP Command Reference document for full details. Release 1.8 introduces the requirement for certificates for the H.323 Gateway, see section Note: If you experience issues with a SIP call then you may have configured a loop in your dial plan. Refer to the Troubleshooter for Acano Clients, WebRTC and SIP endpoints for advice on what to avoid, and typical symptoms indicating a configuration problem. The Troubleshooter also contains many other useful pieces of advice for troubleshooting issues in your deployment. Note: From release an MMP command has been added to configure the number of login attempts allowed before the 15 minute lockout. See section Name change from cospaces to spaces cospaces are now called spaces. The new name is intended to reflect the versatility of a space. For instance, a space can be a project space, a team s collaboration space, or a place to meet external people. Some documentation and software may still refer to cospace, but will change shortly. Acano Solution: Acano Server R Release Notes Az Page 4

5 2 New Features/Changes in R1.8 Release 1.8 comprises: new features for Lync meetings, improved TURN server, support for multi-tenancy, XMPP multi-domains on a single Acano server, tenanted dial plans, tenant call limits, new functionality and changes to the H.323 Gateway, support for two CDR receivers, additional voice prompts and more sampling rates supported, customizing the text within invitations, further improvements to screen layout handling, locking and unlocking a meeting lobby, and a few miscellaneous improvements. The following are beta features: firewall traversal for SIP and Lync devices, XMPP resiliency certificate based login from clients You are advised not to use these beta features in a production environment. 2.1 New Features for Lync meetings Release 1.8 improves the user experience in Lync meetings: providing improved layouts to Acano users providing familiar layouts to Lync users both Lync users and Acano users receive a full combined list of all participants in the meeting, regardless of where they are connected Lync client users now see a non-square aspect ratio for video from SIP endpoints and Acano clients. Previously, video was always cropped to a square format to match video from other Lync clients. Lync client users will now see content in a separate area of their Lync client rather than in the main video area. by sending video using the best quality codec supported by each participant in Lync meetings. This optimizes the experience when using a mixture of Lync client versions. Acano Solution: Acano Server R Release Notes Az Page 5

6 These improvements are provided via three new features: Dual Homed Conferencing RDP support Multiple video encoder support Dual Homed Conferencing Dual homed conferencing improves the user experience for both Lync users and Acano users in Lync scheduled meetings and in Lync drag and drop style meetings (also known as ad hoc calls). Lync participants can use drag and drop to add Acano users to a Lync meeting, and can use conference controls to mute Acano users or disconnect them. For Acano users joining a Lync scheduled conference, they will see the video from up to five Lync participants, as well as video from the Acano users. Lync users now see video in a gallery format from all of the Acano users, as well as the Lync users in the meeting. Both Lync users and Acano users receive a full combined list of participants in the meeting. Lync participants can also directly dial into a cospace or use drag and drop to add a cospace to a Lync meeting. These are useful if a large meeting is being held in an Acano cospace which the Lync user wants to join. In the first case they will receive a composed layout of multiple participants. When adding a complete cospace to a Lync meeting, the Lync user will receive only one video stream from the cospace (the main speaker) and will not receive a full combined participant list. They can continue to add additional Lync participants as normal. Notes: The user experience in Lync meetings is best with Lync 2013 or Skype for Business 2015 because those versions allow for the ability to transmit multiple streams to the Acano side of the conference. This enables an endpoint or client connecting to the Acano side to view multiple Lync participants providing the Acano server has been upgraded to release 1.8. The user experience using Lync 2010 is not so good, as in this version of Lync only a single stream is available and this is always the loudest speaker, and the loudest speaker could be on the Acano side of the conference already RDP transmission Release 1.8 provides support for transmission of RDP (Microsoft s Remote Desktop Protocol), improving the experience for Skype for Business and Lync client users when they participate in the same calls and conferences as users of other systems. When a non-lync client user, for example an Acano client user or SIP endpoint user, shares an application, or their desktop, with Lync client users, the Acano Call Bridge encodes the content as RDP and sends the content to the Lync client in a separate RDP channel from the H.264 video stream. This results in both the content and video being displayed in separate areas on the Lync client. Prior to R1.8, both video and content were shown in the same area on the Lync client. Figure 1 shows a call from a non-lync client sharing to multiple Lync clients. Note: From R1.8, sharing from non-lync clients is supported to both Lync clients and to Lync conferences. Acano Solution: Acano Server R Release Notes Az Page 6

7 Note: there is a known limitation with sharing content from Acano Mac clients in a Lync conference. Lync clients do not receive the shared content, but it is received by other endpoints in the Lync meeting. Figure 1 Content sharing from a SIP endpoint to a Lync client/conference Multiple video encoder support Different versions of Lync support different video codecs, and this affects the quality of the video they can receive. Lync 2013 and Skype for Business support H.264 SVC which gives the best quality while Lync 2010 and Lync for Mac 2011 support RTV but not H.264 SVC. In previous releases the Call Bridge only sent a single video stream to the Lync AVMCU. In the 1.8 release the Call Bridge can send both RTV and H.264 SVC streams to the AVMCU. This then allows the AVMCU to send RTV to clients that don t support H.264 SVC while sending higher quality H.264 SVC to clients that support it. Figure 2 Multiple video encoders for different Lync clients Acano Solution: Acano Server R Release Notes Az Page 7

8 2.2 Improved TURN server Release 1.8 introduces an improved TURN server which supports TCP to UDP interworking. This allows TCP media from browser clients to be received which the TURN server converts back to UDP media. This is useful when UDP traffic from browsers is blocked. In addition there is a new parameter tcpportnumberoverride for the API object /turnservers allowing the port number to be overridden when using the new TURN server to receive TCP media from browsers. This allows you to set a non-standard port for TCP on the TURN server. Figure 3 TURN server supporting TCP and UDP Use the MMP command turn tls <port none> to select the port for the TURN server to listen on. For example: turn listen a turn tls 443 turn enable Note: the Web Bridge and TURN Server cannot listen on the same interface:port combination. To run both on port 443 requires them to be run on separate servers/vms, or if on the same server/vm they need to be on different interfaces and different subnets. For maximum connectivity from external locations, Acano recommends that port 443 is used for both the Web Bridge and TURN Server Using TLS If you plan to use TLS (a cryptographic protocol), then you will need a certificate on each TURN server that will be used for TLS communication. You do not require a certificate on TURN servers that are not being used for TLS. You are advised to create a similar private key and signed certificate to the one created for the Web Bridge, using the same CA to sign the certificate. Remember to restart the TURN server after you have assigned the certificate (and certificate bundle) and private key pair. Acano Solution: Acano Server R Release Notes Az Page 8

9 2.3 Multi-tenancy Release 1.8 supports additional multi-tenancy functionality by allowing the hosting of: multiple deployments on the same server. This enhancement is provided via the following new features: tenants can be assigned to a tenant group. This provides a mechanism for splitting tenants into separate independent groups. Each group consists of one or more tenants. Set tenant groups up through the API, see section IVRs and web bridges can now be created for a group of tenants as well as for an individual tenant through the API. See section tenanted dial plans, this enables the outgoing dial plan to have rules set that are tenant specific. Outbound connections can have tenant specific Local From Domain to allow call back to reach the correct tenant. See section 2.5. tenanted call IDs. Prior to R1.8, Call IDs had to be unique across the system. In this release, Call IDs must still be unique within a tenant group, but maybe reused for different tenant groups. Note: If you require more than one customization, for example one per tenant, then you will require a separate Web Bridge for each customization. This can be a standalone Web Bridge on a VM server. Multiple branding of a Web Bridge is not supported. 2.4 XMPP multi-domains XMPP multi-domain enables a single Acano server to host multiple XMPP domains. For example, both example.com and example.org can exist on the same Acano server. It is possible to configure multiple tenants with the same XMPP domain (as in previous releases), or each tenant with their own domain, or mix these schemes. Use the MMP commands in section to configure multiple domains for the XMPP server to listen to. Note: Every domain will require a DNS SRV record. 2.5 Tenanted dial plans Different dial plan rules for forwarding calls and for outbound calls can be setup for tenants through the API, see section This is applicable to single tenant and multi-tenant deployments Forwarding rules Forwarding rules can have a tenant associated with them. When a forwarding rule with an associated tenant is used, the call (conference) spawned by that rule is associated with the same tenant. Acano Solution: Acano Server R Release Notes Az Page 9

10 2.5.2 Outbound dial plan rules You can associate an outbound dial plan rule with a tenant. Once associated, the only call legs that can be placed using that rule are those that originate from calls (conferences) associated with the same tenant, or associated with no tenant. 2.6 Tenant call limits This feature enables an administrator to limit the number of calls a tenant can make to ensure that a tenant does not consume all of the resources. This feature works across distributed deployments and is applicable to single tenant and multi-tenant deployments. To set the tenant call limit, set participantlimit on the /tenants/<tenant id>/ API object. See section Note: Call limits may be exceeded when simultaneous calls occur to different Call Bridges. 2.7 H.323 Gateway changes R1.8 introduces the following changes that affect the H.323 Gateway: change in IP address to use in h323_gateway sip_proxy command and Outbound Dial Plan rule (see section 2.7.1). requirement to install certificates for the H.323 Gateway (see section 2.7.2). improvements in the way the H.323 Gateway handles outgoing and incoming dial plans for legacy gatekeepers and endpoints (see section 2.7.3). See Section for additional MMP commands for the H.323 Gateway Change to h323_gateway sip_proxy command and Outbound Dial Plan rule In R1.7, if the H.323 Gateway and the Call Bridge were running on the same host (X series or VM), then the IP address specified in the h323_gateway sip_proxy command was the IP address of one of the external interfaces that the Call Bridge was listening on. Similarly, the entry in the outbound dial plan relating to the H.323 Gateway also needed to point to one of these external interfaces listened to by the Call Bridge In R1.8, if the H.323 Gateway and the Call Bridge are running on the same host (X series or VM) then the IP address specified in the h323_gateway sip_proxy command needs to be set to , and the SIP Proxy to Use in the Outbound Dial Plan Rule needs to be set to :6061. If the H.323 Gateway and the Call Bridge are running on different hosts, then the IP address of the external interfaces that the Call Bridge is listening on may still be used H323 Gateway Certificates From R1.8, a certificate is required on each H.323 Gateway. The certificate can be signed by an internal CA. Follow these steps: Acano Solution: Acano Server R Release Notes Az Page 10

11 Generate a private key and the Certificate Signing Request (.csr) file for the Acano H.323 Gateway application. For information on how to generate a private key and.csr file, refer to one of the Certificate Guidelines on Note: the public key is created and held within the.csr file. Submit the.csr file to the CA (public CA or internal CA) for signing You can use the pki command on the Acano server to generate the private key and.csr file, and submit the pair to an internal CA such as an Active Directory server with the Active Directory Certificate Services Role installed. SSH into the MMP Upload the signed certificate and intermediate CA bundle (if any) to the Acano server using SFTP. Check that the certificate (and certificate bundle) and the private key match pki verify <certicate> <cert bundle/ca cert> [<CA cert>] Assign the certificate (and certificate bundle) and private key pair to the H.323 Gateway h323_gateway certs <keyfile> <certificatefile> [<cert-bundle>] Restart the H.323 Gateway h323_gateway restart Note: if you perform TLS certificate verification by using the command: tls SIP verify enable then certificate verification will be undertaken against the TLS SIP trust store on the Call Bridge and the SIP service on the H.323 Gateway. Use the tls SIP trust <crt bundle> command to set up the TLS SIP trust store H.323 Gateway address handling for older gatekeepers and endpoints Release 1.8 introduces improvements in the way that the H.323 Gateway handles outgoing and incoming dial plans for legacy gatekeepers and endpoints. Some old H.323 gatekeepers do not provide the domain in destination addresses for outgoing calls, and cannot handle a domain for incoming calls. These gatekeepers supply and require an E.164 address or H.323 ID for the address. Release 1.8 provides new commands to support these devices, see section Figure 4 illustrates how the destination address for calls from legacy gatekeepers can be accepted by appending a domain to the destination address using MMP command h323_gateway sip_domain <sip_domain_uri >. The source address can also have a domain added which can aid dial-back of that user. Using command h323_gateway h323_domain <h323_domain_uri>, appends a domain which enables the Call Bridge to identify where the call originates, and hence support call back. Acano Solution: Acano Server R Release Notes Az Page 11

12 H.323 Endpoint Legacy H.323 Gatekeeper Acano H.323 Gateway Call Bridge H225 setup Destination address: cospace Source address: h323 INVITE To: From: Incoming call From endpoint "h323" Figure 4 Adding the domain to the source address Figure 5 illustrates how call back can be made to work for calls originating from legacy H.323 gatekeepers. Using command h323_gateway h323_domain_strip yes removes the domain from the destination if it matches h323_domain and using command h323_gateway sip_domain_strip yes removes the domain from the source address if it matches sip_domain, when making a call to the legacy gatekeeper. Figure 5 Removing the domain for call back Note: dialing an IP address does not require removal of the domain, as the Call Bridge recognizes that it is an IP address and does not append the domain. 2.8 Support for multiple CDR Receivers From R1.8, the Acano server supports up to two CDR receivers, enabling you to deploy two different management tools or two instances of the same management tool for resiliency. If you are using Acano Manager, the Acano Manager server must be one of your CDR receivers, you can either add a second Acano Manager server or add a different management platform. Note: The list of CDR receivers is held locally to an individual call bridge, it is not stored in the database shared between clustered call bridges. To enable configuration of the multiple CDRs, R1.8 has two new API objects: /system/cdrreceivers/ /system/cdrreceivers/<cdr receiver id> Acano Solution: Acano Server R Release Notes Az Page 12

13 and a new mechanism to index records using the correlatorindex ; correlatorindex replaces the recordindex object which is deprecated and may be removed in a future release. In addition, for deployments with clustered Call Bridges there is a new Call Bridge GUID which identifies which Call Bridge is sending the record, and which remains the same across all restarts of the system. Alternatively, you can configure the multiple CDRs through the Web Admin Interface, Configure > CDR settings, enter each receiver s HTTP or HTTPS URI. For more information on the correlatorindex and configuring multiple CDR receivers, see the R1.8 Call Detail Records Guide. Notes: From R1.8 the retrieved alarm condition for cdrconnectionfailure has changed. The "cdrreceiver" element now holds the GUID of the configured object, and there is an additional URI element. Prior to R1.8, the response data included an element called "cdrreceiver" that held the configured CDR receiver URI. Legacy alarm processors will now see the textual rendering of a GUID whereas before they saw the URI of the CDR receiver. To process cdrreceiver alarms, first look for the "uri" element to determine the configured URI, and, if absent, look for the URI in the "cdrreceiver" element. Alternatively, try parsing the "cdrreceiver" element to see if it a GUID first and, if it is, look then at the "uri" value. 2.9 Changes to voice prompts The default voice prompts, used for the in-call experience when dialing into a cospace from a SIP or Lync endpoint, have been re-recorded, some with new wording. In addition there are 4 new prompts: You have been disconnected from the meeting Your meeting has ended You are the only participant Waiting for your host to join the bottom two in the list play on a loop for audio-only calls. The range of supported sampling rates has increased from 8 and 16 khz, to now supporting 22.05, 32, 44.1 and 48 khz. Refer to the R1.8 Customization Guidelines for details on the prompt wording and their filenames Customizing the text shown in invitations Releases 1.8 of the Acano client and Acano server introduce the ability to customize the text shown in invitations, providing a branding license key is uploaded to the Acano server. Customization of the invitation text is done via the use of a template which the client requests from the server. Acano Solution: Acano Server R Release Notes Az Page 13

14 Note: that the templates are cached by the client so any changes to a template will not immediately appear in the client. Configure the template via the API of the server. Within the existing callbrandingprofile object there is a new invitationtemplate field which needs to point at a URL from which the server retrieves the template. Refer to the R1.8 Customization Guidelines for details on the placeholders within the invitation text that can be changed, and an example of the template. Note: Custom text invitations are not supported by Acano client 1.7 releases or earlier Screen layout control using DTMF This release introduces the ability for SIP endpoint users to scroll through different screen layouts using DTMF. The users need to be assigned the necessary permissions. Use the API to configure: the DTMF tones in dtmfprofile. Configure DTMF tones for 'next layout' and 'prev layout' operations permissions to use DTMF in the calllegprofile. Use parameter changelayoutallowed the defaultlayout in calllegprofile. The layouts scroll through in order: 'allequal', 'stacked', 'telepresence', 'speaker only', defaultlayout. If defaultlayout='allequalninths' then the order is 'allequal', 'stacked', 'telepresence', 'speaker only', 'allequalninths'. If the defaultlayout is set to one of the other layouts then only 4 layouts will be in the cycle. For example: if defaultlayout='allequal' then the order is 'allequal', 'stacked ', 'telepresence', ' speakeronly'. Figure 6 Scrolls through allequal, stacked, telepresence (speaker large), speaker only and defaultlayout 2.12 Additional custom layouts Release 1.8 supports 3 additional screen layouts, which may be chosen via the API (see section ) or through the Web Admin interface (Configuration>coSpaces). These new layouts have one main pane for the main speaker and 5, 7, or 9 smaller panes around the main pane. Acano Solution: Acano Server R Release Notes Az Page 14

15 Figure 7 Additional custom layouts 2.13 Locking and unlocking a meeting lobby In previous releases, when an activator (host) was present in a meeting all other participants (guests) would automatically be activated. This release adds the ability to lock and unlock the lobby to stop and start this activation process. Note that members of the cospace and people joining via access methods not needing activation are not affected by this setting. The user who locks and unlocks the meeting lobby needs to be assigned the necessary permission. Use the API to configure: the initial un/locked state of a call. Use a POST request containing the locked parameter with value (true or false) to /calls. the current un/locked state of a running call. Use a PUT request containing the locked parameter to /calls/<call id> to alter the state. This state is not preserved between instances of the meeting. the default lock value. This can be set as part of /callprofiles. Set the locked parameter as true or false, this value will apply until it is overriden via the above methods or by a user. This value is used each time the cospace is used. permission to use DTMF in the calllegprofile. Use parameter calllockallowed the DTMF tones in dtmfprofile. Configure DTMF tones for lockcall and unlockcall parameters The behaviour of a locked/unlocked cospace is as follows: Unlocked - anybody can join, those needing activation continue to be activated as before. Locked - new participants who need activation are not automatically activated. Participants not needing activation and members can still get in. When the conference goes from the unlocked state to the locked state, participants that are already activated are not deactivated. Acano Solution: Acano Server R Release Notes Az Page 15

16 2.14 Support for XMPP resiliency NOTE: XMPP resiliency is a beta feature, it should not be used in production environments. Release 1.8 supports XMPP resiliency in multi-server deployments where there are at least three XMPP servers in the deployment. XMPP resiliency provides fail-over protection for a client being unable to reach a specific XMPP server. NOTE: Deployments with only two XMPP servers will not benefit from resiliency, and if one fails it will cause an outage, effectively doubling the risk of failure versus stand-alone mode. This is due to the failover algorithm requiring more than half of the nodes to be available in order for the system to make good decisions about which XMPP server is the master. When setup in resilient mode, the XMPP servers within a deployment are loaded with the same configuration. Each knows the location of the others and they establish links between them. They use keep-alive messages to monitor each other and elect a master. XMPP messages can be sent to any server. Messages will be forwarded to the master XMPP server, see Figure 8. The XMPP servers continue to monitor each other, if the master fails then a new master is elected and the other XMPP servers forward traffic to the new master. Figure 8 XMPP servers electing master XMPP server In a resilient deployment, the XMPP server that a Call Bridges connects to is controlled via DNS. This choice is based on the DNS priority and weight given. A Call Bridge only connects to one XMPP server at a time. There is no requirement for all Call Bridges to connect to the same XMPP server since all traffic is forwarded to the master. If a network problem results in the Call Bridge losing connection to the XMPP server, the Call Bridge will attempt to reconnect to another XMPP server, see Figure 9. Acano Solution: Acano Server R Release Notes Az Page 16

17 Figure 9 Call Bridges connecting to XMPP servers The Call Bridge must be configured on any XMPP Server that it can connect to. This involves adding the name and secret of each Call Bridge to each XMPP Server, see Figure 10. Call Bridge: cb1 Secret: QeFAAoCcQ8aMhjBCgK1 Call Bridge: cb2 Secret: RHi1E0bmFuPRE9asrt1 XMPP Server 1 cb1, QeFAAoCcQ8aMhjBCgK1 cb2, RHi1E0bmFuPRE9asrt1 XMPP Server 2 cb1, QeFAAoCcQ8aMhjBCgK1 cb2, RHi1E0bmFuPRE9asrt1 XMPP Server 3 cb1, QeFAAoCcQ8aMhjBCgK1 cb2, RHi1E0bmFuPRE9asrt1 Acano Solution: Acano Server R Release Notes Az Page 17

18 Figure 10 Call Bridge names and secrets added to XMPP servers To summarize: Each Call Bridge is set up with one account consisting of its Call Bridge name and shared secret that the XMPP servers know about. Each XMPP server in the cluster needs a list of these Call Bridge accounts. This list needs to be the same on each XMPP server so that all Call Bridges can connect, it is important that the secret is set correctly when adding the Call Bridges to the 2nd and 3rd XMPP servers. The example in section explains the process for configuring the Call Bridges and XMPP servers to setup XMPP resiliency. Clients connect via the load balancer. Each load balancer can be configured to have trunks from one or more XMPP servers. There is no need for a full mesh of connections, see Figure 11. In cases where the load balancer doesn t have a trunk from the master XMPP Server, the traffic is routed internally via another XMPP server. Figure 11 Load Balancers connecting to XMPP servers Example of deploying XMPP resiliency This example of deploying XMPP resiliency uses three XMPP servers, and assumes that you are configuring the XMPP servers for the first time. If you have previously deployed XMPP onto an existing server, then steps 1-4 only need to be done on the new servers. Similarly, steps 8-10 and may have previously been carried out. There is no need to repeat these steps. If XMPP resiliency has previously been deployed then it is recommended to reset all servers apart from the first when following these instructions. Acano Solution: Acano Server R Release Notes Az Page 18

19 For each XMPP server node, establish an SSH connection to the MMP, log in and at the acano> prompt, follow steps 1 to 4 If this node has previously been used for XMPP, reset the XMPP configuration on this node. xmpp reset Create a component secret for this XMPP server xmpp domain <domain-name> Setup the interfaces for the XMPP server to listen on xmpp listen <interface whitelist> Assign the private key, and the certificate file and certificate bundle as provided by your Certificate Authority and required for connection to Acano clients. xmpp certs <keyfile> <certificatefile> [<cert-bundle] Where keyfile and certificatefile are the filenames of the matching private key and certificate. If your CA provides a certificate bundle then also include the bundle as a separate file to the certificate. For example: xmpp certs xmppserver1.key xmppserver1.crt xmppserverbundle.crt If you used the same certificate on all boxes then the following two steps can be skipped and the certificate itself configured as the whitelist. Using SFTP, download and combine all of the XMPP server certificates into one bundle of whitelisted certificates, in one of the following ways: Linux or UNIX-like Operating Systems: cat xmppserver1.crt xmppserver2.crt xmppserver3.crt > xmpp-clusterwhitelist.crt Windows or DOS: copy xmppserver1.crt + xmppserver2.crt + xmppserver3.crt xmpp-clusterwhitelist.crt Manually combine the certificates using Notepad or Notepad++. There must be no spaces on the first certificate s END CERTIFICATE line and the second (and further certificate s) BEGIN CERTIFICATE line, but there MUST be a carriage return at the end of the file. They MUST also be in Base64 encoded format. Using SFTP, upload xmpp-cluster-whitelist.crt to all of the Acano servers On each node, assign the bundle of whitelisted certificates from step 6. For example: xmpp cluster trust xmpp-cluster-whitelist.crt or if you have used a single certificate for multiple servers: xmpp cluster trust xmppserver.crt Set up clustering on one of the nodes with an XMPP server. Follow steps 8 to 14 on this node: Enable the XMPP server node xmpp enable Configure one of the Call Bridges that will connect to the XMPP cluster: Acano Solution: Acano Server R Release Notes Az Page 19

20 xmpp callbridge add <callbridge name> A secret is automatically generated; for example: acano>xmpp callbridge add cb1 Added callbridge: Secret: QeFAAoCcQ8aMhjBCgK1 this configures the XMPP server to allow connections with the Call Bridge named cb1. Note the domain, Call Bridge name and secret generated, you will need this information later when you configure the Call Bridge access to the XMPP server (so that the Call Bridge will present the authentication details to the XMPP server) Repeat step 9 for all of the Call Bridges that will connect to the XMPP cluster. Each Call Bridge will need to have a unique name. Note: If you have not already noted the details for the Call Bridges that you have added to the XMPP server, then use the command: xmpp callbridge list and make a note of the domain, name and secret generated for each Call Bridge that will connect to the XMPP cluster. These are required in step 17. Disable this XMPP server node xmpp disable Enable the XMPP cluster on this node xmpp cluster enable Initialize the XMPP cluster on this node. This command will create a 1 node xmpp cluster, the other nodes (xmpp servers) will be joined to this cluster in step 22. xmpp cluster initialize Re-enable this node xmpp enable Make a note of the IP address of this node, this is required in step 22. xmpp cluster status Follow steps 16 to 22 for each of the remaining XMPP server nodes in the cluster (nodes 2 and 3): Enable the XMPP server node xmpp enable Add each Call Bridge to this node. This requires the Call Bridge to be added using the same Call Bridge name and secret from the first XMPP server node. This is achieved using the command: xmpp callbridge add-secret <callbridge name> Enter callbridge secret> Repeat step 17 until you have added all of the Call Bridge secrets to this node. Disable this node xmpp disable Enable the XMPP cluster on this node xmpp cluster enable Acano Solution: Acano Server R Release Notes Az Page 20

21 Re-enable this node xmpp enable Join this node to the cluster, where <cluster> is the IP address or domain name of the node from step 15. xmpp cluster join <cluster> Now configure each Call Bridge with the authentication details of the XMPP servers in the cluster. This enables the Call Bridges to access the XMPP servers. Log in to the Web Admin interface on one of the Call Bridges Navigate to Configuration>General and enter the following: unique Call Bridge name as used in steps 9 and 10, no domain part is required for example cb1 domain: this is the XMPP server domain example.com server address of the XMPP server. Set this field if you want this Call Bridge to only use a co-located XMPP server, or you don t have DNS configured. Using the co-located XMPP server reduces latency. Leave this field empty to allow this Call Bridge to failover between XMPP servers, this requires the DNS entries to be setup, see Note below. Note: Refer to the Deployment guides for advice on setting up DNS records for the XMPP server nodes. If you plan to use DNS to connect between Call Bridges and XMPP servers you will also need to set up a DNS SRV record for the xmpp cluster to resolve to the DNS A record of each of the XMPP servers in the cluster. The format of the DNS SRV record is: xmpp-component._tcp.<domainnameofxmppserver>. the example below specifies port 5223 (use another port if 5223 is already used). For example: _xmpp-component._tcp.example.com IN SRV xmppserver1.example.com _xmpp-component._tcp.example.com IN SRV xmppserver2.example.com _xmpp-component._tcp.example.com IN SRV xmppserver3.example.com the shared secret used for this Call Bridge as used in steps 9 and 10 and confirm the shared secret Repeat steps 23 and 24 for each Call Bridge that will connect to the cluster. Your cluster should now be running. You can check with: xmpp cluster status Acano Solution: Acano Server R Release Notes Az Page 21

22 you will get a report on the live state of the xmpp cluster. If the cluster has failed, then this command will return the statistics of the xmpp server running on this Acano server only. Use this command to try and help diagnose connectivity problems Identifying issues within an XMPP cluster The table below indicates possible causes to symptoms that might be seen in your syslog sever. Symptom Many TCP failures Client logged me out Frequent elections Possible cause Trust between your XMPP servers may not have been set up correctly, or there are connectivity issues between nodes. Test that each node can reach port Failover detection is set at 10 seconds which occasionally is enough time to cause a client to log out. Acano clients will re-login automatically, unless Call Bridges are not re-connecting. However, WebRTC clients will need to re-login. Frequent elections of the master node in the cluster may indicate problems on your network. If the master node does not hear from the other, slave nodes, within 10 seconds then it steps down from being master. Similarly, the slave nodes will stand for election if they do not hear from the master node in a random time between 10 and 20 seconds (the random time prevents multiple slave nodes assuming the master role) SIP and Lync call traversal Note: Call traversal is still a beta feature. It should not be used in production environments. R1.8 introduces this beta feature to support traversal of local firewalls for SIP endpoints and Lync calls. The Call Bridge uses a TURN server within the Acano solution to traverse the local firewall and sends the SIP signal via a new SIP Edge component. A third party SIP firewall traversal device is no longer required. You need to set up an Outbound dial plan rule, even if you don t plan on making outgoing calls via the SIP edge. This is because any new transaction within the call or sending content to a Lync device uses the outbound rule. Once the SIP Edge has been configured and enabled, incoming calls from SIP devices are automatically traversed across the firewall. Note: this feature assumes that the remote SIP device can see the TURN server. It does not require the remote SIP device to be ICE aware. It also requires the remote SIP device to be able to contact the SIP Edge, the SIP Edge can either have a public IP address or sit behind a NAT with appropriate forwarding of traffic. Figure 12 shows a schematic for SIP call traversal using the TURN server and SIP Edge component on a single Edge server in the DMZ network which is accessible to remote SIP devices via the public IP address The Call Bridge is deployed in the private network on a Core server and accesses the TURN server and SIP Edge via the internal IP address Acano Solution: Acano Server R Release Notes Az Page 22

23 Figure 13 illustrates SIP call traversal using two Edge servers, one for the SIP signaling and the other for the media stream. The table below Figures 12 and 13 lists the ports required to be open for SIP/Lync call traversal. Figure 12 Firewall traversal for remote SIP devices using a single Edge server Figure 13 Firewall traversal for remote SIP devices using two Edge servers Acano Solution: Acano Server R Release Notes Az Page 23

24 Note: SIP endpoints or Lync clients external to the network may still need a third party device to route SIP signaling across their firewall. The table below lists the ports required to be open for SIP/Lync call traversal. Link Component Open port Connecting to Traffic type Traffic direction with respect to component Configurable 1 Edge server (private interface) Any unused port, e.g Call Bridge SIP, TLS Incoming from Call Bridge Yes 2 Edge server (public interface) 5061 (Note 2) Remote SIP devices SIP TLS (Note 3) Incoming/Outgoing Yes 3 Call Bridge (Note 1) TURN server Media UDP (STUN, RTP) Incoming/Outgoing No 3 Call Bridge (Note 1) TURN server Media TCP (RDP) Incoming/Outgoing No 4 TURN server (Note 1) Remote SIP devices Media UDP (STUN, RTP) Incoming No 4 TURN server (Note 1) Remote SIP devices Media TCP (RDP) Incoming No 3,4 TURN server 3478 Remote SIP devices 3,4 TURN server 443 Remote SIP devices UDP Incoming Yes TCP Incoming Yes Note 1: Although the range between the TURN server and the external Acano clients is shown as , currently only is used. A wider range is likely to be required in future releases. Note 2: Port 5061 is normally used for SIP TLS Note 3: R1.8 only supports SIP TLS, there is no support for UDP or TCP on port To configure the SIP/Lync call traversal Set up a SIP Edge on the Edge server. a. Configure the internal interface and port for communication to the Call Bridge. If the Call Bridge is using port 5061, then use a different port sipedge private <interface>:port for example: sipedge private a:3061 b. Configure the external interface and port on the SIP Edge sipedge public b:5061 Acano Solution: Acano Server R Release Notes Az Page 24

25 for example: sipedge public b:5061 Note: The SIP Edge always uses TLS for communication. Typically SIP TLS uses port c. If the SIP Edge is behind a NAT, then configure the public address of the NAT. sipedge public-ip <address> for example: sipedge public-ip Note: DNS records used for external connections must match the public address d. Set up a certificate, key file and trust bundle on the SIP Edge. These files are used to communicate with the internal Call Bridge and the external SIP server. If you have previously assigned a public CA signed certificate to the Call Bridge, then you can use the same certificate on the SIP Edge. If the SIP Edge has direct federation with a Lync Edge server, then the certificate file must be signed by a public CA trusted by the Lync deployment (as was previously required for the Call Bridge). Combine the Call Bridge certificate and the chain of CA certs into one file and use this as the SIP Edge certificate <crt-file>. To enable the SIP Edge to trust the Call Bridge for the TLS trunk, use the Call Bridge certificate as the <trust-bundle> sipedge certs <key-file> <crt-file> <trust-bundle> for example: sipedge certs sipedge.key sipedge.crt callbridge.crt Notes: SIP Edge certificates need to be signed by a public CA and trusted by the third party SIP server. For more information on certificates refer to the Certificate deployment guide. e. Enable the SIP Edge sipedge enable Set up a trunk from the Call Bridge to the SIP Edge. Note that you need to configure trust between the Call Bridge and the SIP Edge before creating the trunk. Note: at the moment only one trunk can be made to any SIP Edge, and only one trunk can be made from the same Call Bridge. a. Set up certificates for the connection to the SIP Edge. This uses the certificate from the SIP Edge as used above. callbridge trust edge <certificate file> for example: callbridge trust edge sipedge.crt b. Create the trunk using the IP address and port of the private interface. callbridge add edge <ip address>:<port> for example: callbridge add edge :3061 Acano Solution: Acano Server R Release Notes Az Page 25

26 Set DNS records to point to SIP Edge(s) for SIP and/or Lync. DNS can point to multiple SIP Edges for resilience. Use the _sips._tcp<domain> SRV record for the external TLS connection. Configure the TURN server as explained in the Acano solution Deployment guide that is most appropriate to your deployment (single combined server, single split server or scalable and resilient). Note that TURN TLS is required for Lync content data packets as they use TCP and not UDP. Create the outbound dial plan. Use the API to PUT to the relevant outbound dial plan rule /api/v1/outbounddialplanrules/ <outbound dial plan rule id>, with callrouting=traversal Notes: - You cannot use the Web Admin interface to select the call routing. - Outgoing calls use the certificates that you setup for incoming calls, see step 1d above. - The SIP Edge only supports TLS. All dial plan rules targeting the SIP Edge must be set to sipcontrolencryption=encrypted. - The Call Bridge determines the next hop of the signaling by doing a DNS lookup. It then sends this information to the SIP Edge using the outbound rules The table below outlines the call flow to establish an outgoing call from the Acano Server to a remote SIP device via the SIP Edge server: See signals in Figure 12 and Figure 13 Call Flow 1 Call Bridge uses an outbound dial plan rule to route SIP signaling via the SIP Edge server 1 Call Bridge sends a DNS request to resolve the next hop to send the request to 1 Call Bridge sends the requests to the SIP Edge with both local address and the TURN address for receiving media 2 The SIP Edge server makes the outgoing call to the remote SIP device The remote SIP device answers the call 3,4 Media flows between the TURN server and the remote SIP device 2.16 Certificate based login from clients Notes: 1) Extension of certificate based logins to client logins is a beta feature. 2) The standard Acano app does not provide the ability to use certificate based logins. A certificate enabled Acano app can be made available upon request. If enabled, certificate based logins allows users in possession of a cryptographic certificate to log into the Acano solution. CAC (Common Access Card) is one example of these certificates. The CAC contains a private key which cannot be extracted but can be used by on-card cryptographic Acano Solution: Acano Server R Release Notes Az Page 26

27 hardware to prove the identity of the card holder. Prior to release 1.8, the Acano solution supported administrative logins to the SSH and Web Admin Interface using certificates, this release extends certificate based access to client logins. Notes: From R1.8: 1) if cac is enabled, then it is possible to use certificate based logins from suitable clients. Users connecting in this manner will not have to enter a password to access the system. 2) if cac enable strict has previously been applied, then users can only log in to the Acano client using a certificate, no password based login to clients will be possible. 3) during authentication, two locations on the certificate are checked to determine the user s identity. The locations are the Common Name (CN) within the Subject field (this is the standard location for names in certificates), and the Principal Name within the Subject Alternative Name field (this is a Microsoft extension) Miscellaneous improvements Release 1.8 supports the following new features: Support for TIP 60fps Support for VP8 and OPUS codecs in SIP calls Acano client user locked out for 15 minutes after 20 failed login attempts. From release an MMP command has been added to configure the number of login attempts allowed before the 15 minute lockout:user rule max_failed_logins <attempts>. Note the Call Bridge must be restarted for this setting to take effect. Addition of ciphers to the tls MMP command The following weak ciphers have been disabled by default: TLSv1.2 3DES-CBC3-SHA 112 bit key TLSv1.1 3DES-CBC3-SHA 112 bit key TLSv1.0 3DES-CBC3-SHA 112 bit key Note: Weak ciphers can potentially lead to the possibility of a session being recorded and decrypted later. License Usage reports. The Acano Server now produces reports of the number of call legs to allow for calculation of port license usage. These reports are sent to the configured syslog server. Added the ability to have the ciphers configured on the Acano server to apply to both inbound as well as outbound TLS calls (from release ) 2.18 Summary of additional MMP commands From R1.8 the following MMP commands have been added. Acano Solution: Acano Server R Release Notes Az Page 27

28 Additional MMP commands for TURN server Command/Examples turn tls <port none> turn certs <keyfile> <certificate file> [<cert-bundle>] turn certs none Description/Notes Select the port for the TURN server to listen on Note: the Web Bridge and Turn Server cannot listen on the same interface:port combination. To run both on port 443 requires them to be run on separate servers/vms, or on different interfaces on the same server/vm. Defines the name of the private key file and.crt file for the Turn Server application and, optionally, a CA certificate bundle as provided by your CA. See section 2.2. Removes certificate configuration The new functionality for the TURN server is described in section Additional MMP commands to support XMPP multi-domains Command/Examples xmpp multi_domain add <domain name> <key-file> <crt-file> [<crt-bundle>] xmpp multi_domain del <domain name> xmpp multi_domain list Description/Notes Add another domain that the XMPP server will listen to. Specify the private key, certificate and optional certificate bundle as provided by the CA. Restart the XMPP server for this change to take effect. Note: the XMPP server will not start if the private key or certificate files are missing or invalid. Delete the domain that the XMPP server listens to. List the domain that the XMPP server listens to Additional MMP commands for the H.323 Gateway Command/Examples h323_gateway certs <keyfile> <certificate file> [<cert-bundle>] h323_gateway certs none h323_gateway sip_domain <uri> h323_gateway del sip_domain <uri> h323_gateway sip_domain_strip <yes/no> h323_gateway h323_domain <uri> h323_gateway del h323_domain <uri> h323_gateway h323_domain_strip <yes/no> Description/Notes Defines the name of the private key file and.crt file for the H.323 Gateway application and, optionally, a CA certificate bundle as provided by your CA. See section Removes certificate configuration Optional. If an incoming H.323 call is made to the gateway without a domain in the destination will be appended to the destination address before the SIP call to the Call Bridge is made. If set to "yes" and "h323_gateway sip_domain" is set, when a SIP call is made to the gateway will be stripped from the source address (if present) before making the H.323 call. Optional. If an H.323 call is made to the gateway without including a domain in the source will be appended to the source address before the SIP call is made. If set to "yes" and "h323_gateway h323_domain" is set, when a SIP call is made to the gateway the Acano Solution: Acano Server R Release Notes Az Page 28

Acano solution. Acano Server & VM Release Release Notes. December Aa

Acano solution. Acano Server & VM Release Release Notes. December Aa Acano solution Acano Server & VM Release 1.8.5.1 Release Notes December 2015 76-1005-20-Aa Contents Contents 1 Introduction... 4 2 New Features/Changes in R1.8... 5 2.1 New Features for Lync meetings...

More information

Acano solution. Acano Server & VM Release Release Notes. September P

Acano solution. Acano Server & VM Release Release Notes. September P Acano solution Acano Server & VM Release 1.8.1 Release Notes September 2015 76-1005-20-P Contents Contents 1 Introduction... 4 2 New Features/Changes in R1.8... 5 2.1 New Features for Lync meetings...

More information

Acano solution. Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide. September B

Acano solution. Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide. September B Acano solution Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide September 2015 76-1056-02-B Contents Contents 1 Introduction... 3 1.1 How to Use this Guide... 3 1.1.1 Commands... 4 2 H323

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.3. H.323 Gateway Deployment Guide. December 20, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.3. H.323 Gateway Deployment Guide. December 20, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.3 H.323 Gateway Deployment Guide December 20, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 4 1.1 How to Use this Guide 5 1.1.1 Commands

More information

Acano solution. Acano Server & VM Release R1.9. Single Split Server Deployment Guide. 06 September E

Acano solution. Acano Server & VM Release R1.9. Single Split Server Deployment Guide. 06 September E Acano solution Acano Server & VM Release R1.9 Single Split Server Deployment Guide 06 September 2016 76-1054-04-E Contents 1 Introduction 7 1.1 How to Use this Guide 8 1.1.1 Commands 9 1.1.2 Management

More information

Acano solution. Acano Server & VM Release Release Notes. June L

Acano solution. Acano Server & VM Release Release Notes. June L Acano solution Acano Server & VM Release 1.9.0 Release Notes June 2016 76-1005-21-L Contents 1 Introduction 4 2 New Features/Changes in R1.9 5 2.1 Recording meetings 5 2.1.1 Overview of steps to configuring

More information

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. March 13, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. March 13, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.0.12 Release Notes March 13, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 4 2 New Features/Changes in 2.0 6 2.1 Introducing the Cisco

More information

Acano solution. Acano Server & VM Release Release Notes. September V

Acano solution. Acano Server & VM Release Release Notes. September V Acano solution Acano Server & VM Release 1.9.5 Release Notes September 2016 76-1005-21-V Contents 1 Introduction 4 2 New Features/Changes in R1.9 5 2.1 Recording meetings 5 2.1.1 Overview of steps to configuring

More information

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. March 05, 2018

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. March 05, 2018 Cisco Meeting Server Cisco Meeting Server Release 2.3.0 Release Notes March 05, 2018 Cisco Systems, Inc. www.cisco.com Contents What's changed 4 1 Introduction 5 1.1 End Of Software Maintenance 6 2 New

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.2. Scalability & Resilience Server Deployment Guide. January 24,

Cisco Meeting Server. Cisco Meeting Server Release 2.2. Scalability & Resilience Server Deployment Guide. January 24, Cisco Meeting Server Cisco Meeting Server Release 2.2 Scalability & Resilience Server Deployment Guide January 24, 2018 Cisco Systems, Inc. www.cisco.com Contents What's new 9 1 Introduction 10 1.1 How

More information

Cisco Meeting Server. Deployment Planning and Preparation Guide. December 20, Cisco Systems, Inc.

Cisco Meeting Server. Deployment Planning and Preparation Guide. December 20, Cisco Systems, Inc. Cisco Meeting Server Deployment Planning and Preparation Guide December 20, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 5 1.1 Configuring the Meeting Server 7 1.2 Using Call Control

More information

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. January 05, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. January 05, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.1.0 Release Notes January 05, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 4 2 New Features/Changes in 2.1 6 2.1 Call Bridge Groups

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.3. Scalability & Resilience Server Deployment Guide. March 20, 2018

Cisco Meeting Server. Cisco Meeting Server Release 2.3. Scalability & Resilience Server Deployment Guide. March 20, 2018 Cisco Meeting Server Cisco Meeting Server Release 2.3 Scalability & Resilience Server Deployment Guide March 20, 2018 Cisco Systems, Inc. www.cisco.com Contents What's new 9 1 Introduction 10 1.1 How to

More information

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. May 12, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. May 12, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.1.7 Release Notes May 12, 2017 Cisco Systems, Inc. www.cisco.com Contents What's changed 5 1 Introduction 6 2 New Features/Changes in 2.1 8 2.1 Load

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.2. Release Notes. May 10, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.2. Release Notes. May 10, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.2 Release Notes May 10, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 4 2 New Features/Changes previewed in 2.2 6 2.1 Displaying security

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.3. with Cisco Unified Communications Manager Deployment Guide

Cisco Meeting Server. Cisco Meeting Server Release 2.3. with Cisco Unified Communications Manager Deployment Guide Cisco Meeting Server Cisco Meeting Server Release 2.3 with Cisco Unified Communications Manager Deployment Guide May 11, 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 1 Introduction

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.0. Single Split Server Deployment Guide. December 15, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.0. Single Split Server Deployment Guide. December 15, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.0 Single Split Server Deployment Guide December 15, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 7 1.1 How to use this guide 8 1.1.1

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.0. Single Combined Server Deployment Guide. February 02, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.0. Single Combined Server Deployment Guide. February 02, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.0 Single Combined Server Deployment Guide February 02, 2018 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 7 1.1 How to use this guide 8 1.1.1

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.4. Single Split Server Deployment Guide. January 16, 2019

Cisco Meeting Server. Cisco Meeting Server Release 2.4. Single Split Server Deployment Guide. January 16, 2019 Cisco Meeting Server Cisco Meeting Server Release 2.4 Single Split Server Deployment Guide January 16, 2019 Cisco Systems, Inc. www.cisco.com Contents What's new 8 1 Introduction 9 1.1 Using the Cisco

More information

Acano solution. Third Party Call Control Guide. 07 June G

Acano solution. Third Party Call Control Guide. 07 June G Acano solution Third Party Call Control Guide 07 June 2016 76-1055-01-G Contents 1 Introduction 3 1.1 How to Use this Guide 3 1.1.1 Commands 5 2 Example of Configuring a SIP Trunk to CUCM 6 2.1 Prerequisites

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.1. with Cisco Unified Communications Manager Deployment Guide. November 08,

Cisco Meeting Server. Cisco Meeting Server Release 2.1. with Cisco Unified Communications Manager Deployment Guide. November 08, Cisco Meeting Server Cisco Meeting Server Release 2.1 with Cisco Unified Communications Manager Deployment Guide November 08, 2017 Cisco Systems, Inc. www.cisco.com Contents Change History 4 1 Introduction

More information

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. June 06, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. June 06, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.2.2 Release Notes June 06, 2017 Cisco Systems, Inc. www.cisco.com Contents What's changed 4 1 Introduction 5 1.1 Interoperability with other Cisco products

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.2. Single Combined Server Deployment Guide. January 25, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.2. Single Combined Server Deployment Guide. January 25, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.2 Single Combined Server Deployment Guide January 25, 2018 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 7 1.1 How to use this guide 8 1.1.1

More information

Cisco TelePresence Conductor with Cisco Unified Communications Manager

Cisco TelePresence Conductor with Cisco Unified Communications Manager Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide TelePresence Conductor XC4.0 Unified CM 10.5(2) January 2016 Contents Introduction 6 About this document 6 Related

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.3. Single Combined Server Deployment Guide. July 03, 2018

Cisco Meeting Server. Cisco Meeting Server Release 2.3. Single Combined Server Deployment Guide. July 03, 2018 Cisco Meeting Server Cisco Meeting Server Release 2.3 Single Combined Server Deployment Guide July 03, 2018 Cisco Systems, Inc. www.cisco.com Contents What's new 8 1 Introduction 9 1.1 How to use this

More information

Acano solution. Third Party Call Control Guide. December F

Acano solution. Third Party Call Control Guide. December F Acano solution Third Party Call Control Guide December 2015 76-1055-01-F Contents Contents 1 Introduction... 3 1.1 How to Use this Guide... 3 1.1.1 Commands... 4 2 Example of Configuring a SIP Trunk to

More information

Acano Solution. Acano Server Release Release Notes. Acano. December I

Acano Solution. Acano Server Release Release Notes. Acano. December I Acano Solution Acano Server Release 1.0.12 Release Notes Acano December 2013 76-1005-12-I Contents Contents 1 Introduction 3 2 New Features/Changes in 1.0.12 3 2.1 Acano Solution Virtual Deployment Release...

More information

Acano solution. Deployment Planning and Preparation Guide. September C

Acano solution. Deployment Planning and Preparation Guide. September C Acano solution Deployment Planning and Preparation Guide September 2015 76-1051-01-C Contents Contents 1 Introduction... 4 2 Single Combined Acano Server Deployment... 5 2.1 VM host... 5 2.2 Syslog to

More information

Configure Recorder in CMS/Acano Call Bridge

Configure Recorder in CMS/Acano Call Bridge Configure Recorder in CMS/Acano Call Bridge Contents Introduction Prerequisites Requirements Components Used Background Information Deployments Supported Deployments Other Setup Configure Step 1. Configure

More information

Configure and Integrate CMS Single Combined

Configure and Integrate CMS Single Combined Configure and Integrate CMS Single Combined Contents Introduction Prerequisites Requirements Components Used Configure Step1. Access CMS Step 2. Change the Hostname Step 3. Configure network settings Step

More information

Cisco TelePresence Conductor with Cisco Unified Communications Manager

Cisco TelePresence Conductor with Cisco Unified Communications Manager Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide XC2.2 Unified CM 8.6.2 and 9.x D14998.09 Revised March 2014 Contents Introduction 4 About this document 4 Further

More information

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. March 25, 2019

Cisco Meeting Server. Cisco Meeting Server Release Release Notes. March 25, 2019 Cisco Meeting Server Cisco Meeting Server Release 2.4.4 Release Notes March 25, 2019 Cisco Systems, Inc. www.cisco.com Contents What's changed 5 1 Introduction 6 1.1 Cisco Meeting Server platform maintenance

More information

Cisco TelePresence Conductor with Unified CM

Cisco TelePresence Conductor with Unified CM Cisco TelePresence Conductor with Unified CM Deployment Guide TelePresence Conductor XC3.0 Unified CM 10.x Revised February 2015 Contents Introduction 5 About this document 5 Related documentation 5 About

More information

Cisco Meeting Server. Single Server Simplified Setup Guide. October 26, 2018

Cisco Meeting Server. Single Server Simplified Setup Guide. October 26, 2018 Cisco Meeting Server Single Server Simplified Setup Guide October 26, 2018 Cisco Systems, Inc. www.cisco.com What's new What's new Version October 25, 2018 Change First version published. Single Server

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.0+ Multi-tenancy considerations. December 20, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.0+ Multi-tenancy considerations. December 20, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.0+ Multi-tenancy considerations December 20, 2017 Cisco Systems, Inc. www.cisco.com Contents Change History 3 1 Introduction 4 1.1 How to use this Document

More information

Implementing, Configuring and Managing Cisco Meeting Server (ICMCMS-CT)

Implementing, Configuring and Managing Cisco Meeting Server (ICMCMS-CT) 6210 Central Ave, Portage, IN. 46368 Phone: 219.764.3800 Fax: 219.764.3805 Web: http://www.ctclc.com Implementing, Configuring and Managing Cisco Meeting Server (ICMCMS-CT) In this course, students will

More information

Multiparty Conferencing for Audio, Video and Web Collaboration using Cisco Meeting Server

Multiparty Conferencing for Audio, Video and Web Collaboration using Cisco Meeting Server Multiparty Conferencing for Audio, Video and Web Collaboration using Cisco Meeting Server Paul Giralt (pgiralt@cisco.com) Markus Schneider (marschne@cisco.com) LTRCOL-2250 Agenda Cisco Meeting Server Overview

More information

Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2

Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2 Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2 First Published: 2017-11-29 Last Modified: 2017-12-01 Americas Headquarters Cisco Systems,

More information

Cisco Meeting App. Troubleshooter for desktop and mobile. December 06, 2017

Cisco Meeting App. Troubleshooter for desktop and mobile. December 06, 2017 Cisco Meeting App Troubleshooter for desktop and mobile apps, WebRTC, and SIP endpoints December 06, 2017 Troubleshooter for desktop and mobile apps, WebRTC, and SIP endpoints : Troubleshooter 1 Contents

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.0. Certificate Guidelines for Single Combined Server Deployments. January 12,

Cisco Meeting Server. Cisco Meeting Server Release 2.0. Certificate Guidelines for Single Combined Server Deployments. January 12, Cisco Meeting Server Cisco Meeting Server Release 2.0 Certificate Guidelines for Single Combined Server Deployments January 12, 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 1 Introduction

More information

Configure Proxy WebRTC With CMS over Expressway with Dual Domain

Configure Proxy WebRTC With CMS over Expressway with Dual Domain Configure Proxy WebRTC With CMS over Expressway with Dual Domain Contents Introduction Prerequisites Requirements Components Used Configure Network Diagram Technical Information DNS Configuration Internal

More information

Cisco Expressway Session Classification

Cisco Expressway Session Classification Cisco Expressway Session Classification Deployment Guide First Published: December 2016 Last Updated: December 2017 Expressway X8.10 Cisco Systems, Inc. www.cisco.com 2 Preface Preface Change History Table

More information

Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure

Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure Deployment Guide First Published: December 2016 Last Updated: October 2017 Expressway X8.9.2 Cisco Systems, Inc. www.cisco.com

More information

Acano Solution. Acano Server Release Release Notes. Acano. February Ahb

Acano Solution. Acano Server Release Release Notes. Acano. February Ahb Acano Solution Acano Server Release 1.2.14 Release Notes Acano February 2015 76-1005-15-Ahb Contents Contents 1 Introduction 4 1.1 Before upgrading... 4 1.2 After upgrading... 4 2 New Features/Changes

More information

Cisco Expressway Cluster Creation and Maintenance

Cisco Expressway Cluster Creation and Maintenance Cisco Expressway Cluster Creation and Maintenance Deployment Guide Cisco Expressway X8.6 July 2015 Contents Introduction 4 Prerequisites 5 Upgrading an X8.n cluster to X8.6 6 Prerequisites 6 Upgrade Expressway

More information

Unified Communications in RealPresence Access Director System Environments

Unified Communications in RealPresence Access Director System Environments [Type the document title] 2.1.0 March 2013 3725-78704-001A Deploying Polycom Unified Communications in RealPresence Access Director System Environments Polycom Document Title 1 Trademark Information POLYCOM

More information

Cisco TelePresence Conductor with Cisco VCS (Policy Service)

Cisco TelePresence Conductor with Cisco VCS (Policy Service) Cisco TelePresence Conductor with Cisco VCS (Policy Service) Deployment Guide TelePresence Conductor XC3.0 Cisco VCS X8.x Revised January 2015 Contents Introduction 5 About the Cisco TelePresence Conductor

More information

Solution Sheet. The Acano solution. March 2016

Solution Sheet. The Acano solution. March 2016 Solution Sheet The Acano solution March 2016 Imagine having all of the tools your team needs to work in one place and always accessible. That s Acano. 1. What Acano can do for your team Acano joins video,

More information

Cisco TelePresence VCS Cluster Creation and Maintenance

Cisco TelePresence VCS Cluster Creation and Maintenance Cisco TelePresence VCS Cluster Creation and Maintenance Deployment Guide Cisco VCS X8.5 Cisco TMS 13.2 or later December 2014 Contents Introduction 4 Prerequisites 5 Upgrading an X7.1 or later cluster

More information

Cisco Expressway with Jabber Guest

Cisco Expressway with Jabber Guest Cisco Expressway with Jabber Guest Deployment Guide First Published: Decemeber 2016 Cisco Expressway X8.9 Cisco Jabber Guest Server 10.6.9 (or later) Cisco Systems, Inc. www.cisco.com Contents Preface

More information

Yealink Meeting Server (YMS)

Yealink Meeting Server (YMS) Yealink Meeting (YMS) Powerful collaboration software makes meeting simpler Enterprise Communication Challenges Globalization, mobile devices and an on-the-go work environment are changing how and where

More information

Vidyo Server for WebRTC. Administrator Guide

Vidyo Server for WebRTC. Administrator Guide Vidyo Server for WebRTC Administrator Guide Product Version 3.2 Document Version A April, 2016 TABLE OF CONTENTS Overview... 1 Understanding the Configuration Procedure... 1 1. Using Vidyo Server for WebRTC

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.1. Certificate Guidelines for Scalable and Resilient Server Deployments.

Cisco Meeting Server. Cisco Meeting Server Release 2.1. Certificate Guidelines for Scalable and Resilient Server Deployments. Cisco Meeting Server Cisco Meeting Server Release 2.1 Certificate Guidelines for Scalable and Resilient Server Deployments January 12, 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 1

More information

Polycom RealPresence Access Director System

Polycom RealPresence Access Director System Release Notes 3.1.1 April 2014 3725-78700-001C1 Polycom RealPresence Access Director System Polycom announces the release of the Polycom RealPresence Access Director system, version 3.1.1. This document

More information

Installing and Configuring VMware Identity Manager Connector (Windows) OCT 2018 VMware Identity Manager VMware Identity Manager 3.

Installing and Configuring VMware Identity Manager Connector (Windows) OCT 2018 VMware Identity Manager VMware Identity Manager 3. Installing and Configuring VMware Identity Manager Connector 2018.8.1.0 (Windows) OCT 2018 VMware Identity Manager VMware Identity Manager 3.3 You can find the most up-to-date technical documentation on

More information

Polycom RealPresence Access Director System

Polycom RealPresence Access Director System Release Notes Polycom RealPresence Access Director System 4.0 June 2014 3725-78700-001D Polycom announces the release of the Polycom RealPresence Access Director system, version 4.0. This document provides

More information

SIP Proxy Deployment Guide. SIP Server 8.1.1

SIP Proxy Deployment Guide. SIP Server 8.1.1 SIP Proxy Deployment Guide SIP Server 8.1.1 5/4/2018 Table of Contents SIP Proxy 8.1 Deployment Guide 3 SIP Proxy Architecture and Deployment 4 Supported Features 7 Prerequisites 9 Deploying SIP Proxy

More information

Cisco Expressway Web Proxy for Cisco Meeting Server

Cisco Expressway Web Proxy for Cisco Meeting Server Cisco Expressway Web Proxy for Cisco Meeting Server Deployment Guide First Published: December 2016 Last Updated: December 2017 Expressway X8.10 Cisco Systems, Inc. www.cisco.com Preface Preface Change

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.0. API Reference Guide. January 12, Cisco Systems, Inc.

Cisco Meeting Server. Cisco Meeting Server Release 2.0. API Reference Guide. January 12, Cisco Systems, Inc. Cisco Meeting Server Cisco Meeting Server Release 2.0 API Reference Guide January 12, 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 9 1 General Information 10 1.1 How to Use this Document

More information

Pexip Infinity v11.1 Release Notes

Pexip Infinity v11.1 Release Notes Pexip Infinity v11.1 Release Notes Contents Introduction 1 Upgrading to version 11.1 2 New features and improvements in this release 3 Changes in functionality in this release 6 Issues fixed in v11.1 6

More information

Acano solution 1.6. Customization Guidelines. May S

Acano solution 1.6. Customization Guidelines. May S Acano solution 1.6 Customization Guidelines May 2015 76-1032-03-S Contents Contents 1 Introduction... 3 1.1 License Keys... 3 1.2 Web Server Requirements... 4 2 WebRTC Client Customization... 5 2.1 File

More information

Cisco Expressway Cluster Creation and Maintenance

Cisco Expressway Cluster Creation and Maintenance Cisco Expressway Cluster Creation and Maintenance Deployment Guide First Published: December 2009 Last Updated: April 2017 Cisco Expressway X8.9.2 Cisco Systems, Inc. www.cisco.com Contents Preface 3 Change

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.3. Certificate Guidelines for Single Split Server Deployments. January 12,

Cisco Meeting Server. Cisco Meeting Server Release 2.3. Certificate Guidelines for Single Split Server Deployments. January 12, Cisco Meeting Server Cisco Meeting Server Release 2.3 Certificate Guidelines for Single Split Server Deployments January 12, 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 1 Introduction

More information

Setting Up an Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection

Setting Up an Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection up Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection Up an Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection, page 1 Up an Alcatel 4400 Digital PIMG Integration with Cisco

More information

IP Office Platform R11.0

IP Office Platform R11.0 Issue 03d - (09 October 2018) Contents 8. Remote SIP Deskphones 8.1 Provisioning... the Deskphones 59 8.2 Configuring... Application Rules 61 1.1 Example Schematic... 4 8.3 Configuring... Media Rules 61

More information

Cisco Meeting Server (former Acano)

Cisco Meeting Server (former Acano) Cisco Meeting Server (former Acano) Ken Reeves Fall 2016 1 Meeting Objectives Overview of Acano integration into Cisco Opportunity to scale Acano-Cisco Meeting Server, globally Technical Overview of Cisco

More information

ACANO SOLUTION RESILIENT ARCHITECTURE. White Paper. Mark Blake, Acano CTO

ACANO SOLUTION RESILIENT ARCHITECTURE. White Paper. Mark Blake, Acano CTO ACANO SOLUTION RESILIENT ARCHITECTURE White Paper Mark Blake, Acano CTO September 2014 CONTENTS Introduction... 3 Definition of Resilience... 3 Achieving Resiliency... 4 Managing Your Data Secure from

More information

Setting Up a Mitel SX-2000 Digital PIMG Integration with Cisco Unity Connection

Setting Up a Mitel SX-2000 Digital PIMG Integration with Cisco Unity Connection Up a Mitel SX-2000 Digital PIMG Integration with Cisco Unity Connection Up a Mitel SX-2000 Digital PIMG Integration, page 1 Up a Mitel SX-2000 Digital PIMG Integration Task List for Mitel SX-2000 PIMG

More information

Cisco Meeting Management

Cisco Meeting Management Cisco Meeting Management Cisco Meeting Management 1.0 Release Notes December 07, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 Introduction 4 1.1 The software 4 2 Deploying Meeting Management with

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.4 and later. API Reference Guide. March 25, 2019

Cisco Meeting Server. Cisco Meeting Server Release 2.4 and later. API Reference Guide. March 25, 2019 Cisco Meeting Server Cisco Meeting Server Release 2.4 and later API Reference Guide March 25, 2019 Cisco Systems, Inc. www.cisco.com Contents Change History 11 1 General Information 13 1.1 How to Use this

More information

Deploy Webex Video Mesh

Deploy Webex Video Mesh Video Mesh Deployment Task Flow, on page 1 Install Webex Video Mesh Node Software, on page 2 Log in to the Webex Video Mesh Node Console, on page 4 Set the Network Configuration of the Webex Video Mesh

More information

Cluster creation and maintenance

Cluster creation and maintenance Cluster creation and maintenance Cisco TelePresence Deployment Guide Cisco VCS X6.1 Cisco TMS 12.6 or later D14367.08 May 2011 Contents Contents Document revision history... 5 Introduction... 6 Prerequisites...

More information

Configure Call Control

Configure Call Control Call Control Overview, page 1 Cisco Expressway and TelePresence Configuration Tasks, page 2 Configuring Cisco Unified Communications Manager, page 5 Provisioning Endpoint Display Names, page 10 Call Control

More information

Setting up Alcatel 4400 Digital PIMG Integration

Setting up Alcatel 4400 Digital PIMG Integration up Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection Up an Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection, on page 1 Up an Alcatel 4400 Digital PIMG Integration with

More information

Acano solution. Certificate Guidelines R1.7. for Single Combined Acano Server Deployments. March K

Acano solution. Certificate Guidelines R1.7. for Single Combined Acano Server Deployments. March K Acano solution Certificate Guidelines R1.7 for Single Combined Acano Server Deployments March 2016 76-1053-01-K This guide is part of the documentation set (shown in Figure 1) for the Acano server. The

More information

Unified Communications Mobile and Remote Access via Cisco Expressway

Unified Communications Mobile and Remote Access via Cisco Expressway Unified Communications Mobile and Remote Access via Cisco Expressway Deployment Guide Cisco Expressway X8.1.1 or later Cisco Unified CM 9.1(2)SU1 or later D15068.01 April 2014 Contents Mobile and remote

More information

Acano solution. Virtualized Deployment R1.7 Installation Guide. March G

Acano solution. Virtualized Deployment R1.7 Installation Guide. March G Acano solution Virtualized Deployment R1.7 Installation Guide March 2016 76-1025-06-G Contents Contents 1 Introduction... 3 1.1 How to use this Guide... 3 1.2 Before You Start... 4 1.2.1 About the Acano

More information

Cisco Meeting Server. Load Balancing Calls Across Cisco Meeting Servers. White Paper. 22 January Cisco Systems, Inc.

Cisco Meeting Server. Load Balancing Calls Across Cisco Meeting Servers. White Paper. 22 January Cisco Systems, Inc. Cisco Meeting Server Load Balancing Calls Across Cisco Meeting Servers White Paper 22 January 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 Introduction 5 Load balancing across Cisco

More information

Cisco TelePresence MCU Series

Cisco TelePresence MCU Series Cisco TelePresence MCU Series Administrator Guide 4.4 (3.42) 15010.01 December 2012 Contents Using the web interface 7 Logging into the web interface 8 Failing to log into the web interface 9 Joining and

More information

PCoIP Connection Manager for Amazon WorkSpaces

PCoIP Connection Manager for Amazon WorkSpaces PCoIP Connection Manager for Amazon WorkSpaces Version 1.0.7 Administrators' Guide TER1408002-1.0.7 Introduction Amazon WorkSpaces is a fully managed cloud-based desktop service that enables end users

More information

Cisco Meeting Server. Administrator Quick Reference Guide. Screen Layouts and Pane Placement. October 02, Cisco Systems, Inc.

Cisco Meeting Server. Administrator Quick Reference Guide. Screen Layouts and Pane Placement. October 02, Cisco Systems, Inc. Cisco Meeting Server Administrator Quick Reference Guide Screen Layouts and Pane Placement October 02, 2018 Cisco Systems, Inc. www.cisco.com Contents Introduction 3 Layouts on SIP endpoints 4 Overview

More information

Cisco Unified Communications XMPP Federation

Cisco Unified Communications XMPP Federation Cisco Unified Communications XMPP Federation Deployment Guide First Published: December 2014 Last Updated: March 2018 Cisco Expressway X8.10 IM and Presence Service 9.1.1 or later Cisco Systems, Inc. www.cisco.com

More information

Jamvee Unified Communications

Jamvee Unified Communications Jamvee Unified Communications Enterprise Firewall/ Proxy Server Guidelines Jamvee Unified Communications Enterprise Firewall/Proxy Server Guidelines This guide provides information required to provision

More information

Cisco Expressway Cluster Creation and Maintenance

Cisco Expressway Cluster Creation and Maintenance Cisco Expressway Cluster Creation and Maintenance Deployment Guide First Published: December 2009 Last Updated: December 2017 Cisco Expressway X8.10 Cisco Systems, Inc. www.cisco.com Contents Preface 3

More information

Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(1)

Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(1) Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(1) First Published: 2014-01-29 Last Modified: 2017-12-01 Americas Headquarters Cisco Systems, Inc.

More information

Interdomain Federation for the IM and Presence Service, Release 10.x

Interdomain Federation for the IM and Presence Service, Release 10.x First Published: 2014-01-29 Last Modified: 2018-11-05 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)

More information

Caution: Once you upgrade to v3.5, you cannot downgrade to an earlier version.

Caution: Once you upgrade to v3.5, you cannot downgrade to an earlier version. Release Notes LifeSize Transit Release v3.5 Upgrading from v3.0.1 to v3.5... 1 New Features... 2 Resolved Issues... 2 Known Issues... 3 Product Limitations... 4 Browser Support... 5 Interoperability...

More information

Cisco TelePresence Video Communication Server

Cisco TelePresence Video Communication Server Cisco TelePresence Video Communication Server Administrator Guide D14049.09 December 2010 Software version: X6 Contents Contents Contents 2 About the Cisco TelePresence Video Communication Server (Cisco

More information

VidyoGateway. Administrator Guide. Product Version Document Version A February, 2017

VidyoGateway. Administrator Guide. Product Version Document Version A February, 2017 VidyoGateway Administrator Guide Product Version 3.5.1 Document Version A February, 2017 2017 Vidyo, Inc. all rights reserved. Vidyo s technology is covered by one or more issued or pending United States

More information

Acano solution. Virtualized Deployment R1.1 Installation Guide. Acano. May D

Acano solution. Virtualized Deployment R1.1 Installation Guide. Acano. May D Acano solution Virtualized Deployment R1.1 Installation Guide Acano May 2014 76-1025-03-D Contents Contents 1 Introduction... 3 1.1 Before You Start... 3 1.1.1 About the Acano virtualized solution... 3

More information

Integrating VoIP Phones and IP PBX s with VidyoGateway

Integrating VoIP Phones and IP PBX s with VidyoGateway Integrating VoIP Phones and IP PBX s with VidyoGateway Updated February 2011 INDEX: I. ABSTRACT.1 II. III. IV. VIDYOGATEWAY OVERVIEW.. 1 NETWORK TOPOLOGIES AND DEFINITIONS...2 CONNECTING TO VIDYOCONFERENCES

More information

Pexip Infinity v17.2 Release Notes

Pexip Infinity v17.2 Release Notes Pexip Infinity v17.2 Release Notes Contents Introduction 1 Upgrading to version 17.2 2 New features and improvements in this release 4 Changes in functionality in this release 6 Issues fixed in version

More information

while the LAN interface is in the DMZ. You can control access to the WAN port using either ACLs on the upstream router, or the built-in netfilter

while the LAN interface is in the DMZ. You can control access to the WAN port using either ACLs on the upstream router, or the built-in netfilter When the LAN interface is in a private IP DMZ, you can write the firewall rule-set to restrict the number of hosts the VBP can communicate with to only those devices. This enhances security. You can also

More information

Application Note 3Com VCX Connect with SIP Trunking - Configuration Guide

Application Note 3Com VCX Connect with SIP Trunking - Configuration Guide Application Note 3Com VCX Connect with SIP Trunking - Configuration Guide 28 May 2009 3Com VCX Connect Solution SIP Trunking Table of Contents 1 3COM VCX CONNECT AND INGATE... 1 1.1 SIP TRUNKING SUPPORT...

More information

Designing and Deploying Multiparty Conferencing for Telepresence Video

Designing and Deploying Multiparty Conferencing for Telepresence Video BRKCOL-2803 Designing and Deploying Multiparty Conferencing for Telepresence Video Abhijit Dey, Technical Marketing Engineer Albert Amparan, Technical Marketing Engineer Cisco Spark How Questions? Use

More information

VMware AirWatch Content Gateway for Linux. VMware Workspace ONE UEM 1811 Unified Access Gateway

VMware AirWatch Content Gateway for Linux. VMware Workspace ONE UEM 1811 Unified Access Gateway VMware AirWatch Content Gateway for Linux VMware Workspace ONE UEM 1811 Unified Access Gateway You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

Cisco Meeting App. Cisco Meeting App (ios) Release Notes. October 06, 2017

Cisco Meeting App. Cisco Meeting App (ios) Release Notes. October 06, 2017 Cisco Meeting App Cisco Meeting App (ios) 1.9.19.0 Release Notes October 06, 2017 Cisco Systems, Inc. www.cisco.com Contents 1 What's changed in the Release Notes 1 2 Introduction 2 2.1 Installation Instructions

More information

Cisco TelePresence MCU 4.3

Cisco TelePresence MCU 4.3 Cisco TelePresence MCU 4.3 Product administration guide D14845.03 April 2012 Contents Using the web interface 7 Logging into the web interface 7 Failing to log into the web interface 7 Joining and viewing

More information

Pexip Infinity v10.2 Release Notes

Pexip Infinity v10.2 Release Notes Pexip Infinity v10.2 Release Notes Contents Introduction 1 Upgrading to version 10.2 2 New features and improvements in this release 3 Issues fixed in v10.2 5 Issues fixed in v10.1 5 Issues fixed in v10

More information

Cisco TelePresence Conductor

Cisco TelePresence Conductor Cisco TelePresence Conductor Deployment Guide XC1.2 D14827.02 May 2012 Contents Contents Introduction... 4 About the Cisco TelePresence Conductor... 4 Call flow with the Cisco TelePresence Conductor...

More information