- Joined
- Sep 11, 2010
- Messages
- 3
- Reaction score
- 0
I have set up 3cx Ver 9 on a windows 2008 server. The server has an IP address of 192.168.1.2
The server is Natted through a Draytek router, ip 192.168.1.1 (internal)
Phones on the internal network will connect fine.
The same phones, on the external network never connect(*) always failing sip registration.
(*) Not entirely true, one did once, then we had to reboot the server and never again.
Running wireshark I can see that:
a) all the ports are redirected correctly
b) the requests from the external phones are getting through to the 3cx server.
The requests from internal phones get one 407 Proxy auth required sent to them, they reply with the same register request with proxy information and register correctly.
Requests from external phones get a 407 Proxy authentication required sent, and they reply with the same request again without the required proxy authentication code. This happens for each and every register request. The 3cx server resends the 407 and the phone responds again without the auth information.
Please remember that these are the same phones, same firmware etc etc. Just ones external to the network do not send the authentication information for the proxy.
Testing with the 3cx softphone from the external location works fine.
I've tested the 3cx server with both port redirection and by putting it in the dmz and it always has the same outcome. (I.e the softphone can connect, IP Phones cannot)
The phones are the Siemens C460IP phones (complete rubbish, but they are what we have to work with). They worked ok when using an external voip provider, but bringing it in house has caused a bag load of hassle.
Does anyone have any idea why the phones aren't responding to the 407 in the correct way ONLY when they are external to the lan?
Or
Is there any way I can turn off the proxy authentication within 3cx? Given that I don't want to have to replace a load of actual phones this is by far the most attractive option!
Cheers
The server is Natted through a Draytek router, ip 192.168.1.1 (internal)
Phones on the internal network will connect fine.
The same phones, on the external network never connect(*) always failing sip registration.
(*) Not entirely true, one did once, then we had to reboot the server and never again.
Running wireshark I can see that:
a) all the ports are redirected correctly
b) the requests from the external phones are getting through to the 3cx server.
The requests from internal phones get one 407 Proxy auth required sent to them, they reply with the same register request with proxy information and register correctly.
Requests from external phones get a 407 Proxy authentication required sent, and they reply with the same request again without the required proxy authentication code. This happens for each and every register request. The 3cx server resends the 407 and the phone responds again without the auth information.
Please remember that these are the same phones, same firmware etc etc. Just ones external to the network do not send the authentication information for the proxy.
Testing with the 3cx softphone from the external location works fine.
I've tested the 3cx server with both port redirection and by putting it in the dmz and it always has the same outcome. (I.e the softphone can connect, IP Phones cannot)
The phones are the Siemens C460IP phones (complete rubbish, but they are what we have to work with). They worked ok when using an external voip provider, but bringing it in house has caused a bag load of hassle.
Does anyone have any idea why the phones aren't responding to the 407 in the correct way ONLY when they are external to the lan?
Or
Is there any way I can turn off the proxy authentication within 3cx? Given that I don't want to have to replace a load of actual phones this is by far the most attractive option!
Cheers