Scott1234
-
Posts
206 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Scott1234
-
-
12 hours ago, GenesisHaley said:
Integrating VODIA Cloud PBX with ZENDESK CRM is indeed possible and can offer some great benefits. It can streamline your communication processes and enhance customer support. To get started, you'll need to check if VODIA Cloud PBX offers integration with ZENDESK CRM.
¯\_(ツ)_/¯ useful
-
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.
-
10 hours ago, PCS said:
You might simply just need to go to, Settings -> Security -> General -> and edit "Include extension password and PIN in user welcome email" settings.
-
12 hours ago, RichardDCG said:
I can call from Teams to any number ok, it is returning internal calls from Teams app to non teams app (vodia desk top app). The returned call is to +xxx not xxx. I can manually dial xxx and get the Teams app fine. Ideally I would like the PBX to strip the + off inbound 3 digit number..
good point.
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.
-
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.
-
Nope, because the call is being held in the Microsoft side, just upload your custom hold music to teams.
-
16 hours ago, RichardDCG said:
@Scott1234 thanks for your help on this. I'm getting confused by this a bit.
my vodia pbx domain is hosted.com with tenants customer1.hosted.com, customer2.hosted.com, customer3.hosted.com
I want to use Teams trunks with customer1.hosted.com
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.
-
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.
-
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.
-
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.
-
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.
-
On 2/27/2024 at 12:30 PM, RichardDCG said:
where can I get a list of settings to make bulk changes? i.e. I want to do a bulk change on mailbox options, I can see Announcement mode (name_use) but nothing I enter makes any change..
I want to change Announcement mode - to name, explanation prompt to not on personal.
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.
-
9 hours ago, RichardDCG said:
Thanks, I see it now in status when I make the selection.
Any chance the options can be placed in alphabetical order? At the moment you have to read each option to get to the one you want...
Yeah, I find I am endlessly scrolling up and down that list looking for what I want, some additional structure would be nice.
-
1 hour ago, RichardDCG said:
Audio is a bit 'electric' compared to SIP phones and the Vodia app .... is this to be expected or any changes to make?
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.
-
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.
-
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 ?
-
13 minutes ago, RichardDCG said:
Some success. Seems to be some expression changes.
https://learn.microsoft.com/en-us/powershell/module/teams/set-csphonenumberassignment?view=teams-ps
I used below:
Set-CsPhoneNumberAssignment -Identity user@company.com.au -PhoneNumber XXX -PhoneNumberType DirectRouting
When I call from Teams to an ext. on the Vodia it works, but my number is presented as +XXX . When I call the ext. XXX from the Vodia it all works, Teams and Phones ring. However, returned calls are using +XXX and looks to be using the right trunk but not calling the Teams app. Is there a way to get Teams to present as XXX and not with the leading + ?
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?
-
21 minutes ago, RichardDCG said:
@Scott1234 excellent info! Mostly working, can dial out ok external and extensions ... just not back to the Teams app from the PBX yet...
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.
-
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.
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.
-
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?
-
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)?
-
Switching back the updated cfg line, makes them come back online.
dm.server.address = {get provserv2}
back to,
dm.server.address = dmtcp.yealink.com
-
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.
-
11 hours ago, Vodia PBX said:
Hmm actually not sure. There were some changes with the identification with the trunk, and that could have to do with Teams. I guess we'll find out! But I know that the net mask was causing a lot of erratic problems with Teams trunks that were set up versions ago when the associated IP addresses were a much smaller range.
It was really just the label. The settings internally were not affected so that you don't have to change anything, it will just show on the front end the other way around and hopefully now makes sense.
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
provserv2for Yealink - Find the right trunk with trunk domain match and IP
thanks
-
Added global setting
No web access after update to v68.0.37
in Web Interface
Posted
Do you have custom HTML pages for the login screen ? as 68.0.32 jQuery was updated to a new version, so your old custom pages will be referring to the old version and break like you have described.
You can only get in on your laptop because it's using cached data.. before you lose that quickly reset your welcome.htm and or user portals depending on what you have modded.