< Previous by Date Date Index Next by Date >
  Thread Index  

Re: [reSIProcate-users] [reSIProcate] ClientAuthDecorator is deleted after its creation


Oh good!  I was starting to think I was going crazy - I know I tested that change.  : )

Scott

On Thu, May 26, 2011 at 3:43 PM, Dmytro Bogovych <dmytro.bogovych@xxxxxxxxx> wrote:
Sorry, it was my bug.
I missed to update DialogUsageManager.* files.
Sorry for disturbing.


On Thu, May 26, 2011 at 12:30 PM, Dmytro Bogovych
<dmytro.bogovych@xxxxxxxxx> wrote:
> Greetings.
>
> I migrate client VoIP toolkit to new 1.7 version. I made simple test
> with registration.
> I discovered that now client authentication is handled through
> ClientAuthDecorator. Cool.
> There is a call stack for decorator creation point on response message.
>
>>       IntTalkCore.dll!ClientAuthDecorator::ClientAuthDecorator(bool isProxyCredential=false, const resip::Auth & auth={...}, const resip::UserProfile::DigestCredential & credential={...}, const resip::Data & authQop={...}, const resip::Data & nonceCountString={...})  Line 20   C++
>        IntTalkCore.dll!resip::ClientAuthManager::RealmState::addAuthentication(resip::SipMessage
> & request={...})  Line 416 + 0x3d bytes C++
>        IntTalkCore.dll!resip::ClientAuthManager::AuthState::addAuthentication(resip::SipMessage
> & request={...})  Line 260 + 0x16 bytes C++
>        IntTalkCore.dll!resip::ClientAuthManager::addAuthentication(resip::SipMessage
> & request={...})  Line 174      C++
>        IntTalkCore.dll!resip::DialogUsageManager::send(resip::SharedPtr<resip::SipMessage>
> msg={...})  Line 839    C++
>        IntTalkCore.dll!resip::DialogSet::handledByAuthOrRedirect(const
> resip::SipMessage & msg={...})  Line 259        C++
>        IntTalkCore.dll!resip::DialogSet::dispatch(const resip::SipMessage &
> msg={...})  Line 496 + 0xf bytes        C++
>        IntTalkCore.dll!resip::DialogUsageManager::processResponse(const
> resip::SipMessage & response={...})  Line 1858  C++
>        IntTalkCore.dll!resip::DialogUsageManager::incomingProcess(std::auto_ptr<resip::Message>
> msg=auto_ptr {tu=0x01bfe268 })  Line 1407       C++
>        IntTalkCore.dll!resip::DialogUsageManager::internalProcess(std::auto_ptr<resip::Message>
> msg=auto_ptr {tu=??? })  Line 1234      C++
>        IntTalkCore.dll!resip::DialogUsageManager::process(resip::RWMutex *
> mutex=0x00000000)  Line 1438 + 0x67 bytes       C++
>        IntTalkCore.dll!SIPEndPoint::Process()  Line 1174 + 0xd bytes   C++
>        IntTalkCore.dll!SIPEndPoint::thread()  Line 1251        C++
>        IntTalkCore.dll!Thread::ThreadProc(void * arg=0x01bf4890)  Line 160
> + 0xf bytes     C++
>        IntTalkCore.dll!_callthreadstart()  Line 293 + 0xf bytes        C
>        IntTalkCore.dll!_threadstart(void * ptd=0x01c008e0)  Line 277   C
>        kernel32.dll!76221174()
>        [Frames below may be incorrect and/or missing, no symbols loaded for
> kernel32.dll]
>        ntdll.dll!7790b3f5()
>        ntdll.dll!7790b3c8()
>
> ClientAuthDecorator instance is add to message object. Good.
>
> BUT the next line in DialogUsageManager::send(), line 866 clears
> message decorators.
> Of course client is not authenticated by server.
>
> Is it my bug or resiprocate's one?
>
> Thank you :)
>
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel