Doesn’t look like that is correct.
The SIP Notify message that FPBX sends from EPM says “Reboot=true”, hence the reboot. There should be a way to avoid that. According to Yealink a reboot is not necessary for the new config to get applied, unless a change to LLDP, VPN etc requires it, but generally not. Maybe the “Check Sync” is enough.
<------------->
— (8 headers 0 lines) —
Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS
Scheduling destruction of SIP dialog ‘[email protected]:5060’ in 32000 ms (Method: NOTIFY)
Reliably Transmitting (NAT) to 10.124.193.26:5060:
NOTIFY sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.178:5060;branch=z9hG4bK315410bd;rport
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as1249226e
To: sip:[email protected]:5060
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-13.0.190.7(11.22.0)
Date: Thu, 15 Dec 2016 01:32:52 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Subscription-State: terminated
Event: check-sync;reboot=true
Content-Length: 0