@dafyre said in Windows 10 PC's not renewing DHCP lease:
Your DHCP range isn't close to being full, is it?
Its a remote office, with basically only 5 PC's, the phones and a couple of printers. The range has a lot of free ips still.
@Dashrender said in Windows 10 PC's not renewing DHCP lease:
Try updating the firmware on the phone as well.
But hopefully the logs will tell you something.
How long is your lease on DHCP?
Changed the lease to 24 hours, before todays morning report.
So the issue is with two Windows 10 machines that are apparently not renewing their DHCP leases and are just letting them expire. They end up being completely offline when users find them the next day and the users have been rebooting them to get the network working again. Network drivers have been updated on both machines and they just reported the issue keeps happening. Both machines are connecting to the network, via the integrated switch of a Yealink t42s, not sure if this could be part of what is causing the issue but I thought it was worth mentioning. Phones are not having any issue at all and they are also set for DHCP.
This is what has been done so far:
-Power management set for max performance and machines done go to sleep.
II will dig into the logs later today, so truly check if they are really just letting the leases expire since I originally thought it would be driver related. Any other idea what could be happening?
Wouldn't you just either keep an image with only the stuff you require and deploy that or just use config management to get the default minimal install to you what you require as well?
@rcuadra Is there a time frame of when the endpoint manager will be working with PJSIP extensions?
I am not doing it 
, I am not the OP.
@JaredBusch Quoted the wrong post?
I didn't express an opinion regarding if this was good or not, just said Vital allowed it =).
@JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.
@JasGot Are you using the autogenerated password? Have you tried setting a different one and using that?
Also worth checking is the device for the extension set as SIP and not PJSIP?
It appears that currently, endpoint manager is only working for SIP extensions and not PJSIP. When trying to test it, I can't add PJSIP extensions on the device mapping but SIP have no issues.
@JaredBusch said in Extensions not registering:
Fully updated FreePBX and zero issues. I use pretty much only use pjsip.
This is VitalPBX, its super weird still. I didn't really touch anything on the extensions.
@Dashrender said in Extensions not registering:
Were updates ran on the PBX recently?
Yes, the previous night
@scottalanmiller I had rebooted already, recreated extensions as pjsip as well no registering. Changed the port to something else other than 5060 and still nothing.
Recreated the extension as sip and they registered. So for now they are sip extensions.
@JaredBusch No passwords where changed they where registering properly yesterday.
Even with that I tried a couple extension and copied over the password again and still no luck
This is the error I am seeing:
[2019-07-10 00:11:54] NOTICE[8195] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '"USER" <sip:[email protected]>' failed for 'xxx.xxx.xxx.xxx:1027' (callid: [email protected]) - No matching endpoint found
[2019-07-10 00:11:54] NOTICE[8195] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '"USER" <sip:[email protected]>' failed for 'xxx.xxx.xxx.xxx:1027' (callid: [email protected]) - Failed to authenticate
This is actually happening for existing endpoints, in this case extension 301 is in the system as a PJSIP extension, password is correct as this was working properly yesterday.
From what I have found online, it would seem that I was trying to use the wrong channel driver, sip vs pjsip but the extensions are indeed pjsip. The system has pjsip as port 5060. No idea why this is happening.
Any idea about this?
@Curtis check:
tail -n 500 /var/log/cron.log
or
journalctl | grep CROND
They would be expecting a POST request with the login details in the message body.
There really shouldn't be a way to login to those sites via a GET request, login parameters in the URL is not good really.
Does someone have any idea on why this pbdirectory extension is apparently keeping a channel open? Here is the channel detail
Channel: PJSIP/Twilio-000003c5/AGI Up 00:57:30
Exten: pbdirectory CLCID: "" <>
This same issue is happening today once again, VPN is connecting properly but I can't properly reach anything properly on the local lan or the internet.
@JaredBusch said in ZeroTier vs VPN:
@Romo said in ZeroTier vs VPN:
Remote users wanting to RDP into
- Main Server (this will really be the main place to connect)
This is a windows server correct?
Then you need RDS licensing for this no matter what, even to remote into it from in the office. The only reason to use ZeroTier is simply to not expose RDS to the public internet.
Licensing is already set as that is what they have been using internally as well for the users that need to RDP into the server.
From what he told me today, externally he really only wants access for himself to connect to the server as the admin, apparently, he is his own IT.
- Accounting user's pc
- Owner's pc
ZeroTier on these devices is a very typical use case.
He just mentioned a couple of more users but all of them will be only RDP into their own machine as well. Guess zerotier will serve him well without the need to acquire a new router for now.