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 80.85.85.46;received=80.85.85.46;rport=5060;branch=z9hG4bK2jKN0erN6acjg To: <sip:001110144208202xxxx@sbc.voxbeam.com>;tag=3662377546-339101 From: "972535927644" <sip:97253592xxxx@80.85.85.46>;tag=6NBQDBN3Bg8HQ Call-ID: 47aa3d9c-3af3-1234-64a8-aec02ee4871b CSeq: 86358306 INVITE Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL Contact: <sip:callee@108.59.2.133;did=19b.0a235804> *Reason: Q.850;cause=16* P-Charging-Vector: icid-value=" 7fa379cc7fa379b-0004-00c3-0000-0000@10.11.100.185 ";icid-generated-at=10.11.102.24;term-ioi=italtel.com Content-Length: 0