Solved Call Log throws System.TimeZoneNotFoundException on Firefox

[tmuncks]

This has been a problem for a while. On Firefox (any platform), accessing the Call Log while in Greenland, results in "Internal Server Error(500)":

Exception of type 'System.TimeZoneNotFoundException' was thrown.

The official timezone for Greenland (Nuuk) changed a while back from "America/Godthab" to "America/Nuuk". But while Chrome/Edge still uses the old name, Firefox uses the new one. This can be seen in calls such as:

Intl.DateTimeFormat().resolvedOptions().timeZone

This seems to be what is causing the problem.

The failing API call is:

https://<REDACTED>:5001/api/CallLog?TimeZoneName=America/Nuuk&callState=All&dateRangeType=Today&fromFilter=&fromFilterType=Any&numberOfRows=50&searchFilter=&startRow=0&toFilter=&toFilterType=Any

Changing the TimeZoneName like this, makes the query succeed:

https://<REDACTED>:5001/api/CallLog?TimeZoneName=America/Godthab&callState=All&dateRangeType=Today&fromFilter=&fromFilterType=Any&numberOfRows=50&searchFilter=&startRow=0&toFilter=&toFilterType=Any

3CX should accept the new name while keeping support for the old one, for compatibility.

How do we get this fixed? Should I report the error somewhere else?

 

[ChrisC_3CX]

Are you perhaps running 3CX v16?

I was able to reproduce this on 3CX v16 but not on 3CX v18.

 

[tmuncks]

This is on version 16, yes. I'll try on version 18 straight away, and get back to you.

 

[ChrisC_3CX]

I have tried both Godthab and Nuuk and both worked fine on 3CX v18 so I think it should be fine.

 

[tmuncks]

Just upgraded our test-site and can confirm, this is no longer a problem on version 18. Thank you for the hint @ChrisC_3CX .

 

[ChrisC_3CX]

Just glad everything's in order!

I'll be marking this as resolved then.