Wifi Calling

[Theb]

 I purchased a telephone connected through a smart hub. 

My calls are consistently dropped at just over 11 minutes. My telephone provider checked their end and could not determine any problems (my call to them was even dropped). They said there is a switch inside the smart hub that has to be turned off remotely. How do I talk to someone about that. 

[Theb]

1. Telephone provider: Primus

2 Smart Hub provider: Telus

3. Make and model of Smart Hub: ZTE. Model L: 3730T42P3h6544A2

4> Working: No. I had a previous Smart Hub that crapped out on me. Same problem. I purchased this from a Telus associate store in Campbell River in October 2019

5. I don't know the answer to that question. 

Suggestions.

I did as you suggested and I was able to immediately connect with Telus.

My problem always begins around the 11 minute mark, 

I I receive a call on my cell, it goes to my land line and that is not a problem. 

[BrandonT · Accepted solution]

Hey @Theb

Thanks for answering the questions, and completing the troubleshooting. It helps a lot! 

Based on your troubleshooting results, it appears that WiFi calling is not that issue, it seems that your Smart Hub is having trouble keeping a steady connection (common and expected from a smart hub since its using cellular data not a wired connection). 

Below lets try some more troubleshooting to narrow down the issue further.

Troubleshopoting #1 - Running a speed test on your smart hub.

WiFi calling required 2mbps upload and download speeds to work correctly.
WARNING: Speed Tests use under 2GB of data. Please make sure you have enough data on your smart hub to avoid costly PPU data overages.

1. Go to www.SpeedTest.net
2. Click the circle button "GO".
3. Once finished (takes 1 minute), you will get results for your PING, Download, and Upload.
4. Please share these results in your reply.

Troubleshooting #2 - Network reset on your cellphone & test WiFi Calling.

WARNING: When doing a network reset, it will delete your saved WiFi passwords, and Bluetooth connections. If you proceed, you will have to manually connect to your WiFi with the password once. Then it will automatically connect like normally. This also applies to any Bluetooth devices you may have connected to your phone. Rest assured, your phones contacts, pictures, apps, and any important information will NOT get deleted. 

1. Disable WiFi Calling.
   
   
2. Reset Network Settings
   Apple: Go to Settings > General > Reset > Tap Reset Network Settings
   Android: Go to Settings > General Management -OR- System > Reset -OR- Reset Options > Tap Reset Network Settings
   (once complete, restart your Apple or Android phone)
   
   
3. Connect to your WiFi & enter the password.
   
   
4. Enable WiFi Calling
   
   
5. Enable airplane mode
   
   
6. Double check WiFi is still on
   
   
7. Make a test call and see if the call drops ~11 minutes.
   If you have a cellphone plan with limited minutes, please make sure you have enough to avoid PPU minute charges. 
   
8. Once you are finished this test,  don't forget to turn airplane mode off.

Troubleshooting #3 - PING test on Smart Hub

We will be checking to see if the Smart Hub is able to keep a steady connection for longer than 11 minutes.

1. Turn on your Windows computer
   hopefully you have one, if not let me know and I will try and find alternative instructions
   
2. On your keyboard, hold down the Windows Key then tap on the R key. Then release both keys.
   This will open a little box called Run on the bottom left of your screen.
   
   
3. In the text area, type CMD and click OK
   A black box will appear with white text.
   
   
4. Type: ping google.com -t and click enter
   
   
5. Let this run for 11+ minutes.
   Every few seconds, a new line of text will appear. Keep watching it. If you see an error: Request timed out, or General failure and its there are multiple errors in a row, than we have determined that the Smart Hub is unable to keep a steady connection and that is the reason your WiFi Calling is having issues. After some time has passed, you can click the X to close the black box.

---

TELUS Employee & Neighbourhood Volunteer :black_small_square:If you found this helpful, let others know by clicking the ❤️ Like button.

[Theb]

I’ve tried to post my reply 3 times and it won’t take it. Just to let you know I’m trying but having technical difficulties.

