[Freeswitch-users] Terminating calls prior to answer using api
steveayre at gmail.com
Mon Feb 11 20:42:51 MSK 2013
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.
On 11 February 2013 17:40, Steven Ayre <steveayre at 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
> 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.
> On 11 February 2013 15:30, Gary Foreman <gaz.foreman at gmail.com> wrote:
>> I'm having an issue gracefully terminating calls prior to them being
>> 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.
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> Official FreeSWITCH Sites
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users