Network extender outage March 26, 2013
Was having issues off and on yesterday to wake up at 1am to the GBS magenta and the SYS blinking red. I finally was able to speak to a tech who said they are getting flooded by calls about the same problem. There is no specific time for it to be fixed but he is hoping sometime in the morning.
Yes, just the red flashing system light and where I am I cannot get a call out without the extender. Hopefully this issue is resolved soon!
Similar Messages
-
I want VERIZON to send us a NETWORK extender at their cost because I pay my bill and am NOT receiving phone service from VERIZON as promised. I am stranded without the use of my cell phone in my home. My contract says that VERIZON will provide me service and I must pay...I DO pay. Why would VERIZON do this to a almost 7 year responsible customer? Our whole family uses VERIZON (seperately) and this is horrible customer service. VERIZON knows that many of the basic phones do not work as promised. I want a working phone. All VERIZON keeps saying is that my upgrade isn't until August? I don't want an upgrade, I want a phone that works. I am contacting the Attorney General's office to see what can be done. I have missed emergency phone calls and now will be in a snowstorm without a reliable phone.
First of all, Verizon does not guarantee service, even in areas where the map says there is full coverage.
Service provided vial radio waves can be affected by multiple things, such as foliage, buildings AND asmospheric conditions such as snowstorms.
Maybe you should have purchased the NE before the snowstorm, but then if your power went out, you would be out of luck. Of course, your power company says they will provide you power, but then again, sometimes there are outages.
If phone service is so important, there is NOTHING as reliable as a land line!!! -
Definitive Network Extender destination IP/port list?
Does anyone have the definitive Network Extender destination IP/port list?
I have heard that it's the following IPs:
* 209.210.15.73
* 69.78.69.206
* 69.78.69.210
* 69.78.95.193
With the following UDP ports
* 53
* 500
* 3500
* 52428
Yesterday, I found that my Network Extender was also requiring access to:
* 66.174.71.40
1. Can anyone confirm the exact list of all IP addresses a Network Extender will contact?
2. For each IP, can anyone confirm which exact destination ports are required?
(I am skeptical that each destination IP needs all four ports)
With this information, Network Extender users can make sure our firewalls are open properly, as well as put in quality of service (QOS) rules to make sure the device gets higher priority transmission than other Web traffic.I got a network extender in July 2011 and it worked beautifully for about a year and a half. I set it up myself and had not problems. Sometime in December 2012 there was a "national outage" and my extender has never worked right since. It would allow me to hear my callers but callers could not hear me. After about 8 hours with CS over a few days, a fruitless service call with my ISP, Time Warner Cable and finally a desperate call to executive offices, Verizon sent me a new extender. I set it up the same way as the first and after about 3 hours all blue lights came one. The identical problem with my phone occurred. My next move was to go to the local store and beg for help. They were very pleasant but their solution, if you can call it that, was to send me a THIRD extender which I took to the store for "checking" and was told it was fine. When I set it up, it did exactly what yours is doing . . . I have blue, flashing red, purple, blue LED. I tried both the build in antenna and the external antenna for GPS. I poured over the manual (sorry, Elector, but don't you think we looked at the manual?????) and it said if this condition occurs, the unit is defective. So, back to the store to return my third unit. If anyone has any helpful suggestions, I would most appreciate it.
-
SPA8000 not re-establishing PPPoE Session after extended outage
Hi,
I have an SPA8000 Bridged to a ADSL2+ Modem and the SPA8000 performs PPPoE Authentication. If there is a drop in the service, it will automatically redial back in, however if there is an extended outage (eg. Loss of Line Sync, Carrier Issues) the SPA8000 will refuse to reconnect automatically without intervention (eg. Rebooting).
The SPA8000 is running version 6.1.11, some basic settings:
Under WAN:
WAN Type: PPPoE
DNS Server: Manual
Username and Password are setup as per the PPPoE Account Details.
Everything is default.
Under Voice:
SIP Registry Expires on the Line are set to 600 seconds, Provider SIP Proxy is set along (DNS Based not IP Address) with Username and Password - everything else is left as default.
This is been tested on 3 separate SPA8000 devices experencing the same issue. NAT Keep Alive has been toggled to no success either.
Are you able to provide insight into this? I can supply further information if required.
Thanks
DavidHi Dan,
Apologies for the late reply to this message - I had to setup a test environment to emulate this problem. It appears there is a problem where by the SPA8000 (and this may apply to other models as well) does not try to re-authenticate again after initially retrying 4 Times (in quick 2 second increments) after receiving an Invalid Username/Password Response or Timeout from a PPPoE Server or LNS. It does however work if there it does not respond to a PPPoE discovery (eg. Unplugging the Ethernet Cable between the SPA8000 and the Modem/NTU or there is no communication between the network and Modem/NTU).
Here are the debug logs from where it did not try to re-authenticate and the only requests that I had back on the LNS. In this example the SIP Registry Expiry was set to 600 seconds and I changed the Password that it originally connected with and dropped/cleared the connection from the LNS. I waited the full 600 seconds and the PPPoE did not try again to re-authenticate.
The Logs don't seem to indicate much (and I have changed IP Addresses/Hostnames in the below logs as well):
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:10:32.642
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:10:32.642
<143>M2: subnet mask: 255.255.255.0
192.168.0.3 23/04 17:10:32.642
<143>M2: gateway ip: 192.168.0.1
192.168.0.3 23/04 17:10:32.642
<143>M2: dns servers(1): 192.168.0.3 23/04 17:10:32.642
<143>M2: 192.168.0.1 192.168.0.3 23/04 17:10:32.642
<143>M2:
192.168.0.3 23/04 17:10:32.642
<159>M0: IDBG: st-0
192.168.0.1 23/04 17:10:32.682
<159>M2: mslink server task up (2)
192.168.0.3 23/04 17:10:34.422
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:10:35.793
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:10:35.793
<143>M3: subnet mask: 255.255.255.0
192.168.0.4 23/04 17:10:35.793
<143>M3: gateway ip: 192.168.0.1
192.168.0.4 23/04 17:10:35.793
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:10:35.793
<143>M3: dns servers(1): 192.168.0.4 23/04 17:10:35.793
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:10:35.793
<143>M3: 192.168.0.1 192.168.0.4 23/04 17:10:35.793
<143>M1: subnet mask: 255.255.255.0
192.168.0.2 23/04 17:10:35.793
<143>M3:
192.168.0.4 23/04 17:10:35.793
<143>M1: gateway ip: 192.168.0.1
192.168.0.2 23/04 17:10:35.793
<143>M1: dns servers(1): 192.168.0.2 23/04 17:10:35.793
<143>M1: 192.168.0.1 192.168.0.2 23/04 17:10:35.793
<143>M1:
192.168.0.2 23/04 17:10:35.793
<159>M3: mslink server task up (3)
192.168.0.4 23/04 17:10:37.493
<159>M1: mslink server task up (1)
192.168.0.2 23/04 17:10:37.533
<159>M1: IDBG: st-0
192.168.0.2 23/04 17:10:38.203
<159>M1: fs:008275:008693:131072
192.168.0.2 23/04 17:10:38.303
<159>M1: fls:af:1:0:0
192.168.0.2 23/04 17:10:38.303
<159>M1: fbr:0:3000:3000:03985:0002:0001:6.1.12
192.168.0.2 23/04 17:10:38.303
<159>M1: PLKUP: 8192, 2102, 12, 1.5
192.168.0.2 23/04 17:10:38.333
<159>M1: fu:0:3997, 0003 0001
192.168.0.2 23/04 17:10:38.483
<159>M2: IDBG: st-0
192.168.0.3 23/04 17:10:39.093
<159>M2: fs:008200:008342:131072
192.168.0.3 23/04 17:10:39.193
<159>M2: fls:af:1:0:0
192.168.0.3 23/04 17:10:39.193
<159>M2: fbr:0:3000:3000:0358b:0002:0001:6.1.12
192.168.0.3 23/04 17:10:39.193
<159>M2: PLKUP: 8192, 2102, 12, 1.5
192.168.0.3 23/04 17:10:39.223
<159>M2: fu:0:359d, 0003 0001
192.168.0.3 23/04 17:10:39.373
<159>M2: mslink client task (2) gw=192.168.0.1 ip=192.168.0.3
192.168.0.3 23/04 17:10:39.423
<159>M0: MSLINK module 2 is at 192.168.0.3
192.168.0.1 23/04 17:10:40.164
<159>M3: IDBG: st-0
192.168.0.4 23/04 17:10:40.174
<159>M0: MSLINK code module 2: 0(32) sn:0
192.168.0.1 23/04 17:10:40.214
<159>M3: fs:008200:008351:131072
192.168.0.4 23/04 17:10:40.254
<159>M3: fls:af:1:0:0
192.168.0.4 23/04 17:10:40.264
<159>M3: fbr:0:3000:3000:04219:0002:0001:6.1.12
192.168.0.4 23/04 17:10:40.264
<159>M3: PLKUP: 8192, 2102, 12, 1.5
192.168.0.4 23/04 17:10:40.284
<159>M3: fu:0:422b, 0003 0001
192.168.0.4 23/04 17:10:40.444
<159>M3: mslink client task (3) gw=192.168.0.1 ip=192.168.0.4
192.168.0.4 23/04 17:10:42.484
<159>M1: mslink client task (1) gw=192.168.0.1 ip=192.168.0.2
192.168.0.2 23/04 17:10:42.524
<159>M0: MSLINK module 3 is at 192.168.0.4
192.168.0.1 23/04 17:10:43.234
<159>M0: MSLINK module 1 is at 192.168.0.2
192.168.0.1 23/04 17:10:43.374
<159>M0: MSLINK code module 3: 0(32) sn:0
192.168.0.1 23/04 17:10:43.374
<159>M0: MSLINK code module 1: 0(32) sn:0
192.168.0.1 23/04 17:10:43.864
<159>M0: fs:025125:025125:131072
192.168.0.1 23/04 17:10:47.215
<159>M0: fls:af:1:0:0
192.168.0.1 23/04 17:10:47.215
<159>M0: fbr:1:3000:3000:17329:0004:0005:6.1.12
192.168.0.1 23/04 17:10:47.215
<159>M0: fhs:01:0:0001:upg:app:0:5.1.10
192.168.0.1 23/04 17:10:47.225
<159>M0: fhs:02:0:0002:upg:app:1:5.1.10
192.168.0.1 23/04 17:10:47.275
<159>M0: fhs:03:0:0003:upg:app:2:5.1.10
192.168.0.1 23/04 17:10:47.315
<159>M0: fhs:04:0:0004:upg:app:0:6.1.12
192.168.0.1 23/04 17:10:47.385
<159>M0: fhs:05:0:0005:upg:app:1:6.1.12
192.168.0.1 23/04 17:10:47.405
<159>M0: fhs:06:0:0006:upg:app:2:6.1.12
192.168.0.1 23/04 17:10:47.435
<159>M0: PLKUP: 8192, 2102, 12, 1.5
192.168.0.1 23/04 17:10:47.525
<159>M0: fu:1:733b, 0003 0001
192.168.0.1 23/04 17:10:47.885
<159>M0: mslink P:12831 V:55495
192.168.0.1 23/04 17:11:00.106
<159>M1: CC_init
192.168.0.2 23/04 17:11:02.516
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:11:02.606
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:11:02.606
<159>M1: IDBG[0]:4
192.168.0.2 23/04 17:11:03.107
<159>M1: IDBG[1]:4
192.168.0.2 23/04 17:11:03.107
<159>M2: CC_init
192.168.0.3 23/04 17:11:03.407
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:11:03.487
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:11:03.497
<159>M2: IDBG[0]:4
192.168.0.3 23/04 17:11:03.997
<159>M2: IDBG[1]:4
192.168.0.3 23/04 17:11:03.997
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.237
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.237
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.237
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.247
<159>M3: CC_init
192.168.0.4 23/04 17:11:04.477
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:11:04.557
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:11:04.567
<159>M3: IDBG[0]:5
192.168.0.4 23/04 17:11:05.057
<159>M3: IDBG[1]:3
192.168.0.4 23/04 17:11:05.057
<159>M0: CC_init
192.168.0.1 23/04 17:11:05.957
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:11:06.517
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:11:06.527
<159>M0: IDBG[0]:6
192.168.0.1 23/04 17:11:07.017
<159>M0: IDBG[1]:4
192.168.0.1 23/04 17:11:07.017
<159>M1: [0]RegFail. Retry in 30
192.168.0.2 23/04 17:11:36.231
<159>M1: [1]RegFail. Retry in 30
192.168.0.2 23/04 17:11:36.241
<151>M1: CID:OSI
192.168.0.2 23/04 17:11:38.231
<151>M1: CID:OSI
192.168.0.2 23/04 17:11:38.241
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:11:38.491
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:11:38.501
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:11:38.792
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:11:38.792
<151>M1: CID:DONE
192.168.0.2 23/04 17:11:39.232
<151>M1: CID:DONE
192.168.0.2 23/04 17:11:39.242
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:11:46.632
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:11:46.632
<143>M0: subnet mask: 255.255.255.255
192.168.0.1 23/04 17:11:46.632
<143>M0: gateway ip: 10.128.1.254
192.168.0.1 23/04 17:11:46.642
<143>M0: dns servers(2): 192.168.0.1 23/04 17:11:46.642
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:11:46.642
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:11:46.642
<143>M0:
192.168.0.1 23/04 17:11:46.652
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.883
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.883
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.883
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.893
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:11:46.933
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:11:46.933
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:11:46.933
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:11:46.943
<134>M0:
192.168.0.1 23/04 17:11:46.943
<134>M0:
192.168.0.1 23/04 17:11:46.943
<134>M0: [pxy]<<127.0.0.1:5060(486)
192.168.0.1 23/04 17:11:46.943
<134>M0: [pxy]<<127.0.0.1:5060(486)
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0: [pxy]->127.0.0.1:5060(395)
192.168.0.1 23/04 17:11:46.953
<134>M0: [pxy]->127.0.0.1:5060(395)
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0: [pxy]<<127.0.0.1:5061(485)
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]<<127.0.0.1:5061(485)
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]->127.0.0.1:5061(394)
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]->127.0.0.1:5061(394)
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<159>M0: [0]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:11:46.963
<159>M0: [1]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]<<127.0.0.1:5060(426)
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]<<127.0.0.1:5060(426)
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]<<127.0.0.1:5061(426)
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]<<127.0.0.1:5061(426)
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->127.0.0.1:5061(363)
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->127.0.0.1:5061(363)
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<151>M0: [0]SubOK
192.168.0.1 23/04 17:11:46.983
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:11:46.993
<151>M0: [1]SubOK
192.168.0.1 23/04 17:11:46.993
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5060(352)
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5060(352)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5061(352)
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5061(352)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:47.003
<134>M0:
192.168.0.1 23/04 17:11:47.003
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:11:47.053
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:11:47.053
<134>M0:
192.168.0.1 23/04 17:11:47.053
<134>M0:
192.168.0.1 23/04 17:11:47.063
<159>M0: [2]RegOK. NextReg in 594 (1)
192.168.0.1 23/04 17:11:47.063
<151>M0: CID:OSI
192.168.0.1 23/04 17:11:48.973
<151>M0: CID:OSI
192.168.0.1 23/04 17:11:48.983
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:11:49.233
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:11:49.243
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:11:49.533
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:11:49.543
<151>M0: CID:DONE
192.168.0.1 23/04 17:11:49.983
<151>M0: CID:DONE
192.168.0.1 23/04 17:11:49.993
<134>M0: [pxy]<<192.168.0.2:5160(487)
192.168.0.1 23/04 17:12:06.235
<134>M0: [pxy]<<192.168.0.2:5160(487)
192.168.0.1 23/04 17:12:06.235
<134>M0:
192.168.0.1 23/04 17:12:06.235
<134>M0:
192.168.0.1 23/04 17:12:06.235
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:12:06.245
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:12:06.245
<134>M0:
192.168.0.1 23/04 17:12:06.245
<134>M0:
192.168.0.1 23/04 17:12:06.255
<134>M0: [pxy]<<192.168.0.2:5161(487)
192.168.0.1 23/04 17:12:06.255
<134>M0: [pxy]<<192.168.0.2:5161(487)
192.168.0.1 23/04 17:12:06.255
<134>M0:
192.168.0.1 23/04 17:12:06.255
<134>M0:
192.168.0.1 23/04 17:12:06.265
<159>M1: [0]RegOK. NextReg in 2130706430 (1)
192.168.0.2 23/04 17:12:06.265
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:12:06.265
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<134>M0: [pxy]<<192.168.0.2:5160(426)
192.168.0.1 23/04 17:12:06.275
<134>M0: [pxy]<<192.168.0.2:5160(426)
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<159>M1: [1]RegOK. NextReg in 2130706430 (1)
192.168.0.2 23/04 17:12:06.275
<134>M0: [pxy]->192.168.0.2:5160(363)
192.168.0.1 23/04 17:12:06.275
<134>M0: [pxy]->192.168.0.2:5160(363)
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0: [pxy]->10.128.1.4:5160(464)
192.168.0.1 23/04 17:12:06.285
<134>M0: [pxy]->10.128.1.4:5160(464)
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<151>M1: [0]SubOK
192.168.0.2 23/04 17:12:06.285
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:12:06.285
<134>M0: [pxy]<<192.168.0.2:5161(427)
192.168.0.1 23/04 17:12:06.285
<134>M0: [pxy]<<192.168.0.2:5161(427)
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]->192.168.0.2:5161(364)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]->192.168.0.2:5161(364)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<151>M1: [1]SubOK
192.168.0.2 23/04 17:12:06.295
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:12:06.295
<134>M0: [pxy]->10.128.1.4:5161(464)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]->10.128.1.4:5161(464)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5161(353)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5161(353)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.305
<134>M0:
192.168.0.1 23/04 17:12:06.305
<151>M0: IDBG: pppld
192.168.0.1 23/04 17:12:26.798
<151>M0: [2]SIP:ICMP Error -1 (7dfe3007:5060, 8)
192.168.0.1 23/04 17:21:41.045
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:21:41.045
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:21:41.045
<134>M0:
192.168.0.1 23/04 17:21:41.045
<134>M0:
192.168.0.1 23/04 17:21:41.045
<159>M0: RSE_DEBUG: getting alternate from domain:sip.siptest.com
192.168.0.1 23/04 17:21:41.055
<159>M0: [2]RegFail. Retry in 30
192.168.0.1 23/04 17:21:41.055
<151>M0: [2]SIP:ICMP Error -1 (7dfe3007:5060, 8)
192.168.0.1 23/04 17:22:11.049
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:22:11.059
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:22:11.069
<134>M0:
192.168.0.1 23/04 17:22:11.069
<134>M0:
192.168.0.1 23/04 17:22:11.069
<159>M0: RSE_DEBUG: getting alternate from domain:sip.siptest.com
192.168.0.1 23/04 17:22:11.069
<159>M0: [2]RegFail. Retry in 30
192.168.0.1 23/04 17:22:11.069
core-rtr#
Apr 23 07:12:28.636: %LINK-3-UPDOWN: Interface Virtual-Access78, changed state to down
Apr 23 07:12:29.636: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access78, changed state to down
Apr 23 07:12:33.688: ppp261 PPP: Authorization required
Apr 23 07:12:33.692: ppp261 PPP: Authorization required
Apr 23 07:12:33.732: ppp261 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:33.776: ppp261 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:33.776: ppp261 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:35.776: ppp261 PPP: Received LOGIN Response FAIL
Apr 23 07:12:35.776: ppp261 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
Apr 23 07:12:37.788: ppp262 PPP: Authorization required
Apr 23 07:12:37.788: ppp262 PPP: Authorization required
Apr 23 07:12:37.832: ppp262 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:37.872: ppp262 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:37.872: ppp262 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:39.872: ppp262 PPP: Received LOGIN Response FAIL
Apr 23 07:12:39.872: ppp262 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
Apr 23 07:12:41.880: ppp263 PPP: Authorization required
Apr 23 07:12:41.880: ppp263 PPP: Authorization required
Apr 23 07:12:41.924: ppp263 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:41.964: ppp263 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:41.964: ppp263 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:43.968: ppp263 PPP: Received LOGIN Response FAIL
Apr 23 07:12:43.968: ppp263 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
Apr 23 07:12:45.980: ppp264 PPP: Authorization required
Apr 23 07:12:45.980: ppp264 PPP: Authorization required
Apr 23 07:12:46.020: ppp264 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:46.064: ppp264 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:46.064: ppp264 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:48.064: ppp264 PPP: Received LOGIN Response FAIL
Apr 23 07:12:48.064: ppp264 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
core-rtr#
Here is the log from a successful reauthentication AFTER the modem/NTU had lost connectivity to the network:
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:26:12.220
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:26:12.220
<143>M1: subnet mask: 255.255.255.0
192.168.0.2 23/04 17:26:12.220
<143>M1: gateway ip: 192.168.0.1
192.168.0.2 23/04 17:26:12.220
<143>M1: dns servers(1): 192.168.0.2 23/04 17:26:12.220
<143>M1: 192.168.0.1 192.168.0.2 23/04 17:26:12.220
<143>M1:
192.168.0.2 23/04 17:26:12.220
<159>M1: mslink server task up (1)
192.168.0.2 23/04 17:26:12.290
<159>M0: IDBG: st-0
192.168.0.1 23/04 17:26:12.430
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:26:14.390
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:26:14.390
<143>M3: subnet mask: 255.255.255.0
192.168.0.4 23/04 17:26:14.390
<143>M3: gateway ip: 192.168.0.1
192.168.0.4 23/04 17:26:14.390
<143>M3: dns servers(1): 192.168.0.4 23/04 17:26:14.400
<143>M3: 192.168.0.1 192.168.0.4 23/04 17:26:14.400
<143>M3:
192.168.0.4 23/04 17:26:14.400
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:26:14.400
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:26:14.400
<143>M2: subnet mask: 255.255.255.0
192.168.0.3 23/04 17:26:14.400
<143>M2: gateway ip: 192.168.0.1
192.168.0.3 23/04 17:26:14.400
<143>M2: dns servers(1): 192.168.0.3 23/04 17:26:14.400
<143>M2: 192.168.0.1 192.168.0.3 23/04 17:26:14.400
<143>M2:
192.168.0.3 23/04 17:26:14.400
<159>M2: mslink server task up (2)
192.168.0.3 23/04 17:26:16.190
<159>M3: mslink server task up (3)
192.168.0.4 23/04 17:26:16.260
<159>M1: mslink client task (1) gw=192.168.0.1 ip=192.168.0.2
192.168.0.2 23/04 17:26:16.280
<159>M0: MSLINK module 1 is at 192.168.0.2
192.168.0.1 23/04 17:26:17.010
<159>M0: MSLINK code module 1: 0(32) sn:0
192.168.0.1 23/04 17:26:17.060
<159>M1: IDBG: st-0
192.168.0.2 23/04 17:26:18.240
<159>M1: fs:008275:008693:131072
192.168.0.2 23/04 17:26:18.330
<159>M1: fls:af:1:0:0
192.168.0.2 23/04 17:26:18.330
<159>M1: fbr:0:3000:3000:03997:0002:0001:6.1.12
192.168.0.2 23/04 17:26:18.330
<159>M1: PLKUP: 8192, 2102, 12, 1.5
192.168.0.2 23/04 17:26:18.370
<159>M1: fu:0:39a9, 0003 0001
192.168.0.2 23/04 17:26:18.540
<159>M2: IDBG: st-0
192.168.0.3 23/04 17:26:18.860
<159>M2: fs:008200:008342:131072
192.168.0.3 23/04 17:26:18.960
<159>M2: fls:af:1:0:0
192.168.0.3 23/04 17:26:18.960
<159>M2: fbr:0:3000:3000:0359d:0002:0001:6.1.12
192.168.0.3 23/04 17:26:18.960
<159>M2: PLKUP: 8192, 2102, 12, 1.5
192.168.0.3 23/04 17:26:18.990
<159>M2: fu:0:35af, 0003 0001
192.168.0.3 23/04 17:26:19.150
<159>M3: IDBG: st-0
192.168.0.4 23/04 17:26:19.931
<159>M3: fs:008200:008351:131072
192.168.0.4 23/04 17:26:20.021
<159>M3: fls:af:1:0:0
192.168.0.4 23/04 17:26:20.021
<159>M3: fbr:0:3000:3000:0422b:0002:0001:6.1.12
192.168.0.4 23/04 17:26:20.021
<159>M3: PLKUP: 8192, 2102, 12, 1.5
192.168.0.4 23/04 17:26:20.051
<159>M3: fu:0:423d, 0003 0001
192.168.0.4 23/04 17:26:20.211
<159>M3: mslink client task (3) gw=192.168.0.1 ip=192.168.0.4
192.168.0.4 23/04 17:26:20.251
<159>M0: MSLINK module 3 is at 192.168.0.4
192.168.0.1 23/04 17:26:20.991
<159>M0: MSLINK code module 3: 0(32) sn:0
192.168.0.1 23/04 17:26:21.041
<159>M2: mslink client task (2) gw=192.168.0.1 ip=192.168.0.3
192.168.0.3 23/04 17:26:21.181
<159>M0: MSLINK module 2 is at 192.168.0.3
192.168.0.1 23/04 17:26:22.262
<159>M0: MSLINK code module 2: 0(32) sn:0
192.168.0.1 23/04 17:26:22.332
<159>M0: fs:025125:025125:131072
192.168.0.1 23/04 17:26:26.852
<159>M0: fls:af:1:0:0
192.168.0.1 23/04 17:26:26.852
<159>M0: fbr:1:3000:3000:1733b:0004:0005:6.1.12
192.168.0.1 23/04 17:26:26.852
<159>M0: fhs:01:0:0001:upg:app:0:5.1.10
192.168.0.1 23/04 17:26:26.852
<159>M0: fhs:02:0:0002:upg:app:1:5.1.10
192.168.0.1 23/04 17:26:26.882
<159>M0: fhs:03:0:0003:upg:app:2:5.1.10
192.168.0.1 23/04 17:26:26.922
<159>M0: fhs:04:0:0004:upg:app:0:6.1.12
192.168.0.1 23/04 17:26:26.962
<159>M0: fhs:05:0:0005:upg:app:1:6.1.12
192.168.0.1 23/04 17:26:26.992
<159>M0: fhs:06:0:0006:upg:app:2:6.1.12
192.168.0.1 23/04 17:26:27.032
<159>M0: PLKUP: 8192, 2102, 12, 1.5
192.168.0.1 23/04 17:26:27.132
<159>M0: fu:1:734d, 0003 0001
192.168.0.1 23/04 17:26:27.442
<159>M0: mslink P:12222 V:58850
192.168.0.1 23/04 17:26:39.354
<159>M1: CC_init
192.168.0.2 23/04 17:26:42.275
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:26:42.355
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:26:42.355
<159>M1: IDBG[0]:4
192.168.0.2 23/04 17:26:42.845
<159>M1: IDBG[1]:4
192.168.0.2 23/04 17:26:42.845
<159>M2: CC_init
192.168.0.3 23/04 17:26:43.175
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:26:43.255
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:26:43.255
<159>M2: IDBG[0]:4
192.168.0.3 23/04 17:26:43.745
<159>M2: IDBG[1]:3
192.168.0.3 23/04 17:26:43.745
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<159>M3: CC_init
192.168.0.4 23/04 17:26:44.245
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:26:44.325
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:26:44.325
<159>M3: IDBG[0]:5
192.168.0.4 23/04 17:26:44.815
<159>M3: IDBG[1]:4
192.168.0.4 23/04 17:26:44.815
<159>M0: CC_init
192.168.0.1 23/04 17:26:45.715
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:26:46.275
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:26:46.275
<159>M0: IDBG[0]:6
192.168.0.1 23/04 17:26:46.755
<159>M0: IDBG[1]:4
192.168.0.1 23/04 17:26:46.765
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:27:13.110
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:27:13.110
<143>M0: subnet mask: 255.255.255.255
192.168.0.1 23/04 17:27:13.120
<143>M0: gateway ip: 125.254.48.254
192.168.0.1 23/04 17:27:13.120
<143>M0: dns servers(2): 192.168.0.1 23/04 17:27:13.120
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:27:13.120
<143>M0: 4.2.2.2 192.168.0.1 23/04 17:27:13.120
<143>M0:
192.168.0.1 23/04 17:27:13.120
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:27:13.420
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:27:13.420
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:27:13.420
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]<<127.0.0.1:5060(485)
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]<<127.0.0.1:5060(485)
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]->127.0.0.1:5060(394)
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]->127.0.0.1:5060(394)
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]<<127.0.0.1:5061(486)
192.168.0.1 23/04 17:27:13.430
<134>M0: [pxy]<<127.0.0.1:5061(486)
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<134>M0: [pxy]->127.0.0.1:5061(395)
192.168.0.1 23/04 17:27:13.430
<134>M0: [pxy]->127.0.0.1:5061(395)
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<159>M0: [0]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:27:13.430
<159>M0: [1]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:27:13.440
<134>M0: [pxy]<<127.0.0.1:5060(433)
192.168.0.1 23/04 17:27:13.440
<134>M0: [pxy]<<127.0.0.1:5060(433)
192.168.0.1 23/04 17:27:13.440
<134>M0:
192.168.0.1 23/04 17:27:13.440
<134>M0:
192.168.0.1 23/04 17:27:13.440
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]<<127.0.0.1:5061(425)
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]<<127.0.0.1:5061(425)
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->127.0.0.1:5061(362)
192.168.0.1 23/04 17:27:13.460
<134>M0: [pxy]->127.0.0.1:5061(362)
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:27:13.460
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<151>M0: [0]SubOK
192.168.0.1 23/04 17:27:13.460
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:27:13.460
<151>M0: [1]SubOK
192.168.0.1 23/04 17:27:13.470
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:27:13.470
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:27:13.470
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:27:13.470
<134>M0:
192.168.0.1 23/04 17:27:13.470
<134>M0:
192.168.0.1 23/04 17:27:13.470
<134>M0: [pxy]<<127.0.0.1:5060(351)
192.168.0.1 23/04 17:27:13.480
<134>M0: [pxy]<<127.0.0.1:5060(351)
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0: [pxy]<<127.0.0.1:5061(350)
192.168.0.1 23/04 17:27:13.480
<134>M0: [pxy]<<127.0.0.1:5061(350)
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:27:13.480
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:27:13.550
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:27:13.550
<134>M0:
192.168.0.1 23/04 17:27:13.550
<134>M0:
192.168.0.1 23/04 17:27:13.550
<159>M0: [2]RegOK. NextReg in 594 (1)
192.168.0.1 23/04 17:27:13.550
<151>M0: CID:OSI
192.168.0.1 23/04 17:27:15.460
<151>M0: CID:OSI
192.168.0.1 23/04 17:27:15.460
<134>M0: [pxy]<<192.168.0.2:5160(486)
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]<<192.168.0.2:5160(486)
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]<<192.168.0.2:5161(486)
192.168.0.1 23/04 17:27:15.490
<134>M0: [pxy]<<192.168.0.2:5161(486)
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<159>M1: [0]RegOK. NextReg in 2130706400 (31)
192.168.0.2 23/04 17:27:15.490
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:27:15.490
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<134>M0: [pxy]<<192.168.0.2:5160(427)
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]<<192.168.0.2:5160(427)
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<159>M1: [1]RegOK. NextReg in 2130706400 (31)
192.168.0.2 23/04 17:27:15.500
<134>M0: [pxy]->192.168.0.2:5160(364)
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]->192.168.0.2:5160(364)
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]->10.128.1.4:5160(463)
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]->10.128.1.4:5160(463)
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<151>M1: [0]SubOK
192.168.0.2 23/04 17:27:15.500
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:27:15.510
<134>M0: [pxy]<<192.168.0.2:5161(426)
192.168.0.1 23/04 17:27:15.510
<134>M0: [pxy]<<192.168.0.2:5161(426)
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<134>M0: [pxy]->192.168.0.2:5161(363)
192.168.0.1 23/04 17:27:15.510
<134>M0: [pxy]->192.168.0.2:5161(363)
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<151>M1: [1]SubOK
192.168.0.2 23/04 17:27:15.510
<134>M0: [pxy]->10.128.1.4:5161(463)
192.168.0.1 23/04 17:27:15.510
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:27:15.510
<134>M0: [pxy]->10.128.1.4:5161(463)
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5161(352)
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5161(352)
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:27:15.720
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:27:15.720
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:27:16.020
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:27:16.030
<151>M0: CID:DONE
192.168.0.1 23/04 17:27:16.470
<151>M0: CID:DONE
192.168.0.1 23/04 17:27:16.470
<151>M1: CID:OSI
192.168.0.2 23/04 17:27:17.500
<151>M1: CID:OSI
192.168.0.2 23/04 17:27:17.510
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:27:17.760
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:27:17.770
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:27:18.060
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:27:18.070
<151>M1: CID:DONE
192.168.0.2 23/04 17:27:18.510
<151>M1: CID:DONE
192.168.0.2 23/04 17:27:18.520
<159>M0: system request reboot
192.168.0.1 23/04 17:28:04.277
<159>M0: fu:1:7380, 0038 0049 043c 0445 0001
192.168.0.1 23/04 17:28:07.347
<151>M0: IDBG: pppld
192.168.0.1 23/04 17:28:07.357
<159>M0: fu:1:742e, 03e4 05b0 0001
192.168.0.1 23/04 17:28:07.437
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:28:22.570
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:28:22.570
<143>M1: subnet mask: 255.255.255.0
192.168.0.2 23/04 17:28:22.570
<143>M1: gateway ip: 192.168.0.1
192.168.0.2 23/04 17:28:22.570
<143>M1: dns servers(1): 192.168.0.2 23/04 17:28:22.580
<143>M1: 192.168.0.1 192.168.0.2 23/04 17:28:22.580
<143>M1:
192.168.0.2 23/04 17:28:22.580
<159>M0: IDBG: st-0
192.168.0.1 23/04 17:28:22.690
<159>M1: mslink server task up (1)
192.168.0.2 23/04 17:28:24.560
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:28:25.620
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:28:25.620
<143>M2: subnet mask: 255.255.255.0
192.168.0.3 23/04 17:28:25.620
<143>M2: gateway ip: 192.168.0.1
192.168.0.3 23/04 17:28:25.620
<143>M2: dns servers(1): 192.168.0.3 23/04 17:28:25.630
<143>M2: 192.168.0.1 192.168.0.3 23/04 17:28:25.630
<143>M2:
192.168.0.3 23/04 17:28:25.630
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:28:25.630
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:28:25.630
<143>M3: subnet mask: 255.255.255.0
192.168.0.4 23/04 17:28:25.630
<143>M3: gateway ip: 192.168.0.1
192.168.0.4 23/04 17:28:25.630
<143>M3: dns servers(1): 192.168.0.4 23/04 17:28:25.640
<143>M3: 192.168.0.1 192.168.0.4 23/04 17:28:25.640
<143>M3:
192.168.0.4 23/04 17:28:25.640
<159>M2: mslink server task up (2)
192.168.0.3 23/04 17:28:27.451
<159>M3: mslink server task up (3)
192.168.0.4 23/04 17:28:27.521
<159>M1: IDBG: st-0
192.168.0.2 23/04 17:28:28.221
<159>M1: fs:008275:008693:131072
192.168.0.2 23/04 17:28:28.321
<159>M1: fls:af:1:0:0
192.168.0.2 23/04 17:28:28.331
<159>M1: fbr:0:3000:3000:039a9:0002:0001:6.1.12
192.168.0.2 23/04 17:28:28.331
<159>M1: PLKUP: 8192, 2102, 12, 1.5
192.168.0.2 23/04 17:28:28.351
<159>M1: fu:0:39bb, 0003 0001
192.168.0.2 23/04 17:28:28.511
<159>M1: mslink client task (1) gw=192.168.0.1 ip=192.168.0.2
192.168.0.2 23/04 17:28:28.541
<159>M2: IDBG: st-0
192.168.0.3 23/04 17:28:29.121
<159>M2: fs:008200:008342:131072
192.168.0.3 23/04 17:28:29.221
<159>M2: fls:af:1:0:0
192.168.0.3 23/04 17:28:29.221
<159>M2: fbr:0:3000:3000:035af:0002:0001:6.1.12
192.168.0.3 23/04 17:28:29.221
<159>M2: PLKUP: 8192, 2102, 12, 1.5
192.168.0.3 23/04 17:28:29.241
<159>M0: MSLINK module 1 is at 192.168.0.2
192.168.0.1 23/04 17:28:29.291
<159>M0: MSLINK code module 1: 0(32) sn:0
192.168.0.1 23/04 17:28:29.341
<159>M2: fu:0:35c1, 0003 0001
192.168.0.3 23/04 17:28:29.401
<159>M3: IDBG: st-0
192.168.0.4 23/04 17:28:30.191
<159>M3: fs:008200:008351:131072
192.168.0.4 23/04 17:28:30.281
<159>M3: fls:af:1:0:0
192.168.0.4 23/04 17:28:30.291
<159>M3: fbr:0:3000:3000:0423d:0002:0001:6.1.12
192.168.0.4 23/04 17:28:30.291
<159>M3: PLKUP: 8192, 2102, 12, 1.5
192.168.0.4 23/04 17:28:30.311
<159>M3: fu:0:424f, 0003 0001
192.168.0.4 23/04 17:28:30.471
<159>M2: mslink client task (2) gw=192.168.0.1 ip=192.168.0.3
192.168.0.3 23/04 17:28:31.441
<159>M0: MSLINK module 2 is at 192.168.0.3
192.168.0.1 23/04 17:28:32.261
<159>M0: MSLINK code module 2: 0(32) sn:0
192.168.0.1 23/04 17:28:32.461
<159>M3: mslink client task (3) gw=192.168.0.1 ip=192.168.0.4
192.168.0.4 23/04 17:28:32.511
<159>M0: MSLINK module 3 is at 192.168.0.4
192.168.0.1 23/04 17:28:33.431
<159>M0: MSLINK code module 3: 0(32) sn:0
192.168.0.1 23/04 17:28:34.211
<159>M0: fs:025278:025278:131072
192.168.0.1 23/04 17:28:37.382
<159>M0: fls:af:1:0:0
192.168.0.1 23/04 17:28:37.382
<159>M0: fbr:1:3000:3000:1742e:0004:0005:6.1.12
192.168.0.1 23/04 17:28:37.382
<159>M0: fhs:01:0:0001:upg:app:0:5.1.10
192.168.0.1 23/04 17:28:37.382
<159>M0: fhs:02:0:0002:upg:app:1:5.1.10
192.168.0.1 23/04 17:28:37.422
<159>M0: fhs:03:0:0003:upg:app:2:5.1.10
192.168.0.1 23/04 17:28:37.482
<159>M0: fhs:04:0:0004:upg:app:0:6.1.12
192.168.0.1 23/04 17:28:37.542
<159>M0: fhs:05:0:0005:upg:app:1:6.1.12
192.168.0.1 23/04 17:28:37.592
<159>M0: fhs:06:0:0006:upg:app:2:6.1.12
192.168.0.1 23/04 17:28:37.632
<159>M0: PLKUP: 8192, 2102, 12, 1.5
192.168.0.1 23/04 17:28:37.692
<159>M0: fu:1:7440, 0003 0001
192.168.0.1 23/04 17:28:38.182
<159>M0: mslink P:12378 V:53243
192.168.0.1 23/04 17:28:50.064
<159>M1: CC_init
192.168.0.2 23/04 17:28:52.534
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:28:52.614
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:28:52.624
<159>M1: IDBG[0]:4
192.168.0.2 23/04 17:28:53.124
<159>M1: IDBG[1]:3
192.168.0.2 23/04 17:28:53.124
<159>M2: CC_init
192.168.0.3 23/04 17:28:53.434
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:28:53.514
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:28:53.524
<159>M2: IDBG[0]:4
192.168.0.3 23/04 17:28:54.024
<159>M2: IDBG[1]:3
192.168.0.3 23/04 17:28:54.024
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.254
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.254
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.254
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.264
<159>M3: CC_init
192.168.0.4 23/04 17:28:54.504
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:28:54.584
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:28:54.594
<159>M3: IDBG[0]:4
192.168.0.4 23/04 17:28:55.084
<159>M3: IDBG[1]:3
192.168.0.4 23/04 17:28:55.084
<159>M0: CC_init
192.168.0.1 23/04 17:28:55.965
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:28:56.525
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:28:56.525
<159>M0: fu:1:7455, 03e4 05b0 0001
192.168.0.1 23/04 17:28:56.605
<159>M0: IDBG[0]:6
192.168.0.1 23/04 17:28:57.025
<159>M0: IDBG[1]:4
192.168.0.1 23/04 17:28:57.025
<134>M0: System started: [email protected], reboot reason:C200
192.168.0.1 23/04 17:29:23.348
<134>M0: System started: [email protected], reboot reason:C200
192.168.0.1 23/04 17:29:23.348
<143>M0: subnet mask: 255.255.255.255
192.168.0.1 23/04 17:29:23.348
<143>M0: gateway ip: 10.128.1.254
192.168.0.1 23/04 17:29:23.358
<143>M0: dns servers(2): 192.168.0.1 23/04 17:29:23.358
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:29:23.358
<143>M0: 4.2.2.2 192.168.0.1 -
Network Extender Not Working - AGAIN!!!
Hello - our extender has been down for over 24 hours. Like everyone else and every other time before that this has happened (more and more frequently) I have disconnected and rebooted all routers and modems on my system. It is not my extender. Nothing has changed. by chance is there an outage somewhere???
Hi Pharris,
Yikes! Frequent disconnects are no good! Its important to have properly work equipment at all times. Let's get this fixed. Disconnect the power supply from the Network Extender for 30 seconds then reconnect the power supply. Note: Allow up to 20 minutes for the Network Extender to complete the startup sequence and detect both its connections and communications. Next, Ensure the GPS antenna is connected. Keep me posted!
Thanks,
Pamelaf_vzw
Tweet us@ vzwsupport -
Anybody getting a solution from Verizon to replacing Network Extender?
Our Network Extender quit working one day short of our one year warranty on August 21st, 2013. We still do not have a replacement or any assurance of a replacement, refund, or any type of solution from Verizon. Where is the customer support?
For RTR15! above:
Suggest that you call into Verizon tech support. They have a whole group that works on supporting these things. When I was having problems, I spent some time on the phone with the tech support folks and found them to be helpful and responsive. My problem turned out to be a router problem.
One thing to try when you have a problem with a Network Extender, that happened to fix my particular problem (for what it's worth), is to reset your router to factory defaults (also known as "clearing the nvram"), and then manually re-enter your router's settings. If there's newer firmware to try, you could also upgrade your firmware, but remember to the reset to factory defaults AFTER upgrading, and to manually re-enter your settings.
Good luck. -
In iCal I have double October 2012 (one instead of November) and no have March in 2013. Why?
In iCal I have 2 October 2012 (one instead of November) and no have March in 2013.
Mac Ox 10.5.8, iCal 3.0.8 (1287), Russian locale
So seems that other month's names moved
So now in Ical ( month view) i have: October, October, November, December, January, February, April
moreover( оr as result) in February ICal shows 30 daysHi Satish,
In the css file, you should have a 'text-align' property set to 'center' for the BEx Table cell element. I'm not sure of the exact element name, maybe you can check. Also check if you can open the file in notepad if the MS VS format is not ok with you.
--Priya -
IPhone 4 and network extender troubles
I live in an area where I need a network extender to receive a signal. All has worked perfectly fine in the last 4 years I've been with Verizon, until about 4 weeks ago when my daughter was trying to send me pictures that I never received. I then noticed a picture I had sent her didn't go through either. I'm usually connected to wifi, but when I'm not and try to access the internet it says "could not activate cellular date network". I have tried every suggestion I could find on the internet from other people who have had this issue with no luck, and I do mean everything from toggling off and on this and that, to taking my phone back to factory settings, which by the way, even with no back up and just adding one picture and one contact this issue exists. When I'm in a 3G area I have cellular data and the phone works fine, including being able to send and receive pictures and being able to access the internet, so I have no reason to believe it's the phone or the settings. I'm thinking it has something to do with the network extender not playing nice with my iPhone because my husbands Android is able to send and receive pictures and access the internet with no problems. I would also like to note that about 2 weeks ago I contacted support to see if they had any news, the tech tried sending me a picture which I did just randomly receive about 2-3 hours later, along with a picture my daughter had sent me earlier in the day. I asked her to send me another one which I got, but after that I tried sending her a picture and the problem was back.
I have been in contact with technical support and network support, who haven't really helped me. I don't think they know what the problem is so they just ignore me, as it's been 8 days since I've heard from them. I think 4 weeks is plenty of time to at least narrow it down. On my first ticket they asked me to run a speed test, which I did and they were going to check the towers. They called me on my cell, but I missed the call, thanks for leaving that VM though, no cellular data=no VM, so I didn't know until days later you left a message saying no problems were found. So I had to start over again, two weeks since the problem started. On my second ticket they said they didn't do the first ticket right, a week later they called back asking for another speed test, which came back above minimum requirements, they were going to pass it on to network support and here I wait 8 days later, 4 weeks total with no end in sight.
Today I stopped at the Verizon store hoping they'd have some suggestions. They said they couldn't do anything on their end, I'd have to call technical support...The only thing they told me that was new was something about a security breach with Samsung extenders, and maybe an update was pushed to my extender that's not playing nice with iPhone. But how do I check on something like that, who do I report this to?? If that was the case wouldn't Verizon tech support know about it? I'm not getting any help and I don't feel like anyone at Verizon really cares, but you can bet if my payment was 4 weeks late there'd be an issue.
Any suggestions?How old is the extender? Can it support 1x or both 1x and 3G? Try checking the Network Extender space for more suggestions and similar questions.
-
Any success stories using the Verizon Network Extender? I'm not having much success. I tried setting the VNE up by connecting it to my AirPort Extreme and got blue LED's on power, GPS, and WAN fairly quickly, but the SYS LED was solid red. After an hour with no change I tried connecting the VNE directly to the modem thinking there may have been a conflict between the VNE and the APE. No such luck, in this config both the SYS and WAN LEDs remained red.
I called Verizon Tech support and they had me reconnect the VNE to my APE and once again the SYS LED remained red. I spent several hours on and off the phone with Verizon Tech support running some tests and doing some troubleshooting but didn't get anywhere. The tech finally told me he would need to submit a troubleshooting ticket and that they would get back to me within 24hrs.
My Google search didn't reveal anything concrete either. There were a number of people reporting success using the VNE with APE as well as a number of people reporting problems. The threads were a year or more old and none had any real solutions.
I'd like to here from fellow forum members of their experience with the VNE.Hey chaseyDog,
I am very sorry to hear about your troubles with the Network Extender. I know they do help a lot in terms of your service indoors so I can understand how much you want them to work. It seems like you have done a lot with your NE and we want to make sure it's working properly. Do you have any update on how it is working now? Was there a resolution provided to you from the ticket? Please let us know since we only want the best for you! Thanks!
MichelleG_VZW
Please follow us on Twitter @vzwsupport -
How can I get my 4g phone to reliably and seamlessly talk to my network extender?
I moved a few months ago, and ever since I've had major problems with dropped calls on my phone.
Before, I was on the inside of a large concrete apartment building, and I had the 3g network extender. Because I was near the center of the building, despite the courtyard in the middle, I had no problem connecting to the 3g extender, as there was no meaningful competing signal.
Now, I'm across the street, but on the outside of the building. Calls were able to connect sometimes from within the apartment (without the extender) because there is some cellular coverage. However, we would occasionally drop calls on all three VZW cell phones in the apartment, I reactivated the network extender. This has helped the two other lines (a Stratosphere II/Galaxy Nexus and a Galaxy S4) immensely. However, my phone will consistently drop calls just a few seconds in - excluding the Lumia, which doesn't hit the network extender and therefore seems to drop slightly less often since there is no handoff. I typically see 1-2 bars of signal.
A few of the troubleshooting steps I've tried:
I have gotten a brand new SIM from a VZW corporate store
I hate tried multiple phones - Galaxy S3, Nexus (the same one that another household user has not had any problems with), and a Lumia 822
I have ensured that I'm on the network extender via #48 - I get on the extender on all phones except the Lumia 822, which doesn't drop calls quite as often. This is even the case when I'm connected to LTE on the Android phones; this makes sense, since the extender is 3g/1x only, and all voice calls are over 1x.
I have tried multiple distances between the phone and network extender - both very close (within 3 feet) and farther (15 feet + wall)
I have tried my phone(s) without cases, and typically use a thin TPU rubber case on the galaxy S3.
I hate tried factory resets on all three phones.
I have ensured that my phone number is on the network extender access list.
If I disable LTE (some phones are easier than others; for example the GS3 makes this rather difficult. The menu under Settings > More Settings > Mobile Networks < Network Mode) offers three options: Global, LTE/CDMA, and GSM/UMTS. However, third-party apps can adjust this; for example, "Advanced Signal Status" can (via Addition Info > Device Information). When I set my phone to CDMA only there, I get a solid connection. #48 still tells me I'm on the network extender, and I have 5 bars of signal. I use another app, SignalCheck Lite, to give me solid signal readings.
Signal Measurements:
Galaxy S3, CDMA only (via 3p app), <3 feet from extender
5 Bars, connected to wifi and non-LTE signal, will not drop calls
1xRTT: -61 dBm
EvDo: -72 dBm, SNR 8 dB
LTE: No connection
Wifi: -64 dBm
Galaxy S3, normal LTE/CDMA mode, <3 feet from extender
1 Bar, connected to wifi and presumably LTTE signal, will drop calls FREQUENTLY
1xRTT: -66 dBm
EvDo: No longer shown in app; eHRPD is shown with no connection
LTE -117 dBm, SNR 7dB
Wifi: -67 dBm
Given that the 1xRTT signal is reasonably strong in both cases, my suspicion is that a handoff is occurring incorrectly. It's prioritizing the LTE base station over the extender, despite the large signal discrepancy. My understanding is that a handoff can occur from extender to VZW tower, but not the other way around - so one it has transferred over, it will inevitably drop, often just a few seconds into the call.
However, the 'CDMA only' is not a good solution. Along with not being something normally in the device's settings, this is a major inconvenience - even if it were the settings screen, that's 5+ taps every time I enter or exit my apartment. (Nor can this be automated with a tool like Tasker.)AdaS_VZW,
I'm not sure if the area has been surveyed; it's a large group of apartment buildings about a within a couple miles of Dulles International Airport in Northern Virginia, so I would imagine that it probably has, but I'm not sure. How would I find out?
I understand that the Network Extender does not support LTE connections (I know there are two models, the 1x-only and 3g, both made by Samsung - I have the 3g model, SCS-2U01). I know that it can support a 3G data connection, but that should be irrelevant - I'm always connected to my wifi network in my apartment.
What's particularly vexing, however, is that both a Galaxy S4 and Galaxy Nexus in my apartment (the other lines on my account) do not seem to have this issue. While I haven't done so with the S4, the Nexus exhibits this problem when my SIM is in it - and again, this is a fresh SIM from just a few weeks ago.
I'm currently trying to disable Mobile Data when in the apartment to see if that will make it more stable. I'll post in a day or two with results from that.
Shawn -
Okay, so I cracked my iPhone 5 and just got a new 5s in the mail. I'm using the same number, sim and everything. My latest backup was on March 14th, 2013. My boyfriend uses my Apple ID for a year now but we just recently got each others contacts and now we receive each other's messages. Will we lose that setting if I don't back my phone up before switching new phones? Cause I didn't have that setting before when it was last backed up. If I could back it up I would but I don't have nearly enough storage so that's why I'm asking lol. We want to keep the setting like that so we still get each others contacts and everything
You can always resync the Contacts, Notes, and Messages by signing into those services with the same AppleID once you have the new phone set up.
-
It was a dark and stormy night...
For the past eight years, I had been happy with Verizon wireless service. Great coverage and rarely a dropped call. However, all of that changed when I moved into a lovely mid-century modern condominium. The solid concrete walls and ceilings were blocking my attempts to communicate with the outside world (i.e. order pizza).
Enter the Verizon Wireless Network Extender! My own personal cell tower! Alas, the VWNE was $250, which was a lot of money. So, being the resourceful recycling advocate that I am, I procured a refurbished one and hooked it up to my network. Then I called Verizon to begin what would soon become one of the Bottom 10 Least Enjoyable Experiences in customer service history (note: obvious foreshadowing).
The first technician I spoke with was Benjamin, who was actually quite helpful. He noted the VWNE's MAC address and other information before attempting to allow me to access my unit. But he could not. Why? Apparently the unit was still registered to another Verizon customer. He told me the matter would be forwarded to "Verizon Correspondence Support" who would contact the registered owner and get their approval to reassign the unit.
A week later, I called in to ask about the status of my request, but was told by Darryl (another tech from the VWNE department) that the "Verizon Correspondence Support" department did not exist. Did. Not. Exist? Fine, I explained the situation again, and Darryl eventually told me he would submit a special access form which may resolve the problem. He apologized for the mixup, thanked me for my patience, and told me to wait 24-48 hours for his return call with the results.
120 hours later, I called to ask about the status of the change access form because I had not received a callback. Michelle, another representative of VWNE support, told me there was no record of this form having been submitted. No. Record...? After which, she made no effort to help me after reading through my transcript. In fact, quite the opposite. To paraphrase...
"I'm sorry we wasted two weeks of your time leading you to believe we had a solution. Actually, there is no Verizon Correspondence Department, there is no special access form, and no tech will be calling you back. Furthermore, I will not allow you to use our unit because the previous owner hasn't filled out Release Form 27B stroke 6. For all I know it might have been stolen. Perhaps by you? I guess we'll never know for sure, because I won't contact the owner for any reason. In fact, there is nothing I can do to help you whatsoever. But if you like, feel free to throw our network adapter in a landfill. Thank you and have a nice day."
OK Michelle, here's the deal. I don't even WANT this doohickey. You see, all I want is for my phone to work. That's why I am calling you. To get THIS piece of your equipment working, at my expense, so that I can continue to be a Verizon customer. Seems like I'm doing my part. Why is this so difficult?
"Sorry"
Lesson of the story? DON'T BE A MICHELLE. If a customer is in trouble and you can't solve his/her problem, contact a supervisor and work out an alternative. In my example, perhaps Verizon could have provided me with an "official" VWNE? At a discount? Or have a technician sent out to examine the signal? Really, *anything* is better than being brushed off. After being brushed off.
After being brushed off.Follow up: I acquired another VWNE from a local seller, just in case he had to be contacted for the Nuclear Priority Phone Release Code (geez). Ironically, it wasn't necessary, because said fellow had already left Verizon after too many negative customer service issues. Oops.
The good news is that Verizon was able to properly activate the second unit. I was connected to a VWNE tech named Bertha who was VERY helpful and treated me like a human being. Which made all the difference and restored my faith in humanity. I requested that my story be relayed to upper management so that the hordes of secondhand VWNE buyers wouldn't also get burned by Verizon's "hands off and look elsewhere" policy. Bingo. Finally. Done.
Epilogue: Until Verizon eases up on their needlessly stringent policy, beware the unchecked VWNE! Be sure to get the MAC code and check it with a local store/tech support before buying it. -
Add Cell Phone Network Extender to Apple Network
I am currently running a Time Capsule which gets its internet feed from a cable modem (Cablevision). I am trying to add a mobile phone network extender (Verizon micro cell) which requires an internet connection (via Ethernet cable) to create a cell phone call, since I have no towers in my area.
The Verizon micro cell requires a VPN output from the router; the TC does not support VPN. So the Verizon micro cell does not get an internet connection if I connect it to the TC via one of its ethernet ports. It does connect to the internet if I connect it directly to the cable modem.
APPLE: WHY DOESN'T THE TIME CAPSULE SUPPORT VPN?!? Honestly, enough is enough, I like the plug and play part of Apple equipment, but maybe, just maybe some people need semi-pro utility out of your equipment. End of Rant.
I could buy another cable modem from Cablevision and simply plug the Verison micro cell into that, but it costs $45 per month, so that's out of the question.
I would like to understand whether the solution I've been given from a very helpful Cablevision tech guy will work and how to execute it with minimum disruption to my network (currently the TC feeds an Airport Express elsewhere in the house as a network extender, so I really do mean minimal disruption, please). In essence, it involves cascading the Linksys to the TC.
I am told to connect the cable modem to a router (I have two unused Linksys routers, one wireless and one without WiFi; my preference is to use the non WiFi router so I don't have two wireless signals), and then connect via the Linksys ethernet ports to the Verizon micro cell and the other to the TC. Apparently this is possible if the TC gets a WAN connection, as opposed to a LAN connection, from the Linksys. The micro cell works fine already, so I guess it just doesn't care.
According to Apple, the input that I'm already using, from the cable modem to the TC, is a 1 GB ethernet WAN port for connecting a cable modem. When I cascade the Linksys to the TC, the TC doesn't see an internet connection, though, and it makes sense that there are conflicting IP addresses causing the problem. The port out of the Linksys works fine as if I switch the wiring, the micro cell gets an internet connection no matter what.
Question 1: How do I configure the Linksys so that its output is something the TC can handle? Will the configuration screw up the signal that's going to the micro cell which is already OK?
Question 2: Or what do I do in AirPort Utility to set up the TC to see the signal correctly (ie as a WAN signal) from the Linksys?
Question 3: Is there anything else I need to know?
Despite the "Go Dog, Go" style of writing above, I know my way around configuring Linksys routers, so your reply can be quite technical. Thanks in advance.
HWell, not much telling unless you ask the carrier that you are trying to use. If it will not work with the SIM you are trying to use, there could be any number of reasons with a phone that has not been purchased through an authorized reseller. I'm afraid no one would really be able to answer your question without a lot more information.
-
My Samsung Network Extender worked for years, but no longer works. How do I fix it?!
My Samsung Network Extender worked for years. I switched away from Verizon only to find out it won't work when my phone is on another network. I have since switched back to Verizon and now my Network Extender does not work AT ALL. I will switch away again if this problem is not resolved.
We would be delighted to assist elsdpe! Have you contacted us to readd the Network Extender to your account? If not please contact us directly at 800-922-0204. We look forward to hearing from you soon, thanks!
MatthewS_VZW
Follow us on Twitter @VZWSUPPORT -
Network Extender has never worked
We received a network extender from Verizon due to the lack of coverage in the area we live - too far from a tower.
I have tried every weekend to get this thing going and I always get a solid blue power light, solid blue wan light a SLOW BLINKING RED SYSTEM LIGHT and a solid magenta GPS light.
I tried calling Verizon for support but the tech rep didn't know what to do and was trying to read through the manual, I think and the call dropped after about an hour (back to the lack of coverage issue). I was so tired of not getting anywhere that I just let it go for the evening.
Bottom line is - this thing has never worked. All I can find is that a slow red blinking light is there is an abnormal condition.
Is there any further troubleshooting I can do or do I just need to see if Verizon can send me another one?Update - now I have a solid red GPS light & the slow blinking red SYS light. Will let it sit for an hour (as the sticker on the side suggests) and see if there's any difference
Maybe you are looking for
-
How can i transfer al my data from a Sony laptop to a new macair?
Hoy can i transfer all my data from a Sony laptop to new Mac airé?
-
JWSDP and J2EE Integration: Doesn't work. What's the point?
My problems involve the integration of JWSDP and J2EE as described in these two documents: http://developer.java.sun.com/developer/technicalArticles/WebServices/wsj2ee/ http://java.sun.com/j2ee/documentation/windows_guide.html It looks like a long on
-
Horizontal Spry Menus are not showing up in ANY browser HELP!
www.tvnewsjunkie.com I am a novice web designer and I need help! The above site listed is the site I am currently working on. As you can see the menu bar...is not a menu bar at all but a long list of links along the left side. HOWEVER, when I click o
-
Assignment Feild in Service entry sheet - ML81N
Dear All, We need to add assignment Feild (ZUONR) in Service entry sheet (ML81N). Can any one suggest the posssible solution. Thanks & Regards
-
Installation Problems: OSX Tiger
Hi all, I have a G4 iMac, I had 10.3.9 Panther on there, and I was starting to have some issues with space and computer running slow, and just recently my Quicktime7Pro just stopped working all together. SO... I got myself a 250GB LaCie Disk external