Thanks Iñaki, I was under the impression that was for INVITE transactions only. I don't see any reference to it anywhere other than section 14 - modifying an existing session - all about re-INVITE. I'm currently interested in non-INVITEs only. Steve
-----Original Message----- From: Iñaki Baz Castillo [mailto:i...@aliax.net] Sent: 05 May 2009 10:39 To: Stephen Paterson Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Multiple concurrent transactions 2009/5/5 Stephen Paterson <stephen.pater...@aculab.com>: > Hi all, > > Just a quick one to confirm something. > Is it perfectly reasonable to have multiple concurrent transactions of > the same method on a single dialog? I.e. can you send a second INFO > (for example, could be any non-INVITE) before receipt of a response > for a previous INFO on the same dialog? I'm talking about separate > transactions, not retransmissions. > > I'm fairly sure you can, I just can't find any text to support it. No, it's no tpossible and the UAS shoule reply "491 Request Pending": http://tools.ietf.org/html/rfc3261#section-21.4.27 -- Iñaki Baz Castillo <i...@aliax.net> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales) P Please consider the environment and don't print this e-mail unless you really need to _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
