[asterisk-bugs] [JIRA] (ASTERISK-22345) Realtime dialplan extension matching fails when extension includes "/" character

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-22345:
-----------------------------------

    Component/s: PBX/pbx_realtime
    
> Realtime dialplan extension matching fails when extension includes "/" character
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22345
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22345
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_realtime
>    Affects Versions: 11.3.0
>         Environment: Tested multiple versions of asterisk 10 thru 11 on ubuntu/centos linux and freebsd
>            Reporter: Philip Mullis
>
> Description : Asterisk not matching any extension logic with / present ie.. number/callerid.
> Versions tested : Asterisk Version 11.4.0 (tested from 10.3 and up issue prevalent in all version, most likely in trunk too)
> SQL DATA test realtime data
> Full Texts	id	context	exten	priority	app	appdata	comment
> from-test	1234	1	NoOp	Test ${CALLERID(num)}
> from-test	1234567890/1111	1	NoOp	Helloooooooooooooooooooooooo
> extensions.conf
> [from-test]
> switch => Realtime
> ;exten => 1234567890/1111,1,NoOp("GOT HERE") ; manual test passes
> ;confirmed ext 1234 works from realtime
> error : 
> [2013-08-20 00:15:51] NOTICE[3550508]: chan_sip.c:23316 handle_request_invite: Call from 'philtest' (10.0.0.2:5060) to extension '1234567890' rejected because extension not found in context 'from-test'.
> *note the callerid of my test sip client is 1111, tested working with static entry for sanity.
> Conclusion: flat file logic working (commented manual test abovc), realtime version failing, although we can see exten 1234 has no issue, only seems to be when / is in there.. could this be some missed escape matching in the c code somewhere? 

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