[Freeswitch-users] recv_refuse but normal_clearing / no failover?

Avi Marcus avi at avimarcus.net
Thu Jan 21 22:56:43 MSK 2016

This leg was marked normal_clearing so it didn't try failing over.
sip_hangup_disposition was recv_refuse but that didn't try the next carrier
in my bridge string.. since it was cause 16/normal, I presume.

Any suggestion on dealing with these kind of bugged calls?
I've told the carrier...

(running FreeSWITCH Version 1.6.5-11-d5520a6~64bit (-11-d5520a6 64bit))

*SIP/2.0 487 Request Terminated*
Via: SIP/2.0/UDP;received=;rport=5060;branch=z9hG4bK2jKN0erN6acjg
To: <sip:001110144208202xxxx at sbc.voxbeam.com>;tag=3662377546-339101
From: "972535927644" <sip:97253592xxxx at>;tag=6NBQDBN3Bg8HQ
Call-ID: 47aa3d9c-3af3-1234-64a8-aec02ee4871b
CSeq: 86358306 INVITE
Contact: <sip:callee at;did=19b.0a235804>
*Reason: Q.850;cause=16*
P-Charging-Vector: icid-value="
7fa379cc7fa379b-0004-00c3-0000-0000 at
Content-Length: 0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160121/cfee8c70/attachment.html 

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