> From: Mark R Lindsey [mailto:lind...@e-c-group.com] > > You're going to have to clarify this use case a little more -- as you > said, it doesn't follow the SIP transaction model, so it's hard to > quite see what you mean. Can you give more detail? >
Sure. In this case my SIP client is contained in a web browser when it receives a call it presents the user with the option to redirect the call to a list of destinations by clicking on different buttons. The goal of the user is to go through the list clicking on each button that is a suitable destination to redirect the call to. The problem I have that once the first button is clicked on that's the end of the user's ability to choose any more destinations. One solution that would easily solve the problem is to use a 1xx informational response with a custom header to indicate a redirect destination. That would keep the transaction alive and since multiple 1xx response are permitted the client could send a new one each time the user clicked a button. Once the server gets an answer on one of the redirected calls it sends a CANCEL request to the SIP client to let it know. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
