On Fri, Jan 8, 2021 at 10:41 AM Dan Cropp <[email protected]> wrote: > 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. >
It would be best if it were a separate variable, and that it also stated it was protocol specific. TRANSFERSTATUSPROTOCOL for example. -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org
-- _____________________________________________________________________ -- 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
