Jabber for android register issue

[kenji8462]

Dear All,

I am deploying a Jabber enviroment

But I faced to some issue of registering Jabber to CUCM

First I found that Jabber for android can registered to my CUCM

But MRA can work find.

That is, Jabber for Android can register to CUCM through vcs-c & vcs-e in the internet

but can not register to CUCM in intranet

And I found that some Android kernal are not support non-secure register

So I change the setting from non-secure to secure (Phone security profile), using authenticated mode and TLS port 5061

So jabber for android can register to CUCM in intranet

but unfortunately the Jabber now can not register to CUCM in internet through vcs-c & vcs-e

I think maybe the connection between CUCM and vcs-c is the problem because I use only TCP connection between CUCM and vcs-c

If I want to register Jabber for android in secure mode, does the connection between CUCM and vcs-c should be TLS??

Or the I loss some key point in my deployment???

Thanks for answer.

[Jaime Valencia · Accepted solution]

If you're using a device or Android version, or both, that are not officially listed as supported, then you only get a it *might* work guarantee.

The connection for the MRA auto generated zone for CUCM is read only, you cannot change anything. It's going to be TCP, and you cannot change that.

The connection is secure all the way from the device to EXP-E, then to EXP-C and from EXP-C to CUCM, it's just SCCP and RTP, if you want to configure a secured connection, you only need to adjust the device security profile and add it to the certificates (this is all explained in the MRA config guide)

For any of the problems you're having, you want to get a PRT, and if you want to troubleshoot the MRA problem, EXP-C and EXP-E logs. Once you review them, you'll find more info on what's wrong.

[kenji8462]

Hi~ Thanks for answer

So even if the TLS verify mode is setted to off, 

Android Jabber still can register to CUCM by secured connection?

[Jaime Valencia]

Assuming you configured this as per the MRA guide, and have mixed mode, yes.

[kenji8462]

Hi~

I try to check the log of the vcs-c

And found some tls alert

I think this problem is about the incorrect certification

I will check the certification again

Thank for help!

[kenji8462]

Hi Jaime,

I generate the certificate of VCSC & VCSE with the phone secure profile name

And solve the certificate problem

But I face a new problem that my android jabber still can not register to CUCM

here is the event log in VCSC

tvcs: Event="Registration Rejected" Reason="Unknown domain" Service="SIP" Src-ip="61.67.111.111" Src-port="7001" Protocol="TCP" AOR="sip:192.168.1.220" Contact="<sip:2a8b565a-f9cb-1d15-9ca0-440dabb157ce@192.168.43.245:53982;transport\=tls>;+sip.instance\="<urn:uuid:00000000-0000-0000-0000-7cef8a3f7abd>";+u.sip!devicename.ccm.cisco.com\="BOT5535";+u.sip!model.ccm.cisco.com\="575";video" Duration="660" Level="1" UTCTime="2016-09-06 03:56:41,763"

tvcs: Event="Registration Requested" Service="SIP" Src-ip="61.67.111.111" Src-port="7001" Protocol="TCP" AOR="sip:192.168.1.220" Contact="<sip:2a8b565a-f9cb-1d15-9ca0-440dabb157ce@192.168.43.245:53982;transport\=tls>;+sip.instance\="<urn:uuid:00000000-0000-0000-0000-7cef8a3f7abd>";+u.sip!devicename.ccm.cisco.com\="BOT5535";+u.sip!model.ccm.cisco.com\="575";video" Duration="660" Level="1" UTCTime="2016-09-06 03:56:41,763"

log in VCSE

tvcs: Event="Registration Rejected" Reason="Unknown domain" Service="SIP" Src-ip="111.81.64.111" Src-port="53982" Protocol="TCP" AOR="sip:192.168.1.220" Contact="<sip:2a8b565a-f9cb-1d15-9ca0-440dabb157ce@192.168.43.245:53982;transport\=tls>;+sip.instance\="<urn:uuid:00000000-0000-0000-0000-7cef8a3f7abd>";+u.sip!devicename.ccm.cisco.com\="BOT5535";+u.sip!model.ccm.cisco.com\="575";video" Duration="660" Level="1" UTCTime="2016-09-06 03:56:41,765"

tvcs: Event="Registration Requested" Service="SIP" Src-ip="111.81.64.111" Src-port="53982" Protocol="TCP" AOR="sip:192.168.1.220" Contact="<sip:2a8b565a-f9cb-1d15-9ca0-440dabb157ce@192.168.43.245:53982;transport\=tls>;+sip.instance\="<urn:uuid:00000000-0000-0000-0000-7cef8a3f7abd>";+u.sip!devicename.ccm.cisco.com\="BOT5535";+u.sip!model.ccm.cisco.com\="575";video" Duration="660" Level="1" UTCTime="2016-09-06 03:56:41,765"

The phone register status in CUCM is rejected

Also

I check the domain of both VCSC & VCSE, the domain I use to sign in is added to the VCSC & VCSE

And my I phone can register successfully using non secure phone profile

What could the problem be?