Re: [OpenSIPStack] STUN support bug?

[Joegen E. B. <joe...@gm...>]

Hi Ilian,

Can we change the STUN code so that it asserts when called after the 
transport has already been initialized?


Ilian Jeri C. Pinzon wrote:
> Hi,
>
> SetSTUNServer should work when it is called before the transport has
> been set up. Have you tried calling this during initialization?
>
> Regards,
> Ilian
>
> H.Kropf wrote:
>   
>> Hello
>>
>> I try to use OSS SoftPhone client (OSS 1.1.7 CVS) with server OpenSER 
>> and with NAT of type NAT::SIPSTUNClient::ConeNat
>> Calling of function SetSTUNServer connect succefully to my STUN-server.  
>> SoftPhone receive true NAT IP-address and NAT port.
>> But after, when i call SoftPhone::SendRegister() then  OpenSER register 
>> client like "NAT, without STUN"
>>
>> Exemples: (correct and wrong)
>> ===============================
>>
>> REGISTER requests via NAT using STUN:  (aliases: 111.111.111.111 - 
>> instead of local SIP-client IP, 222.222.222.222 - instead of NAT IP, 
>> 333.333.333.333 - instead of SIP-server IP)
>>
>> CORRECT (hardware Zyxel SIP-client)
>>   
>>     
> <snip>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>