That doesn't seem reasonable to me. That's like sending an initial INVITE and receiving a CANCEL request in response instead of a final response. Ie: you don't respond to a request with another request... If you did I can see a scenario where the requests would never end.
Brandon Adam Frankel (afrankel) wrote: > Hi All, > > I am seeing a scenario for an established call in which an outbound > reINVITE is being done, the far end is sending a TRYING and then a REFER > immediately. We are rejecting this REFER with a 400 Bad Request because > the INVITE transaction has not been completed. > > I am not clear whether REFER is allowed mid reINVITE or if the far end > should wait for the 200OK/ACK to complete before sending the REFER. > I took a look a RFC3515 but it does not appear to state either way > whether this is allowed. Can anyone comment? > > Thanks, > > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
