HI Parveen I guess reason of putting call on hold before initiating another call from same UA is that UA have single instance of media resources which can be used for one active call . But another thing is for blind transfer scenario, after UA triggering transfer and sending Refer need not to stay in call so call can be disconnected(thats why called blind transfer) rather of putting on hold . In case of consultative transfer ,Add call ,conference scenarios we normally need to put call on hold .
Thanks & regards Ankur Bansal On Mon, Feb 24, 2014 at 8:04 PM, Parveen Verma <parveen.s...@gmail.com>wrote: > Hi All, > > I have a question regarding the below scenario. > > Scenario: > > A calls B, call is established and then A initiates Blind Call Transfer to > C. > > In this case before sending REFER, the UAC of A puts the media as InActive > for A to B call and this way puts the A to B call on hold. > > In Case, Call is not put on Hold by A earlier then our AS puts the Call on > Hold after receiving the REFER and then sends NOTIFY to A. > > > Now my doubt is what is the need for putting the Call between A & B on > Hold. > > I checked the RFC 3515 <http://tools.ietf.org/html/rfc3515>, but do not > found any such specification. > > Does any one has an idea why this is done by UAC/AS or any pointer leading > to this behaviour. > > > Thanks & Regards > > Parveen Verma > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
