Unable to register SIP via WiFi

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












We run a FreePBX server on our LAN and softphones can register using the local SIP server IP.



I need these softphones to be able to register over the internet too so we have configured the firewall and created a dns entry for sip.ourdomain.com.



When the softphones are configured to use sip.ourdomain.com then can register over the internet fine however when they are in the office and are connected to the wifi they are unable to register.



I suspect this is because when in the office they are trying to register to sip.ourdomain.com which resolves to the public IP that redirects to the sip server on the local LAN.



How can this be resolved?



Edit1



LAN is 192.168.1.X/24 & SIP Server is 192.168.1.8







share|improve this question





















  • does your SIP server has an internal private IP address? I see you tagged nat
    – Rui F Ribeiro
    May 9 at 23:12







  • 1




    Yes, 192.168.1.8. Tagged NAT as from the WAN IP to internal IP
    – Dercni
    May 9 at 23:16










  • Bring up a simple DNS server on the LAN and resolve that IP on it. I do that on my Zeroshell router for example.
    – ajeh
    May 10 at 0:06















up vote
1
down vote

favorite












We run a FreePBX server on our LAN and softphones can register using the local SIP server IP.



I need these softphones to be able to register over the internet too so we have configured the firewall and created a dns entry for sip.ourdomain.com.



When the softphones are configured to use sip.ourdomain.com then can register over the internet fine however when they are in the office and are connected to the wifi they are unable to register.



I suspect this is because when in the office they are trying to register to sip.ourdomain.com which resolves to the public IP that redirects to the sip server on the local LAN.



How can this be resolved?



Edit1



LAN is 192.168.1.X/24 & SIP Server is 192.168.1.8







share|improve this question





















  • does your SIP server has an internal private IP address? I see you tagged nat
    – Rui F Ribeiro
    May 9 at 23:12







  • 1




    Yes, 192.168.1.8. Tagged NAT as from the WAN IP to internal IP
    – Dercni
    May 9 at 23:16










  • Bring up a simple DNS server on the LAN and resolve that IP on it. I do that on my Zeroshell router for example.
    – ajeh
    May 10 at 0:06













up vote
1
down vote

favorite









up vote
1
down vote

favorite











We run a FreePBX server on our LAN and softphones can register using the local SIP server IP.



I need these softphones to be able to register over the internet too so we have configured the firewall and created a dns entry for sip.ourdomain.com.



When the softphones are configured to use sip.ourdomain.com then can register over the internet fine however when they are in the office and are connected to the wifi they are unable to register.



I suspect this is because when in the office they are trying to register to sip.ourdomain.com which resolves to the public IP that redirects to the sip server on the local LAN.



How can this be resolved?



Edit1



LAN is 192.168.1.X/24 & SIP Server is 192.168.1.8







share|improve this question













We run a FreePBX server on our LAN and softphones can register using the local SIP server IP.



I need these softphones to be able to register over the internet too so we have configured the firewall and created a dns entry for sip.ourdomain.com.



When the softphones are configured to use sip.ourdomain.com then can register over the internet fine however when they are in the office and are connected to the wifi they are unable to register.



I suspect this is because when in the office they are trying to register to sip.ourdomain.com which resolves to the public IP that redirects to the sip server on the local LAN.



How can this be resolved?



Edit1



LAN is 192.168.1.X/24 & SIP Server is 192.168.1.8









share|improve this question












share|improve this question




share|improve this question








edited May 10 at 7:27









Rui F Ribeiro

34.5k1269113




34.5k1269113









asked May 9 at 22:52









Dercni

14018




14018











  • does your SIP server has an internal private IP address? I see you tagged nat
    – Rui F Ribeiro
    May 9 at 23:12







  • 1




    Yes, 192.168.1.8. Tagged NAT as from the WAN IP to internal IP
    – Dercni
    May 9 at 23:16










  • Bring up a simple DNS server on the LAN and resolve that IP on it. I do that on my Zeroshell router for example.
    – ajeh
    May 10 at 0:06

















  • does your SIP server has an internal private IP address? I see you tagged nat
    – Rui F Ribeiro
    May 9 at 23:12







  • 1




    Yes, 192.168.1.8. Tagged NAT as from the WAN IP to internal IP
    – Dercni
    May 9 at 23:16










  • Bring up a simple DNS server on the LAN and resolve that IP on it. I do that on my Zeroshell router for example.
    – ajeh
    May 10 at 0:06
















