Brian, we are not bridging calls. FreeSWITCH (Leg A) as the caller can not be in a 'not answered' state. Also if I see 200 then it must be come from Leg B (the callee) which means that other party has answered the call. Also, both legs was active but FS had reported us the opposite. And this happened more than 40.000 times between 8 hours. <br>
<br>I would like to know what you are expecting from the sip trace, because the log is detailed enough to be verified that FS has catched the 200 SIP - but it seems to be ignored (maybe hangup timer started or something else) therefor the session is closed with the wrong state. It is also clear for me, that FS is <b>over-challenged</b>
to set the correct hangup cause in bulk calls over 200 cps. <br><div class="gmail_quote"><div><br>@Milena<br>We must to re-call all numbers again to give you a SIP trace but this is to expensive for us :-)<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>---------- Weitergeleitete Nachricht ----------<br>From: Milena <<a href="mailto:testeador01@gmail.com">testeador01@gmail.com</a>><br>
To: FreeSWITCH Users Help <<a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>><br>Date: Mon, 23 Aug 2010 10:17:37 -0500<br>Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while answered session<br>
type "version" on the CLI<div><br></div><div>If the "<span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">sip trace wasnt active" then activate it and pastebin it, that's the only way you can get help with this, you know the developers are experts not <span style="border-collapse: separate; line-height: 19px; white-space: nowrap;">soothsayers :) </span><br>
</span><br></div><div><br></div><div>-Mile</div><div><br><div class="gmail_quote">2010/8/23 Durmuş Ali Öztürk <span dir="ltr"><<a href="mailto:ali.stgt@gmail.com" target="_blank">ali.stgt@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I have setup freeswitch by using git and followed the instructions on the wiki page. How can I retrieve the exact git version?<br></blockquote></div></div>
<br><br>---------- Weitergeleitete Nachricht ----------<br>From: Brian West <<a href="mailto:brian@freeswitch.org">brian@freeswitch.org</a>><br>To: FreeSWITCH Users Help <<a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>><br>
Date: Mon, 23 Aug 2010 10:18:30 -0500<br>Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while answered session<br>Again without a SIP trace I can't say... You have to remember that FreeSWITCH is a B2BUA and a call thru it results in TWO legs. If you were to ANSWER the first but then bridge to the second then it didn't answer you might still get a NO_ANSWER even thou you see the 200ok for the one leg of the call.<br>
<br>
/b<br>
<br>
On Aug 23, 2010, at 10:08 AM, Durmuş Ali Öztürk wrote:<br>
<br>
> I have setup freeswitch by using git and followed the instructions on the wiki page. How can I retrieve the exact git version?<br>
><br>
> 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.<br>
><br>
> 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.<br>
><br>
> What else could be happen?<br>
<br>
<br>
<br>
<br><br>---------- Weitergeleitete Nachricht ----------<br>From: Sergey Okhapkin <<a href="mailto:sos@sokhapkin.dyndns.org">sos@sokhapkin.dyndns.org</a>><br>To: FreeSWITCH Users Help <<a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>><br>
Date: Mon, 23 Aug 2010 11:22:37 -0400<br>Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while answered session<br>You're running concurrent calls, hangup cause NO_ANSWER and log line with 200<br>
OK belong to different calls.<br>
<br>
On Monday 23 August 2010, Durmuş Ali Öztürk wrote:<br>
> I have setup freeswitch by using git and followed the instructions on the<br>
> wiki page. How can I retrieve the exact git version?<br>
><br>
> There is no override of the hangup cause in our code. The algorithm is very<br>
> simple; we call the originate function with the playback action and use a<br>
> wav file as argument. Hangup is done automatically by FreeSWITCH, after eof<br>
> of the wav file is reached. Or the other part hangs up before the file<br>
> ends.<br>
><br>
> We dont traced the communication but in other hand, the sip codes are<br>
> traced out into the log file (183-->180-->200=call established). This show<br>
> to me, that there is no problem with the SIP transactions. Please assume,<br>
> that SIP messages are OK.<br>
><br>
> What else could be happen?<br>
><br>
> 2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable<br>
> string 0 = [sip_from_uri=sip:xxxx@xxxxx]<br>
> 2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable<br>
> string 1 = [ignore_early_media=true]<br>
> 2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable<br>
> string 2 = [sip_cid_type=none]<br>
> 2010-08-17 22:40:51.087402 [DEBUG] switch_ivr_originate.c:1979 variable<br>
> string 3 = [originate_timeout=40]<br>
> 2010-08-17 22:41:09.904378 [NOTICE] switch_channel.c:779 New Channel<br>
> sofia/internal/9055599XXXXX [9e4b396e-3d99-445f-a2e8-<br>
> 227e99f3f0ef]<br>
> 2010-08-17 22:41:12.641362 [DEBUG] mod_sofia.c:3892<br>
> (sofia/internal/9055599XXXXX) State Change CS_NEW -> CS_INIT<br>
> 2010-08-17 22:41:12.641362 [DEBUG] switch_core_session.c:1039 Send signal<br>
> sofia/internal/9055599XXXXX [BREAK]<br>
> 2010-08-17 22:41:12.641362 [DEBUG] switch_core_session.c:454<br>
> sofia/internal/9055599XXXXX set UUID=9dc8a739-f439-4815-981a-347b7a90a1a8<br>
> 2010-08-17 22:41:12.642441 [DEBUG] switch_core_state_machine.c:314<br>
> (sofia/internal/9055599XXXXX) Running State Change CS_INIT<br>
> 2010-08-17 22:41:12.642441 [DEBUG] switch_core_state_machine.c:338<br>
> (sofia/internal/9055599XXXXX) State INIT<br>
> 2010-08-17 22:41:12.642441 [DEBUG] mod_sofia.c:83<br>
> sofia/internal/9055599XXXXX SOFIA INIT<br>
> 2010-08-17 22:41:12.643399 [DEBUG] mod_sofia.c:119<br>
> (sofia/internal/9055599XXXXX) State Change CS_INIT -> CS_ROUTING<br>
> 2010-08-17 22:41:12.643399 [DEBUG] switch_core_session.c:1039 Send signal<br>
> sofia/internal/9055599XXXXX [BREAK]<br>
> 2010-08-17 22:41:12.643399 [DEBUG] switch_core_state_machine.c:338<br>
> (sofia/internal/9055599XXXXX) State INIT going to sleep<br>
> 2010-08-17 22:41:12.643399 [DEBUG] switch_core_state_machine.c:314<br>
> (sofia/internal/9055599XXXXX) Running State Change CS_ROUTING<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_channel.c:1512<br>
> (sofia/internal/9055599XXXXX) Callstate Change DOWN -> RINGING<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_core_state_machine.c:341<br>
> (sofia/internal/9055599XXXXX) State ROUTING<br>
> 2010-08-17 22:41:12.644456 [DEBUG] mod_sofia.c:142<br>
> sofia/internal/9055599XXXXX SOFIA ROUTING<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_ivr_originate.c:66<br>
> (sofia/internal/9055599XXXXX) State Change CS_ROUTING -> CS_CONSUME_MEDIA<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_core_session.c:1039 Send signal<br>
> sofia/internal/9055599XXXXX [BREAK]<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_core_state_machine.c:341<br>
> (sofia/internal/9055599XXXXX) State ROUTING going to sleep<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_core_state_machine.c:314<br>
> (sofia/internal/9055599XXXXX) Running State Change CS_CONSUME_MEDIA<br>
> 2010-08-17 22:41:12.644456 [DEBUG] switch_core_state_machine.c:360<br>
> (sofia/internal/9055599XXXXX) State CONSUME_MEDIA<br>
> 2010-08-17 22:41:12.645373 [DEBUG] switch_core_state_machine.c:360<br>
> (sofia/internal/9055599XXXXX) State CONSUME_MEDIA going to sleep<br>
> 2010-08-17 22:41:42.806367 [DEBUG] sofia.c:4318 Channel<br>
> sofia/internal/9055599XXXXX entering state [calling][0]<br>
> 2010-08-17 22:41:42.890442 [INFO] sofia.c:662 sofia/internal/9055599XXXXX<br>
> Update Callee ID to "9055599XXXXX" <9055599XXXXX><br>
> 2010-08-17 22:41:42.894355 [DEBUG] sofia.c:4318 Channel<br>
> sofia/internal/9055599XXXXX entering state [proceeding][183]<br>
> 2010-08-17 22:41:42.894355 [NOTICE] sofia.c:4390 Ring-Ready<br>
> sofia/internal/9055599XXXXX!<br>
> 2010-08-17 22:41:42.895440 [DEBUG] sofia.c:4318 Channel<br>
> sofia/internal/9055599XXXXX entering state [proceeding][183]<br>
> 2010-08-17 22:41:42.895440 [DEBUG] sofia.c:4329 Remote SDP:<br>
> 2010-08-17 22:41:42.895440 [DEBUG] sofia_glue.c:2444 Set Codec<br>
> sofia/internal/9055599XXXXX PCMA/8000 20 ms 160 samples<br>
> 2010-08-17 22:41:42.896357 [DEBUG] sofia_glue.c:3937 Set 2833 dtmf send<br>
> payload to 101<br>
> 2010-08-17 22:41:42.896357 [DEBUG] sofia_glue.c:2684 AUDIO RTP<br>
> [sofia/internal/9055599XXXXX] 10.100.224.10 port 31416 -> 10.100.199.19<br>
> port 18620 codec: 8 ms: 20<br>
> 2010-08-17 22:41:42.896357 [DEBUG] switch_rtp.c:1413 Starting timer [soft]<br>
> 160 bytes per 20ms<br>
> 2010-08-17 22:41:42.897431 [DEBUG] sofia_glue.c:2894 Set 2833 dtmf send<br>
> payload to 101<br>
> 2010-08-17 22:41:42.897431 [DEBUG] sofia_glue.c:2899 Set 2833 dtmf receive<br>
> payload to 101<br>
> 2010-08-17 22:41:42.897431 [NOTICE] sofia_glue.c:3292 Pre-Answer<br>
> sofia/internal/9055599XXXXX!<br>
> 2010-08-17 22:41:42.897431 [DEBUG] switch_channel.c:2397<br>
> (sofia/internal/9055599XXXXX) Callstate Change RINGING -> EARLY<br>
> 2010-08-17 22:41:42.916461 [DEBUG] sofia.c:4313 Channel<br>
> sofia/internal/9055599XXXXX skipping state [proceeding][180]<br>
> 2010-08-17 22:41:43.434412 [DEBUG] sofia.c:4318 Channel<br>
> sofia/internal/9055599XXXXX entering state [completing][200]<br>
> 2010-08-17 22:41:43.434412 [DEBUG] sofia.c:4326 Duplicate SDP<br>
> 2010-08-17 22:41:52.000488 [DEBUG] switch_channel.c:2309<br>
> (sofia/internal/9055599XXXXX) Callstate Change EARLY -> HANGUP<br>
> 2010-08-17 22:41:52.000488 [NOTICE] switch_ivr_originate.c:3282 Hangup<br>
> sofia/internal/9055599XXXXX [CS_CONSUME_MEDIA] [NO_ANSWER]<br>
> 2010-08-17 22:41:52.000488 [DEBUG] switch_channel.c:2325 Send signal<br>
> sofia/internal/9055599XXXXX [KILL]<br>
> 2010-08-17 22:41:52.000488 [DEBUG] switch_core_state_machine.c:314<br>
> (sofia/internal/9055599XXXXX) Running State Change CS_HANGUP<br>
> 2010-08-17 22:41:52.000488 [DEBUG] switch_core_state_machine.c:535<br>
> (sofia/internal/9055599XXXXX) State HANGUP<br>
> 2010-08-17 22:41:52.000488 [DEBUG] mod_sofia.c:453 Channel<br>
> sofia/internal/9055599XXXXX hanging up, cause: NO_ANSWER<br>
> 2010-08-17 22:41:52.000488 [DEBUG] switch_core_session.c:1039 Send signal<br>
> sofia/internal/9055599XXXXX [BREAK]<br>
> 2010-08-17 22:41:55.204396 [DEBUG] mod_sofia.c:506 Sending CANCEL to<br>
> sofia/internal/9055599XXXXX<br>
> 2010-08-17 22:41:55.204396 [DEBUG] switch_core_state_machine.c:46<br>
> sofia/internal/9055599XXXXX Standard HANGUP, cause: NO_ANSWER<br>
> 2010-08-17 22:41:55.204396 [DEBUG] switch_core_state_machine.c:535<br>
> (sofia/internal/9055599XXXXX) State HANGUP going to sleep<br>
> 2010-08-17 22:41:55.204396 [DEBUG] switch_core_state_machine.c:333<br>
> (sofia/internal/9055599XXXXX) State Change CS_HANGUP -> CS_REPORTING<br>
> 2010-08-17 22:41:55.204396 [DEBUG] switch_core_session.c:1039 Send signal<br>
> sofia/internal/9055599XXXXX [BREAK]<br>
> 2010-08-17 22:41:55.204396 [DEBUG] switch_core_state_machine.c:314<br>
> (sofia/internal/9055599XXXXX) Running State Change CS_REPORTING<br>
> 2010-08-17 22:41:55.205401 [DEBUG] switch_core_state_machine.c:595<br>
> (sofia/internal/9055599XXXXX) State REPORTING<br>
> 2010-08-17 22:41:55.205401 [DEBUG] switch_core_state_machine.c:53<br>
> sofia/internal/9055599XXXXX Standard REPORTING, cause: NO_ANSWER<br>
> 2010-08-17 22:41:55.205401 [DEBUG] switch_core_state_machine.c:595<br>
> (sofia/internal/9055599XXXXX) State REPORTING going to sleep<br>
> 2010-08-17 22:41:55.206428 [DEBUG] switch_core_state_machine.c:327<br>
> (sofia/internal/9055599XXXXX) State Change CS_REPORTING -> CS_DESTROY<br>
> 2010-08-17 22:41:55.206428 [DEBUG] switch_core_session.c:1039 Send signal<br>
> sofia/internal/9055599XXXXX [BREAK]<br>
> 2010-08-17 22:41:55.206428 [DEBUG] switch_core_session.c:1202 Session 18770<br>
> (sofia/internal/9055599XXXXX) Locked, Waiting on external entities<br>
> 2010-08-17 22:41:55.206428 [NOTICE] switch_core_session.c:1220 Session<br>
> 18770 (sofia/internal/9055599XXXXX) Ended<br>
> 2010-08-17 22:41:55.206428 [NOTICE] switch_core_session.c:1222 Close<br>
> Channel sofia/internal/9055599XXXXX [CS_DESTROY]<br>
> 2010-08-17 22:41:55.207463 [DEBUG] switch_core_state_machine.c:427<br>
> (sofia/internal/9055599XXXXX) Callstate Change HANGUP -> DOWN<br>
> 2010-08-17 22:41:55.207463 [DEBUG] switch_core_state_machine.c:430<br>
> (sofia/internal/9055599XXXXX) Running State Change CS_DESTROY<br>
> 2010-08-17 22:41:55.207463 [DEBUG] switch_core_state_machine.c:440<br>
> (sofia/internal/9055599XXXXX) State DESTROY<br>
> 2010-08-17 22:41:55.207463 [DEBUG] mod_sofia.c:358<br>
> sofia/internal/9055599XXXXX SOFIA DESTROY<br>
> 2010-08-17 22:41:55.207463 [DEBUG] switch_core_state_machine.c:60<br>
> sofia/internal/9055599XXXXX Standard DESTROY<br>
> 2010-08-17 22:41:55.207463 [DEBUG] switch_core_state_machine.c:440<br>
> (sofia/internal/9055599XXXXX) State DESTROY going to sleep<br>
><br>
><br>
><br>
><br>
> ---------- Weitergeleitete Nachricht ----------<br>
><br>
> > From: Brian West <<a href="mailto:brian@freeswitch.org">brian@freeswitch.org</a>><br>
> > To: FreeSWITCH Users Help <<a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>><br>
> > Date: Mon, 23 Aug 2010 09:29:32 -0500<br>
> > Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while<br>
> > answered session<br>
> > Without that we can't help. You also need to make sure you're on the<br>
> > very latest code. The one thing I'm sure we get right are the hangup<br>
> > causes unless you're doing something to override them.<br>
> ><br>
> > /b<br>
> ><br>
> > On Aug 23, 2010, at 9:24 AM, Durmuş Ali Öztürk wrote:<br>
> > > I'm afraid, sip trace wasnt active.<br>
> ><br>
> > ---------- Weitergeleitete Nachricht ----------<br>
> > From: Steven Ayre <<a href="mailto:steveayre@gmail.com">steveayre@gmail.com</a>><br>
> > To: FreeSWITCH Users Help <<a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>><br>
> > Date: Mon, 23 Aug 2010 11:53:33 +0100<br>
> > Subject: Re: [Freeswitch-users] Wrong hangup cause (NO_ANSWER) while<br>
> > answered session<br>
> > Do you have a sip trace for those calls?<br>
> ><br>
> ><br>
> > On 23 August 2010 11:36, Durmuş Ali Öztürk <<a href="mailto:ali.stgt@gmail.com">ali.stgt@gmail.com</a>> wrote:<br>
> > Hello,<br>
> ><br>
> > we had some trouble while executing a bulk call process with originating<br>
> > a parallel call of 200. Because in many cases, FreeSWITCH has notified<br>
> > hangups (SWITCH_EVENT_CHANNEL_HANGUP_COMPLETE) with the wrong<br>
> > hangup-cause. Instead of notifying the successful state, we got the<br>
> > NO_ANSWER hangup cause. BUSY and NO_ANSWER states are candidates for<br>
> > retries, therefor many numbers are called/payed twice. See log below.<br>
> ><br>
> > Some other questions:<br>
> ><br>
> > B) Is the originate_timeout value an overall timer or a timer for the<br>
> > ringing (starts if SIP code 180 incomes?) stage.<br>
> ><br>
> > C) We are originating each number in a separate thread and listen to the<br>
> > channel events for updating the call result. Should we change this<br>
> > implementation or is this a good scenario/standard way. Related to the<br>
> > call result, if it is busy or not answered, the call is retried after 30<br>
> > min. What are the recommends on this side to be ensured, the correct<br>
> > hangup case be got and the number is not called twice..<br>
> ><br>
> > D) What do I have to bear in mind for bulk calls with parallel calls over<br>
> > 200.<br>
> ><br>
> > Thanks for your answer in advance.<br>
> ><br>
> ><br>
> > Ali<br>
><br>
<br></blockquote></div><br>