Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

EPearson (IS/IT--Management) (OP)
8 May 12 16:44
I am trying to get UCA Mobile to work on Andriod and IPAD.  UCA is 5.0 and MBG is 7.1.  I have UCA PC Client working on my laptop and on remote IP phones working through MBG. The MBG is in the DMZ...NOT NETWORK EDGE

1. I have UCA Mobile licenses and MBG Licenses
2. I have real world FQDN for UCA Mobile...did NSLOOKUP
3. I have checked ports required between internet and MBG
4.I have checked with IPAD and My Andriod...both are at correct OS
5.  I have created account in UCA and user in 3300 which is an APP Server port.

I am use to doing softphones client on UCA where security certificate is sent and approved on UCA server but with mobile this isn't done? I was going to have IT dept look at firewall to see what is being blocked.  Any help is appreciated
gweetz (TechnicalUser)
8 May 12 21:20
What is the specific error message or symptoms when failing to connect?  Does anything show in the UCA Mobile Diagnostic Settings log?

I have UCA 5.0 and MBG 7.1 supporting UCA Mobile fine, but in a different configuration (MBG is gateway mode and UCA is a separate internal box).  Ports were the big issue, particularly enabling a Port Forwarding rule for TCP 36008 for presence and real-time notifications.  P.86 of the UCA 5.0 Admin Guide claims TCP 36008 isn't needed for MBG 7.1 and above, but I had UCA working prior to the app upgrades.

I did not have to do anything with security certificates until I was doing a Deskphone integration for a UCA laptop client through Teleworker.
 
Billz66 (TechnicalUser)
9 May 12 0:20
I think you need 443,80,36005,36006,36007,36008 from a public Ip to the UCA server . If you can get all those opened up it should work.

Does the web portal work ?

https://FQND of UCAserver or public IP/ucs/webclient




 

If I never did anything I'd never done before , I'd never do anything.....

LoopyLou (TechnicalUser)
9 May 12 8:47
At some point the mobile device has to approve a security request. There isn't much to do on the mobile device other then entering the FQDN, user name and password. Would suspect it is a firewall issue. Unfortuneatley I don't have access to the company's UCA server but we have it running on Android, apple and blackberry devices.  

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.  

EPearson (IS/IT--Management) (OP)
9 May 12 17:28
Does a SIP device have to be created in the MBG for the UCA Mobile to work?

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close