ip office flare setup

[eddiebullman]

Hi
Ok don’t slate me for being thick on this one but I just keep banging my head against a brick wall with this one and the docs don’t help or I just don’t understand them
What I have set up is as follows

Ports forwarded to my one-x server
TCP 5222, 8444, 5269 and 8069
Ports forwarded to IPoffice
TCP/UDP 5060 and RTP ports
I have a FQD to the public address of my router

IPoffice set to sip register for both TCP and UDP

So what do I put in the following fields in the IPAD app

Service
Server ????????????????? (IP address or FQD / IPoffice or one-x server)
Domain ???????????????? (one-x.XXXXXX.co.uk or just XXXXXX.co.uk)
TLS (set off)

Presence
Server ????????????????? (IP address or FQD of the one-x server)

Enterprise Search
I have left blank

Login details
User =Do I put the short extension name or number
Password=I know this one

NO I can’t use vpn so I have to use port forwarding

 

[RTGDFM]

Eddie,

it tells you all this in the setup guide on the Knowledgebase.

Server and domain are the IP address of the IPO.

Username is the ext no, not the name.

ACSS SMEC
APSS SMEC
ACA IP Telephoney Implement

 

[eddiebullman]

like i said i can't make any sence of the knowledgebase

ok what about the port forwarding and presence server

 

[RTGDFM]

Taken from the manual:

http://marketingtools.avaya.com/kno.../flare/FlareExperienceAdministrationGuide.pdf

http://marketingtools.avaya.com/kno...uals/flare/UsingFlareExperienceForWindows.pdf

http://marketingtools.avaya.com/kno...ls/flare/UsingFlareCommunicatorForIPad_en.pdf

Ports
AvayaFlare Experience establishes voice and instant messaging sessions using Transmission
Control Protocol (TCP) to provide a communication channel. The following table lists the ports
that each protocol uses to support a connection between the Flare Experience client and the
IP Office system.
Protocol Port Description
TCP 5060 Flare Experience uses this port on the Avaya
one-X® Portal server for call control functions.
TCP 8069 Flare Experience uses a WebSocket
mechanism to provide a communication
channel over a TCP connection. Using this
channel Flare Experience receives contact
information, call logs, and presence
information from Avaya one-X® Portal. You
must open port 8069 on the Avaya one-X®
Portal server for use by WebSocket.
TCP 5222 Flare Experience uses this port on the Avaya
one-X® Portal server for XMPP functions.
Using this port Flare Experience receives
instant messages, presence, and contact
information that uses XMPP.
TCP 5269 Flare Experience uses this port on the Avaya
one-X® Portal server for XMPP server-toserver
federation.
RTP Dynamic Flare Experience uses this port on the IP Office
server. The RTP port number is dynamic. IP
Office generates these ports during a call.


Server settings
Use the information in the following table to configure the server settings for Flare
Experience.
Name Description
Server IP Address The IP address of the IP Office system.
Server Port The port number of the IP Office system. The
Flare Experience client uses port 5060 as the
default setting for TCP.
Transport Type The transport method used for connection to
the IP Office system. Select TCP. TLS is not
supported.
Domain The IP address of your IP Office system.
Presence Server IP Address This field does not apply when Flare
Experience connects to an IP Office system.
Leave this field blank.
Note:

ACSS SMEC
APSS SMEC
ACA IP Telephoney Implement

 

[eddiebullman]

Ok so in now get that i am logged in but get error message saying that

Server unavailable
Unable to connect to one-X Portal server. Personal and System contacts, Presence an IM will be unavailable

Any ideas

 

[RTGDFM]

It does that first time. Log out then back in.

ACSS SMEC
APSS SMEC
ACA IP Telephoney Implement

 

[sroderick]

I often find the Avaya documentation difficult to process. This is a great example. The Flare Experience app uses a lot of ports on the one-X Portal server, and yet where do you tell the app how to find the one-X server? According to the documentation you place the IP address of the IPO in two locations in the app settings. That's it. There isn't any other location where you should put the address of the one-X server? Seems very strange. Does it just retrieve this information from the IPO? That seems unlikely. Clarification would help immensely. This is straight from the docs:

The following table lists the ports that each protocol uses to support a connection between the Flare Experience client and the IP Office system.

This is immediately followed by a table that lists:

Protocol Port Description
TCP 5060 Flare Experience uses this port on the Avaya one-X® Portal server for call control functions.

There are a number of other ports all of which list the one-X Portal server. So should these ports be forwarded to the IPO or to the one-X Portal server?

hmmmm

 

[tlpeter]

The docs are very clear.
Install it like the doc tells you to and it works fine.
If not then you have made a mistake or something else is not installed by the book.


BAZINGA!

I'm not insane, my mother had me tested!

 

[eddiebullman]

The doc are not very clear at all

As if i port forward 5060 the my one-x server it will not connect but it will if i forward it to my ip office

But i still get the following

Server unavailable
Unable to connect to one-X Portal server. Personal and System contacts, Presence an IM will be unavailable

i have two public ip address with FQD on them so what ports do i forward to what????

 

[tlpeter]

Port 5060 is for SIP and the 1XP server does not do SIP, the IPO does.
You need to setup a VPN when you are not in the same network.


BAZINGA!

I'm not insane, my mother had me tested!

 

[sroderick]

That is the correct answer. You have to setup a VPN when you are not in the same network. I believe that the IPO is sending info to the client telling it how to reach the one-X server, however the IPO sees the one-X on an internal IP which of course the client can't access unless you are connected via a VPN.

And I would reiterate that the docs are very clear that Flare uses TCP 5060 to talk to the one-X server.