Any Suggestion for me?..In my case CSQ is not there in Unauthorized response.
-----Original Message----- From: [email protected] [mailto:[email protected]]on Behalf Of Nobody Nowhere Sent: Saturday, May 16, 2009 3:41 AM To: [email protected] Subject: Re: [sipxtapi-dev] Register Unauthorized issue -- ven if correct Realm is specified Alexander Chemeris wrote: > On Fri, May 15, 2009 at 11:43 PM, Nobody Nowhere <[email protected]> wrote: > >> I think i have the same issue .. i'm using the latest sipxtapi from the >> main branch on 64 bit linux with my-self patched dns packet parsing (the >> one in trunk is not working on 64 bit platforms). >> using placecall example (ofcourse modified - coz the one in trunk - does >> not use szProxy variable at all) >> > > And of course you should have posted your patches to mailing > list as per LPGL. In general, you must publish all changes if you > deploy your application, "if i deploy" i'm not deploying anything yet - i decided to not to publish anything yet because my patches are not "best" quality - those are "fast" fixes as for now .. i've seen on this mailing list that someone had a "solid" patch - but i saw it after i fixed it myself > and it's friendly to send patches for problems > you've found. That's the way open-source lives. > i promise that when i'll done with setting everything up - i'll send full patches > I've seen dns problem on my system - it's 64-bit too, but had no time > to dig into. It would be nice to see you patches. > i can send you only my "fast fix" .. it solves my particular problem - it's not complex fix .. i'm attaching it > re: your problem with registration > > Please, attach sipXtapi log for that session. > download it from here : http://przeklej.pl/plik/placecall-tar-gz-0001o70g36jo would attach but here are limits to 100k per mail > re: recvfrom() > First, please double check your network setup and be sure that > noone uses ports you're trying to listen on, etc. > i'm sure i have 5060 port free i've even wrote a simple udp server to check it out.. > I've seen similar log events before and I recall it was caused by > a stale process preventing new connection to bind to the port thank you for reply _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
