Hi, Could you use the authentcation in RFC2617 for this?
You may know this kind of mechanism is already widely used in SIP. So after the REFER, you'd get a 401 response and then you'd resend the REFER with the credentials. So, you'd get something like this: > epA epB epC > | | | > |<===================>| | * epA has a session > |<=========================================>| * epA has a > | | | > |-----REFER---------->| | * epA REFERs > |<----401-------------| | > | w/challenge nonce and other data | > | | | > |-----REFER---------->| | * epA REFERs(2) > | w/credentials | | > |<----202 Accepted----| | > | |---INVITE----------->| * epB INVITEs > |<-NOTIFY/200(trying)-| | > | |<--200/ACK---------->| > |<-NOTIFY/200(succes)-|<===================>| * epB and epC > | | | > |-----BYE/200-------->| | * epA ends > |------------------------BYE/200----------->| * epA ends > | | | > | | | Is this any use? Regards, Attila Sipos Software Engineer www.vegastream.com <http://www.vegastream.com/> > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: 28 October 2004 10:48 > To: [EMAIL PROTECTED] > Subject: [Sip-implementors] Consultative call transfer > > > Dear SIP gurus, > > My UA application requires "consultative call transfer" (transferor > converses with the destination first). Obviously I need to implement > RFC3515 / REFER method. > > Another requirement of this application is that the destination must > accept the transferee's INVITE directly(without user > interaction), but > ONLY if it contains certain credentials. > > Consider the following scenario where epA (the transferor) > has a session > with epB(the transferee) and epC(the destination): > > epA epB epC > | | | > |<===================>| | * epA has a session > established with the transferee > |<=========================================>| * epA has a > session established with the destination > | | | > | | | > |-----REFER/200------>| | * epA REFERs > epB to epC ### > REFER contains credentials ### > |<-NOTIFY/200(trying)-| | > | |---INVITE/200/ACK--->| * epB INVITEs > epC ### epC > verifies credentials ### > |<-NOTIFY/200(succes)-|<===================>| * epB and epC > establish a > session > | | | > |-----BYE/200-------->| | * epA ends > session with epB > |------------------------BYE/200----------->| * epA ends > session with epC > | | | > | | | > > In some way, epA has to provide epB credentials which epB must use to > INVITE epC. I think these credentials e.g. could be something > like the > epA-epC call ID and from/to tags. > > What headers/bodies etc... are normally used to carry these > credentials to > be interoperable with other UAs other than my own application. > > Other suggestions and comments are more than welcome. > > Martin van den Berg > _______________________________________________ > 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
