<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Question for those that have this interop working. I want to forward calls to MS Teams directly to voicemail, without ringing the Teams client.</div><div dir="ltr"><br></div><div dir="ltr">This appears to be possible from the MS docs as listed below. However they don’t provide an example SIP message for this.</div><div dir="ltr"><br></div><div dir="ltr">I’ve tried adding this as an option with the Ribbon SBC. However I’m clearly doing it incorrectly as it’s not added for the first couple message in to To field.</div><div dir="ltr"><br></div><div dir="ltr">Ironically this was trivial with a LUA script on the UCM trunk however that isn’t passed though the SBC. </div><div dir="ltr"><br></div><div dir="ltr">Which leads to the next question of how are you handing diversions to voicemail? Particularly in the use case that you want to ring UCM controlled endpoints, RMA devices & the Teams client then immediately divert to Teams VM on no answer.</div><div dir="ltr"><br></div><div dir="ltr">Thanks in advance.</div><div dir="ltr"><br></div><div dir="ltr">All MS has to say on the topic:</div><div dir="ltr"><br></div><div dir="ltr"><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">If you want to send the call directly to </span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">voicemail</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">, attach </span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">opaque</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">=</span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">app</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">:</span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">voicemail</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);"> to the Request URI header. For example, "sip:user@yourdomain.com;</span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">opaque</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">=</span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">app</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">:</span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">voicemail</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);">". In this case, the </span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">Teams</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);"> user will not receive the calling notification, the call will be connected to the </span><b style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);">voicemail</b><span style="caret-color: rgb(60, 64, 67); color: rgb(60, 64, 67); font-family: Roboto, HelveticaNeue, Arial, sans-serif; font-size: 18px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0); background-color: rgb(255, 255, 255);"> of the user directly.</span></div><div dir="ltr"><br><blockquote type="cite">On Apr 8, 2020, at 20:45, Kent Roberts <kent@fredf.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>I’d like to see a working config as well </span><br><span></span><br><span></span><br><span>Kent</span><br><span></span><br><blockquote type="cite"><span>On Apr 8, 2020, at 16:06, Carlos G Mendioroz via cisco-voip <cisco-voip@puck.nether.net> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Oh, I've got to the point that SIP options do flow, and even INVITEs but</span><br></blockquote><blockquote type="cite"><span>blow up on answer. (i.e past the cert thingy)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Had to fix ips -> names via profiles, but was fighting with SRTP -> RTP</span><br></blockquote><blockquote type="cite"><span>issues. TLS does make (for me) the troubleshooting more convoluted.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Would love to see a working config :) I was trying to have CUBE doing</span><br></blockquote><blockquote type="cite"><span>CME too for a small office integration with Teams.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>-Carlos</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Brian Meade @ 08/04/2020 18:52 -0300 dixit:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>It should be pretty similar to most SIP CUBE configurations. The main</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>difference is you'll need to do Mutual TLS SIP with Microsoft so you'll</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>need a public certificate on the CUBE that the SIP-UA can use. You also</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>need a public IP on the CUBE and corresponding DNS records that</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Microsoft side can reference.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I don't have a sanitized config I can share. How far have you gotten</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>with your configuration?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Wed, Apr 8, 2020 at 11:25 AM Carlos G Mendioroz <tron@acm.org</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><mailto:tron@acm.org>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> Brian,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> would you care to comment "the right configuration" part of this ?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> I've tried to setup it and failed misserably :(</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> TIA,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> -Carlos</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> Brian Meade @ 24/03/2020 20:27 -0300 dixit:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Cisco CUBE can be used for this as well.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Official documentation should be coming in the near future but you can</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>do it now with the right configuration.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>On Tue, Mar 24, 2020 at 6:07 PM UC Penguin <gentoo@ucpenguin.com</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> <mailto:gentoo@ucpenguin.com></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span><mailto:gentoo@ucpenguin.com <mailto:gentoo@ucpenguin.com>>> wrote:</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> Does anyone have an experience with setting up interop between</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> CUCM/Microsoft Teams with Direct Routing?</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> If so what (supported) SBC did you use and what if any issues did</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> you encounter?</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> Thanks!</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> _______________________________________________</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> cisco-voip mailing list</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> <mailto:cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> https://puck.nether.net/mailman/listinfo/cisco-voip</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>cisco-voip mailing list</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>https://puck.nether.net/mailman/listinfo/cisco-voip</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> -- </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> Carlos G Mendioroz <tron@acm.org <mailto:tron@acm.org>></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>-- </span><br></blockquote><blockquote type="cite"><span>Carlos G Mendioroz <tron@huapi.ba.ar> LW7 EQI Argentina</span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>cisco-voip mailing list</span><br></blockquote><blockquote type="cite"><span>cisco-voip@puck.nether.net</span><br></blockquote><blockquote type="cite"><span>https://puck.nether.net/mailman/listinfo/cisco-voip</span><br></blockquote><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span>cisco-voip@puck.nether.net</span><br><span>https://puck.nether.net/mailman/listinfo/cisco-voip</span><br></div></blockquote></body></html>