RE: [reSIProcate] Setting via headers for STUN

["Matthias Moetje - TERASENS GmbH" <moetje@xxxxxxxxxxxx>]

Joe,

thanks for the hint. I read the discussion and I 
don't fully agree that a wrong via address doesn't 
matter. Other SIP UAs with STUN support also set
the via address to the mapped public ip address.

Today I had the idea to specify a fixed transport 
in the userprofile (STUN only works with UDP anyway)
to prevent the transport selection failure, but 
I haven't tried that yet...

Best regards,

Matthias Moetje



> -----Original Message-----
> From: Joe Liao [mailto:joe.jhliao@xxxxxxxxx] 
> Sent: Thursday, April 06, 2006 4:41 AM
> To: Matthias Moetje - TERASENS GmbH
> Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] Setting via headers for STUN
> 
> Hi Matthias ,
>    I saw this problem on thread before as below, 
> http://list.sipfoundry.org/archive/resiprocate-devel/msg02732.html
> But i can't see what's the conclusion there.
> Hope this helps.
> 
> Best regards,
> -Joe
> 
> 2006/4/5, Matthias Moetje - TERASENS GmbH <moetje@xxxxxxxxxxxx>:
> >
> > Hi,
> >
> > I am currently encountering a problem while implementing 
> STUN support:
> >
> > When I adjust the via headers for sending an invite to the 
> discovered 
> > mapped ip address and port, the TransportSelector tells that it is 
> > unable to determine a matching transport. This is because 
> it uses the 
> > first via header to determine a matching transport.
> >
> > How can I work around this (change the via but use the 
> actual local IP 
> > and port for transport selection)?
> >
> >
> > Best regards,
> >
> > Matthias Moetje
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >
> >
>