FTTH Logical cases

For FTTH Lines: Speed Variance Override any Logical case

• TRUE

• FALSE

For FTTH Lines: Delayed SLA for ''Unable to obtain IP'' case:

• 1 hour SLA

• 2 hours SLA

• From 2 : 5  hours SLA

For FTTH Lines: CCA should inform customer to let the ONT power turned on in all logical and physical cases

• TRUE

• FALSE

for FTTH Lines: Responsible team for''Technical visit'' is:

• FTTH field support Team

• FO Team

• Region Team

For FTTH lines : CST has suspended Account issue CCA Action :

• Send mail to [e-mail]

• Create ticket to Application Support Team on IBM

• Escalate TKT to NOC

For FTTH lines : CST has ''NAS Port ID'' issue, Escalation SLA will be :

• 2 H

• 12 H

• 72 H

For FTTH lines : Customer can open Facebook, but contents doesn't appearedm CCA action:

• IF CPE accessed try to adjust MTU and DNS [WE then Google DNS]

• Restart ONT from E-Matrix

• Reset ONT

For FTTH lines : In case Customer input that he paid the package bill within 24 hours, and line is Active on BSS, and Get Online Service in E-matrix Not Blocked, Your first action:

• Restart ONT

• Reset ONT

• Escalate browsing case to NOC

For FTTH lines : In case CCA will direct customer to his compound support SR will be :

• FBB Tech Problem > Technical issue > Other

• FBB Tech Problem > Technical issue > Direct to Compound Support

• FBB Tech Problem > Technical issue > Special compound

For FTTH Lines: Logical Instability TKT back with update''Session is up and stable since 9 PM'', there are many logs after mentioned time and customer didn't restart ONT, CCA action:

• Handle as Logical instability

• Handle as speed case

• Re-escalate the ticket directly