Jump to content

Scott1234

Members
  • Posts

    205
  • Joined

  • Last visited

2 Followers

About Scott1234

  • Birthday 11/20/1984

Profile Information

  • Gender
    Male
  • Location
    +61

Recent Profile Visitors

1,393 profile views

Scott1234's Achievements

Collaborator

Collaborator (7/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare

Recent Badges

0

Reputation

  1. I have seen this too and I end up deleting the old registration manually and it never comes back, sometimes its users with a new device.
  2. You might simply just need to go to, Settings -> Security -> General -> and edit "Include extension password and PIN in user welcome email" settings.
  3. I don't think mine had that issue, might be to do with the country code setup of the pbx. I will test with mine and let you know.
  4. When using the UC dial plans did you use the part to include your local extension range ? Things to consider also are if you need team's users to dial other system numbers, i.e service flags or pbx ring groups, your dial plan needs to accommodate that. Typically, if 2 users are on teams they just use teams <-> teams to call each other, not the extension digits/pbx. I find the best way to think of it is using it like as if you were pairing a mobile number to the extension, teams is really just another end device, with limited PBX functions, like a mobile.
  5. Nope, because the call is being held in the Microsoft side, just upload your custom hold music to teams.
  6. Yeah you will use, customer1.hosted.com as the domain you verify on their 365 then run the config against to add the SBC on their 365. Don't get confused reading the MS doco for wildcard setup, as that is not what is being done here, that is a whole different approach.
  7. It's whatever domain name that is being used on the PBX its self for the customer, hence the PBX manages any cert's related to it.
  8. Yeah, So pbxcustomer.domain.com has to be verified via TXT record on the customers 365, and once done then create a temporary resource account in their teams tenant under the voice menu that uses that verified domain. Then do the normal SBC / dial plan setups, and it should be good to go, with the team's trunk added on that customer's pbx domain.
  9. Can't comment on the way you are going about it. I basically just run or have the customer run the commands directly against their own tenant, nothing to do with my own. So basically, I am just adding the pbx domain/sbc to their team's instance. If you are going about the above, I would be going down the path of looking at the proper wildcard setup to see if it works but you will need a proper non let's encrypt certificate I think to maintain, otherwise not worth the effort.
  10. I think the issue here is that the PBX is not dealing with 1300/1800 correctly with the regex java script for Australia. It wants to add an area code in front of 1300 or 1800 numbers when routing it out, which is why when you set country code and area code on a domain and then try dial 1300 or 1800 numbers it won't work correctly, unless your dial plan or rates card accommodates it wanting to add an area code to that number. At the moment I don't set the area code on the domain just the country code, which works well for all numbers except for presenting 1800xxxxxx/1300xxxxxx/13xxxx and local numbers correctly formatted. Basically if you have area code and country code set on a domain and dial 1800123123 and your area code is 2 the pbx will make it 6121800123123 It needs to be fixed by Vodia, I posted about it here, What you are experiencing with the re writing is the "domain number presentation". but even if your dial plan is set to Don't Rewrite, it still seems to do it any way, especially if there is any country or area code running on the domain.
  11. You can all ways set global the domain -> settings -> voicemail and set the option "Mailbox explanation prompt" so you don't have to worry about that one.
  12. Yeah, I find I am endlessly scrolling up and down that list looking for what I want, some additional structure would be nice.
  13. I have not noticed the audio being bad, if anything I thought it more stable and works better with call kit Intergrations to interface with car audio systems etc.
  14. You need to setup the primary SBC on your MS tenant as a wildcard setup, which will also require the appropriate wildcard certificate. The customer will still need to verify the tenant domain in their instance, but it then allows you to make a voice route that points directly to the tenant.hosted-pbx.com wild card teams SBC without needing to establish and maintain a dedicated SBC in each customers MS tenant. when creating the voice route, you just link it to the wildcarded domain such as, New-CsOnlineVoiceRoute -Identity "AU" -OnlinePstnGatewayList tenant.hosted-pbx.com -NumberPattern ".*" -OnlinePstnUsages "AU" I have tested with another SBC but not tried the setup with the PBX. I posted before but I was not logged in.
×
×
  • Create New...