50 likes | 230 Views
KPML. draft-ietf-sipping-kpml-01 Eric W m . Burger. Changes from draft-burger-sipping-kpml-02. draft-ietf-sipping-kpml-00 Was a Placeholder From Markup Language to Protocol Add Mid-Call Trigger Detector Model Functionally Identical to Phone Adds 3 rd -Party Trigger Requests
E N D
KPML draft-ietf-sipping-kpml-01 Eric Wm. Burger IETF 58
Changes fromdraft-burger-sipping-kpml-02 • draft-ietf-sipping-kpml-00 Was a Placeholder • From Markup Language to Protocol • Add Mid-Call Trigger Detector Model • Functionally Identical to Phone • Adds 3rd-Party Trigger Requests • SUBSCRIBE Filters, NOTIFY Reports IETF 58
Changes to <regex> • Removed href • No HTTP Reporting • Added MSCML tag Attribute to regex to Label Different Triggers in Responses • Added Inter-Digit Timer • Digit Suppression via pre attribute <regex pre="*8" pattern="XXXXXXXXXX"/> IETF 58
Addressing Stream of Interest • SUBSCRIBE on Dialog is Easy • Monitor Stream of Related INVITE-Initiated Dialog from Device • This is collecting digits from phone, e.g. • 3rd Parties Need to Address Streams Directly • Supply c and m lines from SDP • c of endpoint: Monitor from Device • c of remote UA: Monitor to Device IETF 58
Is SUBSCRIBE/NOTIFY Model OK? Is SDP Addressing OK? 3 Ways to Specify Digit Map, all Mandatory. OK? Regular Expressions J.162 (MGCP) H.248 (MEGACO) Immediate NOTIFY Response to SUBSCIBE Request KPML code 100, or Empty NOTIFY Body? Issues IETF 58