| Summary: | ASTERISK-26076: Show user agent in PJSIPShowEndpoint | ||
| Reporter: | Ludovic Gasc (Eyepea) (gmludo) | Labels: | |
| Date Opened: | 2016-05-31 10:41:56 | Date Closed: | 2017-11-06 14:11:46.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | 13.8.2 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Debian 8 64bits | Attachments: | |
| Description: | With SIPshowpeer AMI command, you have an header "SIP-Useragent" to know the current user agent.
With pjsip, to my knowledge, the almost equivalent is PJSIPShowEndpoint. PJSIPShowEndpoint emits several Events, especially ContactStatusDetail, where you can found the URI. But, I don't see an user-agent header. I've missed something ? Thanks for your answer. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-05-31 10:41:57.487-0500 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: Rusty Newton (rnewton) 2016-06-02 20:31:09.915-0500 Both {{ContactStatus}} and {{ContactStatusDetail}} should provider the User Agent. https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+ManagerEvent_ContactStatus https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+ManagerEvent_ContactStatusDetail Can you verify that on your system and provide debug showing the events you receive? By: Asterisk Team (asteriskteam) 2016-06-17 12:00:01.513-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||