| Summary: | ASTERISK-26600: SIP User to User (UUI) | ||
| Reporter: | Cyril CONSTANTIN (dose) | Labels: | |
| Date Opened: | 2016-11-15 07:58:45.000-0600 | Date Closed: | 2020-01-14 11:21:10.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 11.20.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Debian | Attachments: | |
| Description: | Hi Guys,
I'm trying to send through SIP a UUI (User to User) field from Asterisk to Avaya Session Manager, from last exchange I got with them it looks that I'm not sending UUI under expected format by Avaya using RFC standard https://tools.ietf.org/html/rfc7433. I tried to send it under different way in my dialplan by adding SIP Private header as per below, but no one is accepted by Avaya even if they can see it, Avaya can't decode it properly, here you have all different way I tried: same => n,SIPAddHeader(User-to-User: 123434) same => n,SIPAddHeader(X-User-to-User: 123434) same => n,SIPAddHeader(User-to-User: 123434\;encoding=hex\;purpose=foo\;content=bar) same => n,SIPAddHeader(X-User-to-User: 123434\;encoding=hex\;purpose=foo\;content=bar) same => n,SIPAddHeader(User-to-User: 123434\;encoding=hex) same => n,SIPAddHeader(X-User-to-User: 123434\;encoding=hex) Any help on it would be appreciated. Thanks for the usual support Best Regards | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-11-15 07:58:46.617-0600 The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process. By: Asterisk Team (asteriskteam) 2016-11-15 07:58:46.842-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Asterisk Team (asteriskteam) 2016-11-15 07:58:46.967-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||