[asterisk-bugs] [JIRA] (ASTERISK-23173) PJSip missing feature: SIPPEER

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214283#comment-214283 ] 

Matt Jordan commented on ASTERISK-23173:
----------------------------------------

No, you're right about useragent. PJSIP_ENDPOINT does get *most* of what is in SIPPEER, but there's a number of things that I wouldn't think are SIP endpoint related items in SIPPEER as well. Going down the list:

| ip - (default) The IP address. | Yes, through the CHANNEL function (pjsip,local_addr/remote_addr) |
| port - The port number. | Yes, through the CHANNEL function (same) |
| mailbox - The configured mailbox. | Yes, PJSIP_ENDPOINT function |
| context - The configured context. | Yes, PJSIP_ENDPOINT |
| expire - The epoch time of the next expire. | I'm not sure how this is useful, so no. |
| dynamic - Is it dynamic? (yes/no). | No, but again, I'm not sure how this is useful. |
| callerid_name - The configured Caller ID name. | No, but we shouldn't either. CALLERID function does this. |
| callerid_num - The configured Caller ID number. | No, but again, we shouldn't do this. |
| callgroup - The configured Callgroup. | Yes, PJSIP_ENDPOINT |
| pickupgroup - The configured Pickupgroup. | Yes, PJSIP_ENDPOINT |
| namedcallgroup - The configured Named Callgroup. | Yes, PJSIP_ENDPOINT |
| namedpickupgroup - The configured Named Pickupgroup. | Yes, PJSIP_ENDPOINT |
| codecs - The configured codecs. | Yes, PJSIP_ENDPOINT (allow) |
| status - Status (if qualify=yes). | No. This might be useful. |
| regexten - Extension activated at registration. | No. This may or may not be useful; I'm not sure how it would be used right now. |
| limit - Call limit (call-limit). | No, and call-limits have been obsoleted for some time.
| busylevel - Configured call level for signalling busy. | No, and PJSIP doesn't really work that way. |
| curcalls - Current amount of calls. Only available if call-limit is set. | No. It might be useful to have some way to determine how many channels are associated with that - but that would be drilled through the AOR |
| language - Default language for peer. | Yes, PJSIP_ENDPOINT |
| accountcode - Account code for this peer. | No, which means we probably need it as a feature on an endpoint (whoops). It would be accessible through PJSIP_ENDPOINT. Granted, you can set this using CHANNEL still, but having it as a convenience (all channels created through this endpoint get this accountcode) is nice and relatively common. |
| useragent - Current user agent header used by peer. | Nope. This feels like a CHANNEL thing (useragent of the active dialog). |
| maxforwards - The value used for SIP loop prevention in outbound requests | No, not sure this is needed. |
| chanvarname - A channel variable configured with setvar for this peer. | Kind of. You could drill through PJSIP_ENDPOINT to get this, but multiple values would be interesting to extract. Again, not sure how this is very useful - why not just get the channel variable? |
| codecx - Preferred codec index number x (beginning with zero). | No, but this might be useful. I'd prefer to do it through a different mechanism however. |

So it's a mixed bag. Looking at what we don't have, I'd group it into one of the following categories:
 * Information about the current registration. I'd rather have a function that provides that run-time information, rather than crowding the CHANNEL or PJSIP_ENDPOINT. PJSIP_REGISTRATION maybe?
 * Run-time PJSIP information about the channel. In general, these should probably be added to CHANNEL where appropriate. Media information is a bit tricky; it may end up running into/combined with PJSIP_MEDIA_OFFER.

                
> PJSip missing feature: SIPPEER
> ------------------------------
>
>                 Key: ASTERISK-23173
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23173
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 12.0.0
>            Reporter: xrobau
>            Severity: Minor
>
> There is no equivalent feature of 'SIPPEER' for PJSip endpoints.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira