< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
Can you attach a DEBUG_STACK log. I haven't seen that behavior before. Jason On 8/26/07, Sgregor1 <sgregor1@xxxxxxxxxxxxx> wrote: > Hi all, > > Undoubtedly this is my fault as I have only been playing for a day or so but > I cant figure out why the following happens. > > I assumed that a line like: > > clientDum.getMasterProfile()->setDefaultRegistrationTime(60); > > would cause REGISTERs to be sent every 54s or so. > > > What I see against my own proxy is: > > REGISTER > 401 > REGISTER > 100 > 200 > DialogUsageManager::addTimer() code executed > > ... 54 s elapsed ... > > > REGISTER > 100 > 200 > DialogUsageManager::addTimer() code executed > > ... no more REGISTERs thereafter ... > > > > If I put a trap on DialogUsageManager::addTimer() where what I assume is a > timer message being placed on the fifo somewhere? This looks like it is > being successful both times, but the 2nd time round it seems to never result > in the firing of the case DumTimeout::Registration leg in the DUm process() > code 54s later. > > i.e. the auto-refresh works once then never again. > > > Has anyone seen this or am I being daft? > > Many thanks for any help. > > > ________________________________________________ > Message sent using UebiMiau 2.7.2 > > _______________________________________________ > resiprocate-users mailing list > resiprocate-users@xxxxxxxxxxxxxxxxxxxx > List Archive: > http://list.resiprocate.org/archive/resiprocate-users/ >