Thanks for all your replies. In my previous mail, I in-correctly stated "early dialog". It should have been INFO sent before any provisional response (except 100 trying) by proxy or UA. I don't think this is possible. The UA won't accept this INFO message and it is not as per standard.
On 6/16/06, Sarabia Antonio-ASARABI1 <[EMAIL PROTECTED]> wrote: > > this approach could be used to modify the call characteristics before it > is established. > it is not standard, so may or no may not succeed based on the > implementation of the proxy. > ideally it would, as it is no different, from a routing perspective, > from a CANCEL, without > to tag, but most likely end clients will not take it. maybe yours will, > Paul. > > Antonio. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dale R. > Worley > Sent: jueves, 15 de junio de 2006 23:51 > To: Sip-Implementors > Subject: Re: [Sip-implementors] INFO sent on early dialog? > > On Thu, 2006-06-08 at 23:37 -0400, Paul Kyzivat wrote: > > > In my case, I need to send INFO request before 18X response itself. > > > Consider this situation where the proxy sends INFO request to the > > > originating UA after it has forwarded the initial INVITE to the > > > terminating UA but before it has received any 18X/final response > from terminating UA. > > > Is this possible? > > > > That is a pretty clearly invalid. The *proxy* is not allowed to be > > *originating* any messages in the dialog. > > Well, the proxy could pretend to fork the request to a UA that is inside > the same process. *That* UA can respond with 180, followed by an INFO > in the dialog created by that 180. Then it has to do some sort of > failure response to terminate that early dialog. (Actually, it can omit > generating the 180, and pretend the network lost the 180, but that the > INFO got through...) > > Not pretty. > > But that's probably not what you want, as the INFO would be in a > *different* early dialog than the 180 that the real UAS will provide. > Indeed, you can't fake a request that's in the early dialog that the > real UAS is creating, as you can't predict the to-tag and CSeq that it > will use. > > What exactly are you trying to do? > > Dale > > --- > interop.pingtel.com -- the public SIP phone interoperability test server > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
