Why would I be expecting KPML, if I have only indicated that I support DTMF-over-INFO?
If I was to expect KPML, I would first need to establish a subscription for KPML (or, in our "controlled network", the subscription would be established by default, and I would know you are going to send KPML). Regards, Christer > -----Original Message----- > From: Eric Burger [mailto:[EMAIL PROTECTED] > Sent: 22. heinäkuuta 2007 4:41 > To: Christer Holmberg (JO/LMF); IETF SIP > Subject: Re: [Sip] INFO and Content Negotiation > > The point is that content type alone is not sufficient for > INFO negotiation. > You are a RFC 4722-aware device. You advertise you accept a > DTMF payload type. I am an INFO-aware device. I see you > understand a DTMF payload, so I send it to you in an *INFO* > message. You barf, because you were expecting KPML. > > > On 7/21/07 2:51 PM, "Christer Holmberg (JO/LMF)" > <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > I don't really understand your issue here... Did you send the text > > using INFO, or something? ;) > > > > Regards, > > > > Christer > > > >> -----Original Message----- > >> From: Eric Burger [mailto:[EMAIL PROTECTED] > >> Sent: 20. heinäkuuta 2007 23:14 > >> To: IETF SIP > >> Subject: [Sip] INFO and Content Negotiation > >> > >> 12 second proof point of why content type doesn't work. > >> > >> So here comes an INVITE. I am an INFO-friendly UAS. I > negotiate by > >> using Accept. > >> > >> This INVITE has the line: > >> Accept: application/kpml-response+xml > >> > >> > >> Wow! This is great! I know the UAC *wants* DTMF. Why? > >> Because it accepts a DTMF content type. Excellent - I can > now send > >> them DTMF. > >> > >> The user enters a digit, and I send an INFO with type > >> application/kpml-response+xml. > >> > >> UAC says, "What the heck was that?" > >> > >> > >> Notice: This email message, together with any attachments, may > >> contain information of BEA Systems, Inc., its > subsidiaries and > >> affiliated entities, that may be confidential, proprietary, > >> copyrighted and/or legally privileged, and is intended solely for > >> the use of the individual or entity named in this message. > If you are > >> not the intended recipient, and have received this message > in error, > >> please immediately return this by email and then delete it. > >> > >> > >> _______________________________________________ > >> 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 > >> > > > > > > Notice: This email message, together with any attachments, > may contain information of BEA Systems, Inc., its > subsidiaries and affiliated entities, that may be > confidential, proprietary, copyrighted and/or legally > privileged, and is intended solely for the use of the > individual or entity named in this message. If you are not > the intended recipient, and have received this message in > error, please immediately return this by email and then delete it. > _______________________________________________ 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
