Re: reregister fails after 6-8 hours

This has been fixed on the sipXtapi branch.  Thanks for tracking this
down.

On Saturday, August 5, 2006, 7:13:32 AM, Wolfgang Pichler wrote:

> Hi all,

> its good to be on the right list for such questions...

> Maybe some of you have already read my posts on the other list - it is
> about the reregister problem...

> for all the other persons...

> sipxtapi (i am using the sipxtapi-media-update branch) does seem to be
> unable to reregister after around 6-8 hours (with 3600 sec expiration 
> period). I have found out that this get caused by a Message Queue which
> gets filled because of the thread which should read the messages does 
> not get startet. In particular the SipRefreshMgr does receive the 
> Messages in its Queue form the SipUserAgent. On the SipRefreshMgr their
> is also a observer registered - the SipLineMgr. So the SipLineMgr does
> get the messages also in its queue. But the SipLineMgr does not get 
> startet within the sipxtapi. It gets constructed - but not startet. So
> the queue of the SipLineMgr does fill up - gets full - so the send 
> (without a timeout) will wait infinitly - so the SipRefreshMgr will stop
> working...

> The question now is - is the SipLineMgr needed any more (its not running
> - so i assume it is not needed) - why does it get constructed ?

> Please, someone with deeper knowledge of the sipxtack stack - tell me if
> the SipLineMgr is needed any more !

> I have created an issue for this:
> http://track.sipfoundry.org/browse/XSL-136

> regards,
> Wolfgang

> _______________________________________________
> %(real_name)s mailing list
> %(real_name)s <at> %(host_name)s
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
> Archive: http://list.sipfoundry.org/archive/%(listname)/

_______________________________________________
%(real_name)s mailing list
%(real_name)s <at> %(host_name)s
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Archive: http://list.sipfoundry.org/archive/%(listname)/