Jump to content

Scott1234

Members
  • Posts

    202
  • Joined

  • Last visited

Everything posted by Scott1234

  1. 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.
  2. 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.
  3. Nope, because the call is being held in the Microsoft side, just upload your custom hold music to teams.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Yeah, I find I am endlessly scrolling up and down that list looking for what I want, some additional structure would be nice.
  11. 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.
  12. 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.
  13. I notice when you release versions such as 68.0.36 I installed one that was build date 31st then I see there is now a build date 5th feb, can this not be documented and made public, I would like to know what changes within these build dates, so I can be aware of any anomalies and changes, or if you add items to the release notes, segment with build date markers ?
  14. They will all way's use the +, have you configured your PBX base system settings with country code and or domain you are testing on?
  15. Did you do the part where you set the teams user tel uri ? and have enabled teams on the extension feature set? Like, Set-CsPhoneNumberAssignment -Identity "blah@blah.com" -LineURI tel:500 -EnterpriseVoiceEnabled $true -HostedVoiceMail $true When you do that, it takes some time, and you have to close down the Teams app and re-open to get the changes once its finally updated.
  16. I have it working, but it's still with lots of 'gotch ya's' Try this trunk config, aadr: 52.112.0.0/14 52.120.0.0/14 analog: false ani_emergency: ani_regular: area_code: bcp: behind_nat: false cid_update: cobusy: 500 Line Unavailable code: codec_count: codec_lock: false codecs: codest: contact_hdr: sip:customerpbxdomain:5061 country_code: 61 dial_extension: ! dialplan: dir: dis: false dtmf: false dtmf_mode: earlymedia: true expires: 3600 failover: never fraction: 128 from_source: pai from_user: glob: noplus global: false hcv: hd: hf: {from} hpai: hppi: hpr: {if clip true}id{fi clip true} hrpi: {from} hru: {request-uri} ht: {request-uri} ice: false icid: identity: ignore_18x_sdp: false info_agent: false interoffice: true minimum: 10 name: Teams other_headers: outbound_proxy: sip:sip.pstnhub.microsoft.com pidflo: false prack: true prefix: redirect: false reg_account: teams reg_display: Teams reg_keep: reg_registrar: customerpbxdomain.com reg_user: teams remote_party: request_timeout: require: reregister_dns: false rfcrtp: false ring180: false rtcpxr: false rtp_begin: rtp_end: sdpreq: send_email: sip_port: spam: false stir: t38_enabled: false teams: true tel: false trusted: true type: options use_epid: false use_history: false use_sdes: use_uuid: true user_defined_hdr: wrtc_dest_name: wrtc_dest_number: Then head over and donate to this guy for being a legend and use his builder to build a power shell script to set everything up with regards to dial plans. https://www.ucdialplans.com He has a FAQ guide on how you can re-set and reverse everything so you can start over fresh, as you have already created some stuff.
  17. Is there any general tuning advise we should be aware of for system tuning with regards to the host network stack for optimal running of the PBX? with regards to SIP/RTP communication. such as the net.core , net.ipv4 settings?
  18. Can there be some logic statement in the button profile template when it builds to remove BLF that match the sip profile and move the order up to accmodate the removal. Basically, so I can have one global button template that all phones sub to for easy management and updates, but they don't have a repeating BLF of themselves on it given the first soft key is their own line/extension etc, (Yealink)?
  19. Switching back the updated cfg line, makes them come back online. dm.server.address = {get provserv2} back to, dm.server.address = dmtcp.yealink.com
  20. Thanks, ok so that sounded ok for an upgrade without danger. Now my YMCS looks like this, basically all offline expect the pbx that was not upgraded. I did sync and reboot handsets to see if any diff but same same.
  21. Great, Can you give a bit more insight on these, just curious to its creation to better understand the use case and or effects Added global setting provserv2 for Yealink Find the right trunk with trunk domain match and IP thanks
  22. Thanks, the zoho fix will be apricated by my zoho customers that log in and out of agent groups a lot. Does this teams related fix's fix being able to use teams call park? Label for night more active/inactive was wrong - Does this mean the service flag naming difference between auto attendant and call queue?
  23. FYI I think that post was before the 6.0.4 version it was the new version before the new new version ... ha ha. 6.0.4 is ok at the moment.
  24. FYI, setting the Failover behaviour 5xx and 408 only seems to still trigger with a 603, I have noticed this with other code too that are not 5x 408
×
×
  • Create New...