EMS and/or MUID macro is used within Profile_Rule URL:
<Profile_Rule ua="na">https://test.....cz/Provisioning.php?EMS=$EMS;MUID=$MUID</Profile_rule>
On first resync (either periodic or use SIP NOTIFY) the phone will reboot - then keep rebooting again and again. Reset to factory default will stop it.
The syslog shows:
18:08:37.471304 IP (tos 0x0, ttl 64, id 114, offset 0, flags [none], proto UDP (17), length 315)
10....8.1024 > 10....1.514: SYSLOG, length: 16
Facility local3 (19), Severity debug (7)
Msg: pbs 230912\0x0a
18:08:37.472220 IP (tos 0x0, ttl 64, id 115, offset 0, flags [none], proto UDP (17), length 315)
10....1024 > 10....1.514: SYSLOG, length: 287
Facility local0 (16), Severity info (6)
Msg: SPA508G e0:..:..:..:..:9d -- Requesting resync https://19....2:443/Provisioning.php?EMS=mobile;MUID=0101\0x0a
18:08:37.472602 IP (tos 0x0, ttl 64, id 116, offset 0, flags [none], proto UDP (17), length 61)
10....8.1024 > 10.....1.514: SYSLOG, length: 33
Facility local3 (19), Severity debug (7)
Msg: FMM >>>> Requesting profile\0x0a
18:08:37.473205 IP (tos 0x0, ttl 64, id 117, offset 0, flags [none], proto UDP (17), length 71)
10....8.1024 > 10....1.514: SYSLOG, length: 43
Facility kernel (0), Severity error (3)
Msg: <<<signal:10 received from thread FLASH\0x0a
18:08:37.474043 IP (tos 0x0, ttl 64, id 119, offset 0, flags [none], proto UDP (17), length 77)
10....8.1024 > 10....1.514: SYSLOG, length: 49
Facility local0 (16), Severity info (6)
Msg: request reboot type=4 reason=System 4(8000)\0x0a
The same configuration file with no EMS and MUID macro within Profile_Rule works as expected with no problem.
Also, both EMS and MUID macro can be used id Report_Rule with no problem.
It is another bug from pile of bugs in 7.5.3 firmware. Several hours of wasted time. Hope it help to someone else to save it's time.
