[EMAIL PROTECTED] wrote:
>> Hello,
>>
>> I have been using release 9183 and sipXezPhone was able to register with
>> my Asterisk server with no problems.
>>
>> However, on upgrading to release 9921, sipXezPhone can no longer register.
>> In fact, no packets are seen on the wire.
>>
>> In the logs, I see:
>> "2007-08-06T16:22:51.945000Z":100:REFRESH_MGR:ERR:Marete:SipRefreshMgr-2:00000474:sipXtapi:"unable
>> to send REGISTER message (send failed)..."
>>
>> I noticed that I could not compile sipXmgr.cpp after upgrading.
>> Apparently, it was something to do with winsock.h/winsock2.h. It compiles
>> cleanly if I #define WIN32_LEAN_AND_MEAN at the very top. Might this be
>> related to the problem, or is there some other aspect of an API change
>> that has come through between revisions 9183 and 9921?

I wonder how you could see that in the logs, if you can't compile
sipXmgr.cpp in the first place. Winsock2 is used instead of winsock1.
Previously at least in msvc8 project, we used winsock1 headers but
linked with winsock2.

> 
> With regard to the above, it turns out that if I replace the
> human-readable name for my Asterisk server with it's IP address,
> everything works OK. once more. The phone is able to register and I can
> make and receive calls as usual. Is this a useful clue?
> 

There is a DNS bug in current sipxtapi branch. We have a fix and it will
be commited soon. It's already fixed in experimental sipxtapi.

Jaro

_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to