HomeFusion disconnecting 5+ times per day, out 5-10 minutes each time

Question

HomeFusion is disconnecting 5+ times per day, out 5-10 minutes each time.
When it is up, it is fabulous. Signal quality is always great.
Main router page says just Connecting... when this happens.
Any one know why? Thanks.
Router logs show this:
Oct 23 20:48:20 2012
System Log
WAN LTE
CAN-Tr69 open admin pdn: pstate(0,0), ifstate(2,2)
Oct 23 20:48:20 2012
System Log
Debug Msg
dbg> mt_cwmp_init_transaction - cwmp->sess (nil) 0 event_code 4 0 0
Oct 23 20:48:18 2012
System Log
WAN LTE
Detect an event code : 0 - state 2 (3)
Oct 23 20:48:18 2012
System Log
WAN LTE
Detect a PDN event : ME DETACH - state 2 (3)
Oct 23 20:48:18 2012
System Log
WAN LTE
Detect a PDN event : ME PDN DEACT 3 - state 2 (3)
Oct 23 20:48:18 2012
System Log
Debug Msg
dbg> if_tryup: ifstate(1,2), pstate(0,0,0), 1(3)
Oct 23 20:48:18 2012
System Log
Debug Msg
dbg> if_disconn: states (1,-0),(0,0,0), reason 1, Enabled(3)
Oct 23 20:48:18 2012
System Log
Debug Msg
dbg> if_notify: 3->2, states(1,2) (0,0,0), 1(3)
Oct 23 20:48:18 2012
System Log
Debug Msg
dbg> if_notify: 4->3, states(1,2) (0,0,0), 1(3)
Oct 23 20:48:18 2012
System Log
Debug Msg
dbg> rm_conn(0): state(3,3)
Oct 23 20:48:17 2012
System Log
Debug Msg
dbg> rm_conn(3): state(0,3)
Oct 23 20:48:16 2012
System Log
Debug Msg
dbg> rm_conn(2): state(3,3)
Oct 23 20:48:16 2012
System Log
Debug Msg
dbg> rm_conn(1): state(0,3)
Oct 23 20:48:16 2012
System Log
Debug Msg
dbg> tm_close_pconn: mdmerr 0 state 8 reason 14
Oct 23 20:48:12 2012
System Log
Debug Msg
dbg> if_disconn: states (8,-0),(3,0,3), reason 14, Enabled(0)
Oct 23 20:48:12 2012
System Log
WAN LTE
Forced IMS disconnection (0)
Oct 23 20:46:44 2012
System Log
Debug Msg
dbg> ver_conn(0): state 3, Enabled(1)
Oct 23 20:46:21 2012
System Log
Debug Msg
dbg> add_conn(0): state 2 Enabled(0)
Oct 23 20:46:21 2012
System Log
WAN LTE
Detect a PDN event : ME PDN ACT 1 - state 9 (0)
Oct 23 20:46:20 2012
System Log
Debug Msg
dbg> add_conn(0): state 0 Enabled(0)
Oct 23 20:46:20 2012
System Log
Debug Msg
dbg> rm_conn(0): state(3,0)
Oct 23 20:46:18 2012
System Log
WAN LTE
Detect a PDN event : NW PDN DEACT 1 - state 9 (0)

Answer 1

Hi Jennifer @ Verizon
A simple reboot of the router and cantenna is not going to permanently fix this issue. Its been going on at least since August 2012. The issue is a bad software on the cantenna and its affecting areas such as KY, GA, TN, and OH.  I have emailed the manufacturer of the cantenna, I think its PCI and they emailed me telling me that its a known issue but no idea when it will be fixed. It could be a few week or a few months or possibly at least a year.
I think what Verizon should do is refund the money including installation and any fees paid for the service to all affected customers and take down the service until fixed or find a new manufacturer for the Cantenna or work with the engineers with PCI to come up with firmware fix asap. This issue is obviously affecting enough customers where telling your customers to wait is not going to work anymore. I don't mind waiting if I know that a fix is definitely coming and an actual date. Its very frustrating to have a company not support their customers in coming up with a fix on this asap such as a solution within the next 2 weeks. I was in the middle of taking another exam and got an F on it because your service disconnected me.
I think I might join the bandwagon and if this issue is not fixed by the end of January 2013 I'll be calling for a full refund. I am not confident that a permanently fix will be generated by Jan 2013 which is sad. Is anyone else with me - I mean what is it going to take for Verizon to come up with a solution on this permanently. The sad part of all of this is Verion tells me its an issue with a firmware on the cantenna and the manufacturer of the cantenna tells me to  be patient and wait for a fix and when I pressed the issue some more, the manufacturer of the cantenna tells me Verizon has to approve the fix but Verizon says they are waiting for a fix from the manufacturer. So, I am not sure what it is.