This is because your endpoint is an idiot and puts the wrong IP in the SDP... its going to cause us to send media to the wrong place until they send us a packet to auto adj. It is a hard situation to solve and if your endpoint can't traverse nat on its own or figure out its info then you're out of luck. Its not the registrars job or place to try to figure out your endpoints nat deficiency. Your situation is a little out of the usual so I totally expect you to find all kinds of edge cases that aren't solved by default. You do remember its SIP right? The most retarded protocol on the planet. :P /b On Mar 29, 2010, at 9:01 AM, Fabio Pietrosanti (naif) wrote:
Unfortunately i am a good tlc, security and it guys but at programming i read piece of code just to isolate issues. For sure the NAT handling have situation that does not precisely identify NATted host. Then maybe the auto Rtp adjust may require some improvement. I've seen FS sending packets to 10.0.0.0 network even with an host that had AUTO-NAT in the "sofia status profile internal", so the RTP packetizer was sending data to the SIP UA internal address that was correctly identified as NATted looking at the Sofia information.