I am using the API to manage calls as they arrive at FS from a trunk
I have a very simple Dial plan rule that parks the incoming call.
<extension name="Trunk_02031701648">
<condition field="destination_number" expression="^02031701648$">
<action application="park" />
</condition>
</extension>
Once the call is parked via the API I first send a ringing (to keep the originator happy)
sendmsg <uuid>
call-command: execute
execute-app-name: respond
execute-app-arg: 180
Via the API I then redirect the call on to another PSTN number back through the same gateway
sendmsg <UUID>
call-command: execute
execute-app-name: redirect
execute-app-arg: sip:<destination>@194.0.147.16
The redirection works well and the originator and destination are connected correctly.
But after the call has left FS I’m still left with some call debris which I cannot clear down using
sendmsg <UUID>
call-command: execute
execute-app-name: hangup
execute-app-arg: <cause code>
Using command “api show channels” I find the following held on FS The only way I’ve found to remove these calls is “api hupall”
-------------------------
uuid,created,created_epoch,name,state,cid_name,cid_num,ip_addr,dest,application,application_data,dialplan,context,read_codec,read_rate,write_codec,write_rate
4 total.
-------------------
The SIP signalling is correct with an outgoing “302 moved temporarily” [with the new destination in the contact] which is then Ack’ed by the switch. From a SIP point of view the call no longer on FS.
The only way I’ve found to remove these phantom calls is either “api hupall”, or restart the Sip profile.
Any suggestions on how I can remove these phantom calls without recourse to “api hupall”. “api hupall” kills any incoming calls as well as the stuck calls.
Regards
Richard Lamkin