[asterisk-bugs] [JIRA] (ASTERISK-24290) Endpoint identifier match value fails to parse when CIDR network format is specified

Rusty Newton (JIRA) noreply at issues.asterisk.org
Tue Sep 2 18:38:28 CDT 2014


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

Rusty Newton updated ASTERISK-24290:
------------------------------------

    Summary: Endpoint identifier match value fails to parse when CIDR network format is specified  (was: "match=" address fails to parse when cdr network format is specified)

> Endpoint identifier match value fails to parse when CIDR network format is specified
> ------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24290
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24290
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_endpoint_identifier_ip
>    Affects Versions: 12.4.0
>         Environment: Debian Wheezy 7.5 ARMHF Linux arm 3.8.13-bone56 #1 SMP Wed Jun 4 23:59:23 UTC 2014 armv7l GNU/Linux Running pjsip 2.1.1
>            Reporter: Ray Crumrine
>
> [Callcentric]
> type=identify
> match=204.11.192.0/24
> endpoint=Callcentric
> When match= is specified in cdr format, Asterisk fails to parse the network address and "pjsip show endpoint" returns no "Identity" matches and as a result inbound calls fail with "not authorized". Also, if multiple addresses are given on the same line, i.e. "match=64.23.45.101,67.45.34.23" the parse fails as well. The Wiki says both should be acceptable and in fact when "match=123.45.67.89" is used, the function converts it to cdr format and returns [correctly] "Identity=123.45.67.89/32"



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



More information about the asterisk-bugs mailing list