03-14-2017, 02:26 PM
Chaps,
we have sites with a populations of W52 on fairly slow broadband. A symptom we've replicated on T41s is below and we suspect it may be happening on W52 sites
A change in the UAD config results in the batch of phones going through their config update simultaneously because the provision timer was set to 120 minutes.
The data load on the ADSL causes the ISP to shut down the link or at least downspeed it. Rebooting the router restores the link.
The same impact occurs if there is a short and otherwise un-noticeable drop in the ADSL. A restart of the router brings everything back until the next time.
The problem was fixed by introducing on each T41 UAD:
sip.reg_surge_prevention = 1-60 . (in steps on each handset)
does this feature exist in the W52p. It's difficult to test on the bench hence my question.
Chris
we have sites with a populations of W52 on fairly slow broadband. A symptom we've replicated on T41s is below and we suspect it may be happening on W52 sites
A change in the UAD config results in the batch of phones going through their config update simultaneously because the provision timer was set to 120 minutes.
The data load on the ADSL causes the ISP to shut down the link or at least downspeed it. Rebooting the router restores the link.
The same impact occurs if there is a short and otherwise un-noticeable drop in the ADSL. A restart of the router brings everything back until the next time.
The problem was fixed by introducing on each T41 UAD:
sip.reg_surge_prevention = 1-60 . (in steps on each handset)
does this feature exist in the W52p. It's difficult to test on the bench hence my question.
Chris