windows client keeps disconnecting

Status
Not open for further replies.

Leon Zetekoff

Free User
Joined
Jan 21, 2017
Messages
172
Reaction score
12
as requested by @nick I've disabled pc AVG and we'll see if it still disconnects.
 
as requested by @NickD_3CX i've disabled AVG to verify it's not the issue. will report back results.
 
ok it happened again and I think I figured out whats happening. Everytime a device seems to register the windows client disconnects and pops up that message.

It happened when I moved my GXP-2170 to 3cx but now it shows up twice, how can that be?
Also, if I try to add it's MAC in it rejects it.

upload_2018-7-1_9-51-49.png

upload_2018-7-1_9-50-16.png
 
now we're back to one 2170 and the client disconnected

upload_2018-7-1_9-58-11.png
 
Something is most likely dropping the TCP connection between the 3CX Client and the Server.

May I suggest you also try the WebClient? For CTI it is also perfect. It would be interesting to see if that also has the problem.
Also it is worth noting that we haven't tested hosting on Vultr. That is not to say that it won't work, just that it's not been tested so it can;t be ruled out. Have you tried connecting to a e.g. a Google VM to check if you have the same problem?
A free one can be created here: https://www.3cx.com/phone-system/download-phone-system/
 
Hi there...the whotba le purpose is to not have a browser running phone stuff. no I haven't used a google VM. as i said it seems when the registration changes the windows client drops. my connection from the physical phones do not drop.

thanks leon
 
I'll checkout the web client to validate the test thanks
 
the web client stayed connected when the windows client dropped
 
i watched as my test GS WP800 phone reconnected and the windows client disconnected. Web client is stable.
 
CTI functionality is slowly moving away from the 3CX Client apps, so I would suggest getting used to the WebClient for this function.

Besides this though, on the issue. I have a feeling that you have manually configured your GXP2170 and have not used the provisioning method outlined here. This could be one reason. This is because when the phone shows up twice, the PBX sees the single device 2 times because the phone decided to re-register with a new Call-ID. Then when the old Call-ID expires, the client disconnects, causing this problem.

Also, I believe the WP800 phone is not supported, and because it is registered against the same extension, this could also be factoring into the issue. So remove it or register it against a different extension.

Furthermore, the GXP2170 I believe is using a newer firmware than what is supported. Check the previous link I sent to see the supported firmware version.

Finally, my advice would be to stick with the WebClient for CTI. If you do all of the above, and with a fully supported setup you still have issues, then I would suggest opening a ticket with the 3CX Support Department to further investigate this.
 
gm @NickD_3CX

Happy 4th!

I originally manually configured the 2170 then as was reported earlier I started to try the provisioning method. Either way the BLF shows up on the display, but does not work. I remember this happening the same way over a year ago when we tested this, we could never get BLF working. (that was on older firmware than what is running now)

I am a beta tester for Grandstream, so I am always on the cutting edge. The WP800 is a new WiFi cordless we are currently testing. We are also making sure extensions can have multiple devices connected as we are currently using freepbx.

The multiple devices on an extension work fine, again so far except for the BLF.

regarding the firmware, I suggest that the recommended firmware be a MINIMUM not a requirement. New firmwares come out for one reason or another and I don't think you guys will be able to keep up? Especially if some of these releases are related to security fixes too. food for thought.

WHat I can try and do is factory reset the 2170 and see what happens. I am potentially headed back to philly later today so I may not get to it till i get back in two weeks. If by some chance I stick around to this weekend here, I can give it a shot.

Ok on the web client. why are things moving to web-based?

thanks leon
 
Update: I factory reset the 2170 and after a few reprovisions/reboots it is working now (BLF). What I'd like to know is why when manually provisioned, it didn't work? Thanks
upload_2018-7-4_16-30-17.png
 
If I had to guess, because the provisioning template passes more information onto the phone that what you do manually. There is a reason why we have a dedicated team working constantly on templates and why we always recommend provisioning with them and not manually.

Anyhow, how is the issue with the CTI with the Client. Is that also OK now? If not, I would also suggest downgrading the firmware to what 3CX suggests.

regarding the firmware, I suggest that the recommended firmware be a MINIMUM not a requirement. New firmwares come out for one reason or another and I don't think you guys will be able to keep up? Especially if some of these releases are related to security fixes too. food for thought.
About this, I strongly disagree. Each template is tested with a specific firmware version. So yes, theoretically newer firmwares are better, but you don't always know what other things have changed and how they will affect provisioning with the template. Stick with the firmware 3CX suggests, because even if they do have things that have been improved, the existing functionality in that firmware should still be fine.
 
take 2 - my laptop restarted :)

BLF worked on other PBXes without strain. The key is when I reconfigure my 2170 manually as I need multiple SIP accounts since I have accounts on at least three PBXes. Getting BLF to work there will be key.

ok on the folks doing template updates. good to hear.

i am a GS beta tester on multiple devices so I run the latest. the 2170 is working ok now.

If I push a provision out from the pbx is the phone always going to ask the end user to respond to the user/pwd prompt? If so that is a potential problem as pushing out a provision is a network thing and end users shouldn't have to know when that's happening or respond to login prompts. Thoughts?

thanks leon
 
As GS beta tester, I understand that you want and must test how multiple accounts work. We as 3CX however only test 1 account, provisioned as per this guide. That is the scope we have decided and it is the same for all phones (except DECT devices of course).

If you are referring to the following prompt
uzn5Ai7Cu6FDDTnLKxd3QlHiRqhPOettTTwiBxkdSueYLtC68_k6N8NfugFFgb1k6BFS9PiDGbXCQkraqSuzcCDJOPNeBabXvQfjzES6RoeQZcPxOnAsnJlNBLeddr8e_A

then this is expected when a phone is configured as a STUN extension (it uses an RPS Server). We feel that entering the Extension Number and the VMail PIN is easy enough for end users to do for "drop-ship" deployments, but you can always pre-configure the phones.
Note: the phones won't show the prompt if already configured once as STUN using RPS and using the template provisioning.
 
hi @NickD_3CX GM....correct. I believe someone has in the Ideas section to allow multiple accounts. I will second that there. Why are DECT phones different?

GS told me last night that with some of their testing, to make sure "Use Actual Ephemeral Port in Contact with TCP/TLS" is ON. I noticed that in the config you pushed to the phone, it is on.

For the pbx I am deploying, this will be fine since the BLF works and users can answer other ringing extensions.

on the user/pass...ok that works. Yes these are all RPS since the pbx is in the cloud. Ok on the prompt not happening after the first configure. I prefer to preconfigure the device here and not have to deal with a remote device in the UK for a first provision :-)

Thanks for the explanation.

Feel free to reach out if you need someone to test some of these.

Leon
 
FYI GS release 1.0.9.102 as GA and it seems to be working a-ok. Will report back more as I use it over the weekend.
 
FYI GS just released new templates this evening; 3CX_Templates_v2.2_V15.5.zip
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,886
Messages
589,559
Members
164,748
Latest member
cmedina