Unable to place Outbound Calls

[MFeliz]

Hello Team,

I really need your help, please.
I am using a 4 Ports GSM BERONET GATEWAY, with 4 sim cards inserted on it. and I configured 4 different SIP Account for each port from 3CX side.
I created the outbound rule as the following:

Calls to numbers starting with prefix : 9
Calls from extension(s) : 3006
Calls to Numbers with a length of : 9-14
Route1: SIP Trunk 01
Route2: SIP Trunk 02
Strip Digits: 1

With all the above setup, I am still not able to place the Outbound Calls. But the Inbound is working perfectly.
Can you please help me find out what is going wrong?

I am looking forward to hear from you.

 

[MFeliz]

what's in log ? do you see your call try?

Here is what appear in the log:

"Call or Registration to 912660637@(Ln.1xxxx@SIP Trunk-9xxxxxxx) has failed. 0.0.0.0 replied: 408 Request Timeout; internal"

 

[AWS2P]

This error means that the caller did not receive a reply from the PBX(or there is no connectivity with it)
Strange to have 0.0.0.0 as IP

 

[AWS2P]

did you follow any documentation from 3CX to set GW?
GW has a static IP on same LAN as PBX ?

 

[MFeliz]

did you follow any documentation from 3CX to set GW?
GW has a static IP on same LAN as PBX ?

Yes, I did. that is why the Incoming calls are working properly, without any issue.
The Gateway is not in the same LAN as the PBX. the PBX is hosted in the cloud and the GW is physically in the local office.

The GW has a static IP, yes. but I was using the public IP to connect with the PBX, because of this outbound situation, I tried to use the GW static IP and see if it will work, unfortunately not. But incoming calls keep working fine.

 

[leejor]

The Gateway is not in the same LAN as the PBX. the PBX is hosted in the cloud and the GW is physically in the local office.

That is the problem. Use of a gateway, when 3CX is hosted, is not supported, for just the reason you have discovered. Some have been able to get gateways working, but you must have forwarding rules setup correctly at the router the gateway sits behind ( I assume it is behind a router), even then voice ports may still have an issue.

Are you able to establish a VPN connection between the two locations?

 

[MFeliz]

That is the problem. Use of a gateway, when 3CX is hosted, is not supported, for just the reason you have discovered. Some have been able to get gateways working, but you must have forwarding rules setup correctly at the router the gateway sits behind ( I assume it is behind a router), even then voice ports may still have an issue.

Are you able to establish a VPN connection between the two locations?

I will look after the forwarding rules and confirm the result here. I am not able to establish the VPN connection for now.

 

[AWS2P]

Ok , I understand know you said pbx is cloud hosted why gateway isn't working and why IP 0.0.0.0.

 

[MFeliz]

Ok , I understand know you said pbx is cloud hosted why gateway isn't working and why IP 0.0.0.0.

The Gateway is working, but only with Inbound... My issue is with the outbound calls.

 

[leejor]

In the 3CX trunk settings you've created, you put in an IP and a port. (With a trunk device, unlike a set, or ATA, registration alone does not tell 3CX how to reach the device, you must specify this) The port will be the one assigned to the particular trunk, on the gateway, if that is how it has been setup. The IP will have to be the public IP, of the router, at the location of the gateway. Again, I'm assuming it is behind a router. So... the router must have port forwarding configured so that with 3CX sending to 123.456.789.101:5060, the router forwards the SIP message to 192.168.1.10:5060 (substitute real public and private IPs).

That takes care of the SIP messaging, now you have to deal with the ports used for voice, and that is where you may have some issues. The make and model of the remote router may play a big part in how well this might work. Some seem to be better at keeping track of which device is using which port.

 

[MFeliz]

In the 3CX trunk settings you've created, you put in an IP and a port. (With a trunk device, unlike a set, or ATA, registration alone does not tell 3CX how to reach the device, you must specify this) The port will be the one assigned to the particular trunk, on the gateway, if that is how it has been setup. The IP will have to be the public IP, of the router, at the location of the gateway. Again, I'm assuming it is behind a router. So... the router must have port forwarding configured so that with 3CX sending to 123.456.789.101:5060, the router forwards the SIP message to 192.168.1.10:5060 (substitute real public and private IPs).

That takes care of the SIP messaging, now you have to deal with the ports used for voice, and that is where you may have some issues. The make and model of the remote router may play a big part in how well this might work. Some seem to be better at keeping track of which device is using which port.

I was first using the public IP of the GW from 3CX SIP Trunk configuration page, then I switched to the Gateway IP just to see if things would have worked out, unfortunately it didn´t. But the incoming calls keep working.

But something I found interesting in your comment is to tell 3CX how to reach the Gateway... Can you please help me with procedures, please? I am not seeing how to do so. Please!

 

[leejor]

You "tell" 3CX how to reach the gateway (outgoing calls) in the trunk settings (the trunk, or trunks, you've created)...through the IP and port(s). The IP will have to be the public IP of the gateway (if it is connected direct to the internet), or, the router it is behind. This IP would normally be a local IP , on the same LAN.

Post one of the 3CX trunk settings, if you are still not clear.

 

[AWS2P]

Leejor explained what to do in #29
first, set on Router/firewall where your gateway is, a nat rule to forward SIP 5060 traffic coming from pbx to local LAN IP from your Gateway (assuming you set a static ip on gateway).
Take Note of Public IP address from that location for future settings on 3CX side.

open 3CX console and in trunks legs you set to be able to use the gateway then set the public IP you just got from remote location and 5060 port if this is the one you set for gateway use.