Looking for the correct ports to foward on the firewall on an ECS
currently we have TCP port 50000-50001 fowared to the lan2 ip address
currently we have UDP ports 6004-6499 forwared to the mbu ip adress

We cannot access the ECS or get ip phone to connect
Any help
Thanks

When you say forwarded, do you mean the public IP address of the network is forwarded as such? Is your IP phone set to look for the public IP address as the server, with the port entered (without leading zeros) ?

Are you properly licensed and configured for an IP phone- is the port in question set to use the public address versus the inside LAN?( LAN/VPN or non-VPN)

Is the public IP address programmed in Stations>IP Station settings? Is the control port still at 50000?

Are the proper ports opened at the phone/remote end?

Lotsa little things,,,,

WE are licenced

What we need is what ports get fowared on the firewall where the ECS resides

We need to connect via ip and connect remote ip phone

You have the correct ports listed, pointed at the proper places.

You need to open the ports you have listed where the ECS is at, forwarded to the IP addresses you have listed. The problem could be at the phone end. The phone has to be programmed with the ECS location public IP in the spot that asks for the ECS server IP, NOT the actual ECS LAN2 address. You'll also have to open port 50004 at the phone end to allow audio back and forth. Also, the IP phones work a lot better with static IP addresses, if possible.

Do you have any IP phone connected on site?

Is remote access available? I'd be happy to take a look...

We cannot get remote access the IT guys are saying its an ECS issue

Do we need tcp port 5001 also to be foward to the lan2 ip address to gain remote access or are we missing progamming on the ECS

Yes...port 5001 for admin access.

You'll need the system password to connect, as well

IT guys always blame the ECS...

We now have remote access.
When trying to connect remote ip phone we get network error.
Any help would be appreciated

I'm watching threads like this because although I've been in the business a long time, I've done very little with VoIP. Today in the shop I did some testing with a spare 5900 phone. Got it to come up, I plugged the phone directly into LAN2 of the CCSU and set a static IP of the phone within the range of LAN2. I was able to connect my laptop to the PC port of the phone and connect to 10.0.0.1 to access the ECS. The phone came up with dial tone, but can't make any calls as the ECS doesn't have an MBU. I was able to configure DSS keys that did light when the corresponding ext. was off hook.

Regarding this thread, if an IP phone is to be used on site, the LAN2 address would be different than one used off site, correct? If someone wanted to bring their phone from the office to be used at home, then would the LAN2 address need to be changed?

Keyset6- correct. The phone CCU address is going to depend on where the phone is physically located, in regards to it's network address. If the phone is in the same network as the ECS, the LAN2 address is used. If it isn't in the same network, the public IP (or appropriate routing address) would be used. You need the MBU asit's the bridge between TDM and IP...it's where the audio passes thru.

Juno- please PM me with access info if you'd like me to take a look....What are your specific settings on the phone- CCU. port, IP address. etc.

JBean3329 - thanks, as I thought. I like being able to test/experiment configurations like this in the shop, so a customer won't be affected. While I had my laptop connected to the PC port of the phone, as expected I was also able to access the phone's IP menu using I.E., but I had to set the 10.0.0.5 address to compatibility mode.

Unrelated note - extreme opposite technology, a while back I mentioned I moved a ZTD system to a new site. This week I installed an additional phone for an Omega III site! I found 2 spare (previously used but phones disconnected) ports, but they would not come up. I then found out a SUB port will not upon system power up unless a phone is connected. To accommodate the customer I moved a port to the new location from a spare office, connected the unused port to where it came from. They'll reset the system when they can. Back at the shop we have an 816. That one I can plug in a phone after power up and it works. I thought with my other employer in was amazing seeing a Rolm 8000 still in service in 2015, I think this Omega III is even older.

I still have a couple 816s in service that I swear I had to convert from coal....

And today guess what I worked on - a 616! Don't want to hijack this thread, will start a new one.

Thanks again JBean for your help goi g to the customer site next week and I will let you know if the phone works both ways.
Hope you all Have a Happy New Year.
Juno

Our ip phone is now connected remotely.

When we go to intercom another station it says channel busy

Any help
Thanks

That generally means your port forwarding to the MBU needs looking at, or the port for the remote phone needs to be set appropriately in programming.