Skype for Business on Prem using teams auto attendant - Call flow?
I am trying to understand the call flow when a Skype for Business implementation (all on prem) uses a teams auto attendant. This is what I know auto attendant number = +1-555-555-1234 555-555-1234 routed from PSTN across SIP trunk to on prem Skype for business Skype for Business sends the call to teams over the internet to connect with an auto attendant. Auto attendant plays a call tree recording and disconnects User can press DTMF selection to be "sent" to a number on premises. This is where I get confused... The call flow is configured to use "user in organization" that is essentially another number that is routed over our SIP trunk. Does Teams proxy a call that comes back over the SIP trunk to terminate in a call queue in Skype for Business on Prem? There is no known integration configured between teams and skype for business.
Delay with rings after another user answers a call
We have a long standing issue we are currently working with Microsoft on but it does not appear like they have been much help with this. I figured I'd see if anyone else is experiencing this issue as well. I have an incoming number routing to an auto attendant, then to a call queue then to 5-10 users in my Cloud S4B system. The Cloud PBX system has about 6 call queues doing this function. If someone, in the call queue, picks up the phone it may continue ringing other users in that call queue even though someone answered that call. We have updated to the latest Office 365 on every computer and we are using Jabra headsets or Polycom phones using BTOE connections to Skype for business. Again, all software and firmware is up to date at these locations experiencing the issue. I've recreated the auto attendants and call queues with no changes. I have put in optimizing for Skype for business using the the suggested IP addresses to whitelist in the firewall (https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges?redirectSourcePath=%252farticle%252f8548a211-3fe7-47cb-abb1-355ea5aa88a2) Has anyone else ran into this issue or have any suggestions on what i could try next?