[asterisk-bugs] [JIRA] (ASTERISK-24596) Park application always fails when using dynamic parking lots

[Philip Correia (JIRA)]

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

Philip Correia commented on ASTERISK-24596:
-------------------------------------------

Thanks Matt,

I was naively hoping to help by indicating whereabouts the problem could be. I think calling it a patch was a gross overstatement. Apologies for that, in future I'll stick to just reporting my experience until my Asterisk hacking skills get better :)

After further investigation I don't think this is necessarily a bug, maybe a requirement in clarifying the feature usage in the documentation, or logging the error better in order to indicate that further configuration is required.

The following is what I am experiencing:

[Scenario 1]
When parkeddynamic = yes and parkext is defined in [default] in res_parking.conf and Park(VBX48) is called in the dial plan, the park fails with the error
'res_parking.c:1008 create_dynamic_lot_full: Extensions for dynamic parking lot 'VBX48' could not be registered. Dynamic lot creation failed.'

[Scenario 2]
When parkeddynamic = yes and parkext is NOT defined in [default] in res_parking.conf and Park(VBX48) is called in the dial plan, the park succeeds creating the VBX48 parkinglot but using the default 'parkedcalls' context

[Scenario 3]
When parkeddynamic = yes and parkext is defined in [default] in res_parking.conf and the variable PARKINGDYNCONTEXT=VBX48PARKED is set and Park(VBX48) is called in the dial plan, the park succeeds creating the VBX48 parkinglot but using the VBX48PARKED context.

Please see the attached files for each of the scenarios and the debug for the failure.

None of the dynamic park features are documented in the Asterisk 13 as far as I can see, neither on the website nor in the code (as per 'core show  application Park')

The website has the dynamic park features documented for Asterisk 11 and the bit I think is relevant to this issue is alluded to in the following note:

"Parking lots automatically create and manage dialplan extensions in the parking lot context. You do not need to explicitly use this application in your dialplan. Instead, all you should do is include the parking lot context in your dialplan."

I don't think this adequately indicates what needs to be done in order to get it working as per scenario 3. It  is also not clear that if parkext is not defined in the default template, that PARKINGDYNEXTEN must be set for the extensions to be created in the context defined in PARKINGDYNCONTEXT (I'm assuming here that this is the intended outcome)



> Park application always fails when using dynamic parking lots
> -------------------------------------------------------------
>
>                 Key: ASTERISK-24596
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24596
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_parking
>    Affects Versions: 13.0.0, 13.0.1
>         Environment: GNU/Linux 2.6.18  SMP x86_64 
> Centos 5
>            Reporter: Philip Correia
>            Assignee: Philip Correia
>         Attachments: 0001-Fixing-incorrect-condition-check.patch, debug.txt, scenario1-debug.txt, scenario1.txt, scenario2.txt, scenario3.txt
>
>
> When enabling the dynamic parking lot features in res_parking.conf and using the Park application, the application always fails with an error stating the extensions cannot be registered.
> # in default res_parking.conf
> [general]
> parkeddynamic = yes
> # in extensions.conf
> exten => _X.,1,Park(VBX48)
> When placing a call the error appears in the CLI as per the debug.txt attached.
> The attached patch seems to fix the problem.



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