One X Alternative Port

[texmatlock]

Anybody know of a good random TCP port that is rarely used by anything that I can use in stead of 8080. Its being used by another application. So I need a different port for One X but one that isn't in use by any other Avaya software and hopefully by nothing else.

 

[intrigrant]

If you have a firewall then check the logs which ports are scanned from the internet and don't choose one of them.
I would use a unnassigned service port below 1024 like 4,6,8,10,12,14,15,16 etc. Port 471 looks OK to use.

A simple mind delivers great solutions

 

[IPGuru]

it is probably not a good idea best practice to be running One-X (or any other Avaya apps) on a server that is being used for other tasks.

having said that check for spare ports in the 8081-8089 range they should be free.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[intrigrant]

I only answered the question, it is not for me to suggest if it is a good idea or not.
Actually I see no reason not to use the default port and for all installs I made so far I have never changed the default port.

A simple mind delivers great solutions

 

[texmatlock]

Thanks for the help guys.

 

[texmatlock]

Never heard this "best practice for one-x to have its own server" before.
The Catalyst guys sold us the server and assured us it could easily pull double duty as the vm-pro and one-x server.
Its the first one we've set up that way, though. Normally we've just been putting in the UC Module, and never had a hitch with that.
The reason I say we need an alternative port is because we've got to set up port forwarding for the One-x. So if something else is using that port we've got to make a change.

 

[tlpeter]

Vmpro and one x is not a problem but I would keep it like that.
Also I would use port 8080.

BAZINGA!

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

 

[IPGuru]

As per Peter
VM Pro & One-x are ok on the same server (in fact this is probably preferred)

What I meant was don't put Avaya services on a server that you are using for other purposes, as you must have been planning if you have a port clash

This is not because it wont work but more a case of if I am maintaining VM/One-X whatever I do not want the risk of something I do disrupting some other critical part of the customers business that I have no knowledge of, it also stops customers software from interfering with the IPO applications so everybody wins.

This is not always achievable in the real world and Visualization makes a good compromise when possible.

Some Avaya products will not co-exist (CCR & Contact store need to be on separate PC's)


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear