Cisco Jabber Guest
webcommon logs
|
"IOException closing sock javax.net.ssl.SSLHandshakeException: General
SSLEngine problem" appears In the
Cisco Jabber Guest
webcommon-tomcat.log file.
|
When one of
these messages appears, it may indicate a problem with the Expressway
certificate that is uploaded to
Cisco Jabber Guest
Administration.
Verify that
the Expressway certificate that is uploaded to
Cisco Jabber Guest
Administration is either an Expressway certificate or the CA certificate that
signed it:
-
Check
the common name (CN) of the issuer and the subject of the certificate that is
uploaded to Expressway:
-
On
the Expressway, choose
.
-
Click
Show (decoded).
-
Check
the CN of the issuer and the subject of the certificate that is uploaded to
Cisco Jabber Guest
Administration:
-
Sign
in to
Cisco Jabber Guest
Administration.
-
Click
Settings, and then click
Secure SIP Trust Certificate.
-
Make
sure that Tomcat was restarted:
service tomcat-as-standalone.sh restart
|
Cisco
Expressway Event Log
|
tvcs:
Event="Outbound TLS Negotiation Error" Service="SIP" Src-ip="<ip
address>" Src-port="27510" Dst-ip="<ip address>" Dst-port="5061"
Detail="No SSL error available, probably remote disconnect" Protocol="TLS"
Level="1" UTCTime="yyyy-mm-dd
hh:mm:ss,732"
|
On Cisco
Expressway, status of zone for
Cisco Jabber Guest
server shows
Failed
|
SIP: Failed
to connect to
<IP address>:5061 : TLS negotiation failure
|
Cisco Jabber Guest
client
|
Failed to
acquire TURN credentials
|
This message
may mean that the call control and media settings for
Cisco Expressway-C
may not be configured correctly. Check the settings:
-
Sign in
to
Cisco Jabber Guest
Administration as an administrator.
-
Click
Settings, and then click
Call Control and Media.
-
Under
Cisco Expressway-C,
if
Request short-term TURN credentials from is set to
Expressway-C server specified above, make sure that
the value in the
Expressway-C (IP address or DNS name) field is
correct.
-
Check
the value in the
HTTP port field. The default value is
443 .
-
Check
the values in the
Cisco Expressway-C
administrator
Username and
Password fields:
-
Check
Cisco Expressway-C server
certificate or
Cisco Expressway-C certificate authority
certificate.
It must use RSA keys greater than or equal to 1024 bits and must not be signed with MD5.
|
Cisco Jabber Guest
client
|
Link Not
Found
|
Make sure
that the link is active: Click
Links, click the link, and check the
State settings to make sure that the link has not
expired.
|
Cisco Jabber Guest
client
|
Link not valid
|
This message
may mean that the link that has not yet been replicated to the
Cisco Jabber Guest
server that handles the request.
When you
create a click-to-call link on a
Cisco Jabber Guest
server that is a member of a cluster, you must allow a small amount of time
before that link is active on all servers in the cluster.
If you deploy
an application that creates links dynamically by using the link API and pushes
them to the
Cisco Jabber Guest
client, we recommend that you factor this replication delay into your design.
|
Cisco Jabber Guest
client
|
Missing SDP.
There was a networking error between your device and the server.
|
This message
may mean that
Cisco Jabber Guest
is unable to contact the TURN server. One possible cause is that multiple
network interfaces are enabled, including SW VPN. Another possible cause is
that a firewall or NAT blocking UDP port 3478 between the client and the
Cisco Expressway-E
(publicly accessible IP). Some home routers block all UDP.
|
Cisco Jabber Guest
client
|
Not found on
Accelerator
|
You may see
this message because the link between the
Cisco Expressway-C
and
Cisco Expressway-E
is down and domain information hasn't replicated from the
Cisco Expressway-C
to
Cisco Expressway-E.
On
Cisco Expressway-E,
when viewing Unified Communications status (choose
and click
View
ssh tunnel status), make sure that:
|
Cisco Jabber Guest
client
|
Server
error: class java.lang.IllegalStateException: Error creating sipServletRequest
ROAP_EXCEPTION
|
Apache
Tomcat may not be running, perhaps after an upgrade or server interruption.
Restart
Tomcat on the
Cisco Jabber Guest
Server:
service tomcat-as-standalone.sh restart .
|
Cisco Jabber Guest
client
|
SIP Error. The
destination associated with this link is not reachable.
|
You may see
this message for one of the following reasons:
-
The
directory number (DN) embedded in the link or associated with the link, does
not exist on the
Cisco Unified
Communications Manager
or
Cisco TelePresence Video
Communication Server.
-
The link
contains a URI (user@domain.com)
but the
Cisco Unified
Communications Manager
is not configured to route calls by URI. Use a DN instead.
|
Cisco Jabber Guest
client
|
TURN Error.
Your call attempt has failed due to incompatibility with your home or company
security infrastructure. Please contact your network administrator or check
your home network security settings.
|
This message
indicates that the web client could not allocate the TURN relay on the TURN
server. This could occur for one of the following reasons:
-
UDP port
3478 is blocked. You must allow this port inbound from the public Internet to
the
Cisco Expressway-E.
-
The DNS
record for the TURN server is not resolvable (must be a DNS A-record).
-
The
Expressway-E TURN Server (IP Address or DNS Name)
field and
Turn Port fields are not configured correctly in
Cisco Jabber Guest
Administration ().
-
The
Domain name (, under
Cisco Expressway-C) is not a configured domain name
on
Cisco Expressway-C
or is not configured for
Cisco Jabber Guest
services.
|