The network/CPU/memory utilization are next to nothing, I checked the sip 
traffic and I don't see anything that shouldn't be registering with the box. 

-----Original Message-----
From: Ivan Kovacevic [mailto:[email protected]] 
Sent: Tuesday, July 05, 2011 15:02
To: Andy Hallam
Subject: RE: [Bulk] [on-asterisk] Freeswitch Question/Problem

How is your Network/CPU/memory utilization?  Is it possible someone is trying 
to brute-force your FS box and is using up all your resources? Can you log SIP 
traffic on the server to check for unauthorized registration attempts? 


Best Regards,

Ivan Kovacevic

Star Telecom | www.startelecom.ca | [email protected]
T: + 18557827835 x205 | C: +16477714773 | F: +18557827835



-----Original Message-----
From: Andy Hallam [mailto:[email protected]]
Sent: July-05-11 2:55 PM
To: [email protected]
Subject: [Bulk] [on-asterisk] Freeswitch Question/Problem

Hey Everyone;

I know this group is geared to Asterisk, but I'm having a problem with a 
freeswitch box that I look after and I'm kind of stumped with a problem I'm 
having with it.

The box is unable to receive calls, when you dial a number on the box, it comes 
up with "the number is not available" message from the carrier (Execulink 
Telecom).  When looking in to the matter a bit deeper, sometimes the calls make 
it to the box and will ring a phone but there is dead are on the phone and the 
person calling will still get the carrier message saying that the number is not 
available.  There has also been a fair bit of a time delay in the fscli for 
calls coming in to when it shows up in the logs.

I have checked all the registrations with the carrier and they seem to be fine, 
and they have also confirmed that it is nothing on
their end.    This was working fine for a while until a few hours ago.   If 
anyone has any input on this matter, that would be
greatly appreciated.

-Andy


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to