Fanvil X3S - no Hotdesking possible anymore

[JohnS_3CX]

Hi @weimerd

I analysed one X3S we have here in our lab, and I see the phone takes about 15 seconds to login, and the same to log out on a Cloud PBX with the new certificate after applying the Hotfix.

Captured packet 190-263 (13 seconds) Initial Provisioning

Captured packet 190-263 (13 seconds) Initial Provisioning
190    12:57:51.365044    {my X3S LAN IP}    1029    {my DNS IP}    53    DNS                    Standard query 0x0004 A my3cx.fqdn.com
263    12:58:04.614041    {my X3S LAN IP}    1030    {my cloud IP}    5001    TLSv1.2                    Encrypted Alert


Captured packet 1415-1487 (15 seconds) HD Login
1415    13:01:02.138278    {my X3S LAN IP}    1036    {my DNS IP}    53    DNS                    Standard query 0x0008 A my3cx.fqdn.com
1487    13:01:17.708810    {my X3S LAN IP}    1032    {my cloud IP}    5001    TLSv1.2                    Encrypted Alert


Captured packet 2163-2237 (15 second) HD Logout
2163    13:03:55.138056    {my X3S LAN IP}    1045    {my DNS IP}    53    DNS                    Standard query 0x000d A my3cx.fqdn.com
2237    13:04:10.719302    {my X3S LAN IP}    1034    {my cloud IP}    5001    TLSv1.2                    Encrypted Alert

...and it can actually do it under 10 seconds when its a local PBX

The delays you see are not really related to the certificates as far as I can tell. Here are some possible factors that can most certainly cause delays of variable timing, if you wish to look further into it yourself:

- Slow DNS replies
- Slow NTP replies
- Slow cloud PBX replies
- Slow network

 

[weimerd]

Hi @weimerd

I analysed one X3S we have here in our lab, and I see the phone takes about 15 seconds to login, and the same to log out on a Cloud PBX with the new certificate after applying the Hotfix.

Captured packet 190-263 (13 seconds) Initial Provisioning

Captured packet 190-263 (13 seconds) Initial Provisioning
190    12:57:51.365044    {my X3S LAN IP}    1029    {my DNS IP}    53    DNS                    Standard query 0x0004 A my3cx.fqdn.com
263    12:58:04.614041    {my X3S LAN IP}    1030    {my cloud IP}    5001    TLSv1.2                    Encrypted Alert


Captured packet 1415-1487 (15 seconds) HD Login
1415    13:01:02.138278    {my X3S LAN IP}    1036    {my DNS IP}    53    DNS                    Standard query 0x0008 A my3cx.fqdn.com
1487    13:01:17.708810    {my X3S LAN IP}    1032    {my cloud IP}    5001    TLSv1.2                    Encrypted Alert


Captured packet 2163-2237 (15 second) HD Logout
2163    13:03:55.138056    {my X3S LAN IP}    1045    {my DNS IP}    53    DNS                    Standard query 0x000d A my3cx.fqdn.com
2237    13:04:10.719302    {my X3S LAN IP}    1034    {my cloud IP}    5001    TLSv1.2                    Encrypted Alert

...and it can actually do it under 10 seconds when its a local PBX

The delays you see are not really related to the certificates as far as I can tell. Here are some possible factors that can most certainly cause delays of variable timing, if you wish to look further into it yourself:

- Slow DNS replies
- Slow NTP replies
- Slow cloud PBX replies
- Slow network

Thanks for testing. Actually we can clearly state that logon/logoff process was under 10 seconds before 1st of October. Anyway it is working. slowly, but it works. So maybe it's not worth investigating any further here.

Phones are used with an SBC. Network connection is made by 1Gbs glasfibre up and down with static IP.

 

[JohnS_3CX]

Unfortunately some things cannot always be controlled, but at least we know its not something to do with the phone or certs.

You can always investigate further if the delay is too annoying, but under 30 sec is reasonable I would say.

 

[weimerd]

Unfortunately some things cannot always be controlled, but at least we know its not something to do with the phone or certs.

You can always investigate further if the delay is too annoying, but under 30 sec is reasonable I would say.

just curious: could it be that the new v18 version on sbc is causing that slower logon logoff issue as well? Just a thought.

 

[JohnS_3CX]

Not from what I have seen, I was able to eliminate that possibility from the test results