[asterisk-bugs] [JIRA] (ASTERISK-18956) autocreatepeer enhancement (add prefix option for safer peers)

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell closed ASTERISK-18956.
------------------------------------

    Resolution: Suspended

Closing as we received no response to a patch review and the patch no longer applies to current versions of Asterisk.

> autocreatepeer enhancement (add prefix option for safer peers)
> --------------------------------------------------------------
>
>                 Key: ASTERISK-18956
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18956
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 1.8.7.1
>            Reporter: Andrew Kohlsmith
>            Severity: Minor
>         Attachments: 0000-add-inceptor-remove-double-manager-event.patch, 0001-implement-autocreatepeer-prefix-option.patch
>
>
> autocreatepeer uses the 'from' field from the device trying to register as the sip peer name. This can be problematic if you do not have control over the device trying to register.
> This patch adds an autocreatepeer=prefix option, and additionally an autocreateprefix string. The default prefix is "autopeer_". When an unknown device attempts to register with Aterisk and autocreatepeer=prefix is set, the peer name becomes the prefix + number. (e.g. "autopeer_0", "autopeer_1", etc.).
> Additonally, the AMI event for peer registration has an additional field "Inceptor: Automatic" if the registration is due to the autocreatepeer function.
> Finally, a double-register AMI event is removed. Current functionality emits two registration AMI events for every autocreated peer; the patch corrects that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)