69.3.5

[Vodia PBX]

I wanted to point out that we have arrived at 69.3.5. There are a lot of fixes and features, it's all in the release notes. Some highlights:

• Every call now summarizes the jitter and the packet loss of the RTCP packets in the call. This is an invaluable help in troubleshooting quality issues, especially when mobile devices are involved. In the tenant, click on the call record and then there click on CQDR. The SIP packets for the call are also available, which also makes troubleshooting easier. You can still enable PCAP if you want all details of the call. 
• The queue management in the user front end now contains also a mode where you can overlay weeks and days, e.g. to better determine staffing hours. We have also increased the duration for keeping records for this without totally overloading the PBX. If you upgrade from an older version, the history might be a little short. 
• The PBX now also involves an adaptive jitter buffer that is by default enabled only for the mobile devices. This is helping a lot to improve audio quality in difficult environments. 
• You can now enable or disable every feature on the user front end from the admin level. For example, if you don't want to play the hangup tone, you can do this from the administrator now. 
• We have added checking of call forward numbers, so that users don't accidentally forward to a number that does not exist and cause a lot of confusion. 
• We have optimized the registration performance for most popular VoIP phones, so that you can now have several thousand registrations in a single tenant. This further improves the economies of scale for running the PBX in multi-tenant environments.

[RichardDCG]

1 hour ago, Vodia PBX said:

it's all in the release notes. Some highlights

69.3.5 not in there yet?

[anton]

Should be live now

https://doc.vodia.com/docs/releasenotes690#6935

[RichardDCG]

at what point will the leading 0 be removed from being added to the outbound calls on Au numbers?  i.e. I dial 8888 7777 the app dials 08 888 7777, 1300 xxx xxx as 01300 xxx xxx.  Anything that has a leading 0 already is fine - mobile and national calls.

 

A desk phone (HTek 903) dials the local number ok 8888 7777 but adds a 0 to a 1300 xxx xxx

[Scott1234]

5 hours ago, RichardDCG said:

at what point will the leading 0 be removed from being added to the outbound calls on Au numbers?  i.e. I dial 8888 7777 the app dials 08 888 7777, 1300 xxx xxx as 01300 xxx xxx.  Anything that has a leading 0 already is fine - mobile and national calls.

 

A desk phone (HTek 903) dials the local number ok 8888 7777 but adds a 0 to a 1300 xxx xxx

Yep please fix.

[Matevz]

Couple of more things I am still waiting to be fixed in Windows app (hence still not upgrading customers to latest version):

- call hangup in Windows App - when remote party hangs up, windows app will continue flashing until you actually press X to hangup the call

- DTMF - keyboard should be able to be used to enter DTMF, using mouse is painful and it often doesn't transmit correct DTMF tone and remote side will get wrong input (like when entering long DTMF code) This works 

- History tab has wrong date format on search filter; using American Date format, while on Date separation lines it is showing correct one. It will also keep on auto filtering to wrong date and quite often needs blanking dates out

- Got new issue with Queue Management in app, was working OK on previous version and for 1 week on current, but today it is not showing any stats under overview; History and Graphs seem to be OK. Same in web and desktop client

 

would log a case, but not getting any success or response via support portal