i have one public ip in my data center (78.12.x.x). this is the primary interface for my freepbx server.
then i have 3 locations around the world with one router. behind the router here are standing all my sip phones.
i have opened the sip 5060 UDP port on my freepbx for my 3 locations. in my router i dont have done anything.
so for now, how i can setup all 3 locations with the server?
currently i can call from the phones in my locations, but if i call from external, my phone is not ringing… (voicebox answers the phone because not reachable)… why?
i also have running a firewall on my datacenter where i can activate openvpn but how i should do this with the
ip-adresses? i only have set one primary ip address (78.12.x.x). must i setup a lan ip address for the whole openVPN traffic?
You have three LANs (in different locations), with multiple phones at each location - but only one FreePBX server? Incoming calls arrive, I presume, at the location where the server is - you want to be able to answer incoming calls at any of the three locations? Hard to understand your description.
I suspect the answer to your problem will be in the log file at /var/log/asterisk/full – make an outgoing call, then an incoming call from a mobile (or whatever) and see what the log says.
Yes my description is correct. I have one freepbx Server in my datacenter with one trunk and one phone number. And have 3 LAN (192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24). On each LAN i have 5 extension: 10,11,12,13,14,15 lan1, 16, 17, 18, 19, 20 lan2, 21, 22, 23, 24, 25 lan3. So my question how i can or should do it exactly with the serverside and LAN site configure it? Have 3 static ip-addresses (on each LAN one).
If you use an OpenVPN server then you don’t have anything to do. Run the server in your datacenter, open the port the server listens to, set your phones to connect there and after the vpn is established you configure your phones as they were local.
Well there is some overhead but the chance to get hacked leaving a pbx on a public ip is worse. Plus many major phone brands support openvpn, that way you don’t need any extra hardware like a router to connect to the openvpn server.
question 1:
if i change the trunk port to another port as 5060 UDP (PEER details: port=5090),
i get the following error:
– Executing [continue@macro-dialout-trunk:1] NoOp(“SIP/10-0000002e”, “TRUNK Dial failed due to CONGESTION HANGUPCAUSE: 19 - failing through to other trunks”) in new stack
– Executing [continue@macro-dialout-trunk:2] Set(“SIP/10-0000002e”, “CALLERID(number)=10”) in new stack
– Executing [066XXXXXXX@from-internal:7] Macro(“SIP/10-0000002e”, “outisbusy,”) in new stack
– Executing [s@macro-outisbusy:1] Progress(“SIP/10-0000002e”, “”) in new stack
– Executing [s@macro-outisbusy:2] GotoIf(“SIP/10-0000002e”, “0?emergency,1”) in new stack
– Executing [s@macro-outisbusy:3] GotoIf(“SIP/10-0000002e”, “0?intracompany,1”) in new stack
– Executing [s@macro-outisbusy:4] Playback(“SIP/10-0000002e”, “all-circuits-busy-now&pls-try-call-later, noanswer”) in new stack
– <SIP/10-0000002e> Playing ‘all-circuits-busy-now.slin16’ (language ‘de_DE’)
> 0x7f36540441c0 – Probation passed - setting RTP source address to 192.168.10.10:8102
– <SIP/10-0000002e> Playing ‘pls-try-call-later.slin16’ (language ‘de_DE’)
== Spawn extension (macro-outisbusy, s, 4) exited non-zero on ‘SIP/10-0000002e’ in macro ‘outisbusy’
== Spawn extension (from-internal, 066XXXXXXX, 7) exited non-zero on ‘SIP/10-0000002e’
– Executing [h@from-internal:1] Hangup(“SIP/10-0000002e”, “”) in new stack
== Spawn extension (from-internal, h, 1) exited non-zero on ‘SIP/10-0000002e’
all lines are busy. if i change the port return to 5060, then it works fine…
If you " change the trunk port to another port as 5060 UDP (PEER details: port=5090)," do you not realize that on the far end you would also have to reciprocate that association or it just won’t answer? If you don’t have control over that endpoint, then you are pretty well buggered. If you do, then change the sip bindport to 5090.
Just asking if we are all talking rational networking here and you understand how it works.
