[Freeswitch-users] Hangup Cause using ignore_early_media=false w183/SDP

Gonzalo Gasca Meza gascagonzalo at gmail.com
Sun Aug 21 03:15:47 MSD 2016


Hi Forum,

I'm launching calls using ESL originate command. Example:

*originate
{ignore_early_media=false,bridge_early_media=false,originate_timeout=24,call_timeout=24,execute_on_answer_1='sched_hangup
18
ALLOTTED_TIMEOUT',origination_uuid=920a1b14-j02y-7bi9-kgq0-3c1u-920a291166,origination_caller_id_number=+55XXXXXXXXX,RECORD_STEREO=true,execute_on_answer_2='record_session
/var/www/html/recordings/Y90I68RLWX_+55XXXXXXXXX_920a1b14-j02y-7bi9-kgq0-3c1u-920a291166.wav'}sofia/gateway/twilio/+55XXXXXXXXX
handle_calls*

I disabled ignore_early_media from true to false.

What is happening is that when I receive a 183 w/SDP and call is NOT
ANSWERED I used to get NO_ANSWER as reason code, now I get NORMAL_CLEARING
even though call was never connected. My feeling is that after entering in
tone detection and bridge the call is just following rules and end up in
hangup rule which by default should send this reason. handle_calls


   - Dialplan: sofia/external/+XXXXXXXXXX Action answer()
   - Dialplan: sofia/external/+XXXXXXXXXX Action log(INFO handle_calls
   application match)
   - Dialplan: sofia/external/+XXXXXXXXXX Action set(fax_verbose=true)
   - Dialplan: sofia/external/+XXXXXXXXXX Action
   set(transfer_ringback=${us-ring})
   - Dialplan: sofia/external/+XXXXXXXXXX Action
   spandsp_start_fax_detect(transfer 'fax' 10 ced)
   - Dialplan: sofia/external/+XXXXXXXXXX Action
   spandsp_start_tone_detect(55)
   - Dialplan: sofia/external/+XXXXXXXXXX Action
   playback(silence_stream://20000)
   - Dialplan: sofia/external/+XXXXXXXXXX Action spandsp_stop_tone_detect()
   - Dialplan: sofia/external/+XXXXXXXXXX Action hangup()

I know that during 183 w/SDP many things could happen (BUSY, REORDER,
Announcement, RING BACK, etc). What is the recommended way to handle those
situations?

For now Im using the following conditions to rewrite the reason code in my
App:


   - call_progress_183sdp + ring_tone + no_200OK = NO_ANSWER
   - call_progress_183sdp + busy|reorder|sit tone + no_200OK =
   BUSY,INVALID_DESTINATION
   - call_progress_183sdp + no_tone + no_200OK = INVALID_NUMBER (Probably
   an announcement)

Any pointers in how to make Freeswitch handle the above conditions
internally?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160820/76725be4/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.freeswitch
Type: application/octet-stream
Size: 31926 bytes
Desc: not available
Url : http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160820/76725be4/attachment-0001.obj 


Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users mailing list