[Freeswitch-users] Wrong hangup cause (NO_ANSWER) while answered session

[Brian West]

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.

/b

On Aug 23, 2010, at 10:08 AM, Durmuş Ali Öztürk wrote:

> 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?