In any logical cases must Keep CPE Turned ON, TRUE, False, Escalation of logical instability (multiple login) must be to, SLS, IU, NOC, it’s mandatory to follow logical verification before handle logical instability, False, True, In case of delay on logical instability Case right action will be, RE-Escalate ticket t NOC, Renew the SLA and create delay ticket, Troubleshoot the case, CST has a logical inability problem while troubleshooting no multiple login Quota is Not Exceeded Next action will be , Reset & Reconfigure, Inform CST that pc problem, Check spy ware, SLA for Escalate logical instability Multiple Login is, 24h, From 2:5h, 2h, While escalate logical instability Case on 9.00 PM CCA shouldn't check on call before escalation, Ture, False, According to the logs in the picture, it does not relate to the restart port or CPE CCA should handle it, Logical instability no Multiple Login, Logical instability Multiple Login, if customer not beside CPE or CPE not connected right SR will be, FBB Tech Problem- >Logical Instability- >Will Reset & FUB, FBB Tech Problem>Logical Instability->Not beside CPE, FBB Tech Problem->Logical Instability-> Laptop Or CPE Issue, CST has ticket logical instability with updates. This so CCA right action be, Informed cst within SLA, Let customer check with another CPE.

Logical Instability

โดย
สั่งพิมพ์
ฝัง

ลีดเดอร์บอร์ด

สไตล์ภาพ

ตัวเลือก

สลับแม่แบบ

คืนค่าการบันทึกอัตโนมัติ: ใช่ไหม