It may be a good idea to expand on the registration section in the
call-flows document and illustrate message interactions for some of the
trust combinations to supplement the description in the RFC.
regds
arjun
--
Arjun Roychowdhury @ Hughes Software Systems
11717 Exploration Lane, Germantown MD 20876
(O): 301-212-7860 (M): 240-997-0066
"Brett Tate" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
08/14/2002 04:49 PM
Please respond to brett
To: "'Clendenan, Dave'" <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
cc:
Subject: RE: [Sip-implementors] Third-Party Registration
call flow example
> Do any of you have call flow examples
> of Third-Party registration that you
> could share?
It is the same as a normal registration except
the From reflects the sender and the To reflects
the party for which the contact modifications
should apply.
The authentication and trust relationships
can produce various deferent call flows.
The typical case would be to send the REGISTER
to the To's registrar. It would challenge
the request using the To party's authentication
credentials.
Other flows might involve only/additionally
a proxy authentication based upon the From
party. These might involve the From party's
proxy or a 3rd-party authentication validator.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
