| |
[CallCentric] New callcentric issues?Has anyone else experienced callcentric issue yesterday and today?
Yesterday evening for about 4 hours or so, 2 of my 3 ATAs were listed as not-registered and I was unable to make/receives calls.
Today it is working, but voice quality is again spotty?
A trouble ticket to CC has gone unanswered (though you would think being without service is a high priority). |
|
| |
My phones are registered, but call quality is really bad to almost unusable. I also put in a ticket in case my problem was an isolated case and because this seems to be the best way to get info from CC. |
|
| |
to krbvroc1
No problems here (OBi100 with DNS SRV) |
|
 anon
@zoominternet.net |
anon to krbvroc1
Anon
2012-Nov-7 1:24 pm
to krbvroc1
Truthfully I've never ceased to have issues since last month when the DDoS began. After CC got their power back on my devices have consistently been losing registration nearly non-stop and call quality is so poor it's been nearly unusable. |
|
| |
to krbvroc1
No issues at all to report here. 2 lines. |
|
| |
to lacibaci
said by lacibaci:No problems here (OBi100 with DNS SRV)
I am using your configuration with an OBi100 and DNS SRV with zero problems. Keep up the good work Callcentric.... |
|
nonymous (banned)
join:2003-09-08
Glendale, AZ |
to krbvroc1
Maybe some extra delay. |
|
|
| |
to krbvroc1
voice quality issues today.... so bad I had to switch to an alternate provider. |
|
| |
to krbvroc1
I experienced the Callcentric issues too. Their website showed the device as unregistered even though it was registered when I saw the Linksys PAP2. I believe they are still having random issues after this DDoS and the hurricane. I hope they are able to fix them soon. |
|
| |
said by patnitop:I experienced the Callcentric issues too. Their website showed the device as unregistered even though it was registered when I saw the Linksys PAP2.
That is what I saw last evening. Their website said unregistered, phone calls did not work, but my local ATA webpage said registered. My local ATA gave me dialtone, but could not dial out. Oddly, at the time, the two ATA's that failed were using DNS SRV. The one that continued to work was not. |
|
| |
to krbvroc1
It would be incredibly helpful for people to mention their gear and configuration in these posts. If you're using the SRV configuration (or not) please say so, so that perhaps a pattern will evolve. |
|
| |
said by royrogers:It would be incredibly helpful for people to mention their gear and configuration in these posts. If you're using the SRV configuration (or not) please say so, so that perhaps a pattern will evolve.
The two ATA's that failed were using DNS SRV (HT-286). The one that continued to work was not (Snom M3). |
|
| |
to krbvroc1
These are not new issues, but rather indicate new efforts on the part of the attackers to overcome CC's new mitigation efforts, AND the ancillary effects of the defense measures. The attackers may also have felt emboldened in the aftermath of the Sandy situation. As was posted in another thread: said by 29393955:I finally received a reply to the ticket I filed yesterday - here is the applicable info:
Recent issues with registration were due to extra security mechanisms on our network; initiated by further abnormal traffic. We have made some adjustments to our code which we believe should alleviate some registration problems.
My 3CX system is showing registered, at least the 2 test calls I just placed from my cell phone to my home and office numbers (CC DID's) did go through - I tried 1 outgoing and it too was successful, though audio quality on all was pretty rough.
|
|
 VexorgTR
join:2012-08-27
Sheffield Lake, OH |
to krbvroc1
I am seeing performance and behavior similar to what we saw during the DDoS attacks.
It makes me sad. |
|
| |
The attacks make me sad, but the defense makes me glad.
Things are not nearly so bad as at the beginning, even though the attack intensity could be worse. Defense is working but needs to be fine-tuned, I would imagine.
----------------------------------
Wolf 359 was a setback, but the Borg were eventually defeated. |
|
VexorgTR
join:2012-08-27
Sheffield Lake, OH |
It's a stink bomb, since I had new clients lined up to sign up.. and I asked them to wait a few days. |
|
| |
to PX Eliezer704
said by PX Eliezer704:These are not new issues, but rather indicate new efforts on the part of the attackers to overcome CC's new mitigation efforts, AND the ancillary effects of the defense measures.
I would have no way to know this. After spending a bunch of time rebooting routers and ATAs, checking traceroutes, and such yesterday, I logged into Callcentric and there was no notice of any new issues. I posted a trouble ticket yesterday and did not get a response yet. I even went so far as to check their twitter page (mind you, I do not use twitter), and there was nothing there. Your reference to another user in the 100page thread (which I am not following - I actually thought it got locked at some point) is the first I've heard that this is a continuation of the previous DDOS issues. |
|
VexorgTR
join:2012-08-27
Sheffield Lake, OH |
to krbvroc1
Forwarding out to my other DID is working just fine... I wonder if it IS the return of the DDoS monster or what. |
|
 ·Fido
MikroTik RB750Gr3
MikroTik wAP AC
Panasonic KX-TGP500
|
said by VexorgTR:Forwarding out to my other DID is working just fine... I wonder if it IS the return of the DDoS monster or what.
It is. Take a look at a recent hour from my Syslog
Nov 7 22:02:10 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:02:21 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:05:53 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:06:34 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:11:51 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:12:32 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:16:03 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:16:45 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:18:31 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:18:51 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:20:37 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:20:47 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:23:25 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:23:56 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:27:28 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:27:38 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:28:31 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:29:01 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:29:54 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:30:25 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:31:18 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:31:38 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:32:31 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:32:41 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:33:34 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:33:44 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:34:37 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:34:47 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:35:40 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:36:41 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:37:34 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:37:44 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:38:37 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:39:28 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:40:20 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:40:31 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:44:55 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:45:06 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:47:44 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:48:04 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:48:57 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:49:07 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:50:00 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:50:10 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:51:03 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:51:23 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:52:16 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:53:27 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:55:12 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:55:23 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:56:15 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:56:36 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Nov 7 22:59:14 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration failure by (480)
Nov 7 22:59:45 MAC ADDRESS. [SIP][Line-3: 17771234567]Registration Success
Not only that, call quality is terrible. |
|
VexorgTR
join:2012-08-27
Sheffield Lake, OH |
to krbvroc1
Since late last night, things are working properly. It makes me happy. |
|
 XCOMdigitalnUll
Premium Member
join:2002-06-10
Spring, TX
MikroTik CRS125-24G-1S-RM
|
to krbvroc1
CC just add it more servers.
I had to add alpha13 to 20 to my allowed list.
That's why things improved.
I started my porting to voip.ms yesterday. I gave them a chance and things are back like they where with the DDoS.... I hope CC can get out of this one. Good luck CC! |
|
Iscream
Premium Member
join:2009-02-17
New York, NY |
Iscream
Premium Member
2012-Nov-8 1:30 pm
The information above is not correct. The things are back to what they were prior to October 4th when attack started.
By saying "back" - I mean it. Voice quality, reliability of connection, sustainability of calls, etc.
On top of that - Free NY DIDs are also already operational. NYC recovers after the hurricane and snow/ice storm which passed here yesterday.
Good luck with your new provider. And welcome back shall you decide so at any time. |
|
XCOMdigitalnUll
Premium Member
join:2002-06-10
Spring, TX (Software) pfSense
MikroTik CRS125-24G-1S-RM
|
XCOM
Premium Member
2012-Nov-8 1:32 pm
said by Iscream:The information above is not correct. The things are back to what they were prior to October 4th when attack started.
By saying "back" - I mean it. Voice quality, reliability of connection, sustainability of calls, etc.
On top of that - Free NY DIDs are also already operational. NYC recovers after the hurricane and snow/ice storm which passed here yesterday.
Good luck with your new provider. And welcome back shall you decide so at any time.
Iscream, Sorry I should of specify today things are ok. Yesterday afternoon I had nothing but issues. Thanks. |
|
| |
to XCOM
People need to be aware that they increased the number of servers about three weeks ago. I also had to add them to my router to get it to work but I fortunately spotted this on the day they added them. They can add at any time. It is best if you permit the entire range of ip address 0-255. Unfortunately my router won't let me specify a range and I have to add them individually. |
|
XCOMdigitalnUll
Premium Member
join:2002-06-10
Spring, TX (Software) pfSense
MikroTik CRS125-24G-1S-RM
|
XCOM
Premium Member
2012-Nov-8 1:49 pm
said by DBOD:People need to be aware that they increased the number of servers about three weeks ago. I also had to add them to my router to get it to work but I fortunately spotted this on the day they added them. They can add at any time. It is best if you permit the entire range of ip address 0-255. Unfortunately my router won't let me specify a range and I have to add them individually.
Thanks for the tip. My router has CC CIDR block to be allowed so that was not the problem. I have specific rules within asterisk to allow hosts that I tell it to allow as an incoming carrier. Before it was alpha1 to 9. I am now up to 20. |
|
Technicolor CGA4131
Ubiquiti EdgeRouter ERPro8
Ubiquiti UniFi UAP-AC-PRO
|
to Iscream
I see all of the servers are on port 5080 now:
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha13.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha14.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha15.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha16.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha17.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha18.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha19.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha20.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha10.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha11.callcentric.com.
_sip._udp.callcentric.com. 1 IN SRV 20 0 5080 alpha12.callcentric.com.
Previously port 10123 was also used. Is this permanent or are you planning to also use 10123 in the future? I'm asking because I have to add the ports to the SIP signaling list for my firewall. |
|
XCOMdigitalnUll
Premium Member
join:2002-06-10
Spring, TX |
XCOM
Premium Member
2012-Nov-8 2:33 pm
Yes they are coming in on port 5080. |
|
| |
to Iscream
said by Iscream:The information above is not correct. The things are back to what they were prior to October 4th when attack started.
By saying "back" - I mean it. Voice quality, reliability of connection, sustainability of calls, etc.
Since when specifically? On Nov 6 my registrations were failing for around a 4 hour period. On Nov 7 call quality was horrible for most of the day. It has been fine so far today. There has not been a single notification from CC on their website of any current issues, yet other people here seemed to have them. CC took two days to respond to my trouble ticket, only to say 'your stuff looks registered right now'. |
|
·