[cisco-voip] CUCM Interop with MS Teams

[UC Penguin]

Question for those that have this interop working.  I want to forward calls to MS Teams directly to voicemail, without ringing the Teams client.

This appears to be possible from the MS docs as listed below. However they don’t provide an example SIP message for this.

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.

Ironically this was trivial with a LUA script on the UCM trunk however that isn’t passed though the SBC. 

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.

Thanks in advance.

All MS has to say on the topic:

If you want to send the call directly to voicemail, attach opaque=app:voicemail to the Request URI header. For example, "sip:user at yourdomain.com;opaque=app:voicemail". In this case, the Teams user will not receive the calling notification, the call will be connected to the voicemail of the user directly.

> On Apr 8, 2020, at 20:45, Kent Roberts <kent at fredf.org> wrote:
> 
> I’d like to see a working config as well   
> 
> 
> Kent
> 
>> On Apr 8, 2020, at 16:06, Carlos G Mendioroz via cisco-voip <cisco-voip at puck.nether.net> wrote:
>> 
>> Oh, I've got to the point that SIP options do flow, and even INVITEs but
>> blow up on answer. (i.e past the cert thingy)
>> 
>> Had to fix ips -> names via profiles, but was fighting with SRTP -> RTP
>> issues. TLS does make (for me) the troubleshooting more convoluted.
>> 
>> Would love to see a working config :) I was trying to have CUBE doing
>> CME too for a small office integration with Teams.
>> 
>> -Carlos
>> 
>> 
>> Brian Meade @ 08/04/2020 18:52 -0300 dixit:
>>> It should be pretty similar to most SIP CUBE configurations.  The main
>>> difference is you'll need to do Mutual TLS SIP with Microsoft so you'll
>>> need a public certificate on the CUBE that the SIP-UA can use.  You also
>>> need a public IP on the CUBE and corresponding DNS records that
>>> Microsoft side can reference.
>>> 
>>> I don't have a sanitized config I can share.  How far have you gotten
>>> with your configuration?
>>> 
>>> On Wed, Apr 8, 2020 at 11:25 AM Carlos G Mendioroz <tron at acm.org
>>> <mailto:tron at acm.org>> wrote:
>>> 
>>>   Brian,
>>>   would you care to comment "the right configuration" part of this ?
>>>   I've tried to setup it and failed misserably :(
>>> 
>>>   TIA,
>>>   -Carlos
>>> 
>>>   Brian Meade @ 24/03/2020 20:27 -0300 dixit:
>>>> Cisco CUBE can be used for this as well.
>>>> 
>>>> Official documentation should be coming in the near future but you can
>>>> do it now with the right configuration.
>>>> 
>>>> On Tue, Mar 24, 2020 at 6:07 PM UC Penguin <gentoo at ucpenguin.com
>>>   <mailto:gentoo at ucpenguin.com>
>>>> <mailto:gentoo at ucpenguin.com <mailto:gentoo at ucpenguin.com>>> wrote:
>>>> 
>>>>     Does anyone have an experience with setting up interop between
>>>>     CUCM/Microsoft Teams with Direct Routing?
>>>> 
>>>>     If so what (supported) SBC did you use and what if any issues did
>>>>     you encounter?
>>>> 
>>>>     Thanks!
>>>>     _______________________________________________
>>>>     cisco-voip mailing list
>>>>     cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>>>   <mailto:cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>>
>>>>     https://puck.nether.net/mailman/listinfo/cisco-voip
>>>> 
>>>> 
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>> 
>>> 
>>>   -- 
>>>   Carlos G Mendioroz  <tron at acm.org <mailto:tron at acm.org>>
>>> 
>> 
>> -- 
>> Carlos G Mendioroz  <tron at huapi.ba.ar>  LW7 EQI  Argentina
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200616/d691314e/attachment.htm>