Fanvil X4U-V2 - showing BST on their clocks today, not GMT

[stevelup]

Hi

In the UK, over the weekend, we changed from British Summertime (UTC +01:00) to GMT (= UTC) but all our phones are still showing BST.

They've been rebooted and re-provisioned. I've tried changing the global timezone, and the timezone on indvidual users to something else and then back again, but they're all still showing one hour fast.

Any advice would be appreciated.

Thanks,

Steve

 

[RossMarlow]

I've found the same on all our deployments. There seems to be a fault in the Fanvil provisioning template which is setting the DST location to Morocco, instead of United Kingdom.

<option value="25" displaytext="GMT, London" id="36" zone="0:00">
        <item name="timezonename">UCT_000</item>
        <item name="dstenabled">2</item>
        <item name="dstoffsetminutes">60</item>
        <item name="dststartmonth">3</item>
        <item name="dststartweek">4</item>
        <item name="dststartday">0</item>
        <item name="dststarthour">2</item>
        <item name="dststartmin">00</item>
        <item name="dstendmonth">10</item>
        <item name="dstendweek">4</item>
        <item name="dstendday">0</item>
        <item name="dstendhour">2</item>
        <item name="dstendmin">00</item>
        <item name="timezonex3s">0</item>
        <item name="timezonenamex3s">UTC</item>
        <item name="locationx3s">7</item>
        <item name="dstx3s">1</item>
      </option>

locationx3s: 7 is Morocco.

locationx3s: 6 is United Kingdom.

I've edited the Fanvil provisioning template, changing locationx3s to 6 for the London timezone, and the handsets now provision with the correct DST.

Development
It seems that United Kingdom is option 7 on Fanvil X2s, but United Kingdom is option 6 on V64s, so it's inconsistent across models.
I'm not sure about X4U-V2 as I don't have any.

I've edited my Fanvil provisioning template (making it specific to UK now until an updated template is released by 3CX/Fanvil):

{IF ua=X2C,X2,X3S,X4}
<Location>7</Location>
{ELSE}
<Location>6</Location>
{ENDIF}

 

[COIT]

I've found the same on all our deployments. There seems to be a fault in the Fanvil provisioning template which is setting the DST location to Morocco, instead of United Kingdom.

<option value="25" displaytext="GMT, London" id="36" zone="0:00">
        <item name="timezonename">UCT_000</item>
        <item name="dstenabled">2</item>
        <item name="dstoffsetminutes">60</item>
        <item name="dststartmonth">3</item>
        <item name="dststartweek">4</item>
        <item name="dststartday">0</item>
        <item name="dststarthour">2</item>
        <item name="dststartmin">00</item>
        <item name="dstendmonth">10</item>
        <item name="dstendweek">4</item>
        <item name="dstendday">0</item>
        <item name="dstendhour">2</item>
        <item name="dstendmin">00</item>
        <item name="timezonex3s">0</item>
        <item name="timezonenamex3s">UTC</item>
        <item name="locationx3s">7</item>
        <item name="dstx3s">1</item>
      </option>

locationx3s: 7 is Morocco.

locationx3s: 6 is United Kingdom.

I've edited the Fanvil provisioning template, changing locationx3s to 6 for the London timezone, and the handsets now provision with the correct DST.

Development
It seems that United Kingdom is option 7 on Fanvil X2s, but United Kingdom is option 6 on V64s, so it's inconsistent across models.
I'm not sure about X4U-V2 as I don't have any.

I've edited my Fanvil provisioning template (making it specific to UK now until an updated template is released by 3CX/Fanvil):

{IF ua=X2C,X2,X3S,X4}
<Location>7</Location>
{ELSE}
<Location>6</Location>
{ENDIF}

Just to confirm this is an issue too.

We've done the same investigation as @RossMarlow and came to the same conclusions, the index is incorrect (out by 1) and setting the location to Morocco. Our phone fleet is x4u's and we running v20 hosted PBXs

Hopefully we'll get a template asap as we don't want to be recreating all the extensions.

 

[COIT]

The indexes are incorrect (out by 1) for all the GMT locations, not just UK London.

 

[stevelup]

Thanks everyone. I think I'm just going to wait for a corrected template from 3cx if the consensus is that they're likely to do this shortly?

What's the past experience of them resolving things like this?

 

[CPMM]

The same thing is happening with Fanvil V65 handsets.

 

[COIT]

I've opened a ticket with 3CX and essentially been told it's Fanvil's problem to fix.

Please note that the templates are created according to the Vendors instructions. If there is any change, then the Vendor will contact our Interop team in order to apply the changes.

I've opened a ticket with Fanvil too

Deleting existing phones to re-add with a custom template is not an option for us. The short term kludge would seem to be to set the 3CX system time to GMT Portugal which hopefully should pass <item name="locationx3s">5</item> to the phone and that it mistakenly sets the location to London. Will just have to hope that this is fixed in time for the next clock change and also remember to change all our PBXs back

 

[Peter Franks]

Yep. That's the response I got from 3CX

 

[stevelup]

Thanks everyone. Gone for the Portugal trick.

 

[Fanvil Technical Support]

Hi

Apologies for the inconvenience. You can change the location value for the London time zone to 6. I have attached the modified template, and our product manager has already synchronized the new template with 3CX.

 

[COIT]

Got a response to my Fanvil ticket this morning, confirming the above post.

3CX also responded to my ticket to say it had been escalated internally to the vendor team.

Hopefully the new template will be tested and rolled out asap.

 

[COIT]

I've taken a look at the provisioning file posted by Fanvil. Whilst it would resolve the GMT, London issue, I don't think it solves the problem for the other GMT locations as the IDs are still the same as those found in the current published provisioning template (v150003), i.e. wrong.

I've done some testing on my kluge and although the principle is correct, I made a mistake saying to set it to Portugal.

If you are prepared to configure individual phones, just set each phone (under user) to 0 Casablanca, Monrovia. As this is id 6 in the published provisioning file, it will set the phone to GMT, London as required.


If you want to do a bunch of phones at once, you can set the Office hours for your departments to '0.00 Ireland (Dublin)'. This will incorrectly set the phones to Location ID 4, which corresponds to Portugal(Lisboa,Porto,Funchal) on the phone. Whilst this is incorrect, Portugal have the same DST as the UK so the phones will show the correct time and because Ireland also have the same DST as London, so will 3CX.

And of course, all of this will have to be undone when the template is corrected, otherwise the phones will show the wrong time again.


Note all my testing is only on an X4Uv2

 

[KeithA]

Hi,
just looked at this new fanvil.ph.xml and the model definitions all have -fanvil.phhttps.ph appended to their names?

<models>
  <model ua="V62" canbesbc="true" interfaceLink="https://admin:%%PHONE_WEB_PASSWORD%%@%%PHONE_IP%%">Fanvil V62-fanvil.phhttps.ph</model>
  ...
</models>

Is that meant to be there?
Doesn't appear to do any harm just looks weird?