User Profile
Korbyn
Brass Contributor
Joined Oct 02, 2017
User Widgets
Recent Discussions
Re: Teams Auto Attendant - Dial by Extension transfer to Resource Accounts
TrackingID#2406070010003116 Apparently this hasn't been on their radar and they're now working on a global fix to have resolved by the middle or end of June, but I'm sure you can reference the above number to get more immediate intervention. Good Luck. Fastest resolution I've ever had.2.1KViews1like1CommentRe: Teams Auto Attendant - Dial by Extension transfer to Resource Accounts
Rhony_F put in a ticket to MS Support through the admin page. It's a setting in the tenant that the product group can switch back for you. Takes 45-60 mins to kick in. I suspect when enough people call in they'll fix/reverse what they did. I've got more tenant customers for them to reverse.2.3KViews0likes3CommentsRe: Teams Auto Attendant - Dial by Extension transfer to Resource Accounts
Wow. MS Support worked quickly today. The Support Engineer connected with the Product Group and reversed a change on my clients Tenant and ~45 mins later, they were working again. I don't know when change, but I strongly suspect it was related to MC785026. My engineer is gone for the weekend, but if I can get more details to help anyone else speed their recovery along, I will post here again.2.4KViews0likes5CommentsRe: Teams Auto Attendant - Dial by Extension transfer to Resource Accounts
I know it's correct, it's been working for more than 2 years. I'm also checking to see if the Dial by Name works for resource accounts, something I've never tested before, but because the First Name and Last Name haven't been populated till now/today, I'll have to wait the 1-36 hours for that to potentially kick in. Any word back on the MS support ticket, or are you getting the 6 degrees of runaround?2.5KViews0likes7CommentsTeams Auto Attendant - Dial by Extension transfer to Resource Accounts
For the past couple of years, we have been able to populate the Business Phone field of the licensed Resource Account used for auto attendants or call queues, with an extension. Some are the full e.164 +17805551000;ext=1234 or just x1234, and to be clear, this is just in the Business Phone field in Entra, nothing to do with the LineURI. Up until this week, calling into an AA with Dial by Extension, and entering in the extension assigned a resource account, the transfer has worked. Out client can't have been the only one who have used this feature. Anyone else using this and suddenly it's not working?3.4KViews1like13CommentsRe: Does Teams support multiple phone calls at once for an Admin/Receptionist?
I think I want to attempt to clarify the question. Can a user handle more than 2 calls, 3 or more, or is a user limited to 2 lines? I'm reasonable certain if you need to handle 3 or more calls and you to switch to using Call Queues.4.4KViews0likes1CommentRe: Skype for Business messaging skype user due to 'company policy'
wroot The trick to resolving this issue is making sure your own edge server(s) can resolve your own _sipfederationtls._tcp.domain.com SRV record, which is necessary for your Edge to Federate with another edge for MTLS. In other words, your Edge server must be able to correctly resolved its own SRV record, plus the SRV record of the other sip domain you wish to federate with. Nslookup is your friend. People do funny things with DNS settings on Edge servers, sometimes pointing to internal for resolution, which means you need to add the Federation SRV to your internal DNS. You might also be finding in your Skype4b Monitoring Reports Diagnostic ID warnings for 1008, and in the report Detail find the following: 1008; reason="Unable to resolve DNS SRV record"; domain="yourdomain.com"; dns-srv-result="NegativeResult"; dns-source="InternalCache"; source="sip.yourdomain.com"18KViews0likes0CommentsRe: Calls from Polycom VVX phones to call queue dropped after 30 seconds when picked up by Teams client
Ryan Steele Any chance that the sites you're experiencing the issue with are using Palo Alto firewalls? We narrowed the issue down to the firewall as the same phone off their network works perfectly fine. Narrowing down the NAT to a 1-to-1 also resolved, but not tenable for hundreds of phones, so something is up with the pool of IP's being used for proxying to the internet. The client has engaged with the Palo to find a resolution. Renewing the mantra, "Its the network"...9.4KViews0likes5CommentsRe: Calls from Polycom VVX phones to call queue dropped after 30 seconds when picked up by Teams client
Ryan Steele Any luck? I have a customer that calls drop but only with their VVX311's, all other models are fine. Your issue with Teams and VVX phones sounds similar. Seems that all the 5.9.x firmwares fail, but "some" are stable on 5.8... hard to narrow down Teams/VVX support stability.9.5KViews0likes8CommentsRe: iOS 11 Compatibility
I only had to increase on the reverse proxy servers, IIS ARR in our cases. Kemps are usually at 20 mins, or should have been already, but they're a little more hard core, so you may need to make sure the firmware is up to date on the Kemp's. Could also try bumping to 30 mins. Are there any other firewalls in that path, before or after the Kemp? I also use IIS Crypto from Nartec as well to clean up the Cipher's and disable SSL 2.0 and 3.0, which may also be a combined effect with increasing the timeout to 1800s or more. Every time Apple comes up with a new iOS, they find fantastic new ways of mucking up encryption.3.4KViews0likes0CommentsRe: iOS 11 Compatibility
I may have found a possible solution, hopefully the rest of you can test and verify. The clients IIS ARR server was set to a timeout of 960 (16 mins) for some reason, I always prefer as setting of 1200 or higher. Since changing to 3600 from 960, the iOS 11.0.1 based Skype Mobility client isn't getting signed out after 10 mins, and blocked from signing in again. Some blog articles use a 200 sec setting or even 300, which with Skype connections, is never good. 20 mins or higher, including HTTP traffic, is I think always the minimum. Some weird firewalls its actually needs to be 45 min for odd reasons. Our corporate environment was already set to 30 mins, which is why I believe those users didn't have issues. Please let me know what you find and if changing it to 1800 resolves or not.3.7KViews0likes3Comments
Recent Blog Articles
No content to show