I would try isolating the trunk for presence. Eg: put on a new Presence Group with disallow subscription. Use an empty CSS for Subscribe CSS. And also on the SIP Trunk security profile, disable "accept presence subscription".
For the DTMF, I think more likely a third party would use something other than kpml. RFC2833 should be all good and SIP Info or update probably good too. HTH Randall "da ill" Saborio CCIE Voice Wannabe #10054675811 On Tue, Jul 12, 2016 at 5:45 PM, Ed Leatherman <[email protected]> wrote: > I wonder if you could do this with a normalization script to just drop > subscribe messages? I know there is a knob in the sip trunk security > profile to have cucm not accept a subscribe, not sure about preventing it > in the outgoing direction. > > would this cause a problem with DTMF relay if CUCM needs to subscribe to > kpml from your IVR? I'm thinking of possibility of your IVR wanting to > outpulsing DTMF digits for some purpose. > > On Tue, Jul 12, 2016 at 4:24 PM, Biffle, Gerrad < > [email protected]> wrote: > >> Does anyone know if it’s possible to disable the SUBSCRIBE messages on a >> SIP trunk from my CUCM to a third party IVR system? If so, any concerns in >> doing so? >> >> >> >> Thanks for the help! >> >> ======================================================= >> Please note that email sent to and from this address is subject >> to the North Carolina Public Records Law and may be disclosed to third >> parties. >> >> _______________________________________________ >> cisco-voip mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> > > > -- > Ed Leatherman > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
