[Spce-user] sip:provider CE (public IP)

[Andrew Pogrebennyk]

Hi,
when you are saying public IP do you mean it has a real public IP or the
public one is mapped to private 1:1 as it's common with Amazon and in
other virtualized environments? if the latter, then you have only
private IP in /etc/ngcp-config/network.yml. So you need to set the
public IP as advertised IP. If your main interface name is eth0, just
execute:
ngcp-network --set-interface=eth0 --advertised-ip=YOUR_PUBLIC_IPADDR
ngcpcfg apply

Hope this helps.
Andrew

On 11/14/2014 03:37 PM, Isaak (Web-e-volution) wrote:
> Good Day.
> 
> I have downloaded SIP:PROVIDER_CE installed in VMware.
> 
> When running VM (running in my computer) through LAN, everything works fine.
> Endpoints using the same LAN can connect to the server, make calls, etc.
> 
> Now, I have a server with its own public IP. This server is not in my LAN. Is in another country, in fact.
> I have deployed to this server the VM as well. I have opened these ports in Firewall:
> 1443 tcp
> 2443 tcp
> 5060 tcp and udp
> 5061 tcp
> 1080 tcp
> 5222 tcp
> 5269 tcp
> 30000:40000 udp
> 
> Using WiFi, Endpoints can connect to the server. When a call is made, the receiving call Endpoint rings.
> The call is answered but the the call is ended automatically.
> The caller Endpoint keeps connected to the call until around 30 seconds when it gets disconnected.
> 
> So in other words, when SIP server uses a public IP, endpoints cannot establish a new call.
> 
> 
> Am I missing a port or something else? SIP:PROVIDER_CE can work in using a public network, right?
> 
> 
> 
> Regards,
> 
> W-E-V
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>