2 Server 1 External IP

[Leckbush]

Is it possible two run two Vicibox server which uses the same IP provided by our ISP? We have client that access access server 1 and some other clients access server 2? Is it conflicting when they type the IP and get the other server on browser instead what he expect?

[ambiorixg12]

Port foward the public IP to different ports , on each server , so they will access using the same public IP but differents ports

[williamconley]

Is it possible two run two Vicibox server which uses the same IP provided by our ISP? We have client that access access server 1 and some other clients access server 2? Is it conflicting when they type the IP and get the other server on browser instead what he expect?

Depends on how they intend to "access" it. You can turn off port 80 web access through the router, and provide each client with a link ... to a port other than port 80. Then forward those two ports (8080 & 82?) both to port 80 on respective server. Nobody's on port 80 so nodoby gets a "default" hit or accidentally sees the other client's server. They must have the port number (provided in your link) to actually hit their server's web (although, admittedly, they could memorize the port number and the could port scan, but that's a different concept and can be resolved with IPtables configuration).

[Leckbush]

Thanks for reply guys. So I manage to use 2 server in one IP by using port forwarding server 1 http port is on 80 x.x.x.x" and the server 2 "x.x.x.x:8080" http port is on 8080. Both are accessible outside.

So I want to use this server 2 while using server 1. Will server 2 overlap some port use by server 1? Like server 1 use sip port 5060,5061,5062

Server1
SIP Port 5060,5061,5062
HTTP Port 80
RTP PORT 10000-40000

Server2
SIP Port (default, not yet configured) 5060
HTTP Port 8080
RTP Port (Havent Checked yet, I dont know how)

Any suggestion I need to do on server 2 so It would not overlap with server 1? Like it might pass the call to server 2 instead of 2. Somethiing like that

[williamconley]

Inbound calls require forwarding a port (such as 5060) to the internal server ONLY if you do not use registration with your Telco. Registration bypasses the port requirement since the registration process grabs a random port and supplies that to the Telco explicitly (very useful in this situation).

Outbound calls have no forwarding requirements.

So the only situation in which you have forwarding requirements is during IP-authenticated inbound calls. Some routers will auto-recognize the rport and forward it to the proper server, so only port 5060 will require forwarding (some call this triggering). Others do not. No rules here, every router manufacturer is different. If forwarding is required, you can specify port ranges and split them among the servers. Asterisk rport ranges and router rport forwarding is complex, but not overly so if you are able to edit conf files and manage your forward ranges. All UDP, of course, unlike http which is TCP.

You could also pass ALL inbound calls through one of the servers, using it as a SIP gateway and forward appropriate calls to the other server. Some will actually use a SIP gateway (or just any old asterisk server) serving that one purpose: Routing of inbound calls to the various local servers. The gateway server would be fairly stripped down, and could even be virtual since it's got very little in the way of decisionmaking process. Depends on the maximum number of simultaneous calls you will have.