Team,

I just installed a summit in a hotel with 52 SLT's and 1 MBX22 for the front desk. Customer want to have a mobile device ring as well as the front desk when someone calls the front desk which is X300. I have heard about this mobile app. But besides sales literature I cannot find any tech info on it. Some one said the app was on the USB stick provided by Mario when trained, but I don't see it on that stick. Any thoughts or help would be appreciated.

Thanks and have a great day!!

The programming information was included on the flash drive inside the power point training presentation. PGM 443 is the place where you register the smartphone or Iphone. The downloadable software is available from Google Play store and wherever you get Apple aps...I don't use an Iphone.

You will need a public IP...the communicator function is not supported behind NAT, in other words, it isn't going to work behind a Sonic wall or router. The Summit CPU ip address has to hang on the public side of any internet connection.

Once this is all installed and the Smartphone has an extension number from the Summit, you can program the cell to ring like any other extension.

Was wondering if you got the mobile app working? I have been able to get the app working off my wifi, but not on the public cell network. I was programming something else to get it to work on the cellular network and it all stopped. Now putting the info back in after a default. It has been a protracted experience to say the least.

Is your wifi behind NAT? Remember the Summit needs a static public ip if you want to reach it outside your network.

Not true. Just need to forward the correct ports. Communicator is the old app, Ipecs UCS client is used now, uses different ports also. The list of ALL ports for the Summit are available on the ftp site. I have the list needed for the ipecs ucs mobile client if anyone wants it can pm me.

The following ports must be open on the firewall itself for the Summit to work properly over the
internet. Contact the appropriate IT personnel to have these ports opened.
TCP 1720 IP networking
UDP 5060 SIP networking
UDP 7000-7023 Audio and video on locally-originated calls
UDP 7100-7123 Audio and video on remotely-originated calls
UDP 7300-7323 H.323 & SIP networking audio
UDP 9200-9211 t.38 relay ports for H.323/SIP devices

Unless there has been a change, Vertical does not officialy support running the UCS client or Communicator behind NAT. That is what tech support told me but it has been awhile.

Ok, there seems to be much conflicting information. I can understand this because it is hard to get one single definitive answer. I am trying to run the UCS client on a static IP behind a router. The port forwarding seems to be the problem, but I haven't been able to nail it down. Derrick's ports don't seem to be the answer. The ports Derrick mentioned seem to be for the IPECS Communicator. Different for the UCS app. But maybe if I try it without the router. Beats me, I'll try.

I know this is old but I want to clarify for others who might find it in the future. UCS mobile and the old communicator app do work with proper port forwarding. The summit does NOT need to be on the public side of the firewall. As far as which ports the tech doc on the ftp server seems to be incomplete so I can't say for sure which ports are truly needed for ucs. My hail mary fix was to forward 1720-9999 and cover them all and it has been working fine. I also have been using intermedia sip trunks through the firewall without a hitch.

Here is a list of the ports for anyone wondering..they all are listed on the ftp doc, had to watch my firewall to gather the correct ones but was easy enough.

5003 isn't necessary for ucs but it will give you access remotely to trace logs. If customer has credit card through the network this will get flagged for plain text and they will fail their accreditation. A few of the ports aren't necessary for standard ucs client but really doesn't hurt to just forward them anyway (80-82 and one or two more that I forget off the top of my head).


UDP
7000-7330

TCP/UDP
80-82
25054-25060
6254
5060
5588
8899
5003
1720

I just set one up behind a firewall that already had port forwarding used for another device and it was a cheap router with only a few forwarding fields left so i had to get creative to get ucs mobile to work. The bare minimum (for ucs standard with no video) was 5588, 7000-7330 and 8899. It works without 8899 but the presence data doesn't sync. Fun fun fun

I know this is an older post, but I wanted to let you all know that I had the same issues with it not connecting remotely using port forwarding, but it would connect locally. It turns out that when you set up the app and it asks to use "tcp" or "udp". I naturally used tcp and it worked internally, but wouldn't work remotely until I changed it to "udp". Now all is good. Toni @ Vertical suggested to try it and BAM! Came right up.

So has anyone figured out how to get the android version to blank screen from the proximity sensor when you put it to your ear. I've been through all the updates since the app was released and it still keeps the screen active and my ear does all kinds of nasty stuff while I'm talking.....

Not sure which Android you have, but I have the Galaxy S8 Plus and it works fine with cell and UCS calls. It is probably a setting in your phone and not your app, but not sure. Does it go blank on cell calls? Might need to turn on "smart view" or some other proximity censor setting?