Please see RFC 3725. 3PCC is a B2BUA. That should be in the path of SIP signaling for billing purpose. If your application requires 3PCC to be out of the signaling path, you could use REFER to achieve this provided both endpoints support it.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darshan Bildikar Sent: Monday, April 23, 2007 1:19 AM To: [email protected] Subject: Re: [Sip-implementors] Question related to 3PCC Apologies for the retransmit. Would appreciate any pointers. I am stuck with this. Darshan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darshan Bildikar Sent: Thursday, April 19, 2007 6:00 PM To: [email protected] Subject: [Sip-implementors] Question related to 3PCC A question related to transfer I have achieved a call transfer through 3PCC between parties A and B and have individual dialogs with both. After completion of the call, I now want to drop out of the signalling path (either immediately or after an arbitrary amount of time). Is this legal? Can I send a refer with a replaces to A or B to achieve this? Another related question I've noticed that most endpoints accept a REFER (inside INVITE dialog) only if we hold the INVITE dialog first. Is this because it is inside dialog? Can I expect different behaviour if I send the request outside of a dialog? Darshan _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
