Terminating calls prior to answer using api
Hi, I'm having an issue gracefully terminating calls prior to them being answered. When I issue the uuid_kill command prior to the call being answered my sip client gives an error "unable to connect" with an error tone. Is it possible to cancel the client dial without causing an error? Maybe using a sip notify message or something? I can't seem to find a list of valid sip notify messages anywhere. Thanks
probably need to use the cause parameter to uuid_kill This doesn't seem to be documented well, though. On 11 February 2013 15:30, Gary Foreman <gaz.foreman@gmail.com> wrote:
Hi,
I'm having an issue gracefully terminating calls prior to them being answered.
When I issue the uuid_kill command prior to the call being answered my sip client gives an error "unable to connect" with an error tone.
Is it possible to cancel the client dial without causing an error? Maybe using a sip notify message or something?
I can't seem to find a list of valid sip notify messages anywhere.
Thanks
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director *T <info@cassidywebservices.co.uk> *03300 100 960 *F<info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk
You either answer a call with 200, redirect with 3xx, or give an error 4xx 5xx or 6xx... basically without answering your only option is to return an error. The specific error code can show a varying number of levels of 'error' though. Some might be a perfectly valid result (eg 486 User Busy) while other's imply a more serious error (eg 500 Server Internal Error). But there's not really one for a successful unanswered call. How your phone behaves on the various errors is really up to the SIP client though. A generic unable to connect message doesn't sound very useful, I'd expect different error tones depending on the response code. -Steve On 11 February 2013 15:30, Gary Foreman <gaz.foreman@gmail.com> wrote:
Hi,
I'm having an issue gracefully terminating calls prior to them being answered.
When I issue the uuid_kill command prior to the call being answered my sip client gives an error "unable to connect" with an error tone.
Is it possible to cancel the client dial without causing an error? Maybe using a sip notify message or something?
I can't seem to find a list of valid sip notify messages anywhere.
Thanks
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
The NORMAL_CLEARING ISDN clearing cause (16) has no mapping to any SIP code for example, it's a code you normally would only see a) when the caller hangs up at any time (regardless of answered or not) or b) when call has been answered *then* callee hangs up. -Steve On 11 February 2013 17:40, Steven Ayre <steveayre@gmail.com> wrote:
You either answer a call with 200, redirect with 3xx, or give an error 4xx 5xx or 6xx... basically without answering your only option is to return an error.
The specific error code can show a varying number of levels of 'error' though. Some might be a perfectly valid result (eg 486 User Busy) while other's imply a more serious error (eg 500 Server Internal Error). But there's not really one for a successful unanswered call.
How your phone behaves on the various errors is really up to the SIP client though. A generic unable to connect message doesn't sound very useful, I'd expect different error tones depending on the response code.
-Steve
On 11 February 2013 15:30, Gary Foreman <gaz.foreman@gmail.com> wrote:
Hi,
I'm having an issue gracefully terminating calls prior to them being answered.
When I issue the uuid_kill command prior to the call being answered my sip client gives an error "unable to connect" with an error tone.
Is it possible to cancel the client dial without causing an error? Maybe using a sip notify message or something?
I can't seem to find a list of valid sip notify messages anywhere.
Thanks
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Andrew Cassidy
-
Gary Foreman
-
Steven Ayre