Hello, > I don't know whether you access that singleton from the GUI thread as > well. If you do it without locking then it's > not thread safe and you might get random crashes. To avoid locking I > access a copy of configuration in the thread. > That copy is passed as a parameter to initialization. Yeah, I do use it in the GUI thread. I never had any crashes but will definitely improve this, thanks for pointing out.
> You should see how many IP addresses there are, and await so many STUN > responses. There is no STUN > response for 127.0.0.1 (loopback). Yes, I meant this only :). > I found out the problem was in supplying sip proxy hostname instead of > IP address. When I supply IP address it works. > My phone strangely somehow works also if you provide hostname, but > somewhat slower. Kool, atleast it worked! > Also if you try to send a message during call to the same sip uri, or > after a call, you will get a nice crash :-) Actually, I added IM just for experimenting. I have wanted to add a feature which lets the user translate the coming messages to a different language. The translation is done on the fly using Google's translation services and it's working fine for now. > I also noticed the same problem in my phone although it seems to be > happening less often. It occured to me in vmware only. > On my host operating system, I couldn't reproduce it with my phone. Its > probably a problem in sipxtacklib. Thanks. Regards, Hitesh _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
