Re: [cisco-voip] Microsoft Graph/OAuth 2.0

2019-10-02 Thread Benjamin Turner
Dang!! This is right around the corner. Thanks, Ben From: Brian Meade Sent: Wednesday, October 2, 2019 1:24:46 PM To: Benjamin Turner Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Microsoft Graph/OAuth 2.0 Unity Connection still just supports

Re: [cisco-voip] Microsoft Graph/OAuth 2.0

2019-10-02 Thread Brian Meade
Unity Connection still just supports EWS. Microsoft Graph is on the roadmap last I heard. On Wed, Oct 2, 2019 at 10:41 AM Benjamin Turner wrote: > Has anyone found any documentation from Cisco regarding Microsoft > Graph/OAuth 2.0 and Unity authentication for 365 customers? Seems that EWS >

Re: [cisco-voip] Separate cluster for third party SIP clients with SIP/ICT trunk to production

2019-10-02 Thread Pawlowski, Adam
Ah, so we have some internal VLANs that dispense only private address space, which can be used for printers and dummy devices. The fight with that in the past, was that we did not have the internet call proxy available with Expressway, so third party video systems couldn’t do anything video

[cisco-voip] Microsoft Graph/OAuth 2.0

2019-10-02 Thread Benjamin Turner
Has anyone found any documentation from Cisco regarding Microsoft Graph/OAuth 2.0 and Unity authentication for 365 customers? Seems that EWS will not be supported. Thanks, Ben ___ cisco-voip mailing list cisco-voip@puck.nether.net

Re: [cisco-voip] Separate cluster for third party SIP clients with SIP/ICT trunk to production

2019-10-02 Thread Lelio Fulgenzi
Not hijacking at all… very good points. I was thinking about the HA availability (HAA?) on these third party SIP devices as well. From what I recall, they only have one spot to enter the registrar. I too, would think about the Expressway as the registrar – but I have much less experience with

Re: [cisco-voip] Separate cluster for third party SIP clients with SIP/ICT trunk to production

2019-10-02 Thread Anthony Holloway
Actually I don't know that it doesn't exist, I was just saying I had not heard of it before. I am curious if it is, and no one has addressed it yet. Also, I realize I have a type on this line: *National Pattern strips + prefixes *#*02 and routes to SIP trunk (*#*1301212) * It should

Re: [cisco-voip] Separate cluster for third party SIP clients with SIP/ICT trunk to production

2019-10-02 Thread Lelio Fulgenzi
Thanks for this great information Anthony. Back to work after a few days off… As for my harping on the CSS mapping feature, you know, it could have just been me making that up in my mind. Although, when I think of it, it could be a PBX feature that exists (ROLM -> HICOM) over digital trunks