03-27-2015 09:41 AM - edited 03-18-2019 04:15 AM
hi folks,
I've deployed Collaboration Edge with VCS Control and Expressway:
my Jabber for iPhone succesfully can log in from Internet and it can IM but not calls and I see next messages in VCS Expressway when Jabber is logging in:
"Digest User" in the "Protocol Specific Information" section of Phone Configuration selected right user. in this Jabber I see following error "Failed to get device configuration". however Jabber for Windows and for Android hasn't such issues - they succesfully can log in from Internet and it can do calls and IM but I see next messages in VCS Expressway when Jabber is logging in. The same log line appears when Jabber for Android log in:
tvcs: Event="Inbound TLS Negotiation Error" Service="SIP" Src-ip="Client-in-the-Internet-IPaddress" Src-port="56751" Dst-ip="Expressway-IPaddress" Dst-port="5061" Detail="No SSL error available, probably remote disconnect" Protocol="TLS" Level="1" UTCTime="2015-03-27 14:19:11,769"
and I can't find any information which describe such types of error.
thanks!
05-12-2015 08:58 PM
Hi Ruslan,
Were you able to resolve this issue? I am currently running into the same problem and can't seem to find any information on it either. It works on windows but when I try and connect to my phone services on the iphone it doesn't work.
Thanks,
Mike
05-13-2015 01:39 AM
hi,
unfortunately no, there is a little information in the Internet regarding this error. I still haven't resolve this issue.
but since then I have done many reconfigurations and somehow Jabber for Iphone sometimes can connect phone services and I can't find out pattern of this behavior:).
as far as I remeber, major changes were updating CUCM and CUP from 10.5.1 to 10.5.2 and maybe migration of VCS to Expressway.
if you find out the truth, let me know please.
03-13-2016 11:19 PM
Hi Ruslan,
Do you have any luck to resolve the issue as I am hitting the same issue as well. Is this certificate related issue? Looking forward your reply, Thanks.
03-14-2016 01:59 AM
Hi,
I had the same problem.
In my case, the problem was caused by the Expressway E certificate.
It had the role Basic Constraint: "Subject Type=CA" assigned.
After signing a new CSR with End Entity role, the problem was fixed.
I can recommend to open a TAC case, my TAC engineer found the certificate error within minutes.
Johannes
03-14-2016 07:03 AM
hi,
great news!
unfortunately I don't have opportunity to test this solution now.
kelvinffhan I would appreciate if you reported back whether it solved your issue or no.
thanks in advance!
07-25-2017 10:54 AM
Hi Ruslan,
I have the same kind of problem: I cannot login to Phone Services from jabber on internet. And I'm getting same errors in log.
Did you find a solution? Certificate seems to be right.
07-25-2017 12:24 PM
hi,
seems like I've dealt with the issue but it was really long ago and unfortunately I don't remember details. sorry.
have you tried solution suggested above?
07-26-2017 06:21 AM
Hi Ruslan,
We are using self-signed certificates for now, will check that as soon as certificates will be signed. But I tried so many variations of settings, so now I'm not sure could it be so obvious issue like certificate. I have a NAT reflection through Sonicwall and I'm not sure is it translating everything properly. Anyways, I opened SR and hope Cisco guys will figure that out.
Thanks for quick respond!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: