verizon wifi calling stopped working

Thu Oct 18 15:28:10 UTC 2018

If someone from Verizon Wireless specifically for WiFi calling could reach
out to me to fix our devices I would appreciate it.  The WiFi calling works
just fine when we reboot in the office, but it will never reconnect (ie we
leave the office, get 4G, come back).  I've opened 3-4 tickets with no
resolution.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373

On Wed, Oct 17, 2018 at 1:13 PM, Sean Heskett <afmug at zirkel.us> wrote:

> Hello,
>
> Is anyone from verizon wireless on here.  clients across our network
> started complaining 2 weeks ago that wifi calling stopped working.  below
> are some pings at traceroutes to wo.vzwwo.com which fail.  the first set
> is with our normal DNS servers and the second set is using 8.8.8.8
>
> Thanks,
>
> *Sean Heskett*
>
> *ZIRKEL Wireless *
> *High-Speed Internet for NW Colorado*
> 970-871-8500 x100 - Office
> 970-846-8065 - mobile
> 866-903-4628 - Fax
> Website <http://www.zirkelwireless.com/> | Facebook
> <http://www.facebook.com/zirkelwireless>
>
>
> MBP-Sean:~ sean$ ping wo.vzwwo.com
>
> PING wo.vzwwo.com (141.207.177.233): 56 data bytes
>
> Request timeout for icmp_seq 0
>
> Request timeout for icmp_seq 1
>
> Request timeout for icmp_seq 2
>
> Request timeout for icmp_seq 3
>
> ^C
>
> --- wo.vzwwo.com ping statistics ---
>
> 5 packets transmitted, 0 packets received, 100.0% packet loss
>
> MBP-Sean:~ sean$ traceroute wo.vzwwo.com
>
> traceroute: Warning: wo.vzwwo.com has multiple addresses; using
> 141.207.177.233
>
> traceroute to wo.vzwwo.com (141.207.177.233), 64 hops max, 52 byte packets
>
>  1  192.168.12.1 (192.168.12.1)  0.810 ms  0.586 ms  0.571 ms
>
>  2  rtr-edge-rht.zirkelwireless.com (65.117.208.1)  1.547 ms  1.640 ms
> 1.550 ms
>
>  3  65-117-210-178.zirkelwireless.com (65.117.210.178)  2.494 ms  2.412
> ms  2.249 ms
>
>  4  72-55-193-5.mammothnetworks.com (72.55.193.5)  5.149 ms  6.783 ms
> 5.540 ms
>
>  5  be5274.rcr21.b006467-6.den01.atlas.cogentco.com (38.140.187.145)
> 5.996 ms  5.880 ms  5.756 ms
>
>  6  be3414.ccr21.den01.atlas.cogentco.com (66.28.4.205)  6.072 ms
>
>     be3415.ccr22.den01.atlas.cogentco.com (154.54.30.241)  6.252 ms
>
>     be3414.ccr21.den01.atlas.cogentco.com (66.28.4.205)  6.203 ms
>
>  7  be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90)  17.542 ms
>
>     be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90)  17.646 ms
>
>     be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90)  17.038 ms
>
>  8  be2433.ccr32.dfw01.atlas.cogentco.com (154.54.3.213)  27.259 ms
> 27.265 ms
>
>     be2432.ccr31.dfw01.atlas.cogentco.com (154.54.3.133)  27.198 ms
>
>  9  be2764.ccr41.dfw03.atlas.cogentco.com (154.54.47.214)  28.024 ms
>
>     be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74)  27.870 ms
> 27.955 ms
>
> 10  verizon.dfw03.atlas.cogentco.com (154.54.12.206)  27.478 ms  48.841
> ms  40.085 ms
>
> 11  0.et-10-1-0.gw8.chi13.alter.net (140.222.236.209)  40.159 ms
>
>     0.et-11-3-0.gw8.chi13.alter.net (140.222.231.217)  39.879 ms
>
>     0.et-10-1-0.gw8.chi13.alter.net (140.222.236.209)  40.217 ms
>
> 12  * * *
>
> ^C
>
> MBP-Sean:~ sean$ ping wo.vzwwo.com
>
> PING wo.vzwwo.com (141.207.193.233): 56 data bytes
>
> Request timeout for icmp_seq 0
>
> Request timeout for icmp_seq 1
>
> Request timeout for icmp_seq 2
>
> ^C
>
> --- wo.vzwwo.com ping statistics ---
>
> 4 packets transmitted, 0 packets received, 100.0% packet loss
>
> MBP-Sean:~ sean$ traceroute wo.vzwwo.com
>
> traceroute: Warning: wo.vzwwo.com has multiple addresses; using
> 141.207.193.233
>
> traceroute to wo.vzwwo.com (141.207.193.233), 64 hops max, 52 byte packets
>
>  1  192.168.12.1 (192.168.12.1)  0.896 ms  0.593 ms  0.583 ms
>
>  2  rtr-edge-rht.zirkelwireless.com (65.117.208.1)  1.453 ms  1.312 ms
> 1.181 ms
>
>  3  65-117-210-178.zirkelwireless.com (65.117.210.178)  2.446 ms  2.061
> ms  2.237 ms
>
>  4  72-55-193-5.mammothnetworks.com (72.55.193.5)  5.152 ms  5.121 ms
> 5.124 ms
>
>  5  be5274.rcr21.b006467-6.den01.atlas.cogentco.com (38.140.187.145)
> 5.716 ms  5.748 ms  5.506 ms
>
>  6  be3414.ccr21.den01.atlas.cogentco.com (66.28.4.205)  5.919 ms
>
>     be3415.ccr22.den01.atlas.cogentco.com (154.54.30.241)  6.004 ms
>
>     be3414.ccr21.den01.atlas.cogentco.com (66.28.4.205)  7.184 ms
>
>  7  be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90)  17.233 ms
>
>     be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90)  17.397 ms
>
>     be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90)  17.859 ms
>
>  8  be2433.ccr32.dfw01.atlas.cogentco.com (154.54.3.213)  27.428 ms
> 27.476 ms
>
>     be2432.ccr31.dfw01.atlas.cogentco.com (154.54.3.133)  27.606 ms
>
>  9  be2764.ccr41.dfw03.atlas.cogentco.com (154.54.47.214)  28.129 ms
>
>     be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74)  28.009 ms
> 27.497 ms
>
> 10  verizon.dfw03.atlas.cogentco.com (154.54.12.206)  27.402 ms  27.451
> ms  27.445 ms
>
> 11  0.et-11-3-0.gw10.dfw7.alter.net (140.222.228.115)  29.849 ms  29.039
> ms
>
>     0.et-10-1-0.gw10.dfw7.alter.net (140.222.0.113)  29.132 ms
>
> ^C
>
> MBP-Sean:~ sean$
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20181018/24c761f0/attachment.html>