Hi all,
I'm getting a problem when a user behind a windows gateway (NATed client) connects to my ser box. I think this was already discussed here but I didn't find anything on the logs.
The problem is with the '407 Proxy Authentication Required' signal that never reaches the client.
Here is the scenario: 1- The user sends the INVITE from a higher port to the SIP server. It looks like this: User:63040 -> SER:5060
2- SER responds with a 407 Proxy Authentication Required on the client's local sip port: SER:5060 -> User:5060
At this point, I think windows drops the package because it don't refer to any entry at the NAT table, but I'm not sure about that.
I want to know if there's a solution to this 'problem'.
Thank you all.
We've also had serious problems with boxes behind Windows as a NATted gateway. It does some very funky thing with the way it handles ports. It doesn't seem to want to keep open ports for return communications after an outgoing communication.
For instance, when I send data out port 3510, awaiting a response, it immediately closes the port. It's incredibly, frustratingly non-standard behaviour.
N.
Thomas Britis wrote:
Hi all,
I'm getting a problem when a user behind a windows gateway (NATed client) connects to my ser box. I think this was already discussed here but I didn't find anything on the logs.
The problem is with the '407 Proxy Authentication Required' signal that never reaches the client.
Here is the scenario: 1- The user sends the INVITE from a higher port to the SIP server. It looks like this: User:63040 -> SER:5060
2- SER responds with a 407 Proxy Authentication Required on the client's local sip port: SER:5060 -> User:5060
At this point, I think windows drops the package because it don't refer to any entry at the NAT table, but I'm not sure about that.
I want to know if there's a solution to this 'problem'.
Thank you all.
inline...
2007/6/12, Thomas Britis thomas@tcnet.com.br:
Hi all,
I'm getting a problem when a user behind a windows gateway (NATedclient) connects to my ser box. I think this was already discussed here but I didn't find anything on the logs.
The problem is with the '407 Proxy Authentication Required' signalthat never reaches the client.
Here is the scenario:1- The user sends the INVITE from a higher port to the SIP server. It looks like this: User:63040 -> SER:5060
2- SER responds with a 407 Proxy Authentication Required on the client's local sip port: SER:5060 -> User:5060
Shouldn't SER send 407 to port 63040?? Which config file are you using?? In the onsip/getting started examples, authentication is done before NAT check and the challenge is not directed to the right port.
If you provide the auth+INVITE section of your config file, we might try to point wihch are the required changes..
At this point, I think windows drops the package because it don't
refer to any entry at the NAT table, but I'm not sure about that.
Most routers will do that, not only windows...the first and probably not last time I don't blame exclusively w$ ;)
Samuel.
I want to know if there's a solution to this 'problem'.
Thank you all.-- Thomas Storino Britis TCNet Informatica e Telecomunicacoes LTDA _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
samuel -
SIP -
Thomas Britis