IPOffice 10.1 in Cloud

[vladcbv]

Hi all,

I have started testing IPO Powered by solution.
I have IPO 10.1 in a datacenter, and now, for test purposes have it directly connected to the internet. so you can simply access the

https://ip:7070.

I can login from communicator, an 9
Now I wait for the provider to link the SIP trunk to the IPO.

Please reffer to this thread last 3 posts:

http://www.tek-tips.com/viewthread.cfm?qid=1781896

So I am at the point where I will have to configure all voice on one LAN, which I've never done yet

To understand my situation I am leaving a picture of the current topology.

So my current network si soething like : 92.87.xxx.xxx /255.255.255.0
and the SIP will be something like: 2.0.xxx.xxx /255.255.248.0
Are there changes needed to be done on the Gateway, or some IP routes added to IPO? Or can this be done by adding an IP in the centos network file for eth0 (I am an amateur on CentOS, but on Windows you can add a second IP to the same NIC and have conenctivity to the other network)?

Thank you all in advance!

 

[janni78]

What is the problem you're trying to solve?

"Trying is the first step to failure..." - Homer

 

[vladcbv]

Well 1st I am trying to understand how all voice on one lan works - I have only worked with cabinets and I've always connected SIP to LAN2.
So my issue is how do I configure 2 subnets on one LAN in IPO ?

 

[janni78]

You don't connect 2 subnets on the same interface, you route traffic between your subnets through your router/firewall.

"Trying is the first step to failure..." - Homer

 

[vladcbv]

So that is forward traffic coming on SIP trunk to the SIP ports (and RTP range) of the PBX ?

 

[IPGuru]

and NEVER place the IP Office on a public IP address!



Do things on the cheap & it will cost you dear

 

[vladcbv]

Yes I agree with you, never directly connected to public. That's why we want to have them connected via VPN to the customers environment.

 

[janni78]

You can have public IPs as long as they are not directly connected to the internet, you still should have a firewall in place.

As I understand you're trying to design a hosted solution?
You should get a network guy onboard that understands VoIP so you can design this properly.

"Trying is the first step to failure..." - Homer

 

[vladcbv]

So I already have IPO and IPOCC as demo set up as VMs in a datacenter. So now they are directly connected to internet.
In my company I am that network guy that you are talking about , but I am also discussing this with IT guy from the datacenter.

 

[karlzre]

install a sbc and a firewalll or you will be hacked in a few days, that will cost you more than a sbc ...

sip is a 2.X.X.X is it a public ip or a private ip ?
If it's public, it doesn't matter, internet should route it for you.
If it's private then you need to add a virtual network card in you vmware vswitch, do vlan on the vmware server etc.. or route it with the missing firewall/router but all of that you should know as you are the network guy ;-)


ACIS - ACSS

 

[vladcbv]

Hi and sorry for late respnse.

karlzre , the 2.x.x.x is a public Ip, but I've just found out that it is used when customers have vpn with provider.
For my case I will receive another ip, 92.x.x.x - still public .

I may have to add another virtual NIC but Avaya recommends in its documentation not to use eth1 for Powered By.
I am still waiting SIP information from provider.