down in toronto now
-
- Just Passing Thru
- Posts: 9
- Joined: 08/25/2010
- SIP Device Name: SPA2102
- ISP Name: teksavvy
- Router: sonicwall
down in toronto now
down in toronto now 9:07pm Sept 29.
-
- One Hit Wonder
- Posts: 1
- Joined: 05/27/2009
down in Ottawa now
Down in Ottawa now at 9:07 pm sep 29
-
- Quiet One
- Posts: 48
- Joined: 01/17/2010
- SIP Device Name: Asterisk/FreePBX
- ISP Name: Acanac Inc.
- Computer OS: Windows 7
- Router: DD-WRT 24 pre-SP2
- Smartphone Model: Nexus 5
- Android Version: 4.4
- Location: Toronto, Ontario
Re: down in toronto now
This isn't regional. Down in London too. Looks like a repeat of Monday night.
-
- Just Passing Thru
- Posts: 6
- Joined: 09/29/2010
Re: down in toronto now
Down in Kitchener/Waterloo
-
- Quiet One
- Posts: 44
- Joined: 09/28/2009
Re: down in toronto now
down in quebec city. 10h30 PM
-
- Just Passing Thru
- Posts: 16
- Joined: 09/11/2009
Re: down in toronto now
Same herelgqyqj wrote:Down in Kitchener/Waterloo
-
- Active Poster
- Posts: 53
- Joined: 08/16/2010
- SIP Device Name: Mediatrix 4102S
- ISP Name: Bell FibeGigabit 940/100 on FTTH
- Computer OS: MacBook Pro OS X 10.10.5 Yosemite
- Router: Sagemcom F@st5850 HH2000
- Smartphone Model: iPhone 6
- iOS Version: iOS 9.0.2
- Location: QuebecCity
Re: down in toronto now
Yet down in Montreal and QuebecCity for the second evening this week... 

-
- Just Passing Thru
- Posts: 9
- Joined: 08/25/2010
- SIP Device Name: SPA2102
- ISP Name: teksavvy
- Router: sonicwall
Re: down in toronto now
no official words on this outage?
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: down in toronto now
Down in the heart of montreal
-
- *Go-To Guy*
- Posts: 532
- Joined: 08/06/2010
- SIP Device Name: Grandstream HT-502
- Firmware Version: 1.0.1.63
- ISP Name: DSL TekSavvy
- Computer OS: OSX Snow Leopard
- Router: Linksys WRT54GL w/tomato
Re: down in toronto now
My ATA complained "Device not registered!" around 6pm today in Montreal.


-
- Site Moderator
- Posts: 2131
- Joined: 07/16/2009
- SIP Device Name: Grandstream 286 & 701
- ISP Name: Worldline.ca
- Computer OS: Windows 7 Ultimate / Mac OS X
- Router: TR1043ND w/ DD-WRT Mega
- Smartphone Model: Galaxy S3
- Android Version: 4.0.4
- Location: Cambridge
Re: down in toronto now
That wouldn't have been us, I just checked the logs and saw quite a few hundred calls going through the server at that timelaurent wrote:My ATA complained "Device not registered!" around 6pm today in Montreal.

Steve
Fongo
Development Support Specialist.
Fongo
Development Support Specialist.
-
- *Go-To Guy*
- Posts: 532
- Joined: 08/06/2010
- SIP Device Name: Grandstream HT-502
- Firmware Version: 1.0.1.63
- ISP Name: DSL TekSavvy
- Computer OS: OSX Snow Leopard
- Router: Linksys WRT54GL w/tomato
Re: down in toronto now
Damn 
I check my phone/ATA about twice a day, and every few days, it's not registered. As soon as I hang up and pickup again, it's registered. Can't find what this annoying problem is.

