5 Nov
2011
5 Nov
'11
1:15 p.m.
On 11/4/11 9:45 PM, Alex Balashov wrote:
P.S.
I have tried dropping them conditionally in the tm:local-request event
route and onsend_route. It doesn't work when the request is
endogenously generated.
dropping in tm:local-request is not possible, afaik (being
considered
that the decision was made by sender code), although should be added
being sometimes useful, imo.
Not sure what is the reason for onsend_route, does it get there and drop
does not work? Or it does not get there?
Maybe the best would be to add an event_route specific for uacreg, just
before sending the request to tm for building and sending the sip
register, providing in a PV the details of that registration. That will
save some processing and memory to build the local transaction.
Cheers,
Daniel
On 11/04/2011 04:44 PM, Alex Balashov wrote:
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
Is there some way by which credentials can be
loaded into the uacreg
table, but not all of them used at once?
The problem I have is a need to make these registrations active and
inactive periodically, whereas the registration facility that the uac
module provides is fully managed/largely unattended.
Using $uac_req(...) is not an option because I need to capture the
failure replies (which is not supported in TM) in order to do digest
challenge authentication.