I have setup freeswitch by using git and followed the instructions on the wiki page. How can I retrieve the exact git version?
There is no override of the hangup cause in our code. The algorithm is very simple; we call the originate function with the playback action and use a wav file as argument. Hangup is done automatically by FreeSWITCH, after eof of the wav file is reached. Or the other part hangs up before the file ends.
We dont traced the communication but in other hand, the sip codes are traced out into the log file (183-->180-->200=call established). This show to me, that there is no problem with the SIP transactions. Please assume, that SIP messages are OK.
What else could be happen?
2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable string 0 = [sip_from_uri=sip:xxxx@xxxxx]
2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable string 1 = [ignore_early_media=true]
2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable string 2 = [sip_cid_type=none]
2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable string 3 = [originate_timeout=40]
2010-08-17 22:41:09.904378 [NOTICE] switch_channel.c:779 New Channel sofia/internal/9055599XXXXX [9e4b396e-3d99-445f-a2e8-
---------- Weitergeleitete Nachricht ----------
From: Brian West <brian@freeswitch.org>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Date: Mon, 23 Aug 2010 09:29:32 -0500
Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while answered session
Without that we can't help. You also need to make sure you're on the very latest code. The one thing I'm sure we get right are the hangup causes unless you're doing something to override them.
/b
On Aug 23, 2010, at 9:24 AM, Durmuş Ali Öztürk wrote:
> I'm afraid, sip trace wasnt active.
---------- Weitergeleitete Nachricht ----------
From: Steven Ayre <steveayre@gmail.com>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Date: Mon, 23 Aug 2010 11:53:33 +0100
Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while answered session
Do you have a sip trace for those calls?
On 23 August 2010 11:36, Durmuş Ali Öztürk <ali.stgt@gmail.com> wrote:
Hello,
we had some trouble while executing a bulk call process with originating a parallel call of 200. Because in many cases, FreeSWITCH has notified hangups (SWITCH_EVENT_CHANNEL_HANGUP_COMPLETE) with the wrong hangup-cause. Instead of notifying the successful state, we got the NO_ANSWER hangup cause. BUSY and NO_ANSWER states are candidates for retries, therefor many numbers are called/payed twice. See log below.
Some other questions:
B) Is the originate_timeout value an overall timer or a timer for the ringing (starts if SIP code 180 incomes?) stage.
C) We are originating each number in a separate thread and listen to the channel events for updating the call result. Should we change this implementation or is this a good scenario/standard way. Related to the call result, if it is busy or not answered, the call is retried after 30 min. What are the recommends on this side to be ensured, the correct hangup case be got and the number is not called twice..
D) What do I have to bear in mind for bulk calls with parallel calls over 200.
Thanks for your answer in advance.
Ali