Firstly, I agree with the comments & logic. They should NEVER not need to get into your network, much less into a computer on your network, to talk to their device to solve the problem. Though likely reason for request is they need to use web browser on lan to open the device's management interface. If that's the need simply create a guest account on PC, login to it, and then let them in OTS with you via TeamViewer.
Lack of management interface WAN side would be unusual IMHO given it's their managed device, they'd have a way into it. If you can dial out barring a subset of numbers, then you should be asking them well "what do your server logs show about my calling activity and how my device is talking to your servers?". They must log errors, for sure they log some kind of traffic for billing, I'd find it very odd if there's lower level audit trail. My guess is the support person is trained to verify things according to script to achieve known state rather than how to look at their servers for actual errors since that's $13/hr vs. $50. :/ On Mar 26, 2015 9:39 AM, "Winterlight" <[email protected]> wrote: > > Yeah, that is what I thought. The only thing on my end that could be at > fault is their device failing in some fashion, but then it is only certain > numbers and it is not intermittent or random. > > > Frankly, if you're making other calls it's not on your end, it is on >> theirs >> or Verizon's. How would you be successfully making other calls if it were >> on your equipment? Your equipment doesn't handle any routing of calls, >> just the sending of voip packets to their network, which you have proven >> that you can do by calling other numbers. >> > >
