[Freeswitch-users] FreeSWITCH-users Digest, Vol 64, Issue 174
Dip Mehta
dipkumar.mehta at gmail.com
Fri Oct 28 22:51:54 MSD 2011
Thanks MC. You got it right.
Appreciate your reply.
Cheers !
Dip Mehta
On Sat, Oct 29, 2011 at 12:07 AM, <
freeswitch-users-request at lists.freeswitch.org> wrote:
> Send FreeSWITCH-users mailing list submissions to
> freeswitch-users at lists.freeswitch.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> or, via email, send a message with subject or body 'help' to
> freeswitch-users-request at lists.freeswitch.org
>
> You can reach the person managing the list at
> freeswitch-users-owner at lists.freeswitch.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of FreeSWITCH-users digest..."
>
> Today's Topics:
>
> 1. Re: Hangup Causes (Michael Collins)
> 2. Re: Dialing issues (Michael Collins)
> 3. Re: High load on database server (john at mobex.biz)
>
>
> ---------- Forwarded message ----------
> From: Michael Collins <msc at freeswitch.org>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Date: Fri, 28 Oct 2011 11:10:21 -0700
> 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
>>
>>
>
>
> ---------- Forwarded message ----------
> From: Michael Collins <msc at freeswitch.org>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Date: Fri, 28 Oct 2011 11:15:13 -0700
> Subject: Re: [Freeswitch-users] Dialing issues
> This is a newfies configuration issue. I've only looked briefly at the
> newfies dialer (I don't want to get anywhere near it because it's AGPL -
> yuck) and I do know that it requires you to specify your gateway in some
> manner. It does not look like you have done that. I'd review this
> information from the newfies-dialer.org documentation site:
>
> Newfies-Dialer’s Gateway
>
> Log into the Newfies-Dialer interface using your root username and password
> previously created in these instructions.
>
> Click Admin, and locate and enter the “Dialer Gateways” panel on the
> dashboard, then add a dialer gateway. Only the fields in bold need to be
> filled in. That is to say, the name of gateway, for identification, and the
> Gateway’s field, e.g.
>
> sofia/gateway/myprovider/
>
> “myprovider” is the name of the gateway which you can take from the gateway
> name when you typed “sofia status” when configuring the Freeswitch Gateway.
> Finally, check the status is active, and save. The trunk should now appear
> in the gateway list.
> -MC
>
> On Fri, Oct 28, 2011 at 1:28 AM, Dip Mehta <dipkumar.mehta at gmail.com>wrote:
>
>> Hi,
>>
>> I am trying to integrate Newfies Dialer with Freeswitch.
>>
>> This is my sofia status
>>
>> freeswitch at 127.0.0.1@internal> sofia status
>> Name Type
>> Data State
>>
>> =================================================================================================
>> *:XX.XX.XX.XX* alias
>> internal ALIASED
>> external profile sip:mod_sofia@*
>> :XX.XX.XX.XX*:5080 RUNNING (0)
>> external::example.com gateway
>> sip:joeuser at example.com NOREG
>> * external::XX.XX.XX.XX gateway sip:password at XX.XX.XX.XX
>> REGED*
>> internal profile
>> sip:mod_sofia at 199.167.145.102:5060 RUNNING (0)
>> internal-ipv6 profile sip:mod_sofia@[::1]:5060
>> RUNNING (0)
>>
>> =================================================================================================
>> 3 profiles 1 alias
>>
>>
>> Looks like the Service provider is now registered with the Freeswitch. I
>> am asuming as it says REGED in the status.
>>
>> However, when i start my campaign through the dialer, I am unable to make
>> the outgoing calls which results in these errors.
>>
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_ivr_originate.c:1884 Parsing
>> global variables
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_request_uuid]=[48df3dbe-013e-11e1-8b92-bc305bec2901]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_answer_url]=[http://*XX.XX.XX.XX*:9080/api/dialer_cdr/answercall/]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_hangup_url]=[http://*XX.XX.XX.XX*:9080/api/dialer_cdr/hangupcall/]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [origination_caller_id_number]=[8888888888]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [bridge_early_media]=[true]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [hangup_after_bridge]=[true]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_app]=[true]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [absolute_codec_string]=[PCMA]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [originate_timeout]=[1800]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_event.c:1521 Parsing variable
>> [ignore_early_media]=[true]
>> 2011-10-28 04:24:41.992674 [ERR] switch_core_session.c:426 *Could not
>> locate channel type* *XX.XX.XX.XX Customers contact number*
>> 2011-10-28 04:24:41.992674 [NOTICE] switch_ivr_originate.c:2459 Cannot
>> create outgoing channel of type [*XX.XX.XX.XX Customers contact number*]
>> cause: [CHAN_NOT_IMPLEMENTED]
>> 2011-10-28 04:24:41.992674 [DEBUG] switch_ivr_originate.c:3348 Originate
>> Resulted in Error Cause: 66 [CHAN_NOT_IMPLEMENTED]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_ivr_originate.c:1884 Parsing
>> global variables
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_request_uuid]=[53a1c460-013e-11e1-8b92-bc305bec2901]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_answer_url]=[http://*XX.XX.XX.XX*:9080/api/dialer_cdr/answercall/]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_hangup_url]=[http://*XX.XX.XX.XX*
>> 2:9080/api/dialer_cdr/hangupcall/]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [origination_caller_id_number]=[8888888888]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [bridge_early_media]=[true]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [hangup_after_bridge]=[true]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [plivo_app]=[true]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [absolute_codec_string]=[PCMA]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [originate_timeout]=[1800]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_event.c:1521 Parsing variable
>> [ignore_early_media]=[true]
>> 2011-10-28 04:25:00.052673 [ERR] switch_core_session.c:426 Could not
>> locate channel type *XX.XX.XX.XX Customers contact number*
>> 2011-10-28 04:25:00.052673 [NOTICE] switch_ivr_originate.c:2459 Cannot
>> create outgoing channel of type [*XX.XX.XX.XX Customers contact number*]
>> cause: [CHAN_NOT_IMPLEMENTED]
>> 2011-10-28 04:25:00.052673 [DEBUG] switch_ivr_originate.c:3348 Originate
>> Resulted in Error Cause: 66 [CHAN_NOT_IMPLEMENTED]
>>
>>
>> Please advice.
>>
>>
>>
>>
>> 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
>>
>>
>
>
> ---------- Forwarded message ----------
> From: <john at mobex.biz>
> To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
> Date: Fri, 28 Oct 2011 11:36:45 -0700
> Subject: Re: [Freeswitch-users] High load on database server
> I'm probably in over my head, but i could use help.
>
> it appears my Freeswitch went down and came back up (possible from volume)
> when it did a large volume accoutn is getting bolcked 407 messages:
>
> Im getting the following message log:
>
> 2011-10-28 14:24:54.778973 [DEBUG] sofia.c:7099 IP 66.42.61.24 Rejected by
> acl "domains". Falling back to Digest auth.
> 2011-10-28 14:24:54.778973 [WARNING] sofia_reg.c:1400 SIP auth challenge
> (INVITE) on sofia profile 'internal' for [18125362643 at 216.134.222.93] from
> ip 66.42.61.24
>
> That IP address is set up as 66.42.61.24/32 in the cidr.
>
> What do i do to get them back up?
>
> Thanks
>
>
>
>
>
> _______________________________________________
> 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/20111029/dd3ab619/attachment-0001.html
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users
mailing list