According to the RFC, the Allow-Events header is specifically used to convey
events that a UA can support using the SUBSCRIBE method. Typically we’ll see
KPML or Presence as a supported Allow-Event value, which makes sense since both
of those events are initiated through SUBSCRIBE/NOTIFY
Happy Friday!
This is probably a dumb basic question but my google-fu is failing me.
What exactly is the "telephone-event" event package used for in the
allow-events: header? Must it be present?
I have been assuming it had to do with rtp-nte but that seems wrong since
that's negotiated in the
Hi Daniel,
That was how I read it as well - i just couldn't find an explanation of
what the telephone-events package was actually for. Thanks for confirming
that the rtp-nte is negotiated fine w/o it.
The issue that prompted me to start digging into this was that calls to the
med center's help
B
Sent from my LG Mobile
Ed Leatherman wrote:
Hi Daniel,
That was how I read it as well - i just couldn't find an explanation of what
the telephone-events package was actually for. Thanks for confirming that the
rtp-nte is negotiated fine w/o it.
The issue that
Sent from my LG Mobile
Daniel Pagan wrote:
According to the RFC, the Allow-Events header is specifically used to convey
events that a UA can support using the SUBSCRIBE method. Typically we’ll see
KPML or Presence as a supported Allow-Event value, which makes sense
I use rtp-nte to SIP KPML in CUBE quite a bit actually, despite the
documentation saying it's not supported. I also use digit-drop too by the
way, because on more than one occasion I have had double DTMF issues.
E.g., dtmf-relay sip-kpml rtp-nte digit-drop
Also, unless you like using MTPs in
Hi Brian,
Thanks for the invaluable support.
regards,
Abebe
On Thu, Jul 7, 2016 at 5:20 PM, Brian Meade wrote:
> Really all the phone is trusting is the locally stored CTL on the ASA with
> just the ASA cert in there. Since you're not using TLS to CUCM (non-secure
>