<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div><div class="ydp3f7ae420msg-body ydp3f7ae420P_wpofO ydp3f7ae420mq_AS" data-test-id="message-view-body-content"><div class="ydp3f7ae420jb_0 ydp3f7ae420X_6MGW ydp3f7ae420N_6Fd5"><div><div id="ydp3f7ae420yiv9144606950"><div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;" class="ydp3f7ae420yiv9144606950yahoo-style-wrap"><div dir="ltr">Hello</div><div dir="ltr"> I'm running K5.5.3 and have checked the 'issues' link in github and saw
nothing regarding what I am seeing. I think that there is a bug in the
tm module with respect to the "tm:local-response" event route. In the
"t_reply.c" file, there is a static variable called
'_tm_local_response_set_lookup'. This variable is initialized at load
time to zero. It is checked in the '_reply_light()' routine and will
initiate a local callback from the config script if "armed". The
problem as I see it is that if the callback is readied, the variable is
set to one. But it is never reset.</div><div dir="ltr">So the practical
outworking is as follows. A register is received and the request_route
arms the callback. The register requires an authorization (local database sqlite). After the
401 is sent back, the callback via the module event route is called as expected.
All good except that the module event route script fragment is never
executed again after the first call.</div><div dir="ltr">I'm no expert
on the tm module but I would think that somewhere in there, the variable
should be reset to zero so that subsequent transactions can initiate
the event route again.</div><div dir="ltr"><br></div><div dir="ltr">thanks for any help,</div><div dir="ltr">Dan<br></div></div></div></div></div></div></div></div><div><br></div></div></div></body></html>