[Theb]

I'm having trouble and the site keeps kicking me out. 

[Theb]

I ran the test for 15 minutes and there was no problems. Times ranged from 10 ms to 300+ ms (one). Average was 40-50 ms. 

On the speed test the download was 23.8 and upload is  ping was  21ms, jitter is 18% and zero loss. 

I will have to wait for another time to do test two, until I retrieve my password, etc. 

[Nighthawk]

Which make and model of phone are you using?

[Theb]

I'm using a Panasonic. I can direct my cell to the Panasonic and there is no interruption in service. I have talked for over an hour. 

[BrandonT]

@Theb 

I too had to re-type my long message 3x before it went through. I am now copying the text before I click the Post button so I don't have to re-type, I can just paste and hope for the best. No error was given, so I have no idea whats happening. 

The 15 min test you ran has great results.

Perhaps running it for a few hours may yield more accurate results. If your up to it, we can try running it for a day.

ping google.com -n 50000 >C:/ping_test.txt

This will save a note called ping_test.txt in your C:/ directory. You could then PM me the results to review for any possible concerns.

As for your speedtest...download is very high for a Smart hub. PING is also really good. The upload speeds did not appear, if you can run the test again to find your upload that will be very useful.

Do you happen to have a 2nd cellphone you could try WiFi calling on to see if it also has the same issue?
If so, we can confidently rule out your cellphone from further troubleshooting. 

Ill await your response when you get the chance to run troubleshooting #2.

[Nighthawk]

@Theb - I think there is something that needs to be identified before going through further connection troubleshooting. If your phone service is with Primus, is it the digital landline or the cellular service? Which make and model of phone do you have?

Primus' website does not indicate that they even support or offer wifi calling for their celluar service. Their digital landline service FAQs list that in some cases port forwarding would need to be enabled for it to work, and that may not even be possible with the Smart Hub due to the way it connects. 

===

Ping tests are not a completely reliable testing method especially when you are testing to a domain, like google.com, that is hosted on a huge number of servers. Each time you test you could end up testing to a different IP. Some servers by default will not respond to ping tests either. This does not mean there is a problem.

[Theb]

I used Primus for 10 years prior to moving on my own. 

They have a box to convert analogue to digital and it is directly connected to my Smart hub for VOIP. I had to purchase that box. It is quite possible the box is malfunctioning but Primus has tried to troubleshoot it and says it's fine. My thinking is the problem is not with that box because my calls are always terminated around 11 minutes. That is the one thing that is consistent. The reality is I just use the phone as a backup for when I have trouble with my cell phone.

I have tried to pursue this matter a couple of times, but have neither the time or the patience to spend hours on hold waiting for customer service. 

[Theb]

ping google.com -n 50000 >C:/ping_test.txt

When I try this I immediately get a message "Access denied". I am listed as the administrator. 

[BrandonT]

@Theb

@Nighthawk made some good points.

• Its worth looking into the Primus phone and ensure all possible troubleshooting efforts are made. More often Wi-Fi Calling issues are from the phone itself, and is often fixed by a network reset, or re-configuration of Wi-Fi calling. Since I have no idea on Primus phone systems, I am unable to assist with the troubleshooting for this. Therefor I will assume the Primus phone is working correctly unless @Nighthawk or another member is able to provide more instructions. In the meantime, I will continue with troubleshooting the SmartHub. - If anyone knows more about Primus and troubleshooting, please chime in.
  
  
• Ping tests are not completely reliable. Very true, however I was hoping to discover a pattern around the 11 minute mark and exclude other false positives to get a better understanding of your network. As for google as the ping, he is right, it may bounce to different servers. So instead we will use Googles DNS which is far more stable. Thanks for catching that.
  
  

Here is my game plan...

• Test the internet connecting between the SmartHub and the Internet.
• Test the internal Wi-Fi connection between the SmartHub and other Wi-Fi devices on your network.
• Hope that we find a pattern with the results to find the root cause of the issue so we know what to reset, and or replace if needed.

