Jabber MRA Login Issue

[JustForVoice_2]

Hello,

I’m trying Jabber MRA, User can login internally without any issue. I have setup the Expressway C and E. traversal zone is active. And everything look OK as per the guide.

The only thing that I have is my customer did not create the SRV records till now. So I used advanced settings and I put the IP address of my Expressway-E. When I tried to log in I got the following error:

Cannot communicate with the server

Any help

[devils_advocate]

I think MRA needs the SRV records, I have tried using the IP or Hostname of the Exp-E box within Jabber and got the same error. 

Does it work with the SRV? 

[JustForVoice_2]

Thank you for your reply,

I'm trying to use the IP address because the SRV records are not configured. I'm waiting my customer to create the records.

Do I need to create the following SRV records:

h323cs
h323ls
sip
sip
sips
turn

or collab-edge is enough? 

[Prabath Godevithanage]

For the service records.please see here .You can select the service records according to the services that you'll be publishing.Edited my reply as i noted that you already got it going internally.Is it through the IP or the service discovery?

[john michael marie rodriguez]

What is the status of the zones to the Call Manager from Expressway C?

You can also try collecting Call Manager Service RTMT logs while logging in to Jabber MRA and check if you can see the SIP requests from your Jabber

[JustForVoice_2]

Hello,

After creating the SRV, I can login but the phone is not registered.

Form the client: Help>> show connection status:

Softphone: Not Connected.

Reason: Connection error. Ensure the server information in the Phone Services tab on the Options window is correct. Contact your system administrator for assistance.

From Inside phone registers.

[Philip Denton]

I have the same problem.  My MRA works (even with SSO) but Phone Services won't connect.  Everything else - voicemail, UDS, etc., is green across the board.  Any suggestions?

[Philip Denton]

TAC found the following warning in my logs.  In response my engineer told me to create a new SIP Trunk Security Profile on the SIP Trunk pointing to Expressway using port 5065 for SIP instead of 5060.  After resetting all the Jabber devices (TAB,TCT,CSF,BOT) everything seems to be working as expected!

2016-03-23T00:28:20-04:00 collabedge tvcs: UTCTime="2016-03-23 04:28:20,176" Module="network.sip" Level="INFO":  Action="Received"  Local-ip="x.x.x.x"  Local-port="7001"  Src-ip="y.y.y.y"  Src-port="25010"   Detail="Receive Response Code=405, Method=REGISTER, CSeq=102, To=sip:+15555555555@FQDN.com, Call-ID=5ce0c5ce-61d50003-0000594d-00000721@z.z.z.z, From-Tag=5ce0c5ce61d5000200001b72-00007c5a, To-Tag=848151973, Msg-Hash=13989714286384994303"

2016-03-23T00:28:20-04:00 collabedge tvcs: UTCTime="2016-03-23 04:28:20,176" Module="network.sip" Level="DEBUG":  Action="Received"  Local-ip="x.x.x.x"  Local-port="7001"  Src-ip="y.y.y.y"  Src-port="25010"  Msg-Hash="13989714286384994303"

 SIPMSG:

|SIP/2.0 405 Method Not Allowed

Via: SIP/2.0/TLS 10.1.199.15:7001;egress-zone=TraversalZone;branch=z9hG4bK236c9bc40d19f0708991e0b0eab0af05130.7eefa7d35f994f3a27d4260a70f2e44c;proxy-call-id=56cd741a-2fff-4c67-abe9-7e41a4b1c4dd;received=10.1.199.15;rport=7001;ingress-zone=TraversalZone,SIP/2.0/TLS z.z.z.z:53714;branch=z9hG4bK00006505;received=w.w.w.w;rport=23473;ingress-zone=CollaborationEdgeZone

Call-ID: 5ce0c5ce-61d50003-0000594d-00000721@w.w.w.w

CSeq: 102 REGISTER

From: <sip:+15555555555@FQDN.com>;tag=5ce0c5ce61d5000200001b72-00007c5a

To: <sip:+15555555555@FQDN.com>;tag=848151973

Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY

Server: Cisco-CUCM10.5

Date: Wed, 23 Mar 2016 04:28:20 GMT

Warning: 399 cucm01 "SIP trunk disallows REGISTER"

Content-Length: 0

[ukirukuk13]

Hi
I had the same problem with windows jabber phones
My MRA worked but Phone Services were not connected.
I had warning message "SIP trunk disallows REGISTER" on Expressway C log
I found mistake, it was sip trunk beetwen CUCM and Expresway C, because it status was Failed.  I deleted it and jabber phone services started to work
Cisco MRA doesn't require sip trunk for local phone

[JustForVoice_2]

Hello,

I’m using single NIC deployment.  Is there any special configuration that I should consider?