does your SIP server has an internal private IP address? I see you tagged nat
– Rui F Ribeiro
May 9 at 23:12





does your SIP server has an internal private IP address? I see you tagged nat
– Rui F Ribeiro
May 9 at 23:12





1




1




Yes, 192.168.1.8. Tagged NAT as from the WAN IP to internal IP
– Dercni
May 9 at 23:16




Yes, 192.168.1.8. Tagged NAT as from the WAN IP to internal IP
– Dercni
May 9 at 23:16












Bring up a simple DNS server on the LAN and resolve that IP on it. I do that on my Zeroshell router for example.
– ajeh
May 10 at 0:06





Bring up a simple DNS server on the LAN and resolve that IP on it. I do that on my Zeroshell router for example.
– ajeh
May 10 at 0:06











1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










What you may need is defining in your infra-structure a split view DNS or multiview DNS architecture.



Thus in your internal network, your internal DNS server will resolve sip.ourdomain.com to 192.168.1.8 and externally to the current public IP address.



Another alternative is enforcing a public IP address for the SIP server instead of a private IP address.



I usually advise network administrators using public IP addresses for SIP servers and VPN servers for not having to deal with some corner cases of NAT problems.






share|improve this answer



















  • 1




    Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
    – Dercni
    May 10 at 1:42










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442878%2funable-to-register-sip-via-wifi%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










What you may need is defining in your infra-structure a split view DNS or multiview DNS architecture.



Thus in your internal network, your internal DNS server will resolve sip.ourdomain.com to 192.168.1.8 and externally to the current public IP address.



Another alternative is enforcing a public IP address for the SIP server instead of a private IP address.



I usually advise network administrators using public IP addresses for SIP servers and VPN servers for not having to deal with some corner cases of NAT problems.






share|improve this answer



















  • 1




    Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
    – Dercni
    May 10 at 1:42














up vote
1
down vote



accepted










What you may need is defining in your infra-structure a split view DNS or multiview DNS architecture.



Thus in your internal network, your internal DNS server will resolve sip.ourdomain.com to 192.168.1.8 and externally to the current public IP address.



Another alternative is enforcing a public IP address for the SIP server instead of a private IP address.



I usually advise network administrators using public IP addresses for SIP servers and VPN servers for not having to deal with some corner cases of NAT problems.






share|improve this answer



















  • 1




    Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
    – Dercni
    May 10 at 1:42












up vote
1
down vote



accepted







up vote
1
down vote



accepted






What you may need is defining in your infra-structure a split view DNS or multiview DNS architecture.



Thus in your internal network, your internal DNS server will resolve sip.ourdomain.com to 192.168.1.8 and externally to the current public IP address.



Another alternative is enforcing a public IP address for the SIP server instead of a private IP address.



I usually advise network administrators using public IP addresses for SIP servers and VPN servers for not having to deal with some corner cases of NAT problems.






share|improve this answer















What you may need is defining in your infra-structure a split view DNS or multiview DNS architecture.



Thus in your internal network, your internal DNS server will resolve sip.ourdomain.com to 192.168.1.8 and externally to the current public IP address.



Another alternative is enforcing a public IP address for the SIP server instead of a private IP address.



I usually advise network administrators using public IP addresses for SIP servers and VPN servers for not having to deal with some corner cases of NAT problems.







share|improve this answer















share|improve this answer



share|improve this answer








edited May 10 at 7:20


























answered May 9 at 23:18









Rui F Ribeiro

34.5k1269113




34.5k1269113







  • 1




    Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
    – Dercni
    May 10 at 1:42












  • 1




    Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
    – Dercni
    May 10 at 1:42







1




1




Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
– Dercni
May 10 at 1:42




Thanks created an A record on the LAN DNS server that points sip.ourdomain.com to 192.168.1.8
– Dercni
May 10 at 1:42












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442878%2funable-to-register-sip-via-wifi%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)