< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Documentation


Unfortunately, (as you may have guessed), the ones that report "must
log in to edit" don't exist, so it is prompting you to create it.

We do need to all make an effort to get more of them filled in...

--David

On 7/26/05, John Draper <lists@xxxxxxxxxxxxxxxx> wrote:
> Hi again,
> 
> many of you have been most helpful in pointing out documentation on how
> to use
> reSIProcate.  In particuar...   I would run into a URL like this:
> 
>   http://warsaw.sjc.purplecomm.com/wiki/index.php?title=DUM_Usages
> 
> In it,  would be links like this...
> 
>     *      Usages are blah, blah, blah.
>     *     Describe what handles are here.
>     *     ClientRegistration
>     *     ServerRegistration
>     *     ClientPublication
>     *     ServerPublication
>     *     ClientSubscription
>     *     ServerSubscription
>     *     Invitation
>     *     Pager
>     *    OutOfDialogReq
> 
> Almost every one of these links will reveal....
> 
>     Login required to edit
> 
> Ok,  so whats up with this?   Does this mean this stuff hasn't yet been
> added?  Or does it
> mean I just don't have access to it for some reason.  If the latter,
> why?  and would I
> be out of line asking for it?
> 
> In particular,  I would run across - "How to use DUM" and say - Aha,
> just what I need,
> so I go and read it,  and sadly only discover only the main sections are
> mentioned,  but
> the expected links are gone.
> 
> Anyway - I don't want to be a "pest" but does anyone have any of this
> information kicking
> around?
> 
> So - Yea guys,  I DO read the docs, source code, readme's - Honest - I
> do...  :-)
> 
> I read everything...  but only what I have access to.
> 
> John
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> 


-- 
David Bryan
Please continue to send me email at the address bryan@xxxxxxxxxxxx