[reSIProcate] Turning on DebugLog; also routing

[Byron Campen]

	Pass the command-line option --log-level=DEBUG to get the DebugLog  
macros to start outputting. I think that repro forwards to all routes  
that match (and it looks like the behavior is full parallel on this  
one). Specifying a routing rule like the one you described means  
writing a single regular expression to do the job.

Best regards,
Byron Campen

> What is the Right Way to turn on output from the DebugLog macros?  I'm
> running sanityTests, and it looks like the DebugLog messages are not
> being output.
>
> Also, how is the routing intended to work?  Does repro iterate through
> all the routes and choose the first one that matches, or does it  
> forward
> the request according to all routes that match?  (And if the  
> latter, how
> does one specify a rule "All XXX that are not also YYY"?)
>
> Thanks,
>
> Dale
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060301/471312fe/attachment.bin>