> -----Original Message----- > From: Elwell, John [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 04, 2007 3:07 AM > To: Hadriel Kaplan; Francois Audet; Dean Willis; Brian Stucker > Cc: [email protected]; Adam Roach; Mary Barnes > Subject: RE: [Sip] INFO > > Hadriel, > > Are those applications necessarily on the INFO path? KPML doesn't > require the applications to be on the INFO path.
As far as I've ever seen yes the apps are in the signaling path, but it's not my area. One would think, though, that for an app server to know whom to generate a KPML subscribe to, and for what dialog identifiers to put in the Event header, the app server would have to be in the signaling path regardless. If one could KPML subscribe without that info, which is not clear to me is or is not allowed by 4730, then sure one could just subscribe to UAs without being in call signaling. > I believe plenty of SIP devices only support RFC 2833, not INFO, and > those that do support INFO are likely to do so in different ways, > because it is not standardised. So how can the application provider be > sure, even with INFO, that there will be devices to support it? That's why I was thinking we could define a simple way to indicate such a thing. Usually I don't like to have more than one, mandatory way to do something, but that ship has already sailed for DTMF, IMHO. So the next-best thing is at least negotiation/indication. -hadriel _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