I check my phone/ATA about twice a day, and every few days, it's not registered. As soon as I hang up and pickup again, it's registered. Can't find what this annoying problem is.
-
- Tried and True
- Posts: 330
- Joined: 09/21/2010
- SIP Device Name: PIAF/Mitel/PolyCom/Cisco
- Firmware Version: Asterisk 1.8
- ISP Name: Rogers
- Computer OS: CentOS/Windows2008/Win7/Android
- Router: pfSense/Neoware thin client
- Location: Ottawa
Re: down in toronto now
Try and lower your sip keepalive timer to around 30 seconds. Maybe your router is closing the port on you?
-
- *Go-To Guy*
- Posts: 532
- Joined: 08/06/2010
- SIP Device Name: Grandstream HT-502
- Firmware Version: 1.0.1.63
- ISP Name: DSL TekSavvy
- Computer OS: OSX Snow Leopard
- Router: Linksys WRT54GL w/tomato
Re: down in toronto now
My Keep-alive interval is already set to 20 seconds. Furthermore, I progressively lowered the registration expiration down to 1 minute (from 60). The occurence of picking up the phone and hearing "Device not registered" are considerably less often now, but it still happens from time to time.
However, as I type this, I notice that the port1 settings page has this:
NAT Tranversal (STUN): No, No but send keep-alive, Yes.
Mine was set to "No." Perhaps the keep-alive settings from the advanced page (the one I said above that was at 20 seconds) is not doing anything unless the NAT traversal is set to "No, but send keep-alive" ?
I'll try that, and see in a week or so if it works. I could lower the registration expiration to provoque the problem I guess.
However, as I type this, I notice that the port1 settings page has this:
NAT Tranversal (STUN): No, No but send keep-alive, Yes.
Mine was set to "No." Perhaps the keep-alive settings from the advanced page (the one I said above that was at 20 seconds) is not doing anything unless the NAT traversal is set to "No, but send keep-alive" ?
I'll try that, and see in a week or so if it works. I could lower the registration expiration to provoque the problem I guess.
-
- Site Moderator
- Posts: 2131
- Joined: 07/16/2009
- SIP Device Name: Grandstream 286 & 701
- ISP Name: Worldline.ca
- Computer OS: Windows 7 Ultimate / Mac OS X
- Router: TR1043ND w/ DD-WRT Mega
- Smartphone Model: Galaxy S3
- Android Version: 4.0.4
- Location: Cambridge
Re: down in toronto now
I believe the keep-alive settings of the Linksys' use a $NOTIFY as a keep-alive. One user here once said that changing this to $PING gave him better success when he had a similar issue.laurent wrote:My Keep-alive interval is already set to 20 seconds. Furthermore, I progressively lowered the registration expiration down to 1 minute (from 60). The occurence of picking up the phone and hearing "Device not registered" are considerably less often now, but it still happens from time to time.
However, as I type this, I notice that the port1 settings page has this:
NAT Tranversal (STUN): No, No but send keep-alive, Yes.
Mine was set to "No." Perhaps the keep-alive settings from the advanced page (the one I said above that was at 20 seconds) is not doing anything unless the NAT traversal is set to "No, but send keep-alive" ?
I'll try that, and see in a week or so if it works. I could lower the registration expiration to provoque the problem I guess.
It's been a while since I've used a Linksys since we transitioned to Grandstream though, so I couldn't tell you off hand where this setting is located in the configuration pages.
Steve
Fongo
Development Support Specialist.
Fongo
Development Support Specialist.
-
- *Go-To Guy*
- Posts: 532
- Joined: 08/06/2010
- SIP Device Name: Grandstream HT-502
- Firmware Version: 1.0.1.63
- ISP Name: DSL TekSavvy
- Computer OS: OSX Snow Leopard
- Router: Linksys WRT54GL w/tomato
Re: down in toronto now
Well Steve, I have a GrandStream HT502. I know this is not the unit you support, but I suspect it should be pretty close to the 286...
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: down in toronto now
I have the 286 and the 502 grandstream and both of mine are registered I get a bit of snowy backgroound when both partes are quite on both machines... i have tried the noice reduction <still no fix> is anyone else experinacing this on there grandstreams?
thanks!
thanks!