Author Topic: Teleworker Issues Using Fios Home Router  (Read 1026 times)

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Teleworker Issues Using Fios Home Router
« on: March 17, 2020, 01:26:05 PM »
We're seeing some issues with teleworker phones that we ~think~ seem to be related to Fios home routers.
Specifically, the issues we've see are with Mitel 5560 devices.  We may only ones using these but I'm wondering if anyone else has seen problems with these.

Has anyone else see issues with these Fios routers?

Ralph



Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: Teleworker Issues Using Fios Home Router
« Reply #1 on: March 17, 2020, 01:36:44 PM »
don't see many of the Turret sets. What kind of problems? The Turrent is, essentially, two 53xx sets glued together. From a TW perspective, both haves register separately and appear as separate sets.. Call control and the sets themselves take care of making it look like a single set to the user (though it hardly does ;).

they aren't connecting? no audio? what?

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Teleworker Issues Using Fios Home Router
« Reply #2 on: March 18, 2020, 11:46:59 AM »
The issue is that the two sides need to sync.  It stops at "sync 4".
This only seems to happen when connected to FiOS routers.

Ralph

Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: Teleworker Issues Using Fios Home Router
« Reply #3 on: March 18, 2020, 11:55:44 AM »
ooo, that's cool... so we did have a problem, years ago, with Actiontec cable modems that had buggy nat f/w code that couldn't handle two TW sets behind the same NAT because they were connecting to the same mbg ip/port... I certainly hope this isn't what you are seeing as there was no solution aside from a, eventual, fix from the manufacturer... I think our customers ended up switching out modems at the time. A tcp trace of the traffic on MBG ( tcpdump ... host mbg-ip and tcp and port 6801 ) and one on the set side (if you can get a ethernet hub in there, PITA I know) would be nice to take a peek at to see what's going on.

Do other set types work? is this only a problem with the turret?


 

Sitemap 1 2 3 4 5 6 7 8 9 10