Hello, > Are you executing this in another thread? Because some of the functions > take longer to complete. There you also access a singleton, if this is > in another thread then application might not be thread safe. Yes, I execute this in another thread. Can you please elaborate the second point? How does this make an application thread unsafe?
> I have noticed crosstalk doesn't freeze during initialization like > sipxezphone. > When waiting for STUN result, be careful you need to wait for all > results, not just the first success, as PC can have multiple interfaces > which lead to different networks and they can be in different NATs. You > should get a result for each IP address. Ok, so you mean that I should see how many interfaces there are and wait for equal number of STUN responses? >I will compare the code with > mine later, as I have to do something else right now, but I see you > followed the bad habbit in sipxezphone to call sipxtapi functions > without checking results. No, I just stripped the error checking to make it easy to read. Please see my code to find the problem, I'm grateful to you. >I have a special class that is for calling > sipxtapi functions and does checking of all results and logs errors and > sipxtapi error codes. This is important if you use a library that is not > 100% stable. This class has 100kb of code (cpp + h file) but if there is > a problem I can quickly find it. Looks like a good idea, learning a lot from you :). Thanks for all the help and guidance, I really appreciate that :). I do update my sources often, but don't understand why this register failed is coming. Do you get the same result with sipXezPhone as well? Best Regards, Hitesh _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
