ContributionsMost RecentMost LikesSolutions"Call Me" number calling from international number first This is an issue that one of our users had noticed, and I wanted to ask some questions to verify if this was a temporary platform issue (not listed in the status site) or if there may be something I'm missing with configurations. One of our users had been using the "Call me" feature for some time now with meetings, as have a number of users. Despite not making any changes, they had noticed that around the beginning of the month, when they try the "Call me" feature, instead of dialing in from a US number, they are getting a call from a European number, and they are unable to join due to the system not recognizing pressing the pound key. When he hangs up and tries again, he gets a US number on the second attempt every time, and is successfully able to get into the meeting. I had verified his settings, and had moved him to the new interface, and verified he had set his "Call me" to US (Admin Center has all available countries checked, since we have users in many countries). After doing so, he had reported that meetings he had started worked with the "Call me" setting fine, but meetings started by others were still having the same issue. No other users in our organization have reported this issue. -Are the "Call me" settings based on the individual user or are they set based on the meeting organizer's settings? All users have all countries available and US is set as the region by default for most users, so the US numbers should be available regardless for the user, but if it's only set based on the organizer, there may be some 'defaults' that are conflicting which would not be resolvable on our end. -Does GTM use numbers from other countries when there are no US numbers available? I know that there have been load issues with GTM lately, so if this is the case, that would explain the recent issue and the somewhat inconsistent nature of the issue, and hopefully this has since been resolved or has/will become less of an issue. -Is there a setting elsewhere that may be causing this to occur? To my knowledge the only area to change this setting is in the web sign-in settings menu where you can set the "Call me" countries, which I have verified is set correctly for them. If there is another setting in the client program or elsewhere that may be affecting this feature, please let me know. Thanks in advance. SolvedRe: Expired recording links? I'm assuming that at some point within the last couple months, a change was made that limits all future recordings to only share by default for 7 days, after which the user will have to reactivate sharing or manually set a longer expiration date for each recording they share. I'm not sure if this change was announced or if there was a notification anywhere about it, but my team had not been aware of it until recently, when I had noticed that recent recording links were suddenly breaking and users were needing to reshare their recordings in order to allow other users to access them. I have two questions regarding this feature: -Is there a way to disable the automatic link expiration? Having the option to set a default expiration date is a good security feature, but for our usecase, we would prefer a method to opt-out if at all possible, since we rely on having long-term access to recordings among our team for several weeks and occasionally months at a time. Older recordings that were shared prior to the change (I have one as late as December 10, 2019) currently do not have an expiration date (see the screenshot below), so I know not having an expiration date set is supportable, but I was unable to find a way to disable the expiration date, either from a user-perspective or from the Admin center. -If it is not possible to disable the expiration date, is it possible to change the default date of expiration? We would like to be able to have it so that instead of expiring 7 days from the time it is shared, it can expire 30 or 60 days from the time it is shared. This would be a great compromise solution, as it would still provide added security without disrupting the current workflow. Thanks in advance.