Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 06-14-2022, 03:51 AM
azapateroalo azapateroalo is offline
Aspiring Member
 
Join Date: Oct 2021
Posts: 1
azapateroalo has 10 reputation points
Default SIP Reason: avaya-action

Hello,
I've been chasing a reported issue from a customer, that happens from ti, me to time: whenever a calls is put "on hold", a header reading


Reason: avaya-action;cause=1;text="Hold"


is sent on the SIP Invite request (reinvite).


The calls is hang up on the SP side, as far as that header is not RFC-compliant.


Does anybody knows where this header is being inserted? SM is discarded, also the ASBCE, and I'm pretty sure that this message is a default one from Avaya (not customized).


Regards.
Reply With Quote
  #2  
Old 10-13-2022, 01:48 PM
jwaber jwaber is offline
Member
 
Join Date: Jun 2014
Posts: 6
jwaber has 11 reputation points
Default Re-INVITE rejected due to Reason header

The use of the "REASON" header is not defined in the foundational SIP standard RFC3261. Instead, it is defined in RFC 3326, and is therefore a standard that a carrier can choose not to support. Ideally, the carrier would ignore a header it does not support, but it appears this one has decided to reject the entire request.

The REASON header can indicate that a call is being put on HOLD because the call is about to be conferenced, transferred, or simply put on hold.

Avaya chooses to use a re-INVITE to change something about an existing call because that conforms to the foundational RFC3261, and therefore is nearly guaranteed to work. Other vendors use an UPDATE for the same purpose, but that request method is not defined in RFC 3261 (it is defined in RFC 3311) and so might not be supported universally.

I believe the REASON header is injected by Communication Manager. I am not aware of any way to disable its inclusion from within CM.

The header can be removed in Session Manager, and in a Session Border Controller. Between the two, I suggest removing it in the SBC just before sending the request to the carrier.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:23 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.