As for the "Access denied" error, lets try this...
Open CMD, and type...

cd documents

Click enter, then type...

ping 8.8.8.8 -n 50000 >ping_external.txt

Now open a 2nd CMD window (Windows+R, type CMD, click OK) , and type...

ipconfig

Click enter. Look for where it says Wireless LAN adapter Wi-Fi and find the Default Gateway. Remember this number. Now type...

cls

Click enter, then type...

cd documents

Click enter, then type...

ping xxx.xxx.xxx -n 50000 >ping_internal.txt

Note: Make sure to change xxx.xxx.xxx with the Default Gateway.

Once both of these scripts are finished running (should take around 8 hours), the black boxes will disappear. Then go to your documents folder, find and open the text files labeled ping_external.txt and ping_internal.txt. Copy the text, go to https://pastebin.com/ and paste the text into the text area. Click the button "Create new paste", and you will be given a share link. Please share that link in your reply, or send it by Private Message. 

---

TELUS Employee & Neighbourhood Volunteer :black_small_square:If you found this helpful, let others know by clicking the ❤️ Like button.

[Theb]

I couldn't get the text to save to a file but ran the test 50,000 times and here is the summary:

Packets sent: 50,000

Received 49959

Lost 41 (0%)

Approximate round trip times in milli-seconds

minimum = 22 ms

Maximum 3604 ms

Average 64 ms

[Theb]

Here is a test that Primus provides its customers. Does this make sense? Unfortunately the test does not last 11 minutes, when my troubles begin. 

Test on 2020-05-21 8:23:18.73

Windows IP Configuration

