Thank you Jean From: asterisk-dev <asterisk-dev-boun...@lists.digium.com> On Behalf Of Jean Aunis Sent: Friday, January 8, 2021 8:47 AM To: asterisk-dev@lists.digium.com Subject: Re: [asterisk-dev] Looking to input on a feature I would like to write...in depth Transfer (REFER) failure reasons
Le 08/01/2021 à 15:40, Dan Cropp a écrit : Before I submit a feature request and take ownership of it, trying to gather some feedback. I'm looking to write code for an additional feature in asterisk. Currently, when performing a Transfer (REFER), the channel variable TRANSFERSTATUS only reports 3 values: SUCCESS, FAILURE, UNSUPPORTED. We have some customers asking for a few additional results: 404 Not Found, 408 Request Timeout, and 486 Busy Here. >From past experience, these same customers will likely come up with some >additional results they think should be returned. Would it be better to add support where the TRANSFERSTATUS had new values for each of the additional result codes I make asterisk look for? Or would it be better to add a new variable, example TRANSFERSTATUSCODE and have it return the SIP error code for the failure notification? Personally, I like this approach because it means not having to add values for each possible sip error code that anyone would ever look for. Dan Hello Dan, I would prefer the second approach of using a new variable, otherwise it may break existing dialplan. Regards Jean
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
