On a Mac OSX system, you can use openssl to generate the base64 string. Let's start with the base64 conversion process. So, you will need to have that information handy. The API calls also are built using specific application hostnames in your environment. Therefore, you need a way to generate Base64 values (such as openssl). The web-based API on the Edge appliance uses API calls comprised of Base64 values. This troubleshooting step is a little more involved. In a properly implemented solution, this query should return one or more records that point to your Expressway Edge (or VCS-E) cluster.Īssuming everything is configured correctly and fully operational, the Jabber client will attempt to establish a TLS connection to one of your Edge appliances. If the client fails to receive a positive response to the UDS/cuplogin queries, it will then send a DNS SRV query is for _collab-edge._. In a MRA scenario, where a client is outside of the corporate network, the above SRV records should not be resolvable. _cuplogin._ : Legacy record that points to XMPP service on IM&P service _cisco-uds._ : Points to the UDS service on a UCM cluster Once the service domain is known, the Jabber client will go through the sub-process of Service Discovery. Though, the service domain can also be administratively assigned in the jabber-config.xml file. The service domain is usually specified by the user the first time they attempt to log into Jabber. For example, if my JID is then the service domain is. The service domain is derived from the Jabber ID (JID) assigned to the end user. Specifically, the Jabber client will query for specific DNS service records (SRV record) based on the assigned service domain. At this stage, the client is trying to determine if it is inside the corporate network or outside of the network. Upon initialization, the Jabber client enters into a "Service Discovery" mode.
0 Comments
Leave a Reply. |