- Joined
- May 24, 2012
- Messages
- 3
- Reaction score
- 0
Hello all, I am a new user to 3cx, I work for an ITSP and we are testing 3cx hosted. I have installed the multi tenant framework, and have a test 3cx working, I have managed to register my trunks to our ITSP service, and if I use the 3cx softphone I can register and make and receive calls no problems.
The problems begin when I try and register a remote extension. So scenario is 3cx (V10.0.24018.2322) running on win2k8 on real IP address in a colo, within the multi tenant framework.
Trying to register extensions from a NAT environment, so phones have 10.0.10.x IP. Softphone is tested ok from this same network, but if I register a normal SIP phone, EG SPA504g then the register goes to 3cx, and 3cx responds with 407 proxy authentication required. The phone does not see this though, and re transmits the REGISTER.
From wireshark trace, the reason the phone does this is because 3cx erroneusly sends the 407 back to port 5060 not the port from which the register originated, which it would have to do for the NAT router to route the reply back to the handset.
But it does manage to reply to the REAL IP the register originated from, not 10.0.10.x IP so it must have some NAT intelligence, just that it replies to the wrong port (5060)
Why is 3cx doing this, is it a bug? I don't see this issue with other PBX's like Asterisk, and Brekeke, so not sure what is going on.
I have enabled and disabled STUN support - no change, I have also followed the guide here
http://www.3cx.com/blog/voip-howto/remote-extensions/? to no avail, it seems that if 3cx is set on a server with a real IP and the remote extension is behind a NAT then 3cx cannot handle?
Any advice appreciated.
Thanks
WJ
The problems begin when I try and register a remote extension. So scenario is 3cx (V10.0.24018.2322) running on win2k8 on real IP address in a colo, within the multi tenant framework.
Trying to register extensions from a NAT environment, so phones have 10.0.10.x IP. Softphone is tested ok from this same network, but if I register a normal SIP phone, EG SPA504g then the register goes to 3cx, and 3cx responds with 407 proxy authentication required. The phone does not see this though, and re transmits the REGISTER.
From wireshark trace, the reason the phone does this is because 3cx erroneusly sends the 407 back to port 5060 not the port from which the register originated, which it would have to do for the NAT router to route the reply back to the handset.
But it does manage to reply to the REAL IP the register originated from, not 10.0.10.x IP so it must have some NAT intelligence, just that it replies to the wrong port (5060)
Why is 3cx doing this, is it a bug? I don't see this issue with other PBX's like Asterisk, and Brekeke, so not sure what is going on.
I have enabled and disabled STUN support - no change, I have also followed the guide here
http://www.3cx.com/blog/voip-howto/remote-extensions/? to no avail, it seems that if 3cx is set on a server with a real IP and the remote extension is behind a NAT then 3cx cannot handle?
Any advice appreciated.
Thanks
WJ