Hi Marut! This is because, for unattended transfer, you don't need to put the first guy(or gal) on hold. In practice, you disconnect from the first guy(or gal) and then send an INVITE to the second guy(or gal). That's it! It's when you want to do an attended call transfer or a consultation call hold, that you may need to put the 1st UA on hold and then dial out to another UA. i.e you want to keep the first call in-case you need to get back to it. Warm Regards,
Jerry Ipe Thomas Engineer(R&D) D-Link India Ltd. Software & R&D Center Bangalore - 68 Ph: +91-80-26788350/1 Extn: 117 Mob: +919886442530 -----Original Message----- From: Marut Das [mailto:[EMAIL PROTECTED] Sent: Saturday, July 31, 2004 3:36 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Sip-implementors] Confusion with unattended call txfer In the call flow for unattended call transfer, in the document draft-ietf-sipping-cc-transfer-02.txt, it is first shown that call is put on hold before a REFER for the transfer is sent out. In the service example document,draft-ietf-sipping-service-examples-07.txt, in the example of the same on page 41, the REFER is sent without putting the call on hold. This is in contradiction to the above document. Am I misinterpreting something over here. Could anyone explain the behaviour of the same ? Rgds Marut
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
