[Freeswitch-users] Hangup Causes

[Jason Moran]

Are there any linux packages that will look within subdirectories and
automatically delete files/directories either after age or file size
thresholds are met?  (I installed pcapsipdump, but of course I worry
about how much hard drive space will be used).

 

-Jason

 

From: Michael Collins [mailto:msc at freeswitch.org] 
Sent: Friday, October 28, 2011 2:10 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] Hangup Causes

 

Although not easy on a production system, your best bet is to catch the
behavior in the act. Usually this means that you have to rely upon
humans to report the symptoms to you in a timely and accurate manner. 

 

One way you can help track these down is to use something like
pcapsipdump and do a ring buffer that covers at least several days.
Then, when you hear about a symptom you can go back and look at the
corresponding pcap file which will have both signaling and audio. From
there you can hopefully trace the root of the problem.

 

-MC

 

http://wiki.freeswitch.org/wiki/Packet_Capture#pcapsipdump

 

On Fri, Oct 28, 2011 at 9:19 AM, Jason Moran
<jmoran at secureachsystems.com> wrote:

I have some questions about the types of statuses we are getting (Yes,
I'm already familiar with http://wiki.freeswitch.org/wiki/Hangup_causes
)

 

We just deployed FS to production a couple of days ago and here is a
sample of our Hangup Causes:

CALL_REJECTED                1

NO_ANSWER     738

NO_USER_RESPONSE    175

NORMAL_CLEARING      1667 (Expected that this is only Early Hangups)

NORMAL_TEMPORARY_FAILURE             4

NORMAL_TEMPORARY_FAILURE (Rang)               37 (Rang means this status
happened more than 5 seconds after the session was started)

Complete            224  (Complete is our own status instead of
NORMAL_CLEARING, meaning WE hung up because we finished the entire
message).

ORIGINATOR_CANCEL (Rang)    3

RECOVERY_ON_TIMER_EXPIRE (Rang)   9 

UNALLOCATED_NUMBER            2

USER_BUSY        35

 

My questions:

1.       NORMAL_TEMPORARY_FAILURE happens a lot, and often returns 30 or
more seconds after starting. Could this be a "silent call" (etc)? We
have gotten 3-4 complaints of silent calls and I'm hoping to find the
cause.

2.       Is there anything here (or ideas elsewhere?) to explain why a
call will be silent once in a while?

3.       Is this spread of causes normal or does it seem strange

4.       We've had a few people note that the message on their voicemail
is over before they can hear it - even though we play the message twice
(to make short messages longer). Does anybody know of a solution for
this?

 

Thanks! -Jason

 



FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20111108/94d89936/attachment-0001.html