On Nov 29, 2012, at 10:20 PM, Mircea Carasel <mirc...@ezuce.com> wrote:
> Hi Alan,
>
> We had an attempt to implement call transfering through callcontroller, but
> unfortunatelly this does not work properly. We will give another try post 4.6
> to make this working properly
>
> Here is how it should be done to accomplish a transfer (does not properly
> work)
>
> 1)user1 calls user2 through callcontroller using INVITE
> callcontroller/user1/user2?sipMethod=INVITE
> (http://wiki.sipfoundry.org/pages/viewpage.action?pageId=4882956)
> 2)user 1 would like to transfer the call to user3 so that user2 and user3 to
> start talking:
> /callcontroller/user1/user2?target=user3&action=transfer&agent=user1
> 3)original call between user1 and user2 should automatically drop
>
> However what you can do is to just place a call from user1 to user 3 and the
> original call between user1 and user2 will be put on hold:
> This does not respect SIP transfer specifications, but does work, and maybe
> it is useful to you:
> 1)user1 calls user 2 through callcontroller using REFER
> /callcontroller/user1/user2
> 2)user1 places a call between user2 and user3
> callcontroller/user2/user3?agent=user1&timeout=30&isForwardingAllowed=true
> 3)original call between user1 and user2 will be put on hold
Mircea,
Does the difference between having two calls between internal users directly
between endpoints, and a call with one internal user connected via sipXbridge
to an external number make any difference in the ability to transfer? For the
specific scenario we are looking at it would be almost entirely calls between
an internal user and an external number via the sipXbridge.
Thanks,
Trevor Benson
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
