69.3.1

[Vodia PBX]

We found a few things in 69.3 that we fixed in 69.3.1 plus we linked the new Android app in this build. We'll send a separate newsletter about this separately. As usual, see the release notes for what has changed.

[Scott1234]

Thanks,

FYI the AU handling for 1300 xxx xxx | 1800 xxx xxx, still not right when a domain area code is set.

Still seems to be adding the full area code Infront of the 1300/1800 number sent out to dial, which is invalid.

[Vodia PBX]

12 hours ago, Scott1234 said:

FYI the AU handling for 1300 xxx xxx | 1800 xxx xxx, still not right when a domain area code is set.

Is anyone still using area codes in Australia? Like in the US, area codes are practically redundant as every one dials 10 digits. 

[Scott1234]

12 hours ago, Vodia PBX said:

Is anyone still using area codes in Australia? Like in the US, area codes are practically redundant as every one dials 10 digits. 

Yep, its common & standard practice to dial an area code when calling between states, except for the user's local state.

A user's local state is just an 8-digit number as such, 6123-1234

An Interstate would be 10-digit, 02-6123-1234

A mobile would be 10-digit, 0441-234-567

A 1300/1800 would also be 10-digit, 1300-123-123 or 1800-123-123

A Special Rate would be 6-digit, 13-30-30

Happy to help you decode AU numbers if you need a hand with it. 

An example of how to send to trunk of the above, with the local sate being Melbourne. obviously different depending on trunk provider and what they accept with +/61 etc. 

2;o-trk1;;000;+61000;;false
3;o-trk2;;000;+61000;;false
20;o-trk1;;^([0-9]{8})@;+613*;;false
21;o-trk2;;^([0-9]{8})@;+613*;;false
22;o-trk1;;^0([0-9]{9})@|^61([0-9]{9})@;+61*;;false
23;o-trk2;;^0([0-9]{9})@|^61([0-9]{9})@;+61*;;false
24;o-trk1;;^([18,13][0-9]{9}|13[0-9]{4})@;+61*;;false
25;o-trk2;;^([18,13][0-9]{9}|13[0-9]{4})@;+61*;;false
30;-;;*;The number you have dialled is incorrect. Please check the number and dial again. Thank You.;;false

 

[Scott1234]

I replaced the Internal & External ring tone in this version to my unified tones but uploaded the wrong one when I try remove it to replace it the replacement never takes over, it will always play the previous custom tone.

Tried incognito modes, pbx reboot etc, If I remove all custom ring tone files, I can get it to default back to the OEM ringtones but when I upload again it will still be wrong, not seeing any errors generated in logs. 

Please note this is the first time I am doing this for 69 build, so might not be specific to this version in particular.   

Edit - I had deleted everything and come back a day later and added back and now ok.  ¯\_(ツ)_/¯

[Vodia PBX]

On 6/11/2024 at 9:49 AM, Vodia PBX said:

Is anyone still using area codes in Australia? Like in the US, area codes are practically redundant as every one dials 10 digits. 

Well what I was trying to say is that is there anyone still dialing local numbers without area codes... Anyhow, seems like there were two places where the PBX would not convert numbers starting with 1 into the right format on the PBX server side. We'll include that in the next build.

[RichardDCG]

On 6/17/2024 at 9:06 PM, Vodia PBX said:

is there anyone still dialing local numbers without area codes

In the Windows app I need to dial using the area code each time for the call to work.  The number below is a local Australia NSW format  91234567 - the IOS app and IP phones can dial it fine.  The Windows app adds a leading 0 and then formats it as +6191234567.  For me to call it properly I need to dial 0291234567

[Scott1234]

Yep, I can confirm as well it's not handling local numbers correctly. 

[Scott1234]

20 minutes ago, Scott1234 said:

Yep, I can confirm as well it's not handling local numbers correctly. 

It's the same number formatting that is adding the extra 0 in front of 1800/1300 numbers its buried in the number formatting java script that I deep dived on before. But can't self mod that part.