Host Name . . . . . . . . . . . . : ASUS-RoG
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Lan Canble:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30)
Physical Address. . . . . . . . . : 40-16-7E-88-8E-8F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 56-27-1E-97-AF-49
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 56-27-1E-97-A7-49
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter
Physical Address. . . . . . . . . : 54-27-1E-97-AF-49
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7075:710d:1002:c213%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.179(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : May 19, 2020 9:28:07 AM
Lease Expires . . . . . . . . . . : May 22, 2020 7:09:26 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 173287198
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-C9-30-89-40-16-7E-88-8E-8F
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 54-27-1E-91-27-41
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Interface: 192.168.0.179 --- 0x11
Internet Address Physical Address Type
192.168.0.1 60-14-66-bf-3a-fc dynamic
192.168.0.123 74-9e-af-88-65-70 dynamic
192.168.0.172 70-77-81-81-08-3d dynamic
192.168.0.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

IPCONFIG Complete.

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:5354 ASUS-RoG:51715 ESTABLISHED
Bonjour Service
[System]
TCP 127.0.0.1:5354 ASUS-RoG:51716 ESTABLISHED
Bonjour Service
[System]
TCP 127.0.0.1:51715 ASUS-RoG:5354 ESTABLISHED
[System]
TCP 127.0.0.1:51716 ASUS-RoG:5354 ESTABLISHED
[System]
TCP 192.168.0.179:51762 17.248.130.35:https CLOSE_WAIT
[iCloudServices.exe]
TCP 192.168.0.179:51781 17.248.130.40:https CLOSE_WAIT
[iCloudChrome.exe]
TCP 192.168.0.179:51832 17.248.130.40:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:51833 17.248.130.71:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:51835 17.248.130.35:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:51836 17.248.130.71:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:51837 17.248.130.40:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:51859 17.248.130.71:https CLOSE_WAIT
[iCloudChrome.exe]
TCP 192.168.0.179:51874 17.248.130.40:https CLOSE_WAIT
[iCloudDrive.exe]
TCP 192.168.0.179:51994 13.107.4.52:http CLOSE_WAIT
[System]
TCP 192.168.0.179:52021 a2-22-74-79:https CLOSE_WAIT
[System]
TCP 192.168.0.179:52022 a2-22-74-79:https CLOSE_WAIT
[System]
TCP 192.168.0.179:52024 a2-22-74-79:https CLOSE_WAIT
[System]
TCP 192.168.0.179:52263 wj-in-f188:5228 ESTABLISHED
[System]
TCP 192.168.0.179:52283 52.179.224.121:https ESTABLISHED
WpnService
[System]
TCP 192.168.0.179:52481 17.57.144.181:5223 ESTABLISHED
[APSDaemon.exe]
TCP 192.168.0.179:52490 52.179.224.121:https ESTABLISHED
[OneDrive.exe]
TCP 192.168.0.179:56011 52.114.159.133:https CLOSE_WAIT
[System]
TCP 192.168.0.179:56035 40.122.160.14:https CLOSE_WAIT
[System]
TCP 192.168.0.179:56153 17.248.130.162:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:56154 17.248.130.162:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:56156 17.248.130.33:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:56207 192.168.0.123:51503 ESTABLISHED
[System]
TCP 192.168.0.179:61945 a2-22-72-27:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:61946 17.248.130.47:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:61947 17.248.130.47:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:62039 17.248.130.153:https CLOSE_WAIT
[iCloudDrive.exe]
TCP 192.168.0.179:62055 a2-22-72-163:https ESTABLISHED
[System]
TCP 192.168.0.179:62056 a2-22-72-163:https ESTABLISHED
[System]
TCP 192.168.0.179:62061 40.97.160.2:https TIME_WAIT
TCP 192.168.0.179:62063 40.90.137.124:https TIME_WAIT
TCP 192.168.0.179:62065 primus:http TIME_WAIT
TCP 192.168.0.179:62066 primus:http TIME_WAIT
TCP 192.168.0.179:62068 primus:https TIME_WAIT
TCP 192.168.0.179:62069 151.139.128.14:http TIME_WAIT
TCP 192.168.0.179:62071 primus:https TIME_WAIT
TCP 192.168.0.179:62086 a2-22-72-84:https ESTABLISHED
[System]
TCP 192.168.0.179:62090 a2-22-72-84:https TIME_WAIT
TCP 192.168.0.179:62091 72.21.91.29:http TIME_WAIT
TCP 192.168.0.179:62092 a23-36-242-101:https ESTABLISHED
[System]
TCP 192.168.0.179:62093 a23-36-242-101:https TIME_WAIT
TCP 192.168.0.179:62094 a2-22-72-84:https ESTABLISHED
[System]
TCP 192.168.0.179:62096 207.194.199.105:https ESTABLISHED
[System]
TCP 192.168.0.179:62097 207.194.199.105:https ESTABLISHED
[System]
TCP 192.168.0.179:62098 207.194.199.105:https TIME_WAIT
TCP 192.168.0.179:62099 207.194.199.105:https TIME_WAIT
TCP 192.168.0.179:62100 72.21.91.29:http TIME_WAIT
TCP 192.168.0.179:62101 72.21.91.29:http TIME_WAIT
TCP 192.168.0.179:62119 52.114.159.22:https ESTABLISHED
[System]
TCP 192.168.0.179:62130 207.194.199.105:https ESTABLISHED
[System]
TCP 192.168.0.179:62131 primus:https ESTABLISHED
[System]
TCP 192.168.0.179:62133 13.64.117.133:https TIME_WAIT
TCP 192.168.0.179:62134 13.68.225.90:https TIME_WAIT
TCP 192.168.0.179:62136 40.90.137.124:https ESTABLISHED
wlidsvc
[System]
TCP 192.168.0.179:62137 a2-22-74-79:https ESTABLISHED
[System]
TCP 192.168.0.179:62138 ec2-54-70-156-78:https TIME_WAIT
TCP 192.168.0.179:62139 server-99-86-38-25:https ESTABLISHED
Can not obtain ownership information
TCP 192.168.0.179:62140 edge-star-shv-01-sea1:https ESTABLISHED
[System]
TCP 192.168.0.179:64340 40.97.80.18:imaps ESTABLISHED
[System]
TCP 192.168.0.179:64391 17.248.130.17:https CLOSE_WAIT
[iCloudPhotos.exe]
TCP 192.168.0.179:64399 17.248.130.152:https CLOSE_WAIT
[iCloudPhotos.exe]

netstat -b Complete.

Pinging www.google.ca [172.217.3.195] with 32 bytes of data:
Reply from 172.217.3.195: bytes=32 time=25ms TTL=50
Reply from 172.217.3.195: bytes=32 time=52ms TTL=50
Reply from 172.217.3.195: bytes=32 time=81ms TTL=50
Reply from 172.217.3.195: bytes=32 time=56ms TTL=50
Reply from 172.217.3.195: bytes=32 time=38ms TTL=50
Reply from 172.217.3.195: bytes=32 time=52ms TTL=50
Reply from 172.217.3.195: bytes=32 time=75ms TTL=50
Reply from 172.217.3.195: bytes=32 time=35ms TTL=50
Reply from 172.217.3.195: bytes=32 time=27ms TTL=50
Reply from 172.217.3.195: bytes=32 time=59ms TTL=50
Reply from 172.217.3.195: bytes=32 time=42ms TTL=50
Reply from 172.217.3.195: bytes=32 time=36ms TTL=50
Reply from 172.217.3.195: bytes=32 time=25ms TTL=50
Reply from 172.217.3.195: bytes=32 time=26ms TTL=50
Reply from 172.217.3.195: bytes=32 time=32ms TTL=50
Reply from 172.217.3.195: bytes=32 time=25ms TTL=50
Reply from 172.217.3.195: bytes=32 time=27ms TTL=50
Reply from 172.217.3.195: bytes=32 time=56ms TTL=50
Reply from 172.217.3.195: bytes=32 time=62ms TTL=50
Reply from 172.217.3.195: bytes=32 time=35ms TTL=50
Reply from 172.217.3.195: bytes=32 time=86ms TTL=50
Reply from 172.217.3.195: bytes=32 time=81ms TTL=50
Reply from 172.217.3.195: bytes=32 time=45ms TTL=50
Reply from 172.217.3.195: bytes=32 time=42ms TTL=50
Reply from 172.217.3.195: bytes=32 time=32ms TTL=50
Reply from 172.217.3.195: bytes=32 time=28ms TTL=50
Reply from 172.217.3.195: bytes=32 time=26ms TTL=50
Reply from 172.217.3.195: bytes=32 time=28ms TTL=50
Reply from 172.217.3.195: bytes=32 time=26ms TTL=50
Reply from 172.217.3.195: bytes=32 time=67ms TTL=50
Reply from 172.217.3.195: bytes=32 time=82ms TTL=50
Reply from 172.217.3.195: bytes=32 time=60ms TTL=50
Reply from 172.217.3.195: bytes=32 time=30ms TTL=50
Reply from 172.217.3.195: bytes=32 time=78ms TTL=50
Reply from 172.217.3.195: bytes=32 time=41ms TTL=50
Reply from 172.217.3.195: bytes=32 time=82ms TTL=50
Reply from 172.217.3.195: bytes=32 time=32ms TTL=50
Reply from 172.217.3.195: bytes=32 time=49ms TTL=50
Reply from 172.217.3.195: bytes=32 time=83ms TTL=50
Reply from 172.217.3.195: bytes=32 time=33ms TTL=50
Reply from 172.217.3.195: bytes=32 time=28ms TTL=50
Reply from 172.217.3.195: bytes=32 time=79ms TTL=50
Reply from 172.217.3.195: bytes=32 time=26ms TTL=50
Reply from 172.217.3.195: bytes=32 time=44ms TTL=50
Reply from 172.217.3.195: bytes=32 time=34ms TTL=50
Reply from 172.217.3.195: bytes=32 time=26ms TTL=50
Reply from 172.217.3.195: bytes=32 time=87ms TTL=50
Reply from 172.217.3.195: bytes=32 time=37ms TTL=50
Reply from 172.217.3.195: bytes=32 time=36ms TTL=50
Reply from 172.217.3.195: bytes=32 time=35ms TTL=50

Ping statistics for 172.217.3.195:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 87ms, Average = 46ms

Ping Complete.

Pinging src.san1.g01.yahoodns.net [98.136.103.24] with 32 bytes of data:
Reply from 98.136.103.24: bytes=32 time=43ms TTL=47
Reply from 98.136.103.24: bytes=32 time=31ms TTL=47
Reply from 98.136.103.24: bytes=32 time=78ms TTL=47
Reply from 98.136.103.24: bytes=32 time=63ms TTL=47
Reply from 98.136.103.24: bytes=32 time=47ms TTL=47
Reply from 98.136.103.24: bytes=32 time=34ms TTL=47
Reply from 98.136.103.24: bytes=32 time=34ms TTL=47
Reply from 98.136.103.24: bytes=32 time=82ms TTL=47
Reply from 98.136.103.24: bytes=32 time=49ms TTL=47
Reply from 98.136.103.24: bytes=32 time=63ms TTL=47
Reply from 98.136.103.24: bytes=32 time=63ms TTL=47
Reply from 98.136.103.24: bytes=32 time=33ms TTL=47
Reply from 98.136.103.24: bytes=32 time=44ms TTL=47
Reply from 98.136.103.24: bytes=32 time=91ms TTL=47
Reply from 98.136.103.24: bytes=32 time=42ms TTL=47
Reply from 98.136.103.24: bytes=32 time=64ms TTL=47
Reply from 98.136.103.24: bytes=32 time=67ms TTL=47
Reply from 98.136.103.24: bytes=32 time=101ms TTL=47
Reply from 98.136.103.24: bytes=32 time=72ms TTL=47
Reply from 98.136.103.24: bytes=32 time=41ms TTL=47
Reply from 98.136.103.24: bytes=32 time=37ms TTL=47
Reply from 98.136.103.24: bytes=32 time=84ms TTL=47
Reply from 98.136.103.24: bytes=32 time=71ms TTL=47
Reply from 98.136.103.24: bytes=32 time=50ms TTL=47
Reply from 98.136.103.24: bytes=32 time=68ms TTL=47
Reply from 98.136.103.24: bytes=32 time=73ms TTL=47
Reply from 98.136.103.24: bytes=32 time=66ms TTL=47
Reply from 98.136.103.24: bytes=32 time=48ms TTL=47
Reply from 98.136.103.24: bytes=32 time=31ms TTL=47
Reply from 98.136.103.24: bytes=32 time=137ms TTL=47
Reply from 98.136.103.24: bytes=32 time=80ms TTL=47
Reply from 98.136.103.24: bytes=32 time=30ms TTL=47
Reply from 98.136.103.24: bytes=32 time=31ms TTL=47
Reply from 98.136.103.24: bytes=32 time=47ms TTL=47
Reply from 98.136.103.24: bytes=32 time=85ms TTL=47
Reply from 98.136.103.24: bytes=32 time=33ms TTL=47
Reply from 98.136.103.24: bytes=32 time=53ms TTL=47
Reply from 98.136.103.24: bytes=32 time=69ms TTL=47
Reply from 98.136.103.24: bytes=32 time=84ms TTL=47
Reply from 98.136.103.24: bytes=32 time=35ms TTL=47
Reply from 98.136.103.24: bytes=32 time=32ms TTL=47
Reply from 98.136.103.24: bytes=32 time=64ms TTL=47
Reply from 98.136.103.24: bytes=32 time=44ms TTL=47

Primus suggested DMZ. They suggested opening the prot for DHP phone modem. This can be done remotely and they feel that will solve my problem. 

Hopefully that makes sense to you. 

[Theb]

How do I go about A DMZ reset?

It’s been suggested that opening the prot for DHP will solve my problem.