Hello. On my company we just need to use outbound calls. Can I use Shared calling? We will not have auto attendant, just a group of users who will call to users. Thanks
Hi Matt, Great uses cases and interesting feature. How can I use the Shared Calling option with SIP devices which are using the SIP Gateway? Right now I'm not able to do so, because the user needs a DID to be able to login. When having a user without a DID you'll get an error which says it's needed. Cheers, Jarno
Many times, we like to show you can do it both ways as Matt did during this session. Also understand that originally Shared Calling was PowerShell only with Teams Admin Center capability coming later on.
@@TeamsPhoneCommUnity the TAC is buggy and slow. Often times I have to refresh or load in incognito - this is proven by companies designing their own interface tapping into Graph .API. When will you improve this for paying customers or will we always have to seek a 3rd party solution to accommodate the problematic interface?
Hello. On my company we just need to use outbound calls. Can I use Shared calling? We will not have auto attendant, just a group of users who will call to users. Thanks
Hi Matt, Great uses cases and interesting feature. How can I use the Shared Calling option with SIP devices which are using the SIP Gateway? Right now I'm not able to do so, because the user needs a DID to be able to login. When having a user without a DID you'll get an error which says it's needed. Cheers, Jarno
Shared Calling with SIP devices is not supported but may be considered in the future. Today you must have a phone number.
i think its amusing he doesnt use the TAC to do alot of this...
Many times, we like to show you can do it both ways as Matt did during this session. Also understand that originally Shared Calling was PowerShell only with Teams Admin Center capability coming later on.
@@TeamsPhoneCommUnity the TAC is buggy and slow. Often times I have to refresh or load in incognito - this is proven by companies designing their own interface tapping into Graph .API. When will you improve this for paying customers or will we always have to seek a 3rd party solution to accommodate the problematic interface?