RE: NAT and firewalls transversal

Michael,

The problems with RTC are a known issue. At one point I added some code in the stack to deal with this client, but I've removed it again since it might interfere with well behaving UACs.

The problem is that the stack API does not provide the IP+port from which a message was received (perhaps a future extension). In the mean time, a workaround is to use TCP (if you can), or else hack the stack a little yourself (not too difficult, RTC code is still there but commented out)

Regards,
Jeroen

-----Oorspronkelijk bericht -----
Van: "Michael kr" <[email protected]>
Aan: "Hagai Sela (TA)" <[email protected]>; [email protected]
Verzonden: 31-10-06 16:28
Onderwerp: RE: [nist-sip] NAT and firewalls transversal


Thanks Hagai,

The only problem I have is that I am using Microsoft's
RTC stack as the UA basis, which is a black box and I
don't have access to the SIP signaling.

I am considering to add "rport" parameter explicitly
to the stack. Are you aware of any bad consequences of
it?

Michael


--- "Hagai Sela (TA)" <[email protected]> wrote:

> Oops. I was wrong; you should specify "rport" in
> your via header and not
> the request URI.
> 
> Hagai. 
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Michael kr