[asterisk-bugs] [JIRA] (PRI-160) Implement Party Category Support

[Timo Teräs (JIRA)]

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

Timo Teräs commented on PRI-160:
--------------------------------

Ping. Any feedback?

As addditional comment - the stuffing Party Category to .plan field makes sense on multiple levels:
 - it is technically indicating additional information about the numbering dialplan
 - it needs to be forwarded as part of connected line information when using Dial app

                
> Implement Party Category Support
> --------------------------------
>
>                 Key: PRI-160
>                 URL: https://issues.asterisk.org/jira/browse/PRI-160
>             Project: LibPRI
>          Issue Type: New Feature
>      Security Level: None
>            Reporter: Timo Teräs
>            Assignee: Richard Mudgett
>            Severity: Minor
>         Attachments: libpri-partycategory.patch
>
>
> This implements properly Party Category on Q.SIG links. Also requested earlier in ASTERISK-16381 .
> The field dumping is fixed to Q.SIG according to EN 300 172 (the previous enum is wrong, Q.SIG is separate from SS7). The patch exposes the party category to asterisk via party_number.plan and *plan fields (bits 0-7 being plan, and bits 8-11 being the new party category field). I feel this was the simplest way to do it, but can implement alternative design if so wanted. This allows category ID to be received without any changes in Asterisk code - sending it out will require patching chan_dahdi a little bit, as it normally overrides the caller dialplan based on configuration.